claude.md: mark the Sleipnir AFK dispatch shape retired (2026-07-22)

/sleipnir-scaffold and /sleipnir-preflight were archived in galdrabok
9e2f59f and are no longer installed, but the AFK dispatch shape still
prescribed them. Mark the shape and the ready-for-agent gate as retired
and dormant, keep them as the record for a revival, and point at
/codex-dispatch as the one AFK skill still installed, which keeps the
prd:-pinned contract drift gate.

home_root/.claude/CLAUDE.md

@@ -477,7 +477,8 @@ draft attached and the recipient count named, and let the operator call it.
 
 Two end-to-end shapes for taking a unit of work from idea to landed.
 Pick by whether the work will be implemented by an AFK agent
-(Sleipnir dispatch) or directly in-session. Both front-load the same
+(Sleipnir dispatch — retired 2026-07-22, see below) or directly
+in-session. Both front-load the same
 deliberation — heid consult → contract → heid contract review →
 contract fixup — so the spec is sound before any code; they diverge
 only at the implementation handoff.
@@ -517,20 +518,31 @@ section is only as honest as the blast-radius pass behind it. (Lesson:
 a contract that names 3 files when the rip touches 6 is a scope miss
 the up-front pass would have caught.)
 
-### AFK dispatch shape (Sleipnir)
+### AFK dispatch shape (Sleipnir) — retired 2026-07-22
+
+⚠ **Retired from active use on 2026-07-22** (galdrabok `9e2f59f`).
+`/sleipnir-scaffold` and `/sleipnir-preflight` were moved to
+`galdrabok/archive/skills/` and are no longer installed, so steps 3
+and 7 below do not run as written. Sleipnir itself has dispatched no
+job since 2026-05-18, and no Sleipnir unit or process runs on nh3-dev.
+The shape stays here as the record for a revival. The only AFK
+dispatch skill still installed is `/codex-dispatch`, the opt-in
+Codex-first pilot (`brokkr-smithy/docs/codex-first-discipline.md`,
+v0.1 draft). It keeps the same `prd:`-pinned contract drift gate.
 
 For work an AFK agent will implement off a contract.
 
 1. Issue created.
 2. Heid consult on the issue (`/heid`) — pressure-test the framing.
-3. Scaffold the issue for AFK dispatch (`/sleipnir-scaffold <N>`) —
-   writes the `prd:`-pinned contract frontmatter.
+3. Scaffold the issue for AFK dispatch (`/sleipnir-scaffold <N>`,
+   **archived**) — writes the `prd:`-pinned contract frontmatter.
 4. Contract generation — the architect writes the contract body.
 5. Heid contract review (`/heid-contract-review`).
 6. Fixup the contract per triaged findings.
-7. Preflight + mark ready-for-agent (`/sleipnir-preflight <N>`) — the
-   irreversible dispatch authorization. See § "Issue → AFK dispatch
-   hygiene (Sleipnir)" for the gate's hard requirements.
+7. Preflight + mark ready-for-agent (`/sleipnir-preflight <N>`,
+   **archived**) — the irreversible dispatch authorization. See
+   § "Issue → AFK dispatch hygiene (Sleipnir)" for the gate's hard
+   requirements.
 
 ### Direct implementation shape — the House Code Discipline
 
@@ -1076,6 +1088,12 @@ directly into the SemVer "v1.0 = discipline-tightening event."
 
 ## Issue → AFK dispatch hygiene (Sleipnir)
 
+⚠ **The Sleipnir label gate is dormant** (see § "AFK dispatch shape
+(Sleipnir) — retired 2026-07-22"): nothing polls `ready-for-agent`
+today. The `prd:`-pinned contract requirement below still governs any
+AFK dispatch, including `/codex-dispatch`, which runs the same drift
+check before it posts.
+
 Before marking any issue `ready-for-agent` (the label that gates AFK
 dispatch via Sleipnir), it MUST have an issue-numbered contract at
 `docs/contracts/issues/<N>.contract.md` AND that contract MUST carry