family.py init --name: the holder's README and AGENTS.md name its folder after the display name, where make siblings needs the repository's name, so a holder laid out as its README says clones nothing #629

Filed by lane openRepoShape-4, into v1.1.0, on Brett Heap's word of 2026-10-15T22:49:27Z. Source: R605's review of #624 (#605), measured on main after #578. It is on #460's checklist as issuecomment-6203011653.

What happens

1. Make a family whose display name differs from its repository: family.py init --org <org> --family Quill --name QuillWorks (measured with --local-remote-dir).
2. The holder's own README tells the reader to git clone …/Quill.git, then cd QuillWorks. It gives the layout as QuillWorks/QuillWorks and says "The doubled QuillWorks/QuillWorks is deliberate".
3. In that layout, make siblings prints WARNING the holder's parent folder is 'QuillWorks', not 'Quill'., clones nothing, and make exits 2.

What follows: a holder laid out exactly as its own README says gets no working clones. The fix the warning prints is to move the checkout, which this standard most wants to avoid.

Why

• What make siblings wants: templates/family-root/scripts/siblings.py's family_folder_name names the folder after the holder's REPOSITORY (the basename of repository:), and 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 made a wrong folder a stop.

• What the templates say: they name it with {{FAMILY_NAME}}, which is --name:

  • templates/family-root/README.md, lines 1, 10, 35-36 and 61;
  • templates/family-root/AGENTS.md, lines 3 and 7.

  The README has said this since Family workstation layout: a plain <Family>/ folder holding the holder and the members' working clones — family.py init lands there, the scaffold learns --family, the holder gains a siblings utility that warns and never moves #76 (The family's workstation layout: init lands at <into>/<Family>/<Family>, and make siblings clones each member beside the holder without ever moving one (#76) #79).

• siblings.py names the family two ways in one run. Its header prints name: (siblings: QuillWorks (…)), while its warning asks for a folder named after the repository (Quill).

• No test catches it: no test builds a holder whose name: differs from its repository and then runs make siblings. R605's mutant M4, which makes family_folder_name prefer name:, survives 166 tests.

Expected

• Every place a family's own files name the FOLDER names it as make siblings does: after the repository. That covers the README's cd, its layout lines, and AGENTS.md.
• The display name stays wherever it is only a title.
• siblings.py says which name it means.
• A test builds a holder with --name different from --family, follows its README's layout, and runs make siblings to a clone.

These are pinned shape copies, so a holder that re-syncs its copies sees an upstream-changed row. The change is to the template text only; no rule changes.