SUBS-026: a sub advanced past the parent pin isn't surfaced by status/head, and a bare post records no gitlink bump

PARTLY SUPERSEDED 2026-07-15: goal 2's "auto-creates ?/<sub>/.<parent> at the new pin" is STALE the dot-branch is removed (URI-016 d5, SUBS-054). The surviving goal (surface an advanced sub, never report it clean) is restated as gitlink != base with no ref involved (URI-016 d11). Native (C) arm; the JS arm is SUBS-054.

A submodule whose mounted worktree HEAD has advanced past the parent tree's 160000 gitlink pin e.g. via a standalone be get inside the mount is reported by be status/be head as clean (0 ahead, 0 behind, 0 changed, blank pin), and a bare be post records nothing; the bump lands only after a manual be put <sub>. Same invariant as PATCH-001, which covers the be patch arm this is the get / manual-mount arm. See Submodules, PATCH-001.

Input

Context

Advancing the beagle sub of beagle-journal with be get ssh://localhost/src/dogs?/main (inside beagle/) moved its wt 5a95cd15 3b41fa69, but the parent never saw it:

status:beagle/abc   ?6e3b93f8…  237 ok    <- pinned, sha shown
status:beagle       ?           1272 ok    <- advanced, BLANK pin, no ahead/behind
be head beagle:  ?trunk: 0 ahead, 0 behind, 0 changed

Goals

Constraints

WIP

Design decisions

TODOs

Blockers and bummers

Outcome