Reconcile with AgentKit v2026.10.07

AGENTS.md

@@ -26,17 +26,11 @@ tracks, applied to the instructions. One file, one answer.
 
 ## Writing a design-state record
 
-This repository has adopted **half** of the kit's `design/state/` system, and the half it did
-not adopt is the half this heading is about. What exists: `/agentkit:track`'s work-mirror
-(`design/state/work/`, one `WorkRef` per issue — `design/90-decisions.md`, 2026-08-24) and
-`design/state-index.md`, the projection over it (2026-09-05). What does not: `design/state/units/`,
-and every other record kind. There are no `Unit`, `Invariant`, `Contract`, `Decision` or
-`Question` records here, which is why five of the index's six regions render an empty-set
-placeholder and only `outstanding` carries rows.
-
-So the full record-writing sequence the kit's own `AGENTS.md` describes under this heading —
-appending to `90-decisions.md`, writing a decision record, updating unit records, regenerating
-projections — still does not apply. **Write the decision-log entry alone**, in
-`design/90-decisions.md`'s own register, in its existing format. Do not hand-write
-`design/state-index.md`: it is generated, `/agentkit:track` regenerates it, and an edit between two of
-its markers is discarded on the next run.
+The kit no longer ships `/agentkit:track`, `Test-DesignState.ps1` or `Update-DesignProjection.ps1`,
+so nothing regenerates this repository's `design/state/` records. What remains from the earlier
+half-adoption is the work-mirror (`design/state/work/`, one `WorkRef` per issue — `design/90-decisions.md`,
+2026-08-24) and `design/state-index.md`, the projection over it (2026-09-05); both are frozen as
+they stand until a separate decision retires them (`design/90-decisions.md`, 2026-10-07).
+
+**Write the decision-log entry alone**, in `design/90-decisions.md`'s own register, in its existing
+format. Do not hand-edit `design/state-index.md` or `design/state/`.

design/90-decisions.md

@@ -2211,3 +2211,9 @@ Reversibility: cheap. Restoring the copies is one checkout of `6a91aec`'s `.clau
 Context: `.claude/settings.json` ran `pwsh … tools/Measure-Session.ps1` on `SessionEnd`, but that script no longer exists — it left this repository when the kit moved to a single home install, and the kit later ported it to Node as `measure-session.ts` — so the hook failed at the end of every session. The kit's setup installs one global `SessionEnd` hook in `~/.claude/settings.json` that logs every project.
 Chosen: remove this repository's `hooks.SessionEnd` entry, in the AgentKit sync to `v2026.10.06.1`. Nothing else in `settings.json` changes.
 Rejected: point it at `measure-session.ts` — the global hook already runs that script, so every session would be logged twice; leave it — it keeps failing at every session end.
+
+### 2026-10-07 — Kit sync to `v2026.10.07`: the track/slice pipeline is retired, and the docs stop naming it
+Context: The kit's `v2026.10.07` ships thirteen commands (`interview`, `design`, `plan`, `next`, `fix`, `align`, `redteam`, `install`, `install-all`, `install-review`, `sync`, `brief`, `agentkit`) and no longer has `slice`, `check`, `pr`, `resolve`, `track`, `docs`, `hold`, `resume`, `help`, `tune`, `spec` or `clean`, nor `Test-DesignState.ps1` or `Update-DesignProjection.ps1`. `CLAUDE.md` and `AGENTS.md` still documented that pipeline, the `skills/<name>/SKILL-local.md` companions and the `design/state/` projection as live.
+Chosen: Delete the 14 `SKILL-local.md` files and the three kit-owned `tools/*.ps1` copies (`Test-DesignDrift.ps1` and its test, `Test-CIWorkflow.Tests.ps1`). Rewrite `CLAUDE.md`'s Design Freeze and Agent Kit sections and `AGENTS.md`'s design-state section to the current command set. The freeze stays, as a manual convention: `design/FROZEN.md` is written and lifted by hand. `design/state/` and `design/state-index.md` stay in place, orphaned, until a separate decision retires them.
+Rejected: **Leave the docs as written** — they point readers at commands that do not exist. **Retire the freeze with the commands that enforced it** — the reasoning for it (no fixed point while implementation is the bottleneck) still holds and a marker costs nothing. **Delete `design/state/` now** — that is a decision about the tracker mirror, not a transcription, and `design/20-contract.md`'s Design-state mechanics section names it. **Edit `design/20-contract.md` here** — it carries the same stale references (`Test-DesignState.ps1`, `Update-DesignProjection.ps1`, `/track`) and belongs to a `/agentkit:align` pass, not an install.
+Reversibility: cheap. The deletions and the prose are one revert of this change.