[brettheap]

Lane: openreposhape-3 (openRepoShape-3)
Claim: #776 (comment)

Closes #776.

Stacked on #771; lands after it. Lands after the v1.1.0 tag. (Its base is #771's branch l3-750-lockstep-next, so this diff is the #776 commits and the merge of #771's latest head; #771 is at f1234bc.)

What changed and why. In a root that lost scripts/repo_shape.py, the agent-files row for a deleted pinned copy (AGENTS-shape.md) ends its WHY with "then python3 <root>/scripts/validate-pins.py --root <root> to confirm the digest". That line exits 1 with ModuleNotFoundError: No module named 'repo_shape' there, on main as on #771 (found by RV-a as S1 of its review of #771; the row's NEXT, git -C <root> checkout -- AGENTS-shape.md, runs). The same sentence also named the root's own validate-pins.py where the root has none.

• shape-doctor.py confirm_digest (:7635-7672, new): the end of that WHY.
  • Where the root's own gate cannot import repo_shape, it puts the file back first, with shape-doctor.py: an own-copy validator row whose crash is a root's lost scripts/repo_shape.py names git -C <root> checkout HEAD -- scripts/repo_shape.py as its NEXT (none where HEAD no longer holds it) and the validator in its WHY (#697) #737's words: ". First git -C <root> checkout HEAD -- scripts/repo_shape.py: it puts back the scripts/repo_shape.py HEAD holds, ... Then run <gate> once the file is back, to confirm the digest; ...". These come from lost_repo_shape_cure (called with again=False, since the reader never ran the gate) and restore_from_head, not re-written.
  • Where HEAD no longer holds the file, the cure is dropped and the same helper says why no command does, where the file comes back from, and the gate to run after.
  • Where the root has no own validate-pins.py, the standard's template copy is named with its PYTHONPATH, as the validator rows name it.
  • Where no line can be named (neither copy readable, or a PYTHONPATH that cannot name the template), nothing is said of a gate, as lockstep_next prints no line there (shape-doctor.py: the legs row's NEXT (and the members row's) runs <root>/scripts/bootstrap.py without asking whether the root has it, so a root that lost it pastes python3: can't open file, exit 2, and for an empty leg mount the legs NEXT would not cure the row even with the file there (bootstrap.py only prints Run git submodule update --init spec) #276).
  • Everywhere else the WHY is byte for byte what it was.
• shape-doctor.py gate_line (:4887-4903, new): (copy, own, line | None) for a gate, which is the validator_for + pythonpath_unnamable + validator_command sequence lockstep_next already ran, now shared with confirm_digest (one definition of "a line that can be named"). lockstep_next (:4906) calls it; its behaviour is unchanged.
• check_agent_files (:7675, call at :7700): the pinned branch's WHY is built with confirm_digest(ctx). The row's NEXT, status and detail do not move.
• Not touched: pin_restore, with_gitlink_repairs, the .gitmodules readers, the partial-clone row.

Tests (stub gh first on PATH that exits 97, GH_TOKEN=bogus, empty GH_CONFIG_DIR; /usr/bin/python3 -m pytest -q -p no:cacheprovider --basetemp=<scratch>/bt -o tmp_path_retention_policy=failed <files>):

• tests/test_doctor_validator_rows.py (shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY still says to run the root's own validate-pins.py "to confirm the digest", a line that exits 1 with ModuleNotFoundError #776 section, beside shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT still names the root's own validate-pins.py line, which exits 1 with ModuleNotFoundError, while the pins row beside it prints the checkout HEAD cure #750's):
  • for the lost-repo_shape.py root the NEXT is unchanged, the WHY names the cure first and the gate after, the gate named dies with ModuleNotFoundError before, and the WHY's three lines (the NEXT, the cure, the gate), run in that order, all exit 0;
  • a committed deletion gives a WHY with no cure that names the file, the parent of the deleting commit and the gate;
  • a root that keeps repo_shape.py has the WHY byte for byte as it was;
  • a root with no validate-pins.py of its own has the standard's template line named;
  • with neither copy readable, no gate is named.
  • Before the change the first two and the template case failed against shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771's doctor; the control passed on both.
• tests/test_doctor_next_is_a_command.py: a CASES entry check_agent_files-pinned-lost-repo-shape, so the NEXT passes the property and the tail guard.
• tests/test_doctor_validator_rows.py tests/test_doctor_next_is_a_command.py tests/test_doctor_legs_members_next.py tests/test_repo_hygiene.py tests/test_cli_reference.py: 354 passed.
• tests/test_shape_doctor.py (once, on this head): 436 passed, 3 skipped, 1 xfailed.

Round 2 (RV-a's review of 676f80a, one MUST and three NITs; head c4c96b1, after a plain merge of #771's f1234bc).

• M1, the gate is the root kind's: confirm_digest (shape-doctor.py:7635-7672) chose PINS_GATE for every root, and the row runs in a family holder (CHECKS applies it to (PROJECT, FAMILY)), where the assembly root's validate-pins.py refuses with a remedy naming a file the holder lacks. It now takes FAMILY_GATE if ctx.kind == FAMILY else PINS_GATE and passes gate[0] to lost_repo_shape_cure, so a holder is told its own validate-family.py, and gets shape-doctor.py: an own-copy validator row whose crash is a root's lost scripts/repo_shape.py names git -C <root> checkout HEAD -- scripts/repo_shape.py as its NEXT (none where HEAD no longer holds it) and the validator in its WHY (#697) #737's cure where it lost scripts/repo_shape.py. The tests are parametrized over pins and family: with repo_shape.py intact the line is the root kind's own gate and, run after the NEXT, exits 0; with it lost, the NEXT, the cure and the gate, in order, all exit 0. Against the round-1 doctor 8 of the 12 agent-files tests fail, the holder ones among them.
• N1: where HEAD lacks the file the WHY reads ". HEAD does not hold ... Then run <gate> once the file is back, to confirm the digest; ...", not a lead-in to a sentence that is no instruction. lost_repo_shape_cure (:1814-1860) takes a purpose for it, and the cure case reads ". First <cure>: it puts back ..." (the lead-in no longer repeats the purpose).
• N2: where the standard's template copy is named because the root has no gate of its own, the WHY ends ". Until is back that exits 1, reporting the file as pinned but absent", said only where pinned_paths has a row for it. A test pastes the NEXT and then that line from /: it exits 1 with shape-copy-missing for the gate.
• N3: the shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY still says to run the root's own validate-pins.py "to confirm the digest", a line that exits 1 with ModuleNotFoundError #776 tests parse each line they run with argv_of (shlex on POSIX, split on Windows, where command_of's split is the only reading of a backslash path), so a basetemp with a blank no longer breaks them.
• CASES: check_agent_files-pinned-lost-repo-shape and a -holder entry.

Round 3 (RV-a's optional NIT, tests only; head below, doctor unchanged). The N2 sentence had a surviving mutant: without its pinned_paths check (shape-doctor.py:7669) no test failed. tests/test_doctor_validator_rows.py now builds a root with no gate of its own whose contracts/shape-pin.yaml has no files: row for it (without_its_own_gate(..., pin_row=False), the row removed as bytes), for an assembly root and a holder: test_the_agent_files_why_says_nothing_of_a_gate_the_pin_has_no_row_for asserts the WHY is the template line named and no "Until" sentence, and test_the_template_line_for_a_gate_the_pin_has_no_row_for_passes pastes the NEXT and then that line from / and asserts exit 0 with no shape-copy-missing. With the check dropped, the first fails for both kinds (2 failed, 14 passed of -k "agent_files or template_line"); on the head all 16 pass. tests/test_doctor_validator_rows.py tests/test_repo_hygiene.py tests/test_cli_reference.py: 170 passed.

Docs. None state the agent-files WHY, so none changed. Pinned copies: none touched; shape-doctor.py is in no copy list.

🤖 Generated with Claude Code

Summary by Sourcery

Make agent-files remediation guidance restore missing validator dependencies before confirming pinned-file digests and select only an appropriate runnable gate.

New Features:

• Improve the agent-files guidance for pinned copies by naming a runnable digest-validation command appropriate to the root type and available validator copy.

Bug Fixes:

• Prevent the guidance from directing users to a validator that fails when the root is missing scripts/repo_shape.py by restoring that file first or explaining when no cure is available.
• Use the family validator for family holders and avoid naming a missing standard validator when the pin has no corresponding file row.

Enhancements:

• Share gate-command selection between lockstep and agent-file guidance so both rows consistently identify runnable validator commands.

Tests:

• Add coverage for lost and committed repo_shape.py, family holders, standard-template validators, unavailable gates, and pin rows without validator files.
• Extend command-property tests to cover the updated pinned agent-files guidance for assembly roots and holders.

[sourcery-ai]

Reviewer's Guide

The PR fixes misleading agent-files guidance by sharing validator command selection and dynamically describing how to restore a missing repo_shape.py before confirming a pin digest, with comprehensive regression coverage for root, template, absent, and committed-deletion cases.

Flow diagram for agent-files digest confirmation guidance

flowchart TD
    A[check_agent_files] --> B[confirm_digest]
    B --> C[gate_line]
    C --> D{Named validator command?}
    D -->|No| E[Return no gate guidance]
    D -->|Yes| F{Root validator imports repo_shape?}
    F -->|Yes| G[Name validate-pins.py command]
    F -->|No| H{HEAD contains scripts/repo_shape.py?}
    H -->|Yes| I[lost_repo_shape_cure and restore_from_head]
    I --> J[Name restore command first]
    J --> G
    H -->|No| K[Explain why no cure is available]
    K --> G

Loading

File-Level Changes

Change	Details	Files
Centralize gate selection and command generation so validator rows consistently identify a runnable root or standard-template copy.	Added gate_line to share copy selection, PYTHONPATH handling, and omission behavior. Updated lockstep_next to use the shared helper without changing its output behavior.	shape-doctor.py
Make the pinned agent-files explanation prescribe a valid digest-confirmation sequence when the root’s validator depends on a missing repo_shape.py.	Added confirm_digest to prepend the existing restore-from-HEAD cure when applicable. Explains the no-cure case when HEAD no longer contains the file. Names the standard template validator when the root lacks its own copy, and omits the gate when no runnable line can be formed. Integrated the helper into the pinned agent-files WHY while preserving NEXT, status, and detail.	shape-doctor.py
Add regression and command-property coverage for all validator-source and missing-module scenarios.	Verify cure-before-gate ordering and successful execution after restoration. Cover committed deletion, unchanged healthy roots, standard-template fallback, and unreadable validator copies. Ensure the generated NEXT remains a valid command.	tests/test_doctor_validator_rows.py tests/test_doctor_next_is_a_command.py

Possibly linked issues

• shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY still says to run the root's own validate-pins.py "to confirm the digest", a line that exits 1 with ModuleNotFoundError #776: The PR fixes the exact issue by revising the agent-files WHY for missing repo_shape.py and unavailable root validators.

---

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.

[brettheap]

(lane openRepoShape-3, 2026-10-17T04:14:33Z) Independent review of #780 by RV-a (opus), on head 676f80a7 (base l3-750-lockstep-next): NOT READY. There is one MUST, and it is small. Three NITs. It lands only after the v1.1.0 tag, after #771.

What works (probe on main and main + #780, every line the WHY names pasted):

case	main	#780
P1 repo_shape.py intact, AGENTS-shape.md deleted		WHY byte-identical to main; the gate prints pins ok
P2 repo_shape.py lost in the tree	the named gate dies, ModuleNotFoundError	cure, then gate. Pasted in order: NEXT, cure and gate all exit 0
P3 committed deletion		no cure; names the parent commit and the gate
P4 no own validate-pins.py	named a missing file, can't open file, exit 2	the template line with its PYTHONPATH

gate_line leaves lockstep_next as it was. The tests bite: against the base's doctor they give 5 failed (all new) and 4 passed.

M1: in a family holder, the WHY names the assembly-root gate.

• Where: shape-doctor.py:7647. confirm_digest calls gate_line(ctx, PINS_GATE) for every root kind, and the agent-files row runs in holders (:9535, (PROJECT, FAMILY)).
• H1, a holder (InkRouter) with AGENTS-shape.md deleted:
  • shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780 names env PYTHONPATH=<std>/scripts python3 <std>/templates/assembly-root/scripts/validate-pins.py --root <holder>. Pasted after the NEXT, it exits 2 with a REFUSED whose remedy names scripts/validate-pins.py, which a holder lacks.
  • Main named <holder>/scripts/validate-pins.py: can't open file, exit 2.
  • The holder's own gate, python3 <holder>/scripts/validate-family.py --root <holder>, exits 0 with "ok contracts/shape-pin.yaml: 10 copied shape file(s) match their digests".
• H2, a holder that also lost scripts/repo_shape.py: shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780 names the same refusing line. validate-family.py dies with ModuleNotFoundError until git -C <holder> checkout HEAD -- scripts/repo_shape.py, then exits 0. A holder needs shape-doctor.py: an own-copy validator row whose crash is a root's lost scripts/repo_shape.py names git -C <root> checkout HEAD -- scripts/repo_shape.py as its NEXT (none where HEAD no longer holds it) and the validator in its WHY (#697) #737's cure exactly as a root does.
• Why it is a MUST: shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY still says to run the root's own validate-pins.py "to confirm the digest", a line that exits 1 with ModuleNotFoundError #776's goal is that no row names a command that cannot run, "as the validator rows do", and a holder's validator row uses FAMILY_GATE. No test covers a holder.
• Fix:
  • use gate = FAMILY_GATE if ctx.kind == FAMILY else PINS_GATE, and pass gate[0] to lost_repo_shape_cure;
  • add two holder tests: intact (the holder's own validate-family.py, which exits 0 when pasted), and lost repo_shape.py (the cure, then validate-family.py).

NITs:

• N1 :7654-7655: in the committed-deletion case the WHY reads ". To confirm the digest, HEAD does not hold …", a lead-in to a sentence that is not an instruction. Write ". HEAD does not hold … Then run … once the file is back, to confirm the digest".
• N2 (optional): P4's template line, pasted after the NEXT, exits 1 with FINDING shape-copy-missing: … scripts/validate-pins.py is pinned but absent. It does confirm AGENTS-shape.md, but the reader sees exit 1 under "to confirm the digest". Say that it also reports the missing gate.
• N3: the shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY still says to run the root's own validate-pins.py "to confirm the digest", a line that exits 1 with ModuleNotFoundError #776 tests run run_argv(line.split()), which breaks on a basetemp with a blank. Parse the line as command_of does.

Mutants (-k agent_files; the head passes 9):

mutant	result
no cure	3 killed
always the root's own path	1 killed
drop the no-line branch	1 killed
holder gate	untested (M1)

Tests:

• five targeted files on main + shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780: 346 passed;
• tests/test_shape_doctor.py once, on main + shape-doctor.py: the the way in rows say a checkout's own contracts/repository-naming.yaml that does not load, or raises, is that checkout's, an n/a environment row, where a tab line was FINDING the way in refused and a pattern that does not compile ended the doctor in a traceback; and the EXIT CODES list says what INVALID and manifest-kinds name (#707) #778 r2 + shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780: 436 passed, 3 skipped, 1 xfailed.

Sonar passes. No doc describes this WHY, and no pinned copy is touched.

Base l3-750-lockstep-next: fine for review and for landing after #771.

• Never merge shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780 before shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771.
• After shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771 squash-lands and its branch is deleted, GitHub retargets shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780 to main, but update-branch refuses after a parent squash. Merge shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771's final head, then main, taking main's side for shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771's files once the squash tree equals shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771's final head. Then re-run CI on the main-based head.

Lane: openreposhape-3 (openRepoShape-3)

[brettheap]

(lane openRepoShape-3, 2026-10-17T04:43:01Z) RV-a's re-verification of #780 round 2 (c4c96b1d): READY. M1 and N1-N3 are fixed. One new optional NIT. It lands only after the v1.1.0 tag, AFTER #771, and never into l3-750-lockstep-next. Linux tests was pending at 04:42Z.

Every line pasted through sh from /, on main + #780:

case	the WHY says	pasted
H1 holder, AGENTS-shape.md deleted	python3 <holder>/scripts/validate-family.py --root <holder>	NEXT exits 0, then family ok, exit 0
H2 holder that also lost repo_shape.py	". First git -C <holder> checkout HEAD -- scripts/repo_shape.py: … Then run …validate-family.py… once the file is back, to confirm the digest"	NEXT, cure and family ok all exit 0
H3 holder without its own validate-family.py	the family template line + ". Until scripts/validate-family.py is back that exits 1, reporting the file as pinned but absent"	exits 1, as stated
H4 holder, committed deletion	no cure; ". HEAD does not hold … Then run … once the file is back, to confirm the digest"	the gate dies until the file is back, as stated
P1-P4 (assembly root)	unchanged from round 1 (P1 byte-identical to main)	as stated

N1 and N2 cannot both apply. The purpose wording is built only on the own-copy branch, and N2 requires not own_copy (:7669).

Mutants (-k agent_files; the head passes 17):

mutant	result
holder gate back to PINS_GATE	6 killed
drop the purpose	4 killed
N2 sentence without the pinned_paths check	survives

New NIT (tests/test_doctor_validator_rows.py:1114): RV-a measured the surviving mutant's case.

• The case: a root without its own validate-pins.py whose pin has no row for it.
• The head is right there: no "Until …" sentence, and the template line exits 0 with pins ok. The mutant would print a false "exits 1".
• Fix: add that case.

Tests:

• five files on main + shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780: 354 passed;
• tests/test_shape_doctor.py: 436 passed, 3 skipped, 1 xfailed.

Merges: clean with bf1f099b and every open lane-3 v1.1.1 PR at its current head.

#771's NIT round (f1234bc6) is READY too.

• unloaded_manifest_row (:2111) says "this root committed", and its CASES opening matches. "this project committed" no longer appears anywhere.
• The body's :1814-1857 span is right.
• 114 passed; clean merges.

Lane: openreposhape-3 (openRepoShape-3)

[brettheap]

(lane openRepoShape-3, 2026-10-17T04:47:37Z) RV-a's re-verification of #780 round 3 (68f27877): READY. Tests only; shape-doctor.py is byte-identical to round 2.

• mC is killed. Dropping and gate[0] in pinned_paths(ctx.root) (:7669) fails 2 tests: test_the_agent_files_why_says_nothing_of_a_gate_the_pin_has_no_row_for[pins] and [family]. The head passes 21.
• The tests assert what the check protects.
  • The first asserts the whole WHY by equality, so a stray "Until …" sentence fails it.
  • The second pastes the NEXT and the template line from /, and asserts exit 0 with no shape-copy-missing. That proves the omitted sentence would have been false, for both a root and a holder.
  • The builder removes exactly one files: row.
• NIT (optional): without_its_own_gate's regex matches \n only. Under a CRLF checkout it fails loudly at removed == 1. Use \r?\n, as shape-doctor.py: a checkout whose own contracts/repository-naming.yaml does not load is CANNOT ANSWER, exit 3, for a project, where it read INVALID (naming), exit 1; any other naming exit 2 "refuses"; and the EXIT CODES list names an unfinished merge (#678) #701's pattern does.
• Merges: clean with bf1f099b. shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771 (f1234bc6) is an ancestor.
• CI at 04:47Z: Sonar and package pass; tests and tests-git-bash were pending after the push.

Lane: openreposhape-3 (openRepoShape-3)

[brettheap]

(lane openRepoShape-3, 2026-10-18T05:31:26Z) #780 is restacked after #771's squash (3bf2d3c), as 40167950, by lane 3's three-merge recipe (writer R780, opus-xhigh):

1. bf2e62e5 merges shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771's final head 28b13d67. It is clean.
2. 40167950 merges the squash 3bf2d3c9, taking ours only in shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771's three files, which conflicted: shape-doctor.py, tests/test_doctor_next_is_a_command.py and tests/test_doctor_validator_rows.py. The squash and the final head have the same tree, 5dee1c95, and this merge changed nothing.
3. Main was 3bf2d3c9 itself, so the third merge was "Already up to date".

• The delta: git diff --name-only origin/main 40167950 lists only shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780's three files, +303/-13. Its -U0 changed lines equal git diff f1234bc6 68f27877, shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780's delta over shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771's head: 316 lines on each side.
• Tests on 40167950, under a stub gh: tests/test_shape_doctor.py, 442 passed, 3 skipped; the rest of shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780's gate set with tests/test_no_auto_maintenance.py, 426 passed.
• Base: shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780's base is now main. GitHub moved it there when shape-doctor.py: in a root that lost scripts/repo_shape.py, the legs and members lockstep NEXT is the pins and family rows' git -C <root> checkout HEAD -- scripts/repo_shape.py (none where HEAD no longer holds it), where it named the root's own gate, which dies on the import (#750) #771's branch was deleted.
• shape-doctor.py: in a root that lost scripts/repo_shape.py, the agent-files row's WHY puts the file back before it names validate-pins.py to confirm the digest (or says why no command does), and names the standard's copy where the root has none (#776) #780 lands at a lane-3 turn by fast refresh, once its CI on 40167950 is green.

Lane: openreposhape-3 (openRepoShape-3)

[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

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