scaffold-project.py, family.py and shape_materialize.py: #622's folder refusals print a folder name raw, so an ESC or a line break reaches the terminal, and family-operation-in-progress prints a holder's path across two lines #692

Goal: every path the creating tools print in a refusal is spelled safe to show.

Filed by lane openRepoShape-5 on Brett Heap's word of 2026-10-16T12:17:02Z ("#459's family lines (~38)"), from checklist lines on #459 (comment 6213775237, L2-77; comment 6213530456, R612's raw-path line). Three lines first drafted here are not in it: the scaffold-bad-id / family-bad-id line (comment 6198174555) is lane 2's #659, and L2-74 and L2-65 are known limits by Brett Heap's word of 2026-10-16T12:14:51Z on lane 2's triage (#473 comment). The first line is MIXED: it touches scaffold-project.py as well as family.py, so whoever triages the scaffold's lines must not file it twice.

Lands after: #634 (open), which renames shown_source to repo_shape.shown_path; use whichever is on main when this starts.

Lines (line numbers at d4a7fab)

• MIXED, L2-77. scaffold-project.py and family.py: both runs ask whether each folder they make can be made and take only gh's not-found answer as "absent", so --dry-run refuses a file where a folder goes, or a gh repo view that fails otherwise, by name as the real run does, and a refused init leaves no empty family folder (#609) #622's new folder refusals print a folder name as it is, so an ESC or a line break in a path reaches the terminal. scripts/shape_materialize.py:1355 and :1357 (folder_cannot_be_made), :1389 (refuse_unmakeable_folder), :1405 (make_folder), scaffold-project.py:1250 (scaffold-target-exists) and scripts/family.py:1791 (family-target-exists). Probed on main: family.py init --into <a file named wd-ESC[31mRED> --dry-run gives REFUSED family-folder-cannot-be-made: the family folder .../wd-^[[31mRED/Orbit cannot be made: ... through cat -v. The same files already spell a --pin-source (shown_source, scripts/shape_materialize.py:2746). Direction: spell each path with shown_source (shown_path once Pinned shape copies: one bump, so AGENTS-shape.md is true of every root, the scaffold's chain WARNING offers only its own sources and spells --pin-source, the root's not-used note spells it too, and THE LOCKSTEP RULE's bump runs (#610) #634 is in), taking it from the from repo_shape import block the other two files already have; a printable path stays byte for byte, so no existing row changes, and why.endswith(CANNOT_WRITE_IN) in refuse_unmakeable_folder still holds. Add a row for an ESC in the name and one for a line break then WARNING forged-line: pwned to SCAFFOLD_CASES and FAMILY_CASES (tests/test_dry_run_parity.py:193 and :236).
• family.py, R612 round 2: a holder whose path holds a newline prints the family-operation-in-progress path raw, across two lines. where.as_posix() in the refusal's detail (scripts/family.py:1032), and the holder in the other refusals of the same block. It is the true path, as git keeps it, so cosmetic. Direction: the same spelling as the line above for the detail's paths; the git -C <holder> command lines are already quoted by shell_line.

Overlaps: #620 (adopt only, the wording source), #621 and #634 (both edit scaffold-project.py; #634 also shape_materialize.py and repo_shape.py), #639 (family.py remove functions only), lane 2's #659 (scaffold-bad-id and family-bad-id, in two of the same files). Lane 5's #646 edits family.py _spellings_refusal (another function). scaffold-project.py, scripts/family.py and scripts/shape_materialize.py are not pinned copies.

Mark the two lines → this issue on #459, and tick them there when this closes (the scaffold's half of the MIXED line ticks with it).

🤖 Generated with Claude Code