abc submodule resolves to the WRONG source (head → ?/abc no-refs; patch → official github)
Recursing into the nested abc submodule of beagle derives the wrong remote on two verbs. be head be://localhost/beagle-journal?/beagle recurses to be://localhost/ beagle-journal?/abc — the journal ROOT coordinate, which advertises no refs (abc is nested UNDER beagle). be patch instead reaches for the OFFICIAL https://github.com/gritzko/libabc.git and hard-fails offline. Either way the local co-resident abc shard is never used. SUBS-017-class. Method: Issues.
be head be://localhost/beagle-journal?/beagle → after the parent head, `be: head
abc → remote be://localhost/beagle-journal?/abc is not a beagle or git repository (reachable, but advertised no refs), HOMENOPROJ / WIRENOTRP. Wrong coordinate: ?/abc` is the journal root, not the abc nested under beagle.
be patch '?6a0ce1b7!' applied cleanly (incl. applied abc) but THEN still did an
ssh/https fetch of https://github.com/gritzko/libabc.git → WIREUNRCH / BEDOGEXIT. It used the OFFICIAL url, not the local abc shard, on a local reconcile.
local nested/co-resident shard. Relates to SUBS-017 (wrong remote target) and SUBS-020/SUBS-024 (parent-kind source resolution).
abc resolves to its local co-resident/nested shard for be head and
be patch when reachable; fall back to official only when genuinely needed.
applied abc does NOT trigger a network fetch.SNIFFSub*); don't re-roll. Repro-first.
under the parent (co-resident / ?/beagle/abc), not the journal root ?/abc.
be head abc → ?/abc no-refs; fix the nested coordinate.be patch abc → official github fetch; prefer the local shard, no net on local.6a0ce1b7.todo/README.mkd) — a board gap.