`_llm/current_state.toml` is a stale manual snapshot presented as current agent context

[forkwright]

Finding

_llm/current_state.toml is hand-maintained (generated = false) but is presented through llms.txt as the repository's current phase, recent work, and open-thread authority. Its snapshot is months behind the repository and already contains tracker facts that are no longer true.

Evidence

• _llm/current_state.toml:10-13 describes Phase 3.5 and carries updated = "2026-05-05".
• The current default branch contains 222 commits after that date.
• Lines 23-30 list only two open threads. One uses sentinel issue = 0; the other points to GitHub epic: retire calibre — ebook parity in harmonia #214, which was closed on 2026-04-24 as migrated to a forge record.
• The [meta].source_docs entry still contains the unresolved placeholder <canonical-state-doc>/STATE.md, so the declared source is not replayable.

Why this matters

This file is a front-door agent corpus. Agents are told to use it instead of rediscovering repository topology, so stale phase and tracker projections actively manufacture wrong planning context. A manually refreshed date would only hide the structural defect until the next commit: mutable Git/tracker facts are being stored at a softer rung than their authorities, with no derivation or freshness witness.

Desired correction

Make current-state corpus data a derived artifact whose inputs are explicit Git, tracker, and canonical planning authorities, and fail a check when the rendered file differs. Keep only non-derivable judgment in an authored source.

Until that derivation exists, remove volatile counts, issue state, and dated recent-work narration from the discovery path in favor of live authoritative pointers. Resolve the canonical State locator and make the schema reject sentinel issue identifiers such as 0.