SUBS-046 HIGH: a LOCAL submodule mount fetches the child via the keeper wire instead of reusing the on-disk source store + making a worktree

submount.mount has only two child-acquire paths: the havePin fast-path (reuse an ALREADY-present sibling shard, checkout only) and, for a fresh mount, fetchChild → wire.fetch. wire.js::classify routes a file:/scheme-less local URI to a LOCAL keeper exec ({bin: keeperBin, …}), so a LOCAL submodule mount spawns keeper — which is absent in the jab-only bin — even though the child's objects already live on local disk in the source store. Per design a LOCAL clone must NEVER touch the wire: reuse the store and create a (store-backed) worktree, exactly like top-level jab get file://… (get.js's localish direct path). Only be:// should reach keeper / the future jab upload-pack (GIT-020).

Input

Context

Goals

Constraints

WIP

Design decisions

TODOs

Blockers and bummers

Outcome