Skip to content

family.py: the by-hand checkout line a failed rollback prints names a branch that is not UTF-8 by its exact bytes, as "$(printf 'caf\351')", not as 'caf\udce9', which typed names no branch (#1079) - #1084

Merged
brettheap merged 2 commits into
mainfrom
l3-1079-by-hand-branch-bytes
Oct 21, 2026

Conversation

@brettheap

@brettheap brettheap commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

What a person now sees

When a bump or remove rollback cannot check a member out, it prints the line to type from _head_by_hand in scripts/family.py. For a member whose branch is not UTF-8 (read from git with surrogateescape) the line was

git -C members/Thing checkout -q 'caf\udce9' --

The stdout stream writes the surrogate as those six characters, and typed they name no branch: git answers fatal: invalid reference: caf\udce9 (reproduced by the new tests on the unfixed code). It is now

git -C members/Thing checkout -q "$(printf 'caf\351')" --

and git is put back on refs/heads/caf\xe9, read as bytes, in sh, dash, bash and (review round) zsh.

The change, scripts/family.py

  • New _branch_by_hand(branch) (line 7753): a name that is UTF-8 text keeps shlex.quote, byte for byte. A name that holds a surrogate escape is spelled "$(printf '<escapes>')". Each byte that is not printable ASCII (below 0x20, DEL, above 0x7E) is a three-digit octal escape, e.g. \351. Each printable ASCII byte passes through, except ', \, % and (review round) !, which are escaped as \047, \134, \045 and \041 too. So the printf format reproduces the exact bytes in any POSIX shell, and the line is pure ASCII whatever stream prints it.
  • _head_by_hand (line 7781) calls it where it called shlex.quote(branch) (line 7787). Nothing else in the file changed. _head_by_hand uses shlex.quote (POSIX), not the host quoter shell_quoted, so tests/test_readme_windows_quoting_sentence.py is not involved (it passes unchanged).

Where the issue left it open, these are decided as lane 3 ruled:

  • All three special bytes are spelled in octal, not %% and \\, so one rule covers every byte and a ' never ends the quotation.
  • $(...) strips trailing newlines, which loses nothing: a ref name cannot hold a newline.
  • The issue's other option (say the name is not UTF-8 and give the commit) was not taken.

Tests, tests/test_family_head_by_hand_bytes.py (new, 45 rows at first, 61 after the review round)

  • A real repository with a branch named by the bytes caf\xe9, a second branch checked out, the printed line (as the stream writes it, backslashreplace) run through sh -c, then git symbolic-ref HEAD read as bytes must be refs/heads/caf\xe9. A second row has a name full of syntax git does hold (', %s, %d, ", $HOME, backticks, braces, ;&|<>()!#) beside a non-UTF-8 byte.
  • A row for a name holding ', \ and % beside a non-UTF-8 byte, and a row of every byte 1 to 255: printf %s <word> in sh, dash, bash and zsh writes the name's exact bytes (git cannot hold \ or a control byte, so the word is asked for itself).
  • The exact text for the issue's branch, the word is ASCII, never holds udce9, every byte the format or its quotes would read is an octal escape, and DEL, newline and 0xFF are escapes.
  • UTF-8 names (including ', %, \, a space, $HOME, and e-acute and CJK text) give shlex.quote's word and the unchanged line; no branch still prints the commit; the path is still shlex.quoted.
  • On main _member_head still raises on a branch that is not UTF-8, so _head_by_hand is tested directly, not the rollback end to end. tests/test_family_member_branch_not_utf8.py is not touched: it exists only on the adopt-project.py and family.py: a source this user cannot enter is source-unreadable, a UTF-8 plan reads its source under the C locale, and a member on a branch that is not UTF-8 is put back on it (#918) #1072 branch.
  • Shell-running rows are skipped on Windows (WINDOWS_SKIP); dash, bash and zsh rows skip where absent.

Left out of scope

Test commands (stub gh first on PATH, GH_TOKEN=bogus, empty GH_CONFIG_DIR, EMAIL set, one file at a time)

  • pytest tests/test_family_head_by_hand_bytes.py: 45 passed in 1.04s
  • pytest tests/test_family_bump_remove_rollback.py: 31 passed in 34.20s
  • pytest tests/test_family_py_unreadable.py: 75 passed in 36.10s
  • pytest tests/test_readme_windows_quoting_sentence.py: 44 passed in 16.58s
  • pytest tests/test_repo_hygiene.py: 100 passed in 2.49s
  • pytest tests/test_no_auto_maintenance.py: 60 passed in 11.43s
  • python3 -m pyflakes scripts/family.py tests/test_family_head_by_hand_bytes.py: no output; the same on scripts/family.py at origin/main.

Mutants (family.py restored after each and checked with cmp)

  1. shlex.quote(branch) back for every name in _head_by_hand: KILLED, 8 failed. The real-repository rows fail with fatal: invalid reference: caf\udce9; test_the_line_for_the_issues_branch_is_spelled_exactly and test_a_name_that_is_not_utf8_never_prints_the_surrogate fail too.
  2. The % escape dropped (not in "'\\"): KILLED, 16 failed: the apostrophe-percent-and-more real-repository rows, test_each_byte_the_format_or_its_quotes_would_read_is_an_octal_escape, and test_the_shell_hands_git_the_exact_bytes rows apostrophe-percent-and-more, apostrophe-backslash-percent, percent-conversions and every-byte, each in all three shells.
  3. The ' escape dropped: KILLED, 13 failed.
  4. The \ escape dropped: KILLED, 4 failed: test_each_byte_the_format_or_its_quotes_would_read_is_an_octal_escape and the apostrophe-backslash-percent row in each shell (a name holding \n, \t, \x41 and \0, which printf would read as escapes).
  5. DEL passed through (byte <= 0x7f): KILLED, 1 failed, test_the_word_holds_printable_ascii_only_whatever_the_bytes (it survived the shell rows, which is why that test exists).
  6. The UTF-8 branch removed (every name in the printf form): KILLED, 43 failed.

Merges (git merge-tree --write-tree, head 1bae5e1656bfa2cd542f4ed2ef5b9fa24558ca84, cut from origin/main bccae28052f8aa786ba3907d6aabd880cc29062d)

After the rebase onto bccae2805 (tests only, no overlap) the new file and tests/test_repo_hygiene.py were run again: 45 passed and 100 passed. The other four files were run on the first base, 5e539a878, and scripts/family.py is byte-identical on both.

Review round (RV1084, issuecomment-6303644023; head 6ab9d3263dffe3e2cc19270c28117ac90da81d6f, one commit on top, pushed as a fast-forward)

Follow-up

Closes #1079

Lane: openreposhape-3 (openRepoShape-3)

🤖 Generated with Claude Code

Summary by Sourcery

Make failed rollback checkout instructions reproduce non-UTF-8 branch names correctly when typed in a POSIX shell.

Bug Fixes:

  • Preserve the exact byte representation of non-UTF-8 branch names in the POSIX shell command printed for failed rollbacks.

Enhancements:

  • Retain the existing quoting behavior for UTF-8 branch names while safely rendering arbitrary branch bytes as printable shell input.

Tests:

  • Add comprehensive coverage for non-UTF-8, shell-sensitive, arbitrary-byte, UTF-8, and unchanged rollback command cases across supported POSIX shells.

… branch that is not UTF-8 by its exact bytes, as `"$(printf 'caf\351')"`, not as `'caf\udce9'`, which typed names no branch (#1079)

`_head_by_hand` quoted the branch with `shlex.quote`. A name read from git
with `surrogateescape` that holds a byte which is not UTF-8 came out as the
surrogate, which the stdout stream writes as the six characters `\udce9`, and
typed they name a branch that is not there: git refuses them as an invalid
reference.

`_branch_by_hand` spells such a name `"$(printf '<escapes>')"`: each byte that
is not printable ASCII is a three-digit octal escape, and so are `'`, `\` and
`%`, so any POSIX shell hands git the exact bytes. A UTF-8 name keeps
`shlex.quote`, byte for byte. `tests/test_family_head_by_hand_bytes.py` runs
the printed line through `sh`, `dash` and `bash` in a repository that holds the
branch `caf\xe9`.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@brettheap brettheap added this to the v1.2.0 milestone Oct 20, 2026
@sourcery-ai

sourcery-ai Bot commented Oct 20, 2026

Copy link
Copy Markdown

Reviewer's Guide

The PR fixes rollback instructions for branches containing non-UTF-8 bytes by rendering those names as ASCII-only POSIX shell commands that reconstruct the original bytes with printf, while preserving existing UTF-8 quoting and adding broad shell-level regression tests.

Sequence diagram for byte-preserving rollback checkout instructions

sequenceDiagram
    participant Rollback as Rollback flow
    participant Family as scripts/family.py
    participant Shell as POSIX shell
    participant Git as git

    Rollback->>Family: _head_by_hand(path, at, branch)
    Family->>Family: _branch_by_hand(branch)
    alt branch is valid UTF-8
        Family-->>Rollback: shlex.quote(branch)
    else branch contains surrogateescaped bytes
        Family-->>Rollback: "$(printf '<octal escapes>')"
    end
    Rollback->>Shell: Execute checkout instruction
    Shell->>Shell: printf reconstructs exact branch bytes
    Shell->>Git: checkout -q <branch bytes> --
    Git-->>Shell: checkout branch
Loading

Flow diagram for branch spelling in _head_by_hand

flowchart TD
    A[_head_by_hand receives branch] --> B{branch.encode utf-8 succeeds?}
    B -->|Yes| C[shlex.quote branch]
    B -->|No| D[Encode with surrogateescape]
    D --> E[Keep printable ASCII except apostrophe backslash percent]
    E --> F[Render all other bytes as three-digit octal escapes]
    F --> G[Wrap as printf command substitution]
    C --> H[Build git checkout instruction]
    G --> H
    H --> I[ASCII-safe instruction reconstructs exact branch bytes in POSIX shell]
Loading

File-Level Changes

Change Details Files
Add byte-preserving POSIX-shell formatting for non-UTF-8 branch names in manually printed checkout commands.
  • Detect surrogateescaped branch names by attempting UTF-8 encoding.
  • Encode non-printable bytes and shell/printf-sensitive characters as three-digit octal escapes inside a $(printf ...) substitution.
  • Keep UTF-8 branch names on the existing shlex.quote path and leave commit and path handling unchanged.
scripts/family.py
Add comprehensive regression coverage for exact branch-byte preservation and unchanged quoting behavior.
  • Test generated commands against real repositories and sh, dash, and bash, including names containing non-UTF-8 bytes and shell/printf syntax.
  • Verify ASCII-only output, exact issue spelling, octal escaping, arbitrary byte handling, and preservation of UTF-8, no-branch, and path behavior.
  • Skip shell-dependent cases on unsupported platforms or when shells are unavailable.
tests/test_family_head_by_hand_bytes.py

Assessment against linked issues

Issue Objective Addressed Explanation
#1079 Ensure the rollback’s by-hand checkout command represents a branch name containing non-UTF-8 bytes in a form a person can type that causes the shell and Git to receive the original branch bytes. ✅

Possibly linked issues


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

@brettheap

Copy link
Copy Markdown
Contributor Author

(lane openRepoShape-3, 2026-10-20T22:57:11Z) Independent review (RV1084) of 1bae5e1: READY. No MUST.

Probe: 453 real branches (every byte value git holds in a ref name, as x<b>\xe9 and x<b>y, plus 23 odd names such as caf\xe91, a)b\xe9, $(id)\xe9, ODD_REF, %b\xe9, !x\xe9, 0x80-0xFF) made in a real repository; the _head_by_hand line, written with backslashreplace, run with <sh> -c in sh, dash 0.5.12, bash 5.2.21 and zsh 5.9; HEAD read back as bytes. 453/453 in each shell, under LC_ALL unset, C and C.UTF-8. The 87 UTF-8 names print exactly as origin/main's line. Interactive bash and zsh do not history-expand a ! inside the printf word (a double-quoted control did expand).

Tests (one at a time, stub gh): test_family_head_by_hand_bytes.py 45 passed; test_family_bump_remove_rollback.py 31 passed; test_readme_windows_quoting_sentence.py 44 passed. pyflakes clean.
Mutants: 1 (shlex.quote back) KILLED 8; 2 (% escape dropped) KILLED 16; 5 (DEL passed through) KILLED 1; extra (outer double quotes dropped) KILLED 3 by the every-byte shell rows. family.py restored and checked with cmp each time.
Merges (merge-tree): origin/main c13c398 clean (bootstrap.py only; family.py and the new test are the same blobs); #1072 2ffd823 clean, and the new file passes on that merge (45 passed); #1073 b58a4e2 clean. On the #1072 merge, _member_head reads caf\xe9 as 'caf\udce9' and the printed line puts HEAD back in dash, bash and zsh.

SHOULD:

  1. tests/test_family_head_by_hand_bytes.py:40: add "zsh" to SHELLS (macOS's default shell; the suite already drives zsh; all 453 probe names pass in zsh; shell_or_skip covers its absence).
  2. tests/test_family_head_by_hand_bytes.py:245: test_the_module_reads_a_name_as_this_test_does never calls the module; no change to family.py can fail it. Rename it to what it checks (Python's surrogateescape decode) or make it call _member_head once adopt-project.py and family.py: a source this user cannot enter is source-unreadable, a UTF-8 plan reads its source under the C locale, and a member on a branch that is not UTF-8 is put back on it (#918) #1072 lands.

NIT:

  1. scripts/family.py:7774: escaping ! as \041 would make the line independent of each shell's history scanner. Optional; no fault found.
  2. The commit trailer names Sonnet 5.5; set the attribution you want in the squash message.

Follow-up, not this PR: a leg path read with surrogateescape (family.py:7991) reaches shlex.quote at 8277, 8279 and, through _head_by_hand, 7787. The printf form cannot be reused as is: $(...) strips a trailing newline, which a path can hold, and dash has no $'...'. Draft title: "family.py: a failed bump's by-hand lines quote a leg mounted at a path that is not UTF-8 as Python's \udcXX, so the typed git -C <member>/<leg> and submodule update -- <leg> name no path".

PR body: closingIssuesReferences is [1079]; it ends Closes #1079, the Lane line and the robot line, then Sourcery's appended summary (as on #1071), which has no closing keyword; nothing above U+007F but the robot.

Lane 3: a fix round (F1084) takes SHOULD-1, SHOULD-2 and NIT-1 (! as \041), then a delta review. The leg-path case is filed as a follow-up issue, outside this PR.

Lane: openreposhape-3 (openRepoShape-3)

… `\041` too, so a line for a branch that is not UTF-8 never depends on a shell's history scanner, and its test also drives zsh (#1079)

Review round on #1084 (RV1084, issuecomment-6303644023).

`_branch_by_hand` now escapes `!` with `'`, `\` and `%`: only a name that is
not UTF-8 uses the printf word, so a UTF-8 name is `shlex.quote`d as before.
`tests/test_family_head_by_hand_bytes.py`:
- SHELLS gains zsh (macOS's default); `shell_or_skip` still skips a shell that
  is not installed, and its rows run here;
- a `!` row for the shell, an exact-text row for the word and a UTF-8 name
  with `!`;
- the test that never called the module is named for what it checks, Python's
  `surrogateescape` decode, and says the module's own read is #1072's
  `_member_head`.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@brettheap

Copy link
Copy Markdown
Contributor Author

(lane openRepoShape-3, 2026-10-20T23:08:32Z) Independent delta review (RV1084d) of the fix round, 1bae5e1..6ab9d32 (one commit, 2 files, +42/-14): READY. No MUST, no SHOULD.

SHOULD-1: SHELLS now holds zsh (tests/test_family_head_by_hand_bytes.py:42). With -v -rs: 61 passed, 0 skipped; all 10 zsh rows ran and passed (2 real-repository rows, 8 shell-bytes rows including bang-zsh).
SHOULD-2: the test is now test_surrogateescape_reads_the_issues_branch_as_caf_and_u_dce9 (:268) and its docstring is true. Checked: at this head _member_head on a real repository sitting on caf\xe9 raises UnicodeDecodeError, as the docstring says.
NIT-1: scripts/family.py:7775 escapes ! as \041; !x!\xe9 prints as "$(printf '\041x\041\351')". UTF-8 names are still shlex.quote's word and line byte for byte (9 of 9, including fix!ec, cafe-acute!, !x, a!b!!c).
Mutant, ! passed through again ("'\%"): KILLED, 1 failed (test_the_bang_is_an_octal_escape_so_no_history_scanner_reads_the_line). family.py restored and checked with cmp; tree clean.

Tests at 6ab9d32 (one file at a time, stub gh exit 97, GH_TOKEN=bogus, empty GH_CONFIG_DIR, GIT_SSH_COMMAND=false, EMAIL set): test_family_head_by_hand_bytes.py 61 passed, 0 skipped; test_family_bump_remove_rollback.py 31 passed. pyflakes clean.
Merges (merge-tree, fresh fetch): origin/main c13c398 clean (fec87ddf); #1072 2ffd823 clean (0f8f4e07); #1073 b58a4e2 clean (a35b505f).
Body: closingIssuesReferences is [1079]; it ends Closes #1079, the Lane line and the robot line; no other closing keyword anywhere; #1086 appears only under Follow-up; nothing above U+007F but the robot.

NIT (optional, body only): the Tests section's second and fifth bullets still say "in sh, dash and bash" and "dash and bash rows skip where absent"; adding zsh would match the Review round section. The round-1 trailer NIT stands: set the attribution you want in the squash message.

Lane 3: the body NIT is fixed now (zsh in both Tests bullets). #1084 lands at 6ab9d32 through its pilot, chained after #1072 and #1073, one HOLD at a time.

Lane: openreposhape-3 (openRepoShape-3)

@brettheap
brettheap marked this pull request as ready for review October 21, 2026 00:33
@sourcery-ai

sourcery-ai Bot commented Oct 21, 2026

Copy link
Copy Markdown

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

@brettheap
brettheap merged commit 680eb4a into main Oct 21, 2026
5 checks passed
@brettheap
brettheap deleted the l3-1079-by-hand-branch-bytes branch October 21, 2026 00:33
brettheap added a commit that referenced this pull request Oct 21, 2026
… fetch that carry it run in bootstrap.py's `untraced()` environment, so `make siblings` and `family.py siblings` write the token to no trace the caller asks git for (#1055) (#1075)

`make siblings` and `family.py siblings` now write the token in `SHAPE_LEGS_TOKEN` or `SHAPE_LEGS_APP_TOKEN` to no trace the caller asked git for. #996 (#1045) did the same for `make bootstrap`.

Lane 5 found this in its independent review of #1045 (rv996, #1045 issuecomment-6288783192) and measured it in #1055.

`templates/family-root/scripts/siblings.py` gives the credential's `-c url.https://x-access-token:<token>@github.com/.insteadOf=...` rewrite, in argv, to two gits:
- the clone in `place`, for a member with no clone beside the holder;
- the fetch in `place`, for a member whose clone is there.

Both ran in the caller's own environment. So every trace2 target the caller named wrote the token in the `start` event of each, one line per member. `scrub` kept it out of the output, and only that part held.

Now:
- **`rewrite_environment(token)`**, a new function in `siblings.py`:
  - with a token in use, it returns `untraced()` from the `bootstrap.py` beside it. That is every `GIT_TRACE*` variable taken out, and `GIT_TRACE2`, `GIT_TRACE2_EVENT` and `GIT_TRACE2_PERF` set to `0`, which also turns off a target the global or the system config names;
  - with no token, it returns None, so the two gits keep the caller's environment and stay traced where the caller asked, as before.
- **The clone and the fetch** each run with `env=rewrite_environment(token)`. Nothing else in the file changes environment.
- **The member's own `scripts/bootstrap.py`**, which `place` runs after a clone, is given no token in its argv, and no `env`, so it keeps the caller's environment and its traces. That environment holds `SHAPE_LEGS_TOKEN` and `SHAPE_LEGS_APP_TOKEN` as before; the shipped member bootstrap (`templates/assembly-root/scripts/bootstrap.py`) reads neither. A test row holds this, and so does `tests/test_validator_child_encoding.py`, which reads that call as handing no `env`.
- **#1023's jobserver handling is untouched**: `dispatch` still runs each member's make with `member_make_environment(make)`, and no `MAKEFLAGS` reading changed.
- **The docstrings** now say the promise in full: `git_prefix` says the token is "never written into `.git/config`, never persisted, never printed, and never traced". `place`'s ABSENT paragraph in the module docstring says the same, and `rewrite_environment` says what was measured.

**One thing the issue did not ask for.** `GIT_TRACE_PERFORMANCE` writes a git's whole command line, `-c` included, on git 2.43.0 and 2.47.1 alike. So at main it held the token too, two lines per run, and the rows below set it. `untraced()` already takes it out: every `GIT_TRACE*` variable goes.

This follows #1045's `untraced()` (#996): the clone and the fetch run in the very environment `make bootstrap` gives every git it hands the token.

`siblings.py` imports `untraced` from the `bootstrap.py` beside it, next to `REWRITE_TARGETS`, `credential`, `member_make_environment`, `member_path` and `members_of`.

The issue left this to the writer, because a holder may keep a `bootstrap.py` older than its `siblings.py` (`update-shape.py apply --accept-local`), and an import of a name that copy lacks would stop `make siblings`, `park` and `resume` with an `ImportError`. The issue's text was written against main `1a47ed07`, where `siblings.py` still kept its own copy of the `MAKEFLAGS` readings. Since then #1023 (`9e154d87`, lane 4's) has decided the question for this pair of files:
- it replaced that copy with an import of `member_make_environment`, because a copy in each script failed SonarCloud's duplication gate;
- it named the price, in the import's comment and its commit: a holder that keeps its own `bootstrap.py` while `apply` writes `siblings.py` is refused, `update-accept-local-missing-name` (#536, #604), before a byte is written, and merges `bootstrap.py` by hand first.

`untraced` takes the same road for the same reasons:
- **One rule.** Which traces a command carrying the token is kept out of has one answer, for `make bootstrap` and `make siblings` alike. A copy here could drift from `bootstrap.py`'s, and the drift would be a token in a file.
- **A kept old `bootstrap.py` is refused in the one-step case, and not in a two-step one.** The guard reads names. `untraced` is new with #996 (#1045), so a kept `bootstrap.py` from before it is refused by that name, where `--accept-local` names it in the same `apply`. Measured with `update-shape.py`'s own readers, in process:
  - `siblings.py` at this head takes `REWRITE_TARGETS`, `credential`, `member_make_environment`, `member_path`, `members_of` and `untraced` from `bootstrap`;
  - the holder's `bootstrap.py` at main `00f6d7f7` lacks none of them;
  - the holder's `bootstrap.py` at `6476c170` (main just before #1045) lacks `untraced` alone, which is the line the refusal names.
- **The one-step case, measured end to end (rv1075).** A holder cut at `6476c170`, and `apply --at c3cf515 --accept-local scripts/bootstrap.py`: exit 2, `scripts/bootstrap.py (kept) lacks untraced, which scripts/siblings.py imports from it`, and the holder's files, HEAD and status unchanged.
- **Two applies in a row are not refused (rv1075's SHOULD 1, filed as #1082).** A holder whose earlier apply kept a `bootstrap.py` without `untraced` (rv1075 applied `--at 00f6d7f --accept-local scripts/bootstrap.py`: that target's `siblings.py` imports no `untraced`, so there was nothing to refuse), and then an apply at this head without `--accept-local`, gets `siblings.py` copied. `scripts/siblings.py` then fails with `ImportError: cannot import name 'untraced' from 'bootstrap'`, and so do `make siblings`, `park` and `resume`. The cause is the guard in `update-shape.py` (`:4288-4289`): it checks only the files `--accept-local` names in the same run. That is the gap of #536's guard, and it is on main already for #1023's `member_make_environment`; this change puts `untraced` into it and does not widen it. The text above this paragraph said no `ImportError` could reach a holder, which was too strong; #1082 is the follow-up, and it is not done here.
- **No copy, so no test to hold two copies to one answer.** `tests/test_update_shape_kept_helper.py`'s `test_what_siblings_takes_from_the_holders_bootstrap_is_found_defined` already holds that every name `siblings.py` takes is defined in the holder's `bootstrap.py`. Its docstring now says six names, not five.

**Setup:**
- git 2.43.0 (`/usr/bin/git`) and git 2.47.1, Python 3.12.3;
- the family of `tests/test_family.py` (two members, local bare remotes, the file transport allowed through `GIT_CONFIG_COUNT`), laid out as `<tmp>/InkRouter/InkRouter`;
- offline: a stub `gh` first on PATH, a bogus `GH_TOKEN`, an empty `GH_CONFIG_DIR`, `GIT_SSH_COMMAND=false`;
- the holder's own `scripts/siblings.py` was main's (sha256 `86bf57e0...`) or this change's;
- the fake token `w1055-a-token-no-forge-takes`.

**Each case was run three ways:**
- `make siblings`, which clones both members;
- `make siblings` again, which fetches both;
- `family.py siblings --family-root <holder>` in a fresh layout, which clones both.

**Traces were asked for in one of three ways:**
- the seven variables `GIT_TRACE`, `GIT_TRACE2`, `GIT_TRACE2_EVENT`, `GIT_TRACE2_PERF`, `GIT_TRACE_PACKET`, `GIT_TRACE_CURL` and `GIT_TRACE_PERFORMANCE`, each set to a file under the run's TMPDIR;
- `trace2.eventTarget`, `normalTarget` and `perfTarget` in a scratch `GIT_CONFIG_GLOBAL`;
- the same three in a scratch `GIT_CONFIG_SYSTEM`.

Each way was run with `SHAPE_LEGS_TOKEN`, with `SHAPE_LEGS_APP_TOKEN`, and with no token.

That is 108 runs at main and at the change, 54 for each git. Each run's TMPDIR and the whole family folder (the clones' `.git/config` included) were searched for the token.

| traces asked by | main, a token set (both variables, both gits) | this change, a token set | no token, either |
|---|---|---|---|
| the seven variables | `trace2-event.json`, `trace2-normal.txt`, `trace2-perf.txt`, `trace-performance.txt`: 2 lines each, in the clone, the fetch and `family.py` alike | none | no token anywhere; the same files written |
| the global config | `cfg-event.json`, `cfg-normal.txt`, `cfg-perf.txt`: 2 lines each | none | the same |
| the system config | `sys-event.json`, `sys-normal.txt`, `sys-perf.txt`: 2 lines each | none | the same |

**What the table rests on:**
- Every one of the 108 runs (and the 54 runs again on this head's final bytes, sha256 `b1e7bb21...`) exited 0 and ended `siblings ok: 2 member(s) beside the holder in ...`, with the token in neither stdout nor stderr.
- The 2 lines in each file are the `start` (or `performance:`) line of the git given the `-c`, one for each member. Each carries the token twice, once for each spelling the rewrite covers.
- With every member a local path, `GIT_TRACE`'s file was written and held no token, and `GIT_TRACE_CURL` wrote nothing, with no http remote. An https member is a different case, measured below.
- With the change and a token set:
  - every trace file but `GIT_TRACE_PACKET`'s was still written, by the run's other gits and the member's own bootstrap;
  - the packet trace was not written, since only the clone and the fetch write one here.

**An https remote, measured offline (rv1075, then the row of Round 2).** The rewrite reaches only `github.com`, and the probes above are offline, with local paths. A member whose `.gitmodules` url is `https://github.com/<org>/<repo>.git` is reached by it, and can be tried offline behind a dead proxy, `http.proxy=http://127.0.0.1:9`, so that nothing leaves the host:
- rv1075 set one member's url so, with `make siblings`, a fake `SHAPE_LEGS_TOKEN`, and the seven variables set to files, on git 2.43.0 and 2.47.1. Main's `siblings.py` (`86bf57e0`) held the token in `trace.txt`, `trace2-event.json`, `trace2-normal.txt`, `trace2-perf.txt` and `trace-performance.txt`; this head held it in no file and no output. The clone failed cleanly, `git clone exited 128`, and `make siblings` exited 2.
- `GIT_TRACE`'s file holds it too, in the `run_command: git remote-https origin https://x-access-token:<token>@github.com/...` lines: 3 lines on git 2.43.0, 4 on 2.47.1 (rv1075).
- Round 2 below holds this in a test row.

**Still not measured:** a github.com clone or fetch that succeeds, since no run here reaches the network.

`tests/test_family_siblings_untraced.py` is new. It uses `tests/test_family.py`'s `family` and `estate`, `offline` from `tests/test_family_add_refusals.py`, `files_holding` and `CREDENTIALS` from `tests/test_family_bootstrap_stops_named.py`, and `NO_CREDENTIAL` and `needs_make` from `tests/test_siblings_family_name.py`. No assert joins conditions with `and`. The token is the fake `w1055-a-token-no-forge-takes`.

**The rows.** Each entry point is crossed with each way traces are asked for:
- entry points: `make siblings` cloning, `make siblings` again fetching (after a first run with no token and no trace), and `family.py siblings` cloning;
- ways: the seven variables, the three targets in a scratch global config (a copy of the session's, which keeps git's automatic maintenance off), and the three targets in a scratch system config.

**Three tests** (the third is round 2's):
- **`test_with_a_token_in_use_the_token_is_in_no_trace`**: 18 rows (3 entries x 3 ways x 2 variables). Each asserts:
  - exit 0 and `siblings ok: 2 member(s) ...`;
  - the token in neither stdout nor stderr;
  - the token in no file under the test's directory: TMPDIR, every trace and config file, and the clones and their `.git/config`;
  - every trace file the way asks for written: 5 for the variables, 3 for each config;
  - the member's own bootstrap traced where a member was cloned: a git traced in a leg of each clone, which only that bootstrap runs. Where nothing was cloned, nothing ran there.
- **`test_with_no_token_the_clone_and_the_fetch_are_traced_as_asked`**: 9 controls (3 entries x 3 ways). Each asserts exit 0, `siblings ok` and the same trace files written. It also asserts the trace2 event file holds `siblings.py`'s own git at each member, read from the events: `git clone -q --no-local ...` to each member's slot, or `git fetch --quiet origin` in each member's clone.

**Fails on main.** The file was run against main's `siblings.py` (sha256 `86bf57e0...`, put in place and then restored, sha256 checked):
- **18 failed, 9 passed**: every row with a token failed, and the 9 controls passed;
- the variables rows found the token in `trace-performance.txt`, `trace2-event.json`, `trace2-normal.txt` and `trace2-perf.txt`;
- the global-config rows found it in `cfg-event.json`, `cfg-normal.txt` and `cfg-perf.txt`;
- the system-config rows found it in `sys-event.json`, `sys-normal.txt` and `sys-perf.txt`.

- **`test_an_https_member_with_a_token_in_use_is_in_no_trace`**: 3 rows, one for each of `CALLERS_CONFIG` (round 2 and round 3, below).

Each mutant was applied alone to the worktree's file and the new test file run (git 2.43.0). The bytes were restored and checked by sha256 after each:
- `siblings.py` sha256 `b776c69b...`: this head's code; it differs from the head only in two docstring lines;
- `bootstrap.py` sha256 `50a16751...`, main's, unchanged here.

All are **killed**.

| mutant | result |
|---|---|
| M1 the token condition dropped: `untraced()`'s environment always | killed, 9 failed (every control) |
| M1b the condition inverted | killed, 27 failed |
| M1c the clone untraced always, the fetch as it is | killed, 6 failed (the clone controls) |
| M2 the clone left in the caller's environment | killed, 12 failed (every clone row with a token) |
| M3 the fetch left in the caller's environment | killed, 6 failed (every fetch row with a token) |
| M4a `GIT_TRACE2_EVENT` not set to `0` (`TRACE2_OFF`) | killed, 12 failed (the global- and system-config rows) |
| M4b `GIT_TRACE2` not set to `0` | killed, 12 failed (the same) |
| M4c `GIT_TRACE2_PERF` not set to `0` | killed, 12 failed (the same) |
| M5 the `GIT_TRACE*` removal dropped (`env = dict(os.environ)`) | killed, 6 failed (the variables rows, by `GIT_TRACE_PERFORMANCE`) |
| M6 the prefix narrowed to `GIT_TRACE2` | killed, 6 failed (the same) |
| M7 the member's own bootstrap run untraced too | killed, 12 failed (the clone rows' bootstrap check) |

M5 and M6 are killed only because the variables rows set `GIT_TRACE_PERFORMANCE`. With a local-path remote, of the issue's six variables none but trace2's writes the `-c`, and trace2's three are set to `0` whatever the prefix does. With an https remote `GIT_TRACE` writes it too, in the `run_command: git remote-https` lines; that is what the row of Round 2 holds, and the mutant R4 below, which keeps the caller's `GIT_TRACE`, passed all 27 earlier rows.

**How every run was made:**
- through lane 5's runner: `/usr/bin/python3 -m pytest -q -rs -p no:cacheprovider -o tmp_path_retention_policy=failed`, one basetemp per run;
- `LANES_*` cleared, a stub `gh` first on PATH, `GH_TOKEN=bogus`, an empty `GH_CONFIG_DIR`;
- `EMAIL=service@opensoft.dev`, `GIT_SSH_COMMAND=false`, `GIT_CONFIG_GLOBAL=/dev/null` at the start of the session.

| git | files | result |
|---|---|---|
| 2.43.0 | `test_family_siblings_untraced.py`, on this change before the docstring fix | 27 passed |
| 2.43.0 | the same file against main's `siblings.py` | 18 failed, 9 passed |
| 2.43.0 | gate shard A: 19 of the 41 files below | 1623 passed, 4 skipped, in 19:51 |
| 2.43.0 | gate shard B: the other 22 of the 41 files | 2415 passed, 8 skipped, in 15:03 |
| 2.47.1 | `test_family_siblings_untraced.py` | 27 passed, in 1:14 |

**What the 41 gate files are:**
- the new file;
- `test_family_member_make_jobserver.py`;
- every file `grep -l siblings tests/` names;
- the pinned-copy and upgrade-row files: `test_pinned_copy_text.py`, `test_update_shape.py`, `test_update_shape_add.py`, `test_update_shape_kept_helper.py`, `test_no_auto_maintenance.py`, `test_template_text_placeholders.py`, `test_bootstrap_spelling.py`;
- the trio: `test_repo_hygiene.py`, `test_agents_md_codes.py` and `test_cli_reference.py`.

**The gate runs** (both shards at once, then the 2.47.1 run) were made on this change as it is committed: `siblings.py` sha256 `b1e7bb21...` and the new test file sha256 `7ba7a416...`, at main `00f6d7f7` (this branch's base; no rebase was needed, see Merges). The runner's `START` line read `dirty=2`, the two tracked files this commit changes, and a sha256 check after the runs found `siblings.py` unchanged (neither it nor the test files were modified after the runs started). The first pair of shards was stopped part way and re-run whole; only the re-runs count here.

**The 41 files, by shard:**
- shard A (19): `test_shape_doctor.py`, `test_validator_child_encoding.py`, `test_family_py_unreadable.py`, `test_pinned_copy_text.py`, `test_siblings_inputs.py`, `test_siblings_family_name.py`, `test_family_member_make_jobserver.py`, `test_update_shape_add.py`, `test_adopt_printed_sentences.py`, `test_family_printed_quoting.py`, `test_family_makefile_siblings.py`, `test_template_text_placeholders.py`, `test_park_resume_targets.py`, `test_windows_paths.py`, `test_doctor_gitmodules_not_utf8.py`, `test_local_remote_dir_urls.py`, `test_family_siblings_untraced.py`, `test_setup_family_folder.py`, `test_bootstrap_refusal_exit.py`;
- shard B (22): `test_repo_hygiene.py`, `test_doctor_legs_members_next.py`, `test_update_shape.py`, `test_family.py`, `test_update_shape_kept_helper.py`, `test_yaml_reader_spaces.py`, `test_bootstrap_spelling.py`, `test_agents_md_codes.py`, `test_family_siblings_placement.py`, `test_no_auto_maintenance.py`, `test_cli_reference.py`, `test_family_siblings_bootstrap_unreadable.py`, `test_bootstrap_branch_bytes.py`, `test_family_init_asks_every_value.py`, `test_validate_workflow_gitmodules_urls.py`, `test_adopt_contracts_dir.py`, `test_doctor_unfinished_merge.py`, `test_family_members_not_a_list.py`, `test_family_init_landing.py`, `test_family_docs_one_spelling.py`, `test_doctor_members_spelled.py`, `test_pins_child_kind_and_siblings_root_spelling.py`.

**The skips are the environment's, each named by its reason:**
- shard A: 3 in `test_shape_doctor.py` (the PowerShell line is printed, and `powershell.exe` exists, only on a Windows host) and 1 in `test_family_member_make_jobserver.py` (`make -j2` here writes `--jobserver-auth=3,4`, not GNU make 4.4's named pipe);
- shard B: 2 in `test_doctor_legs_members_next.py` (this git crashes on `submodule init`, exit 139, as git 2.43 does on a bare `branch`), 4 in the same file (this git dies on a `shallow` of -2**31, as git 2.43 does), and 2 in `test_no_auto_maintenance.py` (the session began with `GIT_CONFIG_GLOBAL` set, and its file includes that one);
- the 2.47.1 run of the new file skipped none.

The full suite was not run.

**Static checks:**
- flake8 finds in `siblings.py` only the three lines it finds at main (two E501, one E127, each moved down by the added lines);
- in the new test file it finds only the F811s every fixture-importing file has;
- both files are ASCII, apart from the dashes and the CJK example already in `siblings.py`.

Fetched with `-c gc.auto=0 -c maintenance.auto=false`, on 2026-10-20 at about 21:03Z. Round 1, `git merge-tree --write-tree` of the first head `c3cf5154` against (round 2's are in its own section):
- **origin/main `6c861635`**: clean, exit 0, tree `225b2a99`.
  - Main has moved two commits past this branch's base `00f6d7f7`: `9cbba9d5` (#1063: `scripts/family.py`, `scripts/shape_materialize.py`, `docs/cli.md` and two tests) and `6c861635` (#1065: `adopt-project.py` and three tests).
  - Neither touches `siblings.py`, `bootstrap.py`, `tests/test_update_shape_kept_helper.py` or the new test file, so there was no rebase and the gate runs above stand.
- **#1062** (`fix/1040-windows-start-errors`, head `957ba038`), the one open PR that touches a family-root script this change reads (`templates/family-root/scripts/bootstrap.py`, with the assembly root's and `validate-family.py`, `validate-pins.py` and three tests): clean, exit 0, tree `84d4b54a`.
  - Its diff does not touch `untraced()`.
  - In the merged tree `bootstrap.py` still defines `untraced` (and the five other names `siblings.py` takes from it), and `siblings.py` is byte-identical to this head's (sha256 `b1e7bb21...`).
- **The other 9 open PRs** (#1073, #1072, #1071, #1070, #1069, #1068, #1067, #1064, #1031): none touches `siblings.py`, `tests/test_update_shape_kept_helper.py`, or a file the new test imports from (`conftest.py`, `test_family.py`, `test_family_add_refusals.py`, `test_family_bootstrap_stops_named.py`, `test_siblings_family_name.py`), read from `gh pr list --state open --json number,headRefName,headRefOid,files`.

`templates/family-root/scripts/siblings.py` is in `FAMILY_COPIED_VERBATIM`, so each holder gets one `upstream-changed` row for it, as #1045 gave one for `bootstrap.py`:
- a holder that takes it with `bootstrap.py` from #1045 or later needs nothing more;
- a holder that keeps an older `bootstrap.py` with `--accept-local` in the same apply is refused, `update-accept-local-missing-name`, naming `untraced`, before anything is written;
- a holder whose earlier apply kept a `bootstrap.py` without `untraced`, and that then applies this change without `--accept-local`, is not refused: `siblings.py` is copied, and `make siblings`, `park` and `resume` meet an `ImportError`. That is the gap of #536's guard, which `member_make_environment` has on main already, and it is #1082's.

No Windows or macOS run was made, since CI is Linux only (#597).

rv1075, lane 5's independent reviewer, found `c3cf5154` READY (#1075 issuecomment-6302090874): no MUST, two SHOULDs and a NIT. One commit on top of it, `041f7831`, with no rebase: main has touched none of this PR's files.

**The three findings:**
- **SHOULD 1** (the body said no `ImportError` reaches a holder, and two applies in a row make one): answered in the body above, in "Where the helper comes from" and "The pinned copy". The gap is #536's guard's, it is on main for `member_make_environment` already, and it is #1082's; this PR does not change `update-shape.py`.
- **SHOULD 2** (every row used a local file remote, so a leak through `GIT_TRACE` on an https member had no test, and rv1075's mutant R4 passed all 27 rows): answered by the new row below.
- **NIT** (three places said the member's own bootstrap "is given no token"): `siblings.py`'s module docstring, `rewrite_environment`'s docstring and the test file's docstring now say it is given no token in its argv. It inherits `SHAPE_LEGS_TOKEN` and `SHAPE_LEGS_APP_TOKEN` in its environment, because `run_member_bootstrap` passes no `env`, and the shipped one reads neither. `rewrite_environment`'s docstring also names the https measurement.

**The code of `siblings.py` is unchanged.** Its syntax tree with the docstrings taken out is the same at `c3cf5154` and at `041f7831` (compared with `ast`); the file's sha256 moved from `b1e7bb21...` to `19107ad4...` over comments and docstrings only. So round 1's two gate shards (1623 passed, 4 skipped; 2415 passed, 8 skipped) were not re-run; the targeted runs below are.

**The new row,** `test_an_https_member_with_a_token_in_use_is_in_no_trace` (the file has 28 rows now). Its setup:
- the estate of `tests/test_family.py`, with `IRRS`'s url in the holder's `.gitmodules` given as `https://github.com/InkRouter/IRRS.git`, and `IRSS` still a local path;
- `http.proxy=http://127.0.0.1:9`, a dead proxy, in git's command scope after the entries the session holds, and `NO_PROXY` and `no_proxy` empty, so nothing leaves the host;
- a fake `SHAPE_LEGS_TOKEN` and the seven trace variables set to files;
- `make siblings`, cloning.

It asserts:
- the proxy is set where the row sets it: `http.proxy=http://127.0.0.1:9` is in the command scope the run's git reads (`command_scope_at`, which runs `git config --show-origin --list` and writes nothing);
- exit 2 and `IRRS: git clone exited 128:` on stderr, which is how the head fails (rv1075 measured the same);
- `IRSS` was cloned and `IRRS` was not;
- the token is in neither stdout nor stderr, and in no file under the test's directory;
- the five trace files the variables ask for are written, by the run's other gits.

No assert names the proxy in git's message. The git 2.47.1 this lane builds has no `git-remote-https` (`git: 'remote-https' is not a git command`, `fatal: remote helper 'https' aborted session`), so there the clone fails at once without reaching the proxy, still with 128. `GIT_TRACE` has written the `run_command: git remote-https origin https://x-access-token:<token>@github.com/...` line before that, so the row finds the leak on both gits. A first local version asserted the proxy's message and failed on 2.47.1 for that reason; the assert was dropped, and the commit amended, before anything was pushed.

**It fails on main.** The file was run against main's `siblings.py` (sha256 `86bf57e0...`, put in place and then restored, sha256 checked each time):
- git 2.43.0, the whole file: **19 failed, 9 passed**, the 18 rows of round 1 and the new row. The new row fails at `assert files_holding(tmp_path, TOKEN) == []`, with 5 files holding the token: `temp/trace-performance.txt`, `temp/trace.txt`, `temp/trace2-event.json`, `temp/trace2-normal.txt` and `temp/trace2-perf.txt`. The round 1 rows find 4 of those, since a local path leaves `temp/trace.txt` clean;
- git 2.47.1, the row alone: **1 failed**, the same 5 files.

**It kills R4.** R4 is rv1075's mutant, in `rewrite_environment`: `return {**untraced(), **{k: v for k, v in os.environ.items() if k == "GIT_TRACE"}} if token else None`, which keeps the caller's `GIT_TRACE` for the clone and the fetch. Applied alone, then restored and sha256-checked:
- git 2.43.0, the whole file: **1 failed, 27 passed**: the new row alone, with `temp/trace.txt` the one file holding the token;
- git 2.47.1, the row alone: **1 failed**, the same one file.

**The runs on the pushed head `041f7831`** (the runner's `START` line read `dirty=0`), through the same runner as round 1:

| git | files | result |
|---|---|---|
| 2.43.0 | the new file, `test_update_shape_kept_helper.py`, `test_family_makefile_siblings.py`, `test_family_member_make_jobserver.py`, `test_pinned_copy_text.py`, and the trio (`test_repo_hygiene.py`, `test_agents_md_codes.py`, `test_cli_reference.py`) | 589 passed, 1 skipped (the jobserver file's named-pipe row, as in round 1), in 5:09 |
| 2.47.1 (`git version 2.47.1`, printed from the exact path first on PATH) | the new file | 28 passed, in 2:13 |
| 2.43.0 | the new file against main's `siblings.py` | 19 failed, 9 passed |
| 2.47.1 | the new row against main's `siblings.py` | 1 failed |
| 2.43.0 | the new file with R4 | 1 failed, 27 passed |
| 2.47.1 | the new row with R4 | 1 failed |
| 2.43.0 | on a predicted merge with main (below): the new file, `test_update_shape_kept_helper.py`, `test_pinned_copy_text.py`, `test_family_makefile_siblings.py` | 305 passed, in 2:50 |

The full suite was not run. flake8 finds in `siblings.py` the same three lines as at round 1, and in the test file only F811s, from the fixtures it imports. Both files are ASCII, apart from the dashes and the CJK example already in `siblings.py`.

**The merges of round 2.** Fetched with `-c gc.auto=0 -c maintenance.auto=false` at about 23:00Z; `git merge-tree --write-tree` of `041f7831` against:
- **origin/main `c13c3985`** (#1076's squash, which touches `templates/family-root/scripts/bootstrap.py` and `tests/test_family_bootstrap_stops_named.py`, among others): clean, exit 0, tree `8ae10d0c`. None of the three files this PR changes is among the files main changed since the base `00f6d7f7`, so there is no rebase. In that tree `siblings.py` is byte-identical to this head's, `untraced()` has the same syntax tree as at the base, and `CREDENTIALS` and `files_holding`, which the new file imports from `test_family_bootstrap_stops_named.py`, are still defined. The 305-passed run above is on that tree;
- **#1062** (`fix/1040-windows-start-errors`, head `957ba038`): clean, exit 0, tree `e6ed1ba2`. Its `untraced()` has the same syntax tree as main's;
- **the other open PRs** (#1031, #1069, #1070, #1072, #1073, #1081, #1084): none touches `siblings.py`, `tests/test_update_shape_kept_helper.py`, `bootstrap.py`, or a file the new test imports from, read from `gh pr list --state open --json number,headRefName,headRefOid,files` at about 23:00Z. #1076 (`fix/1056-signal-anywhere`, head `73906948`) was open when the runs were made, and merged clean with this head then (tree `6ae3e65f`); it has landed since as `c13c3985`, above.

**The failure.** Lane 5's landing gate (log `c1075.log`, #1075 issuecomment-6304830183) failed the https row of round 2 at `041f7831`: 1 failed, 356 passed. The change in `siblings.py` was not at fault; the row depended on the caller's git config.
- The gate ran with neither `GIT_CONFIG_GLOBAL=/dev/null` nor `GIT_SSH_COMMAND=false`, which the writers' runs and round 2's runs had.
- `conftest.py`'s session global file includes the caller's global config (or `~/.gitconfig`, where `GIT_CONFIG_GLOBAL` is unset). The operator's `~/.gitconfig` has `url.git@github.com:.insteadOf=https://github.com/`.
- Git keeps the first of two `insteadOf` prefixes of the same length, and the config files are read before the command line, so that rewrite beat the token's `-c` rewrite of the same prefix. Measured with scratch files and a stand-in token, on git 2.43.0: under a global file with that rewrite, `git -c url.https://x-access-token:T@github.com/.insteadOf=https://github.com/ ls-remote --get-url https://github.com/InkRouter/IRRS.git` printed `git@github.com:InkRouter/IRRS.git`.
- So the row's `https://github.com/InkRouter/IRRS.git` went over ssh to `InkRouter/IRRS`, a real private repository. The dead proxy never applied, the clone succeeded, `make siblings` exited 0 and the placed members were both there, and the row failed `assert result.returncode == 2`.

**The fix** is in `tests/test_family_siblings_untraced.py` only. No other file changed in this round, and `siblings.py` is byte-identical to `041f7831`'s (sha256 `19107ad4...`).
- **`hermetic_config`** gives the https row's git a global file of its own, `session_global_config("")` (`conftest.py`'s own function: automatic maintenance off, and no include of the caller's file), `GIT_CONFIG_NOSYSTEM=1` and `GIT_SSH_COMMAND=false`.
  - It is the least invasive way: only the one row with an https url sets it, `conftest.py` and every other row stay as they were, and the other rows' remotes are local paths, which no rewrite of GitHub's url reaches.
  - `GIT_CONFIG_GLOBAL` set takes git's two user-level files out of the reading, and `GIT_CONFIG_NOSYSTEM` the system file whatever `GIT_CONFIG_SYSTEM` says (checked on git 2.43.0 and 2.47.1 with scratch files).
  - `GIT_SSH_COMMAND=false` is a second wall: a url somehow sent over ssh runs `false`. No mutant can show it needed, since the runner exports it too.
- **`url_after_config`** is a new assert before the clone: `git ls-remote --get-url <url>` (it applies the config's `insteadOf` and asks nothing of the network) must give the url unrewritten under the row's environment. A config that reaches the row now fails by name, before any clone.
- **The row is parametrized by `CALLERS_CONFIG`**: `none` (round 2's row), and `global` and `system`, each a stand-in for a caller's config that would send the url somewhere reachable. `as_the_callers_config` writes a scratch file of the test's own, `url.<file URI of the family's own IRRS remote>.insteadOf=https://github.com/InkRouter/IRRS.git`, into this process's `GIT_CONFIG_GLOBAL` (the session file includes it) or `GIT_CONFIG_SYSTEM`. It is built from tmp files only: no network, and never the real `~/.gitconfig`. The file now has 30 rows.
- With the fix, in each of the three, the clone fails at the proxy with git's 128, `make siblings` exits 2, `IRSS` is placed and `IRRS` is not, and the token is in no output and in no file under tmp_path.

**The variants fail without the fix.** Each was applied alone to the worktree's test file (or `siblings.py`) and run through the runner, with the file's sha256 checked after it was restored:
- **`041f7831`'s file as pushed, under a caller's global config.** Lane 5's runner now honours `L5_GIT_CONFIG_GLOBAL=<scratch file>` as the caller's global config, with ssh impossible. The scratch file rewrote `https://github.com/InkRouter/IRRS.git` to the run's own IRRS remote (a `file://` url under the run's basetemp). The whole file, git 2.43.0: **1 failed, 27 passed**, the https row at `assert 0 == 2`, the gate's failure reproduced with no network.
- **T2, `041f7831`'s row plus the variants:** the new file with `hermetic_config` and the `url_after_config` assert taken out. The https rows, git 2.43.0: **2 failed, 1 passed**, `[global]` and `[system]` at `assert 0 == 2` (the clone went to the local remote and exited 0), and `[none]` passes. On git 2.47.1 the same.
- **T1,** the row's global file dropped and the assert kept: `[global]` fails at the assert, which sees `file:///...IRRS.git` for the url; the other two pass.
- **T3,** `GIT_CONFIG_NOSYSTEM` dropped and the assert kept: `[system]` fails at the assert; the other two pass.

**R4 stays killed.** rv1075's R4 (`rewrite_environment` keeps the caller's `GIT_TRACE`), git 2.43.0, the whole file: **3 failed, 27 passed**, the three https rows.

**The runs on the pushed head `962ae43c`** (`START` read `dirty=0`), through the same runner as before:

| git | files | result |
|---|---|---|
| 2.43.0 | the new file, `test_update_shape_kept_helper.py`, and the trio (`test_repo_hygiene.py`, `test_agents_md_codes.py`, `test_cli_reference.py`) | 359 passed, in 3:05 |
| 2.47.1 (`git version 2.47.1`, printed from the exact path first on PATH) | the new file | 30 passed, in 1:51 |
| 2.43.0 | the new file, with `L5_GIT_CONFIG_GLOBAL` naming that scratch file | 30 passed, in 2:21 |
| 2.43.0 | `041f7831`'s file, with the same | 1 failed, 27 passed |
| 2.43.0 / 2.47.1 | T2, the https rows | 2 failed, 1 passed / 2 failed, 1 passed |
| 2.43.0 | T1, T3, the https rows | 1 failed, 2 passed each |
| 2.43.0 | R4, the whole file | 3 failed, 27 passed |

The full suite was not run. flake8 finds in the test file only F811s from the fixtures it imports, and nothing over 79 columns; the file is ASCII.

**The merge-tree of round 3.** Fetched with `-c gc.auto=0 -c maintenance.auto=false` at about 10:53Z; `git merge-tree --write-tree` of `962ae43c` against:
- **origin/main `2a119f28`** (#1092): clean, exit 0, tree `b5ea0114`. Main has landed #1076 (`c13c3985`) and #1062 (`ff0c72eb`) since the last round, and has changed `templates/family-root/scripts/bootstrap.py` and `tests/test_family_bootstrap_stops_named.py` among others, but none of this PR's three files. In that tree `siblings.py` is byte-identical to this head's, `untraced()` has the same syntax tree as at the base `00f6d7f7`, and `CREDENTIALS` and `files_holding` are still defined where the new file imports them from.
- **#1088** (`fix/1085-nit-texts`, head `88af1b7b`), which touches the same two files of main's: clean, exit 0, tree `365df092`, with the same findings.
- **The other open PRs** (#1087, #1090, #1091, #1097): none touches `siblings.py`, `bootstrap.py`, `tests/test_update_shape_kept_helper.py` or a file the new test imports from, read from `gh pr list --state open --json number,headRefName,headRefOid,files` at about 10:53Z.

Lane: openreposhape-5 (openRepoShape-5)

Review: rv1075, lane 5's independent reviewer, not the writers (w1055 and f1055): READY at `c3cf5154` (issuecomment-6302090874) with no MUST; its two SHOULDs and its NIT were taken in one new commit, and the re-check is READY at `041f7831` (issuecomment-6303900180), with no MUST or SHOULD; its one NIT, a merge-tree number in the body, is fixed in the body. CI (Brett Heap's ruling 27): H0 is the head 962ae43 itself, which passed tests, tests-git-bash and SonarCloud; main has touched none of its files since its base 00f6d7f; and the local gate passed on its predicted squash tree fc2afb3 over main 16f9a0e: the family_siblings_untraced, update_shape_kept_helper, repo_hygiene, agents_md_codes, cli_reference sets, 359 passed. Landed on Brett Heap's word of 2026-10-18T14:45:28Z, relayed to every lane by lane 3 (#473 issuecomment-6251255596): "merge v1.2.0 PRs once reviewed and green".

Closes #1055

Lane: openreposhape-5 (openRepoShape-5)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
brettheap added a commit that referenced this pull request Oct 23, 2026
…ath that is not UTF-8 as a printf word of octal escapes ending in a slash, so `git -C <member>/<leg>` and `submodule update -- <leg>` typed in any POSIX shell name that leg (#1086) (#1098)

When `remove`'s rollback cannot check the member out again,
`PinRollback._work_tree_by_hand` prints the lines to type. Two of them
name a leg: `git -C members/<P>/<leg> checkout -q <branch> --` and the
member's `submodule update --init --no-fetch -- <leg>`. A leg's path is
read from the member's `ls-files -z` with `surrogateescape` (`_legs`),
so `shlex.quote` quoted the surrogate. With a leg mounted at `caf` and
the byte E9, the lines read `'caf\udce9'`, and typed they name no path.

A new `_path_by_hand(path)` spells each word that holds a leg's path. A
UTF-8 path is `shlex.quote`d, byte for byte as before. Any other path is
`"$(printf '<escapes>/')"`, #1084's form for a branch, with a `/` at the
end and a leading `-` as `\055`. The `/` is last because `$(...)` strips
only trailing newlines, and git reads `<dir>/` as `<dir>`. A `'`, a
backslash, a `%`, a `!` and every byte outside printable ASCII is a
three-digit octal escape, so the line is ASCII and holds no newline.
`_head_by_hand` spells its `-C` path with it, and the legs'
`submodule update` spells each leg with it. `_branch_by_hand`'s escape
loop moved into `_printf_escapes`, which both use, and its output is
unchanged. A member's own path comes from `family.yaml`, which is UTF-8,
so the member's lines do not change.

`tests/test_family_leg_path_by_hand_bytes.py` (new, 78 passed) builds
real repositories with a holder, a member and two legs, runs each
by-hand line as printed through `sh`, `dash`, `bash` and `zsh`, and
reads the leg back at its gitlink's commit and on its branch. With
main's `family.py`, 74 of its 78 fail, including all 16 real-repository
rows for a path that is not UTF-8, and the UTF-8 rows pass. Each of the
six mutants run against it is killed.

Closes #1086

Lane: openreposhape-3 (openRepoShape-3)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

family.py: a rollback's by-hand checkout line spells a branch that is not UTF-8 as Python's \udce9, which typed names no branch

1 participant