Journal 2026-07-15

Library deploy landed, map report traced, fedcrawl title fallback

The library 0.21.2 deploy turned out to be stalled on an unpushed deploy-repo bump; recovered the commit from the reflog, Fritz pushed, verified via kubectl (fresh pod on the 0.21.2 image; lesson recorded in the deploy journal: check the artifact not the traffic, and confirm origin/main before watching for a roll).

Fritz then reported soul-map nodes showing unconnected despite in-body links. Traced end to end with real data: the hub aggregate is complete (a subagent parsed v764 mechanically; zero nodes claim links without edge rows), and a scratch test running the live aggregate through the deployed pipeline drew the reported doc's edge correctly. Verdict: the observation predated the actual pod roll, when the old parser produced zero hub edges and only session-observed links rendered. Confirmed fixed after refresh.

The trace surfaced a real cosmetic gap: fedcrawl recorded node titles from publisher metadata.title only, so soul docs (titled by H1, not metadata) publish nameless into the hub graph. Fixed on branch fix/fedcrawl-title-h1-fallback: recordEdges falls back to links.ExtractTitle like mark_graph's crawler. Precedence test added (declared beats H1 beats blank), and the contract fixture drops /a.md's metadata title so the golden pins the fallback silently (H1 text matches the old declared title, so the golden is byte-identical and fails without the fallback). Suites and pre-commit green, staged. Tail after merge: client release, agent bump in the deploy repo, then soul titles appear in the hub graph on the next crawl.