README.md, the handbook, AGENTS.md and the holder's AGENTS-shape.md: init's --into sentence omits the landing refusal, make siblings is described as it was before #578, and nothing names the one-spelling rule for members/ #695

Goal: the documentation of family.py init, make siblings and the members/ directory says what the tools do since #488, #578 and #574.

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 6144829439, the --into sentence; comment 6198183910, the make siblings description; comment 6192725913, the members/ rule).

Lands after: the open README and handbook PRs, one at a time in lane 3's README turn (#519: two README PRs conflict at the handbook markers of a section both change): #627 (lane 2: README.md, docs/handbook.html, tests/readme-cap.d/606.txt) and #630 (lane 3: README.md, AGENTS.md, docs/handbook.html, tests/readme-cap.d/563.txt and more). Neither touches README's ## Families section (README.md:841-958) as far as their file lists show; check the handbook markers when rebasing.

Lane 3's #460 lines. Lane 3 now owns #460's lines, R605's six about the family-root README and AGENTS templates among them; its fix of R605's template line may land first. This issue's third line edits templates/family-root/AGENTS-shape.md, a pinned copy: take it with whichever pinned-file edit goes next.

Lines (line numbers at d4a7fab)

• README's and the handbook's --into sentence gives the default but not the refusal family.py init: AGENTS.md's own command lands the holder inside the openRepoShape checkout, and init's NEXT prints python3 family.py add, which cannot run #488 adds. README.md:883-884 ("scripts/family.py init lands the holder there: --into <dir> is the PARENT directory (the directory you are standing in, by default)") and docs/handbook.html:1310-1312 (the same words). init refuses that default inside a checkout of this standard (family-landing-in-standard, scripts/family.py:1417-1457), AGENTS.md says so (AGENTS.md:384-388, "refused inside a checkout of this standard, hence --into .. above"), and README's own InkRouter example passes --into .. (README.md:924); a reader who runs init bare from the checkout gets the refusal, which names the way on. Direction: "(the directory you are standing in, by default; refused inside a checkout of this standard, family-landing-in-standard)" in both, the README's ledger file (tests/readme-cap.d/<n>.txt, tests/test_repo_hygiene.py:1244-1260; README is 1449 lines against a cap of 1422 plus the ledger) and the handbook's section blob recomputed.
• README.md:903-905 and docs/handbook.html:1330-1333 still describe make siblings as it was before siblings.py and family.py: make siblings asks about the family folder before it clones, clones each member on its tracking branch, and family.py siblings runs the holder's own copy (#543) #578. They say: "When the holder's parent folder is not named after the family, make siblings WARNS and prints the exact mv". Since siblings.py and family.py: make siblings asks about the family folder before it clones, clones each member on its tracking branch, and family.py siblings runs the holder's own copy (#543) #578 it stops before it clones anything, so the run after the move clones each member once, and a family folder reached through a link of the family's name passes with no warning. The holder's README (templates/family-root/README.md:72-79), its AGENTS-shape.md and AGENTS.md:407-411 say both. Direction: one clause in each place, for example "When the holder's parent folder is not named after the family, and no link of that name beside it leads to it, make siblings WARNS, prints the exact mv and clones nothing until it is moved." It needs the same ledger line and handbook hash step; siblings.py and family.py: make siblings asks about the family folder before it clones, clones each member on its tracking branch, and family.py siblings runs the holder's own copy (#543) #578 left it out for that reason.
• Docs: name the one-spelling rule for members/. A holder keeps members/ in one spelling, and add refuses family-members-dir-variant (and member-path-taken for a variant of the mount path) until a human renames the entries under any other spelling (scripts/family.py:2917-3012). Probed: no mention of family-members-dir-variant or member-path-taken in AGENTS.md, README.md, docs/handbook.html, templates/family-root/README.md or templates/family-root/AGENTS-shape.md (grep at d4a7fab). Where: AGENTS.md's family section (AGENTS.md:365-422), README's ## Families, the holder's README (templates/family-root/README.md, "Adding, removing and moving a member", :116-130) and the holder's pinned AGENTS-shape.md. AGENTS.md is at its cap (492 lines, tests/test_repo_hygiene.py:654): the clause there means trimming a line elsewhere, or a raise that needs a word from Brett. Direction: one sentence, the same words in all four places.

Left out: the holder's README cd QuillWorks for a holder made with --name before #629 (the README is rendered, so update-shape.py apply never re-syncs it) needs a decision on how such a holder is corrected, and stays on #459.

Overlaps: #627 and #630 (README.md, docs/handbook.html), #630 also AGENTS.md; lane 3's #460 template lines (templates/family-root/README.md, AGENTS-shape.md).

Mark the three lines → this issue on #459, and tick them there when this closes.

🤖 Generated with Claude Code