[brettheap]

Lane: openreposhape-2 (openRepoShape-2)
Claim: opensoft/openRepoTools#198 (comment)

Act 2, slice 2a: the spec leg's half. This lands together with its code half, opensoft/openRepoTools-code#18 (head 56a9b87), never ahead of it. It is stacked on slice 1b's spec half, #15, and has merged that half's new head.

• Re-homed from Amendment 23 act 2, slice 2a: write-handoff writes a lane's handoff in the checkout its writes go through, handoff-path says where, publish-handoff keeps its contract on one shared act, and set-restart-intent takes the row's spellings (#198) openRepoTools#312 (old head 7bc572c), as Brett Heap's 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 Q28 ruled (Lane writers commit first and sync second, so a pull that refuses or conflicts strands the commit and later writes stack on it: fast-forward before the edit, and refuse before committing (fail closed) openRepoTools#198, comment 6722244541). The old PR stays open as the archived original until Brett decides (T019).

• The head is b3084abfa607a4f05b0aedb53062f843bc3300f5: the slice's commit 3f30c51, then two commits on top of it, both fast-forwards of the draft branch (no force-push; 3f30c51 stays an ancestor).

  • 7f8fd70, the merge of The lane manual carries act 2 slice 1b: every write takes Amendment 23 S3 under its lock and publishes by S4 with no pull, and old main's register hardening keeps its text where the two meet (opensoft/openRepoTools#198, slice 1b) #15's new head. That head, 0cca428, is slice 1b's commit plus a merge of this leg's main aed1852, so this branch now holds main too. The slice's commit was cut on the old 1b head, and a landing's tree has to equal the tree its head was tested with. The merge is clean: git merge-tree --write-tree 3f30c51 0cca428 gave tree 3cb3525ecedf26ae1afb3886170312886b49f323 with no conflict, and the merge commit has exactly that tree. docs/README-lanes.md is the only file either side changed, no conflict was resolved by hand, and no line of the slice's text was changed.
  • b3084ab, NIT 5 of lane openRepoTools-3's review. Exit row 6 lists an Amendment 8(d) handoff whose commit or push in its own repository failed among the causes that keep a commit on HEAD, and the row ends "Every later write from that checkout refuses until the lane publishes or archives it". That is false for 8(d): the commit is in the handoff's own repository, not in the lane checkout. The clause now ends with "(that commit is in that repository; no write here refuses over it)". It changes one sentence of one row (+1 -1). The code half, Amendment 23 act 2, slice 2a: write-handoff writes a lane's handoff in the checkout its writes go through, handoff-path says where, publish-handoff keeps its contract on one shared act, and set-restart-intent takes the row's spellings openRepoTools-code#18, is to carry the same words in lanes-edit.sh's 8(d) clause.
  • This PR's own diff over its base, The lane manual carries act 2 slice 1b: every write takes Amendment 23 S3 under its lock and publishes by S4 with no pull, and old main's register hardening keeps its text where the two meet (opensoft/openRepoTools#198, slice 1b) #15's branch, is still the three rows and +3 -3, as the commit message below says.

• The assembly's code and spec pins move in one commit. The composed job in opensoft/openRepoTools reads the pinned spec, so a pin bump that moves the code half without this half, or the reverse, fails (The lane manual carries act 2 slice 1b: every write takes Amendment 23 S3 under its lock and publishes by S4 with no pull, and old main's register hardening keeps its text where the two meet (opensoft/openRepoTools#198, slice 1b) #15 gives the measured cases).

• Checks run here: the spec leg has no CI workflow. Old 2a's five hygiene tests that read the manual pass against the slice's commit (5 passed), and the shell suite's 18 assertions that quote the manual pass. Lane openRepoTools-3's review ran the hygiene module with this leg's main plus The lane manual carries act 2 slice 1b: every write takes Amendment 23 S3 under its lock and publishes by S4 with no pull, and old main's register hardening keeps its text where the two meet (opensoft/openRepoTools#198, slice 1b) #15 plus the slice as the spec root (tree 3cb3525, the merge's tree): 239 passed, 14 skipped, at code 2b1a232 and at slice 3's 95c52cc. NIT 5's commit came after that run. It changes one sentence of exit row 6, and the code leg's tests that read this manual (the hygiene module's readers and the shell suite's quote sites) do not quote that row; the hygiene module's carry-promise, "nothing pushed", exit-3-row and fork-paragraph rules, applied alone to the manual before and after, give the same result. The full suites were not run for it.

• One figure in the commit message below follows the old slice: "the code leg's main (2a057a6)" names the code leg's v1.1.0 (its code PR 1), not the code leg's main today.

The commit message of 3f30c51, the slice's commit, follows in full: what this carries, the one meeting with opensoft/openRepoTools#263 and how it is resolved, and the receipt.

---

The lane manual's exit rows 2, 6 and 7 carry act 2 slice 2a: write-handoff answers the restart fences 7, keeps on HEAD a handoff origin changed or deleted meanwhile, and names an Amendment 8(d) handoff whose commit or push failed (opensoft/openRepoTools#198, slice 2a)

What this carries: slice 2a's own change to the spec leg's paths, from its
last merge of slice 1b, as git diff 59551dd97f0d7efed966fa0fd357b65c186ed530 7bc572cdbf27afeb692a7f98aeeb095d52c5f38f -- docs specs openspec on
opensoft/openRepoTools (the archived feat/198-a23-slice-2a-handoff-verbs
from its base on 1b). That is three rows of docs/README-lanes.md's exit
table, +3 -3:

• row 2 adds publish-handoff's restart fence on its bound file or
  pre-image, which write-handoff answers 7 instead;
• row 6 adds a whole-file write-handoff whose copy origin changed
  meanwhile (S4.4), a --stamp or --prepend one whose handoff origin
  deleted meanwhile (one moved with its row's cell is replayed into the
  moved file), and an Amendment 8(d) handoff whose commit or push in its
  own repository failed;
• row 7 adds publish-handoff / write-handoff's restart fence.

The patch's base is 2a's base on 1b, which this leg does not hold, so it is
applied as a three-way merge onto the slice 1b commit below (base: the
manual at 59551dd; ours: this leg's 1b; theirs: the manual at 2a). Row 2
merges clean. One conflict, rows 5 to 7, resolved by the 10-24 rehearsal's
rule for rows 5 and 6 (each side changed its own rows; keep both whole):

• row 5: The register's rewrites refuse a copy or write they cannot prove and put a cut-short register back, retire-rows refuses an unpushed log rename before it writes and calls a lane closed only from its published log, and add-row refuses an archive row it cannot read and takes back a row refused after its rebase (#120, #122) openRepoTools#263's, as on the 1b commit (2a left the
  base's row 5 as it was);
• row 6: 2a's, with slice 1b's later change to the same row made in it:
  458cdde spells origin's tracking ref in full there, git cherry -v refs/remotes/origin/main HEAD, and 2a never merged it (its last merge of
  1b is at 59551dd). The two changes touch different words of the row;
• row 7: 2a's (1b left the base's row 7 as it was).

The word diff of this commit is the word diff of 59551dd..7bc572c on
docs/, byte for byte.

Receipt: the old act-2 commits of opensoft/openRepoTools whose changes to
docs/ this carries (git log --format='%h %s' 59551dd..7bc572c -- docs).
The three merges of slice 1b in it brought 1b's own text, which the commit
below this one carries. The split rewrote this leg's history, so these ids
are the assembly's, which kept the whole history:

c962db7 A57: 604, as lane openRepoTools-3 ruled it, write-handoff commits and pushes an Amendment 8(d) handoff in its own repository, as lane-start and lane-handoff did at e2037b9, and never in another clone of the register (opensoft/openRepoTools#198, slice 2a, review of opensoft/openRepoTools#312)
36a25da A56: 603, write-handoff answers the shared act's two restart-fence 2s (the bound file, the pre-image) with 7, so its 2 is never a restart fence's; publish-handoff keeps its documented 2 (opensoft/openRepoTools#198, slice 2a, review of opensoft/openRepoTools#312)
f43deb3 Merge slice 1b at 59551dd into slice 2a: four blocks resolved as unions, and cp_own_commit given the whole message with the Lane: trailer (opensoft/openRepoTools#198, review of opensoft/openRepoTools#312, 606)
68014b4 A48: A46 follows a moved handoff only to a file the replay can write, so a peer that empties the row's cell, or points it at a name origin has no file for or outside handoffs/, keeps the --stamp or --prepend on HEAD (6) instead of dropping it with nothing written (opensoft/openRepoTools#198, slice 2a)
e2037b9 A46: A37 keeps a --stamp or --prepend on HEAD only where a replay could not follow the handoff, so a handoff a peer moves with its row's cell mid-push is replayed into the moved file instead of kept (opensoft/openRepoTools#198, slice 2a)
76a019b A37: write-handoff names the handoff --stamp and --prepend edit in place in slice 1b's CP_KEEP_IF_GONE, so a peer that deletes it while the push is in flight leaves the write kept on HEAD and named, instead of replayed into nothing (opensoft/openRepoTools#198, slice 2a)
287f6e5 Merge slice 1b at e6ea8f8 into slice 2a: exit rows 2 and 6 list both sides' new causes (opensoft/openRepoTools#198)
b02618c Merge slice 1b at 10169f3 into slice 2a: exit 6 names both sides' new causes, and both sides' new globals are kept (opensoft/openRepoTools#198)
357ec07 write-handoff writes a lane's handoff in the checkout its writes go through, as a Rule 3 stamp, a new top block or a whole prepared file, under S3, the translation, the restart fences and S4, and handoff-path says where that is (opensoft/openRepoTools#198, slice 2a stage 2)

Checks: this leg has no CI of its own (no .github/ on any ref). The
composed job in opensoft/openRepoTools runs the code leg's suite against a
pinned spec commit, so this text is checked there once a pin names it.
Run locally, with this tree as OPENREPOTOOLS_SPEC_ROOT:

• the five tests of slice 2a's own tests/test_repo_hygiene.py (at
  7bc572c) that read this manual: 5 passed;
• the shell suite's 18 assertions that quote this manual, replayed alone:
  18 passed;
• against the code leg's main (2a057a6) the exit-3 row test fails, as on
  the commit below, until the code half of slice 1b lands.

Lane: openreposhape-2 (openRepoShape-2)
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

🤖 Generated with Claude Code

[sourcery-ai]

Reviewer's Guide

Documentation

Update the lane exit-status table to distinguish handoff restart-fence refusals from retained or failed handoff writes.

• docs/README-lanes.md L1221-1226

---

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.