docs(ops): refresh current.md live truth (neo version coherence measured; TIN-3277/3299/3300)

[Jesssullivan]

Summary

Truth refresh for docs/ops/current.md only (Strategy-A queue item 10). Four corrections, each evidence-first, no new capability claims:

• Header: added a dated live-verification line — neo/honey rows re-measured 2026-07-29 via a read-only bilateral probe; source boundary text is otherwise unchanged.
• Fleet row / Closed and corrected: neo version coherence is now measured closed. which -a tcfs returns /Users/jess/.local/bin/tcfs then ~/.nix-profile/bin/tcfs, both v0.12.17; the daemon's gRPC status also reports v0.12.17 (measured 2026-07-29). This replaces the stale "effective interactive PATH still selects v0.12.12" claim. The residual defect is reframed as provenance, not version skew: /Users/jess/.local/bin/tcfs is an unmanaged, hand-placed binary (dated Jul 26) shadowing the home-manager symlink, and nothing keeps it converged going forward. Strategy-A queue item 2 is restated to match (quarantine target is the unmanaged binary path, framed as a provenance hazard).
• Agent-state posture row: added the reconcile-canary decay finding — the claude-projects reconcile canary has not run since 2026-06-08 on either host (neo launchd unit idle; honey cache mtime 2026-06-08). Tracked as TIN-3300; left as pending an operator revive-or-demote ruling rather than silently demoted.
• New "Live defect findings (2026-07-29)" subsection under the production-conflict-gate section, linking:
  • TIN-3277 — HM out-of-band writes to secrets/*/devices.json on neo bypass the vclock tick, producing permanent self-conflicts the reconciler cannot push.
  • TIN-3299 — honey: live hydration failure on fp-proof-hMn6.txt, 4,130 orphaned chunks, stale data/index entries, a second unaccounted worker daemon from /etc/tcfsd/config.toml, and plaintext HTTP observed live.
  • TIN-3300 — proof-liveness decay (see Agent-state row).

The TIN-2658 closeout chain, "Gates that remain red", and all other sections are untouched.

Test plan

• Reviewer confirms the diff touches only docs/ops/current.md
• Reviewer confirms claim-tier discipline (measured vs. still-open) matches the rest of the document's voice

[Jesssullivan]

[authority hold — 2026-07-30]

Source review can continue at exact head 5abd6027ee7b9e2fcd6d3741d126daabaf064c04 on base e7bfc1f01c3298c5ed6ad25254f6cc67d2a59213, but the displayed green suite is not sanctioned merge authority.

Every assigned job in runs 30507191383, 30507191394, and 30507191414 ran in the GitHub Actions group on ubuntu-latest, macos-14, or windows-latest. None ran on the required tinyland-* GloriousFlywheel infrastructure. Do not merge, rerun, or treat these hosted greens as durable evidence. Hold for the GF-owned runner authority correction and fresh natural exact-head CI on sanctioned labels.

[Jesssullivan]

[source-integrity fence — corrected 2026-07-30]

Both PR commits are unsigned: 316c9792cbcde0034bb66906f1cf277f84037e3b and exact head 5abd6027ee7b9e2fcd6d3741d126daabaf064c04 each report verification.reason=unsigned. The PR is draft for that source-integrity issue and the separately recorded hosted-only CI authority hold.

Keep this history unmergeable. Preserve the one-file source diff, but replace it through a signed composition path after CI authority is corrected; no force-push or hosted rerun is authorized here.

Correction: an earlier version of this comment incorrectly applied a Lab-repository PR-title convention to tummycrypt. That claim was false here and the original title has been restored.