openDox root: bump code to a99eba03 and spec to a8f5eb73 (§ 4.3 lazy proxy; BUILD slice 1b)

[brettheap]

Lane: openxfactory-4-opendox-extraction

Refs opensoft/openxFactory#656 — routine leg pin-sync at the openDox assembly
root, advancing both legs to their current main.

Sibling search: gh pr list --repo opensoft/openDox --state open = none before
this branch was pushed.

What moved, in the one commit

Both legs' three-fact invariant (README ## The lockstep invariant;
scripts/validate-pins.py):

fact	code leg	spec leg
gitlink	a99eba03e31a0aee1cc15a061fdf718cc88a2c44	a8f5eb73671c209871bc1598fe95ddf83b99ce24
contracts/<role>-pin.yaml commit:	same	same
digests.tree_sha256:	80913dc9392e79182a0b7c3b7684f6ad029ddb90b9a62c8e9328031a4e8d0c22	658c034d6eba529ff19c6d776ddcfb87ed36633ae413a5e3b776fdad4e455e16
was	da8aae969b4057bd46d2550c265e5bb363142458	1a216ea413cdcc14791aa3939712e2e459cfa6b6

• code — opensoft/openDox-code#11 (§ 4.3 lazy proxy: profile_openxfactory
  becomes a lazy proxy registered by the host at process start, read by both
  composition points), merged 2026-09-11T19:04Z.
• spec — opensoft/openDox-spec#7 (BUILD § 3.6, split-opendox slice 1b:
  the 10 stale citations corrected in place, inside the Q-L1 declared lines),
  merged 2026-09-11T17:44Z.

Both digests recomputed under sorted-ls-tree-r-v1 via this repository's own
scripts/repo_shape.py::tree_digest (not reimplemented) — cross-checked
against an independently hand-rolled git ls-tree -r -z reduction for each
leg separately; both agree exactly.

Files changed: code, spec (gitlinks), contracts/code-pin.yaml,
contracts/spec-pin.yaml — exactly the shape of the prior bump, PR #5.

What did NOT move (deliberately)

• contracts/manifest.yaml's carved_from: block — untouched (still
  b075fd91dc8fced8e1373825ba80220c33536bae / opendox-carve-0).
• No .github/workflows/*.yml carries an @<sha> reference to either leg
  repository, so the lockstep invariant's third fact has no member here.
• contracts/CHANGELOG.md — untouched, matching PR openDox root: bump code to da8aae96 and spec to 1a216ea4 (Q-L8 (a), BUILD slices 1+2) #5's precedent (no
  per-bump line kept there for a routine leg-only bump).

Verification

$ git -C code cat-file -t a99eba03e31a0aee1cc15a061fdf718cc88a2c44
commit
$ git -C spec cat-file -t a8f5eb73671c209871bc1598fe95ddf83b99ce24
commit

make validate (both submodules initialised at their new pins) — exit 0:

python3 scripts/validate-repository-naming.py --project project.yaml
  openDox                          neutral-product/assembly   also_matches project-leg/assembly
  openDox-spec                     project-leg/spec
  openDox-code                     project-leg/code
python3 scripts/validate-manifest.py
manifest ok: openDox (opendox), 3 legs
python3 scripts/validate-pins.py
  ok  spec: gitlink == contracts/spec-pin.yaml commit a8f5eb73671c
  ok  spec: tree digest recomputes (658c034d6eba…)
  ok  code: gitlink == contracts/code-pin.yaml commit a99eba03e31a
  ok  code: tree digest recomputes (80913dc9392e…)
  ok  contracts/shape-pin.yaml: 10 copied shape file(s) match their digests
pins ok

Not done here

• No merge — the lane lands this.

🤖 Generated with Claude Code

Summary by Sourcery

Enhancements:

• Synchronize the openDox code and spec legs with their latest commits and update the corresponding lockstep pin metadata and tree digests.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This routine lockstep bump advances the code leg to the lazy-proxy implementation and the spec leg to the BUILD slice 1b corrections, updating each gitlink plus its contract pin and tree digest while leaving manifest provenance, workflows, and changelog unchanged.

File-Level Changes

Change	Details	Files
Advanced the code and spec submodule pins and synchronized their recorded commit and tree-digest metadata.	Moved the code gitlink to a99eba03 and updated its lockfile commit and digest. Moved the spec gitlink to a8f5eb73 and updated its lockfile commit and digest. Preserved the repository’s lockstep invariant and validated both submodule commits and recomputed tree digests.	code spec contracts/code-pin.yaml contracts/spec-pin.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

🟢 Approval recommended

No unresolved review issues were reported.

Pull request overview

Synchronizes the openDox code and spec legs with updated commits and matching pin metadata.

Changes:

• Updates both gitlink references.
• Refreshes commit pins and tree digests.

File summaries

File	Description
contracts/spec-pin.yaml	Updates the spec commit and tree digest.
contracts/code-pin.yaml	Updates the code commit and tree digest.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[sourcery-ai]

Sorry @brettheap, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 2 days and 20 hours by commenting @sourcery-ai review. Upgrade to get a review now.