[brettheap]

Lane: openRepoTools-1
Claim: opensoft/openRepoTools#186 (comment)

What changes

This PR moves the code leg's pin on openRepoShape from v1.1.0 to v1.1.1, in one commit:

• contracts/openreposhape-pin.yaml:
  • commit: moves from 190133d5e704e380c430f87ca9c4e31746de0012 to 50178305e4229275d18e71c2152403b4e9d3004e.
  • digests.tree_sha256 moves from 7a66972c7de193c050f77f97bffa13d8543c28d74f61ea210644e65aa3f37912 to 204d73aabf2379554600234d4b36dc08d3c3a1da422395dec44637b5ca7a5184.
• The gitlink upstream/openRepoShape moves from 190133d5e704 to 50178305e422, together with the pin file.
• tests/test_install_payload_source.py, one docstring line:
  • The citation of openRepoShape's --install pointer changes from openRepoShape:547 at 190133d to openRepoShape:745 at 5017830.
  • The line's bytes are unchanged at the new commit (cmp equal).
  • The test's pipeline string is untouched.

Nothing else moves in this commit.

• Two comments go stale, because they say in the present tense that the pin is 190133d: .github/workflows/release.yml:6-7 and tests/test_release_workflow.py:144-145.
  • The comment-only commit 7e1df87e on this branch fixes both (review finding S2): they now say that the pin moved to 5017830 (v1.1.1).
  • It keeps the 190133d that tests/test_release_workflow.py's HEADER_SECTIONS check needs in release.yml's header.
• These stay as they are, as dated provenance:
  • the two release requirement locks;
  • that header check;
  • the notes on v1.1.0's parse_yaml and layout.

Why

Two rulings of Brett Heap's govern this, on opensoft/openRepoTools#186:

• 2026-10-22: he ruled that openRepoShape v1.1.1 is the pin bump after the cutover (comment 6342293150, item 16: "keep v1.1.0 (190133d). v1.1.1 is a pin bump after the cutover.").
• 2026-11-08: he answered "v1.1.1 b", which he sent at 11:57:46Z and confirmed in a dialog at 13:06:02Z (Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186 (comment)). It means:
  • both of the triad's pins on openRepoShape move;
  • each PR lands only on his word;
  • there is no release.

This PR moves the code leg's mounted pin. opensoft/openRepoTools#348 moves the root's shape copies.

v1.1.1 is the annotated tag fd9316bb8e4f99d13a678b4bfc3846b4759ecbb7. It peels to 50178305…, which is an ancestor of openRepoShape's main (bd3e9c1485d3, 121 commits later). The pinned-standard rule allows only a commit on main, and this one is.

How the values were made

The bump follows the procedure in the pin file's header, with the edit before the git add:

1. Check out 50178305… in upstream/openRepoShape.
2. Recompute the digest with the pinned checkout's own repo_shape.tree_digest.
3. Write the two values.
4. Stage the pin file and the gitlink together.

The digest is recomputed, never adjusted:

• v1.1.0's helper and v1.1.1's helper print the same two numbers on both trees (366 records at v1.1.1). So sorted-ls-tree-r-v1 means the same on both sides.
• A research read of the forge's recursive tree listing on 2026-11-02 gave the same 204d73aa… independently.

Four of the eight files the suite mounts change at v1.1.1:

• scripts/repo_shape.py
• templates/assembly-root/scripts/bootstrap.py
• templates/family-root/scripts/bootstrap.py
• templates/family-root/scripts/siblings.py

The two Makefiles and the two .gitignore files are byte-identical at both commits.

Order

PR C waits for this PR. The root's PR C points the assembly's code gitlink and contracts/code-pin.yaml at the commit this PR leaves on main. C's exact-pins job then runs the composed suite at that commit, with upstream/openRepoShape at v1.1.1. That run also covers the nine composed-acceptance tests that skip below.

The order on the code leg:

• Done: lane 4's nine T017 PRs landed on Brett's word (Releases: annotated tags, release/vX.Y branches, and openrepotools on TestPyPI and PyPI from v1.1.0 openRepoTools#228 comment 6722087863), leaving main at 577110e4.
• Now, first ready, first landed (Amendment 22 act 2: the SQL register under lanes-edit.sh — mode=primary writers in one transaction each, the estate switch and lanes/STORE, the write journal and the renderer (one mirror commit per write), exit 69, fail-closed readers, lanes-index import/rollback, SERIALIZABLE claim order, and the agreement tests openRepoTools#165 comment 6723967774). This PR, lane 2's W2 picks and openRepoShape-2's slices land in the order they become ready, under Rule 6's HOLD. Whichever lands second merges the new main in place and re-runs before it lands.
  • This PR merged main 577110e4 in place, as ce266b1d, with no force-push. The merge is clean, and the PR's change is still its five paths.
  • Its CI runs on ce266b1d.
• After this PR, the root's PR C moves the code pin, together with T017's bump where both are ready.

No release

Nothing here is tagged or published. The leg's release/v1.1 branch and its tag v1.1.0 stay at 2a057a6d.

This PR would still ship in v1.2.0 if it lands before that tag (review finding S3).

• Whatever is on the code leg's main at v1.2.0's tag ships in v1.2.0.
• v1.2.0 carries Amendment 22 act 2: the SQL register under lanes-edit.sh — mode=primary writers in one transaction each, the estate switch and lanes/STORE, the write journal and the renderer (one mirror commit per write), exit 69, fail-closed readers, lanes-index import/rollback, SERIALIZABLE claim order, and the agreement tests openRepoTools#165 and T017's five fixes (Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186 comments 6721648587 and 6721870837).
• So Brett's word to land this PR is also that decision.
• Brett has made it. On 2026-11-08 at 16:21Z he answered "Land them now, in v1.2.0 (Recommended)" for lane 2's seven code fixes and this PR (Amendment 22 act 2: the SQL register under lanes-edit.sh — mode=primary writers in one transaction each, the estate switch and lanes/STORE, the write journal and the renderer (one mirror commit per write), exit 69, fail-closed readers, lanes-index import/rollback, SERIALIZABLE claim order, and the agreement tests openRepoTools#165 comment 6723967774).

Local tests

Setup:

• a fresh clone of main at 2a057a6d, with this commit on top and the submodule checked out at 50178305. These ran before the merge of 577110e4; the PR's CI runs on the merge, ce266b1d;
• standalone mode (OPENREPOTOOLS_COMPOSED=0), in a clean environment;
• Python 3.12.3, pytest 8.3.4.

Results:

• tests/test_upstream_pin.py: 15 passed in 0.07s. It checks:
  • the lockstep of pin and gitlink;
  • the digest, recomputed with the pinned helper;
  • the checkout at the pinned commit;
  • all eight mounted files present.
• tests/test_install_payload_source.py: 100 passed, 9 skipped in 167.96s.
  • All nine skips are composed-acceptance tests that need an assembly root, at lines 917, 951, 974, 1387, 1921, 2014 and 2023.
  • The test whose docstring moves is one of them.
• tests/test_park_resume_commands.py: 223 passed in 45.79s. It builds real estates from the four changed mounted files.

The rest of the suite is CI's job.

CI

The four required tests.yml jobs are guard-launch-mode, tests, tests-no-submodule and package.

This PR touches no shell file: it changes one YAML file, one Python test file and the gitlink. So SonarCloud's charge on lanes-edit.sh does not apply to it.

Landing

This PR lands only on Brett Heap's word.

🤖 Generated with Claude Code

[sourcery-ai]

Reviewer's Guide

Configuration

Update the openRepoShape pin’s commit and tree digest together so the mounted revision and its recorded identity stay in sync.

• contracts/openreposhape-pin.yaml L54, L60

Revise the release workflow’s provenance comments to describe the current pin while retaining the v1.1.0 adaptation history.

• .github/workflows/release.yml L7-10

Tests

Update the source citation for openRepoShape’s unchanged install-pointer line at the new pinned revision.

• tests/test_install_payload_source.py L922

Clarify that the release-workflow test models the workflow at the commit currently named by the pin.

• tests/test_release_workflow.py L144-147

Lock files and vendored code

Move the mounted openRepoShape submodule gitlink to the pinned v1.1.1 commit.

• upstream/openRepoShape L1

---

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.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[brettheap]

Lane openRepoTools-1, 2026-11-08T13:32:45Z: independent review of this PR, a check of the tree, not a landing word. The verdict is LAND after fixes, and the fixes are to text only.

The review was run by a separate agent with no part in writing this PR. It ran on Sonnet 5.5 and worked only from fresh clones and from GitHub.

What it checked, on the head 187991ffc4fadcb66b1eb750e44f7c425d5331f1:

• The diff: exactly three paths. The gitlink is at 50178305…, which is the peeled v1.1.1 (tag object fd9316bb…), and it is an ancestor of openRepoShape's main.
• The digest 204d73aabf2379554600234d4b36dc08d3c3a1da422395dec44637b5ca7a5184 was matched five ways, and the same methods give 7a66972c… on 190133d:
  • the pinned checkout's own helper, by the pin header's exact command;
  • 190133d's helper;
  • an independent re-implementation that walks tree objects with git cat-file (366 records);
  • git ls-tree -r -z | sort -z | sha256sum;
  • the forge's recursive tree listing.
• The docstring: line 745 of the launcher at 50178305 is byte-equal to line 547 at 190133d (cmp 0), and that line occurs once in each.
• tests/test_upstream_pin.py: 15 passed with the submodule, and 5 passed with 10 skipped without it. As a negative control, putting the old digest back makes it fail.
• The commit: the identity is Brett Heap's noreply address, with Lane: and Co-Authored-By: trailers. The body's facts were confirmed.

Findings and what was done with them:

• S1, the ruling's dates. The body now names both rulings: 2026-10-22 (Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186 comment 6342293150, item 16) and 2026-11-08 ("v1.1.1 b", confirmed at 13:06:02Z). The commit message's shorter line stays as it is, because nothing here is force-pushed.
• S2, two present-tense comments. They are .github/workflows/release.yml:6-7 and tests/test_release_workflow.py:144-145. A comment-only follow-up commit fixes them, and it is pushed together with the re-test after the T017 landings, so it costs no extra CI run.
• S3, which release it ships in. The body now says that this PR ships in v1.2.0 if it lands before that tag, so Brett's word to land it is also that decision.
• N2: a bot's summary was appended to the body, and the edit removed it.

Not yet checked: CI. tests and tests-no-submodule were still running at 13:28Z. guard-launch-mode, package and SonarCloud passed.

Lane: openRepoTools-1

[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 openRepoTools-1, session df82f553-7803-49c4-8ddf-3f9acdcb8ee0@Eagle, 2026-11-08T19:29:21Z, PR #15 into opensoft/openRepoTools-code main → into main; head ce266b1; openRepoShape v1.1.1's code-leg pin (B, #186), on Brett Heap's dialog answer 'Land B now (Recommended)' (19:26:48Z); merge commit

[brettheap]

LANDED — lane openRepoTools-1, session df82f553-7803-49c4-8ddf-3f9acdcb8ee0@Eagle, 2026-11-08T19:30:50Z, PR #15 into opensoft/openRepoTools-code main → main e393958 (merge commit of ce266b1 into 577110e; tree 625b7ba4 equals the head's; openRepoShape v1.1.1's code-leg pin, B, #186)