[brettheap]

Lane: openreposhape-2 (openRepoShape-2)
Claim: #538 (comment)

What changed

All six lines of #538 and both rides-along, on main bfed143. Every one reproduces there.

• Paste lines are one word per path. The hand-over's cd <clone> and step (7)'s backstop printed their paths bare, so a run with --into "/home/a b" printed lines the shell splits. Both now go through shell_word, as the family lines do (family.py and siblings.py print commands with unquoted paths, so under a folder with a space the member-git-dir-cached remedy's rm -rf would delete the wrong directory, and add's push line fails #486), and the three words (cd <clone>, and the backstop's cd <parent> and <assembly>) are spelled for sh on every host, Windows included (shell_word(..., posix=True)), as the scaffold's own NEXT STEPS clone already is (shell_line(..., "posix")): Printed commands are POSIX-only: quote the bare paste lines in bump-leg.py and update-shape.py, and say in the docs that pasted commands are for a POSIX shell #532 rules the printed commands POSIX-only, and PowerShell's spelling reads C:\work\Sample as C:workSample in Git Bash. The family lines (family_next_command) are Printed commands are POSIX-only: quote the bare paste lines in bump-leg.py and update-shape.py, and say in the docs that pasted commands are for a POSIX shell #532's and are unchanged. The backstop also names the clone's parent as a cd line of its own (finish_by_hand), so the whole block can be pasted.
• The two local recursive clones can read their legs. Under --local-remote-dir, the backstop's clone and the scaffold's own NEXT STEPS clone lacked -c protocol.file.allow=always, so they failed with transport 'file' not allowed. Both carry it now. The scaffold's line is POSIX-quoted (shell_line(..., "posix"), per the Printed commands are POSIX-only: quote the bare paste lines in bump-leg.py and update-shape.py, and say in the docs that pasted commands are for a POSIX shell #532 ruling). This is rides-along R1 and R2.
• The scaffold's NEXT STEPS stay out of a setup run. scaffold-project.py takes a new --no-next-steps, and setup passes it in step (6), because step (7) runs those steps next. Working trees are at still prints, since README's rehearsal paragraph (README.md:307) sends people to it.
• A file above the clone path is refused in step (3). A file at <into>/<Family> or at --into used to pass step (3). All three repositories were then created, and os.makedirs ended the run in a FileExistsError traceback. Step (3) now refuses anything other than a folder on the way up from the clone's parent. In step (7), a failed os.makedirs (a race, a permission) is now a refusal that prints the lines to finish by hand.
• -- --dry-run ends at the plan. Setup reads its passthrough the way the scaffold's argparse does: the flag whole, any prefix argparse accepts for it, and nothing after an inner --. With --dry-run there, the run stops after the plan with exit 0 and asks nothing. Before, step (7) said "The three repositories WERE created" when none were, and left the family folder behind. The usage text says so.
• Step (4) sees the pins passed through. The naming validator is now asked with --pins=<products> and --referent-chain= taken from the passthrough. A <Domainx><Product> project is then a domain descendant in step (4), as it already was in the plan, where step (4) used to say "no referent pin declared". PASSED_FLAGS records the shortest spelling the scaffold accepts for each flag it reads, and a test checks those against the scaffold's own --help.
• The upstream guard ignores case. is_upstream_org casefolds, so --org OpenSoft and an origin under OpenSoft/ are refused like opensoft. The refusal names the casing that was typed.

docs/cli.md is re-rendered for the usage line and the new scaffold flag, and render-cli-reference.py --check passes. Nothing under templates/ or contracts/ changed, so there is no re-pin.

Tests

Main moved while this PR was open, and the branch now carries three rounds of it.

• CI's merge ref failed on all three OSes with NameError: name 'FILE_PROTOCOL' is not defined in tests/test_scaffold_e2e.py::test_the_next_steps_clone_under_local_remotes_reads_the_legs: tests: every test that clones a just-pushed local remote by its plain path now clones it with clone_just_pushed, so the macOS failed to copy file race of #440 cannot reach it; load_without_bytecode keeps the doctor's and the Windows-path tests' loads of the family root's scripts from writing .pyc into the templates; the not-a-list doctor cases hold INVALID, exit 1; and GOOD_KEYS holds th #554 rewrote the file's first conftest import without that name, and this PR's test still uses it. The branch merged main 2247dbf and then 7d9bec9 (dc87f8a); the first merge keeps tests: every test that clones a just-pushed local remote by its plain path now clones it with clone_just_pushed, so the macOS failed to copy file race of #440 cannot reach it; load_without_bytecode keeps the doctor's and the Windows-path tests' loads of the family root's scripts from writing .pyc into the templates; the not-a-list doctor cases hold INVALID, exit 1; and GOOD_KEYS holds th #554's import line and imports FILE_PROTOCOL again on the file's second conftest import line.
• Merge of origin/main fb786c1 (5e9e3a4, clean; adopt-project.py: check finds, and execute refuses before any leg exists, a path the root keeps at the shape's own pin and a --work-dir this user cannot write in, so contracts/shape-pin.yaml kept in the root and a chmod 500 work directory no longer pass check and fail only after both legs are pushed (#524) #581 and ten other landings). It brought README.md and the handbook: the by-hand setup commands dry-run the scaffold with the --visibility and --elected-by setup passes, and apply --add names all five refusals it gives by their codes, each held by a test (#550, #429) #579's tests/test_setup_by_hand_commands.py, which this PR turned red: the test runs plan_and_confirm and scaffold with run recorded and holds README.md's and the handbook's by-hand scaffold-project.py lines, and plan == real + " --dry-run", to what setup runs, and setup's real run now carries --no-next-steps. Three tests failed on this PR's merge with today's main (the README's, the handbook's and the plan-and-real one).
• The by-hand test says the difference (df67b46, tests/test_setup_by_hand_commands.py only). By hand there is no step (7), so the scaffold's closing block is the person's next work and the documents' lines correctly omit the flag; changing README.md and the handbook instead would put this PR in another conflicted merge with each of the four open PRs that touch both. what_setup_runs now asserts the plan ends --dry-run and the real run is the plan's arguments plus exactly one final --no-next-steps, then returns the real run without it, the reason in its docstring and the module's. test_setup_runs_the_plan_and_the_real_run_with_the_same_arguments keeps plan == real + " --dry-run" and asserts the flag on the recorded argv. One-at-a-time mutants of setup-project.py (the flag dropped, an extra flag on the real run, the flag moved first) each fail three of the five tests.
• setup-project.py: its paste lines, the step (3), (4) and (7) checks, and the upstream-org guard #538's three blocks moved (0b6228f, a pure move: each file's lines are the same multiset, and so are its top-level definitions). setup-project.py: paste lines quote each path, the scaffold's NEXT STEPS wait for step (7), step (3) refuses a file above the clone, -- --dry-run ends at the plan, step (4) hears passed pins, and the upstream guard ignores case (#538) #569 and family.py and scaffold-project.py: --dry-run asks the real run's own question about existing remotes, so family-remote-exists and scaffold-remote-exists come at the plan, and a missing gh is gh-not-found, not a traceback (#537) #573 both insert after assert_a_taken_clone_path_is_refused in tests/conftest.py and after test_a_taken_clone_path_is_refused_before_anything in tests/test_setup_project_py.py and tests/test_setup_sh.py, so whichever lands second conflicts in all three files, and a conflicted merge is a new H0 that needs a full three-OS run. The # --- setup's paste lines... helper block now ends tests/conftest.py, and the # --- #538 wrapper blocks sit before # --- setup.sh is a shim, not a second flag list and # --- self-bootstrap. git merge-tree --write-tree of the head with the predicted main bd0c6b5c (origin/main 8890f57 plus adopt-project.py: check finds, and execute refuses before any leg exists, a path the root keeps at the shape's own pin and a --work-dir this user cannot write in, so contracts/shape-pin.yaml kept in the root and a chmod 500 work directory no longer pass check and fail only after both legs are pushed (#524) #581, scaffold-project.py: a leg gh sees and git cannot read is refused scaffold-remote-exists with git's terminal prompt off, and the reuse re-run's visibility lines go by each leg as it stands (#542) #565 and family.py and scaffold-project.py: --dry-run asks the real run's own question about existing remotes, so family-remote-exists and scaffold-remote-exists come at the plan, and a missing gh is gh-not-found, not a traceback (#537) #573) is conflict-free, and the merge made from it was never pushed.

Final targeted run on the head 0b6228f, in two runs: 2005 passed, 22 skipped, 0 failed. Run A, every tests/test_setup*.py (this includes test_setup_by_hand_commands.py, now green), tests/test_family_init*.py, test_windows_paths, test_openreposhape_command, test_family_printed_quoting, test_cli_reference and test_repo_hygiene: 592 passed, 19 skipped. Run B, every tests/test_scaffold*.py, test_family, test_reuse_visibility, the five test_adopt_*.py files #581 touched and test_shape_doctor: 1413 passed, 3 skipped. The same two runs on the predicted merge with #565, #573 and #581 (bd0c6b5c, so tests/test_dry_run_asks_remotes.py and #573's two plan tests are in): 2053 passed, 22 skipped, 0 failed (A: 594 passed, 19 skipped; B, 20 files: 1459 passed, 3 skipped). render-cli-reference.py --check passes on both.

The new tests are shared helpers in tests/conftest.py, so the twin tests are not duplicated code (Sonar). Each helper has a one-line test in both tests/test_setup_project_py.py and tests/test_setup_sh.py, 14 per file:

• the closing cd (a run with a space in --into; the line is split with shlex and run in sh);
• the backstop, reached because the scaffold is given -- --work-dir <into>; its lines are moved aside, pasted into sh and finish the clone and the bootstrap;
• NEXT STEPS absent;
• a file above the clone path, ×2;
• -- --dry-run / --dry, with and without --yes, ×3;
• --pin, --pin= and --referent-chain reach step (4), ×3;
• OpenSoft and OPENSOFT, ×2;
• an OpenSoft/ origin.

There is also one scaffold test (the NEXT STEPS clone run in sh), plus 24 in-process tests: the passthrough readers, the drift guard on PASSED_FLAGS, what stands above a clone path, step (7)'s makedirs refusal, and one test with three cases that pins the Windows spelling of the changed paste lines. That one lives in tests/test_setup_project_py.py only. It switches os.name and SHELL_BARE for the calls, as shell_word reads them, and reads each printed line back with shlex.split, as Git Bash would. The existing backstop test is updated for the new lines, and test_what_stands_above_a_clone_path[a-link-to-nothing] compares with os.readlink(blocker), because on Windows os.readlink returns the \\?\ form.

Red on main: 51 of the 53 new tests and both updated ones fail on bfed143. The two that pass are controls: a link to a folder, and nothing on the path. The Windows-spelling test is red on bfed143 (finish_by_hand is not there) and on c71eadb (all three cases: PowerShell's spelling, cd C:\work\Sample and Jane O''Neill). Each failure is the defect itself: exit 1 tracebacks, exit 128 "WERE created", exit 0 scaffolding into OpenSoft, "project-leg / assembly" in step (4), and lines split at the space.

Mutants: 14 of 14 killed. One at a time, the change undid: the casefold, the --d prefix, the inner -- handling, the backstop's -c, the --no-next-steps that setup passes and the one the scaffold honours, the step (3) check above the clone path, isdir in that check, the last-chain rule, the quoted cd, the scaffold's -c, the makedirs refusal, the declarations reaching step (4), and the dry-run stop.

On 7baf16b, dropping posix=True from each of the three words in turn (cd <clone>, cd <parent>, <assembly>) fails the Windows-spelling test: 3 of 3 killed.

README follow-up

None required: README.md:338 and AGENTS.md:29-33 still say what the guard refuses. Optionally, README.md:338 could add "in any case" after --org opensoft.

The by-hand lines in README.md's "What setup.sh does" and the handbook's "What setup.sh actually runs" omit setup's --no-next-steps on purpose: by hand there is no step (7), so the scaffold's closing block (the git clone, the cd and make bootstrap) is the person's next work. tests/test_setup_by_hand_commands.py states the difference, so no word of either document needs to change. If a later README change wants to say it, one sentence under that list is enough.

Closes #538

🤖 Generated with Claude Code

Summary by Sourcery

Harden setup-project.py and scaffold-project.py for safe dry runs, reliable pasted commands, robust path handling, and consistent validation.

New Features:

• Add scaffold support for suppressing its closing NEXT STEPS block when invoked by setup-project.py.
• Make setup-project.py stop cleanly at the plan when a passed-through dry-run flag is detected.

Bug Fixes:

• Quote generated pasteable paths for POSIX shells, including Windows paths, and allow local recursive clones to use file-based remotes.
• Reject files blocking the clone path before creation and turn step-seven directory-creation failures into actionable refusals.
• Pass through pin and referent declarations to naming validation and make upstream-organization checks case-insensitive.

Documentation:

• Update the CLI reference for passed-through dry runs and the scaffold's new option.

Tests:

• Add shared end-to-end and unit coverage for command quoting, local clones, dry runs, path validation, naming declarations, and case-insensitive upstream guards.

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

[sourcery-ai]

Reviewer's Guide

Updates setup-project.py and scaffold-project.py to safely handle quoted paths and local recursive clones, correctly coordinate passthrough flags and dry runs, validate clone paths before side effects, and reject upstream organizations case-insensitively, with matching CLI documentation and extensive shared regression coverage.

Sequence diagram for setup dry-run and scaffold coordination

sequenceDiagram
    participant User
    participant Setup as setup-project.py
    participant Scaffold as scaffold-project.py
    participant FS as Filesystem
    User->>Setup: invoke with passthrough flags
    Setup->>Setup: naming_declarations(passthrough)
    Setup->>Scaffold: run plan with forwarded pins
    Scaffold-->>Setup: print plan
    alt --dry-run or accepted prefix passed through
        Setup->>Setup: passes_a_dry_run(passthrough)
        Setup-->>User: report plan only
    else confirmed run
        Setup->>Scaffold: run with --no-next-steps
        Scaffold->>FS: create repositories
        Setup->>FS: os.makedirs(parent)
        Setup-->>User: clone, bootstrap, and hand-over steps
    end

Loading

Sequence diagram for local recursive clone commands

sequenceDiagram
    participant Setup as setup-project.py
    participant Git
    participant Local as Local remote directory
    Setup->>Git: git -c protocol.file.allow=always clone --recurse-submodules assembly
    Git->>Local: read local recursive submodules
    Local-->>Git: provide leg repositories
    Git-->>Setup: create assembly working tree
    Setup-->>Setup: finish_by_hand(parent, assembly, project, local)

Loading

Flow diagram for clone-path validation before side effects

flowchart TD
    A[Resolve clone path] --> B{Clone path exists?}
    B -->|yes| C[refuse_a_taken_clone_path]
    B -->|no| D[nearest_entry of clone parent]
    D --> E{Nearest entry is a folder?}
    E -->|no| F[Refuse file or non-folder above clone]
    E -->|yes| G[Continue to plan]
    C --> H[Stop without creating repositories]
    F --> H
    G --> I[Confirm plan]
    I --> J[Create scaffold and clone repositories]

Loading

File-Level Changes

Change	Details	Files
Make setup-project's generated commands safe to paste and complete for paths with spaces and local file remotes.	Quote clone, cd, and parent paths with shell-aware formatting. Add Git's file-protocol override to recursive local clones. Centralize the step (7) manual recovery commands and improve the race/permission refusal path.	setup-project.py scaffold-project.py tests/conftest.py tests/test_scaffold_e2e.py tests/test_setup_project_py.py tests/test_setup_sh.py
Align setup orchestration with scaffold behavior so dry runs and NEXT STEPS do not perform or duplicate work.	Add scaffold-project's --no-next-steps option and pass it from setup while retaining the working-tree location output. Parse passthrough flags through an inner --, recognize accepted prefixes, and stop setup after the plan for dry runs. Pass pin products and the final referent chain into the step (4) naming validator.	setup-project.py scaffold-project.py docs/cli.md tests/conftest.py tests/test_setup_project_py.py tests/test_setup_sh.py
Strengthen clone-path validation and upstream-organization protection.	Reject files or non-directory symlinks above a prospective clone before any setup work. Casefold upstream organization comparisons across explicit and origin-derived values and preserve typed casing in refusals.	setup-project.py tests/conftest.py tests/test_setup_project_py.py tests/test_setup_sh.py
Add documentation and broad regression coverage for both setup entry points and scaffold execution.	Document passthrough dry-run semantics and the new scaffold option. Share helper-based tests across setup-project.py and setup.sh, including command pasteability, path blockers, dry-run stopping, passthrough declarations, and case-insensitive upstream guards. Add an end-to-end test for scaffold NEXT STEPS under local remotes and a drift check for accepted flag spellings.	docs/cli.md tests/conftest.py tests/test_scaffold_e2e.py tests/test_setup_project_py.py tests/test_setup_sh.py

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#538	Make setup's printed commands safe and accurate to paste: quote paths in the hand-over and step-(7) backstop, keep the scaffold's redundant NEXT STEPS out of setup runs, and allow the printed recursive clones to work with local remotes.	✅
#538	Correct setup's step checks: refuse a non-directory blocking the clone path before creating repositories, stop cleanly at the plan when scaffold passthrough requests a dry run, and include passed pins and referent-chain declarations in the step-(4) naming check.	✅
#538	Refuse the upstream organization regardless of letter casing, both when explicitly supplied and when identified from the origin.	✅

Possibly linked issues

• Tracking: setup, scaffold, family and the shared helpers, creating projects and families #459: Link: the PR fixes all six listed defects—quoting, NEXT STEPS, path checks, dry-run, pins, and case-insensitive upstream guard—and both rides-alongs.

---

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-2, 2026-10-14T23:39Z)

This lane reviewed its own PR #569 at c71eadb read-only, in its own detached worktrees, and authored nothing.

CHANGES NEEDED, for two small fixes. A fix round follows on this branch. The PR lands only on Brett Heap's word.

1. P3, fix here: the cd and backstop paths (setup-project.py:2377, :2176) go through shell_word, which quotes for PowerShell on Windows. Git Bash reads cd C:\work\Sample as C:workSample. Printed commands are POSIX-only: quote the bare paste lines in bump-leg.py and update-shape.py, and say in the docs that pasted commands are for a POSIX shell #532 rules POSIX-only, as this PR's scaffold line already is (scaffold-project.py:1553).
2. Nit, fix here: tests/test_setup_project_py.py:2016 compares the whole os.readlink target. On Windows that target carries a \\?\ prefix (see :1907).
3. Follow-ups for Tracking: setup, scaffold, family and the shared helpers, creating projects and families #459:
   • Step (4) is not given --pin-source as --link-source. A chain's status can differ from the plan's, but the classification agreed in all 12 probes.
   • Step (3) passes an unwritable parent.
   • --no is now ambiguous.

Probes:

• 45 of 45 paste lines ran in sh, bash and zsh -f.
• 39 --dry-run spellings agreed with argparse.
• The upstream guard refused OpenSoft in --org and in https, git@ and ssh:// origins.

Tests:

• c71eadb: 1034 passed, 19 skipped.
• Main with this PR's tests: 50 failed, 2 passed (the controls).
• Union merge with family.py and scaffold-project.py: --dry-run asks the real run's own question about existing remotes, so family-remote-exists and scaffold-remote-exists come at the plan, and a missing gh is gh-not-found, not a traceback (#537) #573: 320 passed.

Merges are clean with main, #565, #570, #561 and #554. #573 conflicts only by adjacent additions to three test files, which a union resolves. docs/cli.md re-renders clean on every merge.

Report: opensoft/brett-wip handoffs/xFactory/attachments/lane-openRepoShape-2/review569-c71eadb/final-report.md.

[brettheap]

(lane openRepoShape-2, 2026-10-15T10:56Z)

This lane re-verified its own PR #569 at 7baf16b read-only and authored nothing.

MERGEABLE WITH NITS on bfed143. CHANGES NEEDED when main 2247dbf is merged in.

• Item 1 is done. On a simulated Windows host, all 20 changed lines read right in sh, bash and zsh -f, against 8 wrong at c71eadb. family_next_command is unchanged.
• Item 2 is done. tests-windows at c71eadb was cancelled by the push, so the old failure is unproven.
• The merge with 2247dbf is clean, but tests: every test that clones a just-pushed local remote by its plain path now clones it with clone_just_pushed, so the macOS failed to copy file race of #440 cannot reach it; load_without_bytecode keeps the doctor's and the Windows-path tests' loads of the family root's scripts from writing .pyc into the templates; the not-a-list doctor cases hold INVALID, exit 1; and GOOD_KEYS holds th #554 rewrote tests/test_scaffold_e2e.py:15 without FILE_PROTOCOL. test_the_next_steps_clone_under_local_remotes_reads_the_legs still uses it at merged line 278 and fails with NameError: 351 passed, 1 failed. The merge commit must keep tests: every test that clones a just-pushed local remote by its plain path now clones it with clone_just_pushed, so the macOS failed to copy file race of #440 cannot reach it; load_without_bytecode keeps the doctor's and the Windows-path tests' loads of the family root's scripts from writing .pyc into the templates; the not-a-list doctor cases hold INVALID, exit 1; and GOOD_KEYS holds th #554's line and import FILE_PROTOCOL again, at line 19.
• No new test needs clone_just_pushed. read_through_git already reads through git.

Report: opensoft/brett-wip handoffs/xFactory/attachments/lane-openRepoShape-2/review569-c71eadb/reverify-7baf16b.md.

[brettheap]

(lane openRepoShape-2, 2026-10-15T16:14:10Z)

This lane re-verified its own PR #569 at 0b6228f, read-only in its own detached worktrees, and authored nothing.

MERGEABLE WITH NITS. Land it after #573. No nit needs a commit.

• The merge commit 5e9e3a4 has the same tree as git merge-tree of its parents (628171fb).
• In df67b46, tests/test_setup_by_hand_commands.py:127-130 holds the real run to exactly the plan's arguments plus one final --no-next-steps. The README and handbook lines are still compared argument by argument. Eight one-at-a-time mutants of setup-project.py were all killed, and main's copy of the test fails 3 on this head. Step (7) does run the closing block's clone and bootstrap (setup-project.py:2271-2290).
• README and the handbook need no more than the follow-up line. The flag changes only what is printed, and docs/cli.md:349 already says that setup passes it.
• 0b6228f is a pure move. In each file, the lines, the top-level statements with their exact source, and the names are equal as multisets. Nothing evaluates a name at import time before that name is bound.
• Nits, wording only:
  • the PR body says "failed on today's main" where it means the merge with main;
  • its heading "(after docs/handbook.html: stop every README PR rewriting the handbook's README blob and line cap, so open README PRs stop conflicting with each other #519)" is stale;
  • 5e9e3a4's body calls its tree the predicted adopt-project.py: check finds, and execute refuses before any leg exists, a path the root keeps at the shape's own pin and a --work-dir this user cannot write in, so contracts/shape-pin.yaml kept in the root and a chmod 500 work directory no longer pass check and fail only after both legs are pushed (#524) #581 step's, when it is fb786c1's tree that equals that step's.

Tests on 0b6228f: 362 passed, 0 failed (test_setup*, test_scaffold_e2e, test_cli_reference, test_repo_hygiene). On the predicted final merge 103b64d6, a spot check passed 84.

Merges from 0b6228f are all clean:

• with the predicted main bd0c6b5c: tree 74829523;
• with origin/main 26c1600: tree 9c5031e8;
• with family.py and scaffold-project.py: --dry-run asks the real run's own question about existing remotes, so family-remote-exists and scaffold-remote-exists come at the plan, and a missing gh is gh-not-found, not a traceback (#537) #573's head c6b32d7: tree 74829523, because c6b32d7's tree equals bd0c6b5c's.

The head before the move conflicted in the three moved files. pyflakes finds no new message on any merge.

The report is at handoffs/xFactory/attachments/lane-openRepoShape-2/review569-0b6228f/final-report.md in opensoft/brett-wip.

The coordinator has since edited the PR body for the first two nits: "on this PR's merge with today's main", and the heading is now "README follow-up". Nothing was pushed.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
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