v1.0.153 — ctx_stats UX cleanup
Hotfix following v1.0.152 (~1 hour ago).
Removed
→ ## Observability machine-readable block in ctx_stats output. The cache.hit_rate / index.total_chunks / index.total_sources / index.last_indexed_at footer was bleeding low-level diagnostics into the curated 5-section narrative report. Users saw an ungrouped block after the storytelling sections and asked "what is this?" — clear signal it didn't belong in the human-facing report.
The underlying state is still available:
ContentStore.getIndexState()API unchanged — useful for/ctx-doctoror future targeted surfaces.report.cache.hit_ratestill computed on theAnalyticsEnginereport — just not rendered.
Verification
renderObservabilityBlockhelper deleted + both call sites removed insrc/session/analytics.ts.- Regression guard added:
formatReportasserted to NEVER emit## Observabilityon either path (narrative or legacy), regardless ofindexState. - Grep across
src/hooks/scripts/for any Observability artifact → 0 matches. - Typecheck clean, full
tests/core/suite 920/922 (2 pre-existing unrelated env-cascade flakes).
Upgrade
/context-mode:ctx-upgrade
# then restart your sessionctx_stats output now ends cleanly at the v{VERSION} footer line — no machine-readable trailer.