prefer-triad-project-shape 5.3: advance the openRepoShape pin to 1a9fc537, the commit that realizes 5.2

[brettheap]

Lane: codeXfactory-5

Governing change: openspec/changes/prefer-triad-project-shape (ratified, #1249), task 5.3, "openxFactory, the pin".

Held for Brett Heap's merge word; do not merge. It touches openspec/changes/, so it lands under a Rule 6 landing window.

Copilot review not requested (Brett Heap, 2026-10-06)

What and why

Task 5.3 advances contracts/openreposhape-pin.yaml onto the openRepoShape commit that realizes 5.2. That commit is 1a9fc537bcce37301c85fc108fabd8a599b02000: opensoft/openRepoShape#164, squash-merged 2026-10-06T22:52:05Z. It carries the Triad advisory, the optional single-repository.yaml and the posture text. The pin moves from e9c4827b (#700). It cannot skip a commit, so the advance also carries the 56 openRepoShape commits before #164. All 57 PR numbers are named in the pin's commit note, and that list was cross-checked against git log e9c4827b..1a9fc537.

The method follows #650 and #700. Every sha256 was recomputed from the real bytes, using the git blob at 1a9fc537 cross-checked against the working-tree bytes the verifier reads. None was transcribed.

	at e9c4827b	at 1a9fc537
digested (files:)	31	37
path-only (pinned_by_commit_only:)	45	67
surface	76	104

Upstream span (git diff --name-status e9c4827b 1a9fc537): 28 files added and 41 modified. Nothing was deleted or renamed. Every member declared at e9c4827b is still present and still in its list. 21 of the 31 earlier digests moved and 10 did not.

Classification of the 28 new files, by the pin header's own rule

The rule: the standard's normative surface is digested. That covers policy and schema data, contract and manifest templates, the tools that create or update a root, shipped validators, shipped root scripts and their libraries, the AGENTS-shape.md pair, AGENTS.md, README.md and LICENSE. Everything else is path-only: tests, CI, ignore and attributes files, CLAUDE.md stubs, template READMEs and Makefiles, rendered per-root AGENTS.md/CLAUDE.md, skeletons, and derived readings.

Digested (6)

• setup-project.py: the flow that creates a root. setup.sh became a shim over it (openRepoShape Register DTN-018..023: the remaining neutrality-sweep candidates #60).
• shape-doctor.py: a shipped validator. It runs the others and prints the verdict (Fix D17 miss: empty projects surface in the project dropdown #96).
• templates/family-root/scripts/siblings.py: shipped into every family holder beside the already-digested bootstrap.py and validate-family.py.
• contracts/single-repository-record.yaml (The publisher declares no pin on itself: unbreak doxBench's model routes #164): the schema of the optional staying-single record, normative like the naming policy.
• templates/single-repository/single-repository.yaml (The publisher declares no pin on itself: unbreak doxBench's model routes #164): that record's template, a contract template like templates/assembly-root/project.yaml.
• scripts/shape_advisory.py (The publisher declares no pin on itself: unbreak doxBench's model routes #164): the library that scaffold-project.py, adopt-project.py and shape-doctor.py import the advisory from.

Path-only (22)

• 7 tests: tests/test_cli_reference.py, test_commit_trailers.py, test_park_resume_targets.py, test_setup_project_py.py, test_shape_doctor.py, test_windows_paths.py and test_shape_advisory.py.
• .gitattributes at the root and in the assembly-root and family-root templates. This follows the .gitignore / Makefile / validate.yml precedent: those three are also copied and pinned upstream, yet have been path-only here since 122d729b.
• The 9 files of templates/workspace-root/. It is a skeleton the shape neither materializes nor pins, and it is rendered per person.
• docs/cli.md, scripts/render-cli-reference.py and docs/handbook.html. These are derived readings of the digested surface: the first is generated from the tools' --help, and the last is the designed reading of the README.

Obligations met beyond the pin file

• tests/openreposhape_pin/test_pin_verifier.py: the hard-coded COMMIT, the counts, the count-named test and the abbreviated-oid case move with the pin.
• docs/project-repo-schema.md: a dated > Amended 2026-10-06 currency note, on the Bump the openRepoShape pin to 122d729b: 27 digested / 33 path-only / 60-file surface #650/Bump the openRepoShape pin to e9c4827b: 31 digested / 45 path-only / 76-file surface #700 pattern. No doctrine requirement moves.
• No manifest row, CHANGELOG entry or contract cut. The pin is measured and not registered (The two sibling consumption pins are unregistered contract members: contracts/openxwallet-pin.yaml and contracts/openreposhape-pin.yaml carry no contracts/manifest.yaml row, and R1 reaches them by its own terms wherever another repository reads them #775/Register the sibling consumption pin R1 actually reaches, and record the measured non-reach for the other #1026), and it is not a release-inventory member. validate-release-tag-gate.py reports "no release surface change".

Ticks recorded (second commit on this PR, tasks.md only)

Each tick is modelled on 5.1's. Each holds on main only through this PR's merge.

• 5.2: Prefer the Triad: the work-start advisory, the optional single-repository.yaml, and the posture text (prefer-triad-project-shape 5.2) openRepoShape#164 → 1a9fc537… (squash). Checks green: tests, tests-macos, tests-windows, SonarCloud. Full suite went from 1159 to 1200 passed, 33 skipped.
• 5.3: this PR → its pin commit, plus the openreposhape-pin gate run on it.
• 5.4: setup-openspeckit: advise a non-Triad repository at bootstrap (prefer-triad-project-shape 5.4) workBenches#139 → 9fbe609c… and A reload keeps your place #140 → d86ba59b…. Post-merge main CI is green. test-openspeckit-bootstrap.sh reports 1042 PASS. workBenches#138 is closed as completed.
• 5.5: the private brettheap/new-workstation, cited by sha and file name only: Release contract-v1.29 wheel, intent, and worker contracts #52 → e081c5ab… and release: contract-v1.28 — the chat-turn request's active_document_path is nullable (G-1) #53 → cb411460…. That repository has no CI. The live ~/.agents files are byte-identical to cb411460.
• 5.6 stays unticked. 5.7 is left exactly as prefer-triad-project-shape 5.7: the estate inventory, a recommendation only #1255 merged it.

Validator results

Run in a scratch checkout named openxFactory, with the submodules CI initializes, against main 0992369a.

check	result
validate-openreposhape-pin.py --checkout <openRepoShape@1a9fc537>	OK: 37 digests recomputed, 67 members present, 104 files declared, none undeclared
gate simulation (fresh git fetch --depth 1 of 1a9fc537 from GitHub, then the gate's own two steps)	same OK; the gate reads 1a9fc537… out of the pin
pinned OpenSpec CLI --change prefer-triad-project-shape --strict	1 passed, 0 failed
pinned OpenSpec CLI --all --strict	113 passed, 1 failed (114), exit 0. Identical on clean main; the one is the accepted add-chain-attestation exception
validate-code-surface.py, validate-target-release.py, validate-sequenced-after.py (+ --ledger-diff: 232 rows), proposal-support.py verify prefer-triad-project-shape	all pass
validate-release-tag-gate.py	no release surface change
doc-health --single-repo vs clean main	zero finding delta (31 critical / 26 error / 68 warning / 19 info on both); +176 ratified words, the amendment note
pytest: tests/openreposhape_pin, every test file naming the pin, and tests/sequenced_after tests/code_surface tests/target_release tests/scope_globs tests/proposal-support	1172 passed
secret scan of the diff (pattern scan; no gitleaks on this host)	0 hits; the 27 new 64-hex strings are all sha256s of files at 1a9fc537

Out of scope, noted

docs/project-repo-schema.md § "Naming, and the four families" is stale. The pinned naming policy had five families at e9c4827b and has six now; the sixth is workspace (<user>-wip, openRepoShape #86). The section says the families are "governed as DATA in the pinned standard's contracts/repository-naming.yaml, not by this prose", so no requirement moves with the pin. The heading is left for a separate follow-up.

🤖 Generated with Claude Code

Summary by Sourcery

Advance the openRepoShape contract pin to the Triad project-shape implementation and synchronize its manifest, documentation, task tracking, and verification tests.

Enhancements:

• Advance the openRepoShape pin to the commit implementing the preferred Triad project shape and optional single-repository support.
• Expand the pinned normative and path-only surface to cover the upstream standard's latest files and update all associated SHA-256 digests.
• Record the completed project-shape tasks and refresh the schema currency note.

Documentation:

• Add a dated note documenting the updated openRepoShape pin and covered surface.

Tests:

• Update pin verifier expectations for the new commit, file counts, surface size, and abbreviated-commit validation.

[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 17 hours and 53 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's Guide

This PR advances the openRepoShape contract pin from e9c4827b to 1a9fc537, the squash merge realizing prefer-triad-project-shape task 5.2, and makes the pin complete for the upstream 104-file surface by recalculating normative digests and classifying path-only files. It synchronizes verifier tests, adds a documentation currency amendment, and records related task progress.

File-Level Changes

Change	Details	Files
Advance the openRepoShape pin to the commit implementing task 5.2 and expand the complete pinned surface declaration.	Replace the pinned commit with 1a9fc537 and update the historical commit narrative. Recompute and update 37 normative file digests, adding six newly digested files. Add 22 newly discovered files to the path-only list, preserving completeness and classification rules. Update pin metadata and explanatory counts for the 104-file surface.	contracts/openreposhape-pin.yaml
Synchronize pin-focused tests with the new upstream revision and surface counts.	Update the expected commit and abbreviated-OID fixture. Raise expected digested, path-only, and total surface counts to 37, 67, and 104.	tests/openreposhape_pin/test_pin_verifier.py
Amend documentation to reflect the current pinned standard without changing doctrine.	Add a dated currency note describing the new commit, expanded surface, and newly included capabilities.	docs/project-repo-schema.md
Record the implementation and validation progress for the governed change.	Add task ticks for 5.2 through 5.5 while leaving 5.6 and 5.7 unchanged.	tasks.md

---

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

[brettheap]

LANDING — lane codeXfactory-5, session ed23f049-7e99-4601-8a6d-760b6aeb5f26@Eagle, 2026-10-07T00:41:13Z, PR #1260 into opensoft/openxFactory main. On Brett Heap's word: "merge the 5.3 pin PR when green".

Lane: codeXfactory-5

[brettheap]

LANDED — lane codeXfactory-5, session ed23f049-7e99-4601-8a6d-760b6aeb5f26@Eagle, 2026-10-07T00:41:26Z, PR #1260 into opensoft/openxFactory main → squash f335c07716c636a994b76389f218a8d0151a3364

Merged on Brett Heap's word "merge the 5.3 pin PR when green", with every required check green at 60eedde5. Tasks 5.2, 5.3, 5.4 and 5.5 of prefer-triad-project-shape are ticked on main. 5.6 stays open with lane openRepoProject-1 (opensoft/openRepoProject#3, #5). The Rule 6 window is closed.

Lane: codeXfactory-5