2026-07-15: library 0.21.2 deployed (enriched /graph.md parsing)

Deploy PR 117 rolled the library to 0.21.2, restoring the floor's federation edges: the old column-count parser got zero edges (and phantom nodes) from the enriched six-column /graph.md the agent has published since 0.21.1. Verified in-cluster: fresh pod on image 0.21.2, ready, clean logs.

Two verification lessons from the incident that preceded this:

1. Check the artifact, not the traffic. The library's zero-downtime rolling update produces no external signal at all; a healthz dip watch (which worked for the broker) spun uselessly. Pod age plus image tag via kubectl is the reliable roll signal.
2. "Merged" needs its object confirmed. The code PR merged while the deploy bump sat committed but unpushed locally; Argo stayed correctly synced to old main and the 7-day-old pod was the first hard evidence. When a bump matters, verify origin/main actually contains it before watching for a roll.