Beagle SCM

SUBS-030 MED: be status renders an advanced-submodule mod <sub> row with no timestamp

A submodule whose tip advanced past the parent gitlink pin reads mod <sub> in be status (correct per SUBS-027), but the row is emitted WITHOUT a timestamp (blank ts column, unlike every file mod row) and as a bare mod that doesn't distinguish "advanced — gitlink bump pending" from a content change. Method: Issues.

Input

Context

• Live repro: in ~/beagle-journal (the beagle submodule advanced 6 commits

  5b11dad9→9e80e5f0 past the journal's gitlink pin), be status shows:

       19:27  mod README.mkd
              mod beagle          <- NO timestamp
  

  Every file mod row carries a ts; the gitlink-advance row is blank.

• The classification is CORRECT (SUBS-027: R4 tip descends R1 pin → Advanced →

  mod). The RENDER is the defect: (a) no timestamp, (b) bare mod conflates an advanced gitlink (needs be put <sub> && be post) with a content modification.

• Render site: sniff/SNIFF.exe.c ~232–248 — the CLASS_BASE_ONLY + RON_s

  gitlink arm runs SUBSDirty and emits the mod row without stamping a ts.

Goals

• The advanced-submodule row carries a sensible timestamp (e.g. the sub tip's

  commit ts) consistent with file rows. Consider a distinct marker for "advanced" (gitlink bump pending) vs content mod — cf. the DIS-048 disapplied-marker semantics discussion (a wrong verb is worse than none).

Constraints

• Fix in the status gitlink-row emit (sniff/SNIFF.exe.c RON_s arm). Do NOT

  regress SUBS-027's advanced / stale / health classification. Repro-first.

WIP

Design decisions

• ts source for the gitlink row: the sub tip's commit ts (R4.base author

  wall-clock) via new read-only SNIFFSubTipTs — LANDED d7eaf5c4.

• marker (user 2026-06-22): an advanced-only sub (gitlink-bump pending)

  renders adv; a content-edited sub keeps mod. in progress

TODOs

• Repro-first ts test test/status/03-sub-advanced-mod-ts (red→green),

  fix the row emit, re-run status/sub suites. LANDED d7eaf5c4.

• Add an adv status verb; render advanced-only subs adv vs content

  mod (distinct from the ts fix). LANDED 69f51bd3. JS parity → JS-045.

Blockers

• None.

Outcome

• ts half LANDED d7eaf5c4 (stamp advanced-sub mod row with sub-tip

  commit ts); merged clean onto trunk past JS-035 / JS-036.

• adv-marker half LANDED 69f51bd3: new adv verb; advanced-only sub

  (SUBS_DIRTY_ADVANCED, EDITED clear) → adv, content edit → mod.

• JS-side parity follow-up filed: JS-045 (bin/lib/subs.js still maps

  advanced→mod; latent until jabc present).