v0.5.62 — Observability Truth

v0.5.62 — Observability Truth

Deployed. Merge b434979ea68da0a2326ad3f62dac30888b93dfcd (PR #340; parents: public base 398700276c22230a9dc0a64ecd4196f43f921f07 + T-PASSED head 73b3fe2049f1764437d278d43b68a6bbc3f89bcb). Cloud Build e3ca9551-0292-4b02-9cbf-0cc2b92daa3e from the exact merge source; serving revision verifimind-mcp-server-00496-g7s at 100% traffic. Post-deploy live Trinity smoke through a raw Streamable-HTTP JSON-RPC session: X/Z/CS = real/real/real, quality gate passed, no degraded agents.

This release makes tool activation and completion budgets measurable without changing any validation behavior:

• tool_invoked run-lifecycle event — a name-only, allowlisted structured event at the tools/call boundary. Per-tool activation frequency is countable from logs for the first time; unknown names are never echoed, and no arguments, payloads, or user content are logged. Live-proven post-deploy (17 events captured in the first 48 hours).
• Effective-budget token monitors — Z and CS monitors now report the provider-effective completion reservation as ceiling while preserving configured_ceiling and disclosing ceiling_source. An admission-clamped budget is visible instead of masked; when a stage makes no provider call, the monitor reports a null ceiling rather than inventing one. First production receipt: a CS stage observed at 89.5% utilization of a 3,708-token effective ceiling (configured 8,192) — the previously invisible truncation mechanism, now measured.
• v0.5.61 release-receipt repair — README/CHANGELOG receipts corrected to deployed evidence; the public docs contract (280 checks) rejects prior merge/build/Registry identities.
• server.json encoding repair — the four double-encoded tool descriptions (escaped em-dash/arrow sequences rendering as mojibake on the MCP Registry) restored to the intended characters, riding this Registry manifest change (3.39.0).

No hosted-provider routing, runtime failover policy, provider catalogue, tool-availability policy, or dependency changes. The Trinity validation pipeline's behavior is unchanged; this release measures it.

Review chain: T S142 observability review → T S144 CodeQL cleanup EXACT-HEAD TECHNICAL PASS at ff24dc1 → Alton-authorized bounded release-identity commit 73b3fe2 (RNA S147) → T S146 exact-head rebind PASS → human merge and auto-deploy.