SUBS-049: put/status treat a primary-anchored nested wt (.be DIR) as parent files the .gitmodules sub boundary is missed

Now
OPEN
Sev
HIGH

Report (gritzko, 2026-07-10): jab get into a subdir + listing it in .gitmodules jab put <subdir> recurs into it like new files instead of recognizing a submodule boundary. Root cause: BOTH boundary probes only accept the SECONDARY anchor form (.be regular FILE = the wtlog): classify.js::wtScan nested-repo detect (be/shared/classify.js:77-79) and recurse.js::isMount (be/core/recurse.js:36-44). But a green-field jab get of a remote plants the PRIMARY form a .be DIR holding wtlog + the shard (be/verbs/get/get.js:217-228 seedRemote ingest.clone + writeWtlog(join(beDir,"wtlog"))) which be.find anchors on (core/discover.js:128-134) yet neither probe recognizes. So the sub's interior rides the parent's wtScan and put <dir> stages it as parent put rows; status floods unk the same way. The .gitmodules declaration never enters this path (expandDir is gitmodules-blind; recurse.walk consults it but gates on isMount). Siblings SUBS-039 SUBS-044 SUBS-045; umbrella DIS-058.

Input

Context

Goals

Constraints

WIP

Design decisions

TODOs

Blockers and bummers

Outcome