URI-008: be:-local must fetch submodule objects (recursive-clone parity)

Now: DONE

Host-less be: (St.1's local keeper) recurses into submodules but fetches only the sub's refs+pack, NOT its objects — so be get be:<parent-with-sub> aborts rc 157 sub checkout: object not found … KEEPNONE, while file:<parent> clones clean. A second gap: a co-resident-shard clone-from-subdir (be:<git2> into an existing-store subdir) silently lands no shard where file: did. Both are pre-existing on trunk (2ea762c2), URI-007-class. They block URI-006 St.2: removing the file: clone path forces ~20 sub/clone tests onto be:-local, which can't yet serve sub objects. Decision (user 2026-06-22): be: MUST fetch submodule objects. Method: Issues.

Input

Context

Surfaced by URI-006 St.2: with file:-clone removed, 20 tests must use be: and go red — get/21,31,33,37,44,45,47,50; head/19,25; post/23,38,41,43,48; blame/01; commit/03; diff/08,09,10. Trunk-binary repro, not a St.2 regression.
be get be:<parent-with-submodule> → rc 157, sub checkout: object not found … project=<sub> KEEPNONE; the sub fetch pulls refs+pack but not objects. file:<parent> succeeds rc 0 — that is the parity baseline to match.
Co-resident-shard gap: be:<git2> cloned into an existing-store subdir (get/21) lands no shard; file: did. Distinct arm from the sub-object gap.
be://host (ssh) sub recursion fetches by PIN sha and works (spot-keeper); the be:-local recursion arm is what URI-007 did not cover.

Goals

be get be:<parent> recurses submodules and fetches their objects by pin (sha), at parity with file:<parent> and be://host (ssh) recursion.
Co-resident-shard clone-from-subdir over be:-local lands the shard like file:.
The 20 URI-006 St.2 migrations go green; full ctest green (be-post-relpath aside).

Constraints

NEVER hand-rolled parsing — ragel grammar + dog dispatch (CLAUDE, ABC).
Don't regress be://host (ssh) sub recursion or file: worktree attach.
Core transport — adversarial, repro-first per Issues.

WIP

Design decisions

Localize (repro-first) where be:-local recursion drops the object fetch; St.1 seam: BE.cli.c be_be_local_route, KEEP.exe.c hostless_local, WIRECLI.c wcli_spawn local-exec — contrast the working ssh by-pin sub fetch.

TODOs

Repro the be:-local sub-object gap (rc 157 / KEEPNONE) as a failing test (get/63).
Fix be:-local recursion to fetch sub objects by pin; verify get parity.
Fix co-resident-shard clone-from-subdir (get/64 arm).
Confirm the 20 St.2 migrations green: 19/20 pass; post/43 still red on a SEPARATE POST-side gap (SUBS-020 official-url sub-push) — its own decision.

Blockers and bummers

None now (LANDED). Surfaced a POST follow-up: post/43 (SUBS-020 git-.git→official sub-push) is the last St.2 blocker; user leans manual/--force (own ticket TBD).

Outcome

LANDED fa31e6f6 — symmetric scheme probe: sniff/SUBS.c subs_loc_cb now path- probes be:/keeper: like file: (no bogus want-by-hash to a git peer); and beagle/BE.cli.c hoists the be:→authority rewrite before be_sub_shard_setup so a host-less be: clone mints the co-resident shard. Repro get/63 + get/64; ctest 388/389 (be-post-relpath ssh aside).