bootstrap.py and validate-family.py: family bootstrap ok with no member checked out, an earlier row's member-uninitialized hiding a case-variant refusal, and member-gitlink-unnamed with no command under --no-members #648

Goal: a holder's own bootstrap and gate name what is wrong after a clone, in every order and mode, and never say ok over members that are not there.

Filed by lane openRepoShape-5 on Brett Heap's word of 2026-10-16T11:21:49Z ("bootstrap.py and gate order"), from lane 5's checklist items (a), (b) and (c) on #459 (comment). Found by #611's writer and lane 5's review rv611b.

Lands after: #639 (#611), which changes the same checks in validate-family.py (member-gitmodules-absent, and member-uninitialized left out for members HEAD gives no section). Both files are pinned copies.

Lines

• (a) templates/family-root/scripts/bootstrap.py says family bootstrap ok, exit 0, when it checked no member out. In a fresh clone of a holder whose HEAD lost .gitmodules, git submodule update exits 0, and bootstrap prints "every member and leg fetched" (:96 at 4cf5fb0), NOT CHECKED OUT; skipped for each member (:144), then family bootstrap ok (:212). In a plain clone with a case-variant gitlink, it prints fatal: No url found for submodule path 'Members/<P>' and still ends ok.
• (b) after a plain clone and git submodule update --init --recursive, an earlier row's member-uninitialized hides a later row's case-variant refusal: in family.py add, under core.ignorecase=true, commits the member's gitlink as Members/<P> when HEAD holds a path under a case variant of members/ that the index no longer does (a git rm -r Members not yet committed), so .gitmodules and family.yaml say members/<P>, the holder's own validator passes in the working clone, and every fresh clone of the pushed holder leaves the member's directory empty and is refused member-gitlink-absent #363's state the update dies (exit 128) at Members/<P>, so an earlier member is left unchecked, and the gate refuses member-uninitialized for it before it reaches the variant row; its remedy is the same update, which dies again. After clone --recurse-submodules this does not happen.
• (c) member-gitlink-unnamed prints no command under --no-members (validate-family.py :1102-1117 at 4cf5fb0), the mode CI runs in (b)'s state.

Direction:

• (a): do not say every member was fetched, or end ok, when a row's member is not checked out after the update. Exit non-zero and name validate-family.py.
• (b): check every row's gitlink path, the variant rule included, before any member-uninitialized.
• (c): print the same index-only move members mode prints.

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

🤖 Generated with Claude Code