docs(state): reconcile open issue/PR snapshot with the live tracker

[forkwright]

Problem

projects/akroasis/STATE.md is presenting a tracker snapshot that is already false enough to mislead an operator.

Evidence

• projects/akroasis/STATE.md:4-6 says: Phase 02 complete. No open issues, 2 open PRs ... Updated: 2026-04-22
• projects/akroasis/STATE.md:19-21 repeats 0 open issues.
• Live GitHub tracker currently shows open issues #112 and #113.
• Live GitHub PR list currently shows four open PRs (#105, #110, #114, #115), not two.

Why this violates the bar

Kanon-side state is supposed to compress live truth, not trail it by enough to give a false operational picture. This is separate from #113: that issue is about roadmap phase drift, while this one is about the basic tracker and queue snapshot being wrong.

Done criteria

• Update projects/akroasis/STATE.md so open issue / PR counts match the live tracker.
• Remove or restate any tracker snapshot text that is too volatile to keep honest.
• Make sure the Current phase summary and recent context do not imply a zero-backlog state while audit and roadmap issues are open.

[forkwright]

Migrated to forge: forkwright/akroasis#2 — canonical tracker is the kanon forge going forward. Closing here as superseded. Forge API: http://127.0.0.1:7878/api/v1/repos/forkwright/akroasis/issues/2

[forkwright]

2026-08-05 recurrence in the agent corpus

The same volatile-snapshot defect remains in _llm/current_state.toml even though the Kanon-side State refresh removes it from projects/akroasis/STATE.md.

• _llm/current_state.toml:11-13 says Phase 02 is complete with “no open issues” and is dated 2026-04-23.
• GitHub now has 25 open issues after CI has no build/test workflow — main broke silently under dependabot auto-merge #262 was correctly reopened; before that reopening it had 24, so the statement was already false independently of this review.
• The file declares generated = false while naming the Kanon State document as a source, which leaves a second hand-maintained projection with no derivation or freshness check.

This recurrence still violates the original done criterion to remove or restate tracker text too volatile to keep honest. The old forge migration target is no longer retrievable through the current tracker, so reopening the repository-visible issue for continuity. The correction should derive current facts or omit them; manually updating the count/date would only reset the drift clock.

[forkwright]

Reopening immediately after PR #394 auto-closed this issue. That PR corrected README truth only; its body explicitly said it did not close #116. The remaining acceptance is still unlanded: the duplicate _llm/current_state.toml snapshot must be removed or derived, and Kanon STATE/ROADMAP posture must stop mirroring stale tracker/phase claims. Keep this issue open until both paired repository changes pass CI, merge, and are verified on their default branches.

[forkwright]

Acceptance is now verified on both owning default branches.

• forkwright/kanon@d3d24b6945a50cba5b437c829023611ee2c7cc3e (PR
  forkwright/kanon#3551) replaces the stale phase/tracker posture with authored
  durable state, live plan owners, and no copied issue/PR counts.
• forkwright/akroasis@e6cff1e2c6fa00ee6886ca9f03dcaff62002ef9e
  (PR docs: remove duplicate mutable state snapshot #403) deletes _llm/current_state.toml and its llms.txt link, removing
  the second hand-maintained mutable snapshot.
• Both PR exact-head checks and every triggered post-merge default-branch
  workflow completed successfully. The Akroasis merge tree is byte-identical
  to the reviewed PR head.

Current issues, pull requests, releases, workspace membership, and phase
execution state now remain with their live GitHub/Kanon owners rather than a
manually refreshed count/date snapshot. This satisfies the original done
criteria and the later recurrence note, so I am closing the issue manually.