ok — an unmounted sub is invisibleFound 2026-07-14 on journal/be: jab status printed 91 ok and no status test hunk while be/test had lost its .be anchor (SUBS-053). A whole submodule had silently dropped out of the status view and the summary still read all-clean.
views/status/status.js:308-322 — const mounted = isMount(repo.wt, gl.path); an unmounted gitlink takes the else and lands in res.counts.ok++, indistinguishable from a clean file.views/status/status.js:432 — the recursion gate if (!s || !s.mounted) continue; drops the sub's own hunk, so nothing else hints at the loss.jab status test even answers 1 ok..gitmodules WITH a live 160000 gitlink but NO anchor is a broken tree state, not an ok one.test/.be in a clean clone reproduces the exact symptom (91 ok, no sub hunk); restoring the anchor brings the hunk back.isMount gate itself is correct (SUBS-049 shape, status.js:480-488) — the bug is the BUCKET an unmounted sub falls into, not the detection.be status reports for a declared-but-unmounted sub before picking the verb.mis-class verb), never a silent ok tally.jab status can't read all-clean over a lost mount.isMount detection shape (SUBS-049).else at status.js:310-311, split "declared + gitlink + no anchor" out of the ok bucket into its own row + counter; keep the recursion skip (there is no shard to recurse into).mis reads naturally (the mount is missing) but must be checked against native be status and the todo bucket table first.be status output for a declared-but-unmounted sub (parity target)rm the sub's .be, assert status does NOT report all-ok