diff --git a/.agents/skills/ask-matt/PHASE-BOUNDARIES.md b/.agents/skills/ask-matt/PHASE-BOUNDARIES.md
new file mode 100644
index 00000000..cb31e6ab
--- /dev/null
+++ b/.agents/skills/ask-matt/PHASE-BOUNDARIES.md
@@ -0,0 +1,55 @@
+# Phase boundaries
+
+A **phase** is a chunk of work inside a session — the grilling, the implementation, the QA. The definition is fuzzy on purpose: a phase ends when you think *"ok, we're done with that"*.
+
+The **phase boundary** is the gap between two phases, and it is the only place this decision belongs. Mid-phase there is no decision to make — continue, or split the work that's left into subagents. Compacting mid-phase makes the agent lose the thread.
+
+## The five options
+
+| Option       | What it does                                                    |
+| ------------ | --------------------------------------------------------------- |
+| **Continue** | Stay in the session. No context switch at all.                    |
+| **`/clear`** | Empty the context window and start from nothing.                  |
+| **`/handoff`** | Write a portable markdown file and seed a session anywhere with it. |
+| **Subagent** | Send the task to its own context window and get a report back.     |
+| **`/compact`** | Compress this context and seed a fresh session with the summary.  |
+
+## The tree
+
+Work top to bottom at the boundary. The first **yes** wins.
+
+**1. Can you continue in this session?** Two things make the answer yes: the next phase needs this phase as a **primary source**, or you have enough [smart zone](https://www.aihero.dev/ai-coding-dictionary/smart-zone) left (~150k tokens) for the next phase to fit. Grilling → implementation is the standard yes: the implementation wants the reasoning verbatim, not a summary of it. Continue costs nothing and loses nothing, so rule it out before anything else.
+
+**2. Is the context irrelevant to what comes next?** Is everything in this session — the exploration, the decisions, the dead ends — disposable? If so, **`/clear`**. It is the cheapest move on the board: it takes no time and hands back the whole window. `/clear` also isn't terminal — the old session stays resumable.
+
+The cost of getting this wrong is one-way. Clear a *relevant* context and you lose the **why** behind what you built, and no amount of reading the diff back gets it returned.
+
+**3. Do you need to hand off?** `/handoff` is narrow. You need it only when you are:
+
+- swapping to a **new harness** (Claude → Codex),
+- moving to a **new directory** or repo,
+- sending the work to a **colleague**,
+- or forking a side task you found **mid-phase** without derailing what you're doing.
+
+That list is the whole clause. What `/handoff` buys is **portability** — a file that travels. If nothing is travelling, you don't need it.
+
+**4. Can the task be done AFK?** Is it scoped tightly enough to run with you away from the keyboard, no steering? Then send it to a **subagent** and leave this session untouched. Automated review is the standard case: the agent reads the diff and reports, and you aren't needed while it does.
+
+**5. Otherwise, `/compact`.** Relevant context, same harness, same directory, and you need to stay in the loop — this is where the tree lands, and it lands here often. Pass it an instruction (`/compact we're going to QA this area`) so the summary keeps what the next phase needs.
+
+`/compact` is the **default, not the first reach**. It sits at the bottom because the four questions above it are all cheaper or more precise. The failure mode when people start here is a fresh session that is confidently wrong about a decision the summary flattened.
+
+## Primary and secondary sources
+
+Every move except **Continue** turns a **primary source** into a **secondary source** — the session as it happened, replaced by a summary of it. The trade is always the same shape:
+
+| Source                            | Information | Noise | Room to move |
+| --------------------------------- | ----------- | ----- | ------------ |
+| Primary (Continue)                | Full        | Lots  | Little       |
+| Secondary (`/compact`, `/handoff`) | Lossy       | Less  | Lots         |
+
+This is why question 1 comes first. You only pay the lossiness when staying costs more than it saves.
+
+## These are judgement calls
+
+The questions are not objective — each has taste in it, and the same boundary can go two ways on two days. The value is in asking them **in order**, at the boundary rather than in the middle of the work.
diff --git a/.agents/skills/ask-matt/SKILL.md b/.agents/skills/ask-matt/SKILL.md
new file mode 100644
index 00000000..7f3ab782
--- /dev/null
+++ b/.agents/skills/ask-matt/SKILL.md
@@ -0,0 +1,90 @@
+---
+name: ask-matt
+description: Ask which skill or flow fits your situation. A router over the skills in this repo.
+disable-model-invocation: true
+---
+
+# Ask Matt
+
+You don't remember every skill, so ask.
+
+A **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.
+
+## The main flow: idea → ship
+
+The route most work travels. You have an idea and want it built.
+
+1. **`/grill-with-docs`** — sharpen the idea by interview. Start here whenever you are **working in a working directory**: it's stateful, retaining what it learns in `CONTEXT.md` and ADRs. (No working directory? Use `/grill-me` — see Standalone. Both run the same `/grilling` primitive; `grill-with-docs` is the one that leaves a paper trail, which makes it the better of the two whenever a repo is there to leave it in.)
+2. **Branch — can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`/handoff`** in both directions (a prototype lives in its own directory, which is exactly what `/handoff` is for — see Phase boundaries):
+   - **`/handoff`** out, then open a fresh session against that file,
+   - **`/prototype`** to answer the question with throwaway code,
+   - **`/handoff`** back what you learned, and reference it from the original idea thread.
+3. **Branch — is this a multi-session build?**
+   - **Yes** → **`/to-spec`** (turn the thread into a spec), then **`/to-tickets`** to split it into tracer-bullet tickets, each declaring its **blocking edges**. On a local tracker that's one file per ticket under `.scratch/<feature>/issues/`, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed — kick off **`/implement`** per ticket, **`/clear`ing context between each one**. Each ticket is self-contained, so the last one's context is disposable.
+   - **No** → **`/implement`** right here, in the same context window.
+
+   Either way, **`/implement`** builds each issue by driving **`/tdd`** internally — one red-green slice at a time — then closes out by running **`/code-review`**, a two-axis review (Standards + Spec) of the diff, before committing. Reach for **`/tdd`** on its own when you just want to build a concrete behaviour test-first without a full spec, and **`/code-review`** on its own whenever you want to review a branch or PR against a fixed point.
+
+### Context hygiene
+
+Keep steps 1–3 in **one unbroken context window** — don't compact or clear until after `/to-tickets` — so the grilling, spec, and tickets all build on the same thinking. Each `/implement` then starts fresh, working from the ticket.
+
+The limit on this is the **[smart zone](https://www.aihero.dev/ai-coding-dictionary/smart-zone)**: the window (~150k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `/to-tickets`, don't push on degraded — `/compact` at the nearest phase boundary and carry on (see Phase boundaries).
+
+## On-ramps
+
+A starting situation that generates work, then merges onto the main flow.
+
+- **Bugs and requests piling up** → **`/triage`**. It moves issues through triage roles and produces agent-ready issues, which **`/implement`** later picks up.
+
+  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Tickets that `/to-tickets` produced are already agent-ready, so **don't triage them**.
+
+- **Something's broken** → **`/diagnosing-bugs`**. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a **tight feedback loop** — one command that already goes red on *this* bug — then fixes with a regression test. Its post-mortem hands off to **`/improve-codebase-architecture`** when the real finding is that there's no good seam to lock the bug down.
+
+- **A huge, foggy effort — a greenfield project or a huge feature build, too big for one session** → **`/wayfinder`**, the most cognitively demanding flow here. When the way from here to the destination isn't visible yet, it charts a **shared map** of **decision tickets** on the issue tracker and resolves them one at a time — producing **decisions, not deliverables** — until the fog is pushed back and the way is clear. Where **`/grill-with-docs`** sharpens an idea you can hold in one session, wayfinder is for the idea you can't — and it's slower and denser, so save it for exactly that, never a well-scoped feature.
+
+  When the map clears, **it hands off, it doesn't build**: merge onto the main flow at **`/to-spec`**, which collapses the map's linked decisions into a buildable plan, then `/to-tickets` and `/implement` as usual. Looping the map straight into `/implement` skips that collapse and throws the linked detail away — go straight to `/implement` only when the effort turned out genuinely small.
+
+## Codebase health
+
+Not feature work — upkeep.
+
+- **`/improve-codebase-architecture`** — run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces **deepening opportunities**; picking one _generates an idea_ you can take into the main flow at `/grill-with-docs`. It's the survey that finds the candidates; **`/codebase-design`** (below) is the bench you design the chosen one on.
+
+## Vocabulary underneath
+
+Two model-invoked references that run *beneath* the other skills — each the single source of truth for its vocabulary. Reach for them directly when the **words**, not the process, are the problem; or let the skills above pull them in.
+
+- **`/domain-modeling`** — sharpen the project's *domain* language: challenge a fuzzy term, resolve an overloaded word ("account" doing three jobs), record a hard-to-reverse decision as an ADR. It's the active discipline `/grill-with-docs` drives to keep `CONTEXT.md` a clean glossary.
+- **`/codebase-design`** — the deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's *shape*: a lot of behaviour behind a small interface at a clean seam. `/tdd` and `/improve-codebase-architecture` both speak it.
+
+## Phase boundaries
+
+A **phase** is a chunk of work inside a session — the grilling, the implementation, the QA. At the **boundary** between two of them you have five options, and picking between them is the fuzziest decision in this whole map:
+
+- **Continue** — stay put. Costs nothing, loses nothing.
+- **`/clear`** — empty the window, when nothing here matters to what's next.
+- **`/handoff`** — write a portable markdown file. Narrow: only for a **new harness**, a **new directory**, a **colleague**, or forking a side task **mid-phase**. What it buys is portability.
+- **Subagent** — send a tightly-scoped task to its own window and get a report back.
+- **`/compact`** — compress this context and seed a fresh session with it. The **default**, at the bottom of the tree rather than the first reach.
+
+Read [PHASE-BOUNDARIES.md](PHASE-BOUNDARIES.md) for the ordered tree — the five questions, the reasoning behind each branch, and why the primary-source cost makes **Continue** the one to rule out first. Make the decision **at** a boundary; mid-phase, continue or split the rest into subagents.
+
+## Standalone
+
+Off the main flow entirely.
+
+- **`/grill-me`** — the same relentless interview as `/grill-with-docs`, but **stateless**: it saves nothing locally and builds no `CONTEXT.md`. Reach for it when you are **not working in a working directory** — sharpening a plan, a design, a piece of writing, anything with no repo under it. If you are in a working directory, use `/grill-with-docs` instead: it runs the same interview and leaves a paper trail, so it is strictly the better one.
+- **`/grilling`** — the interview primitive itself: rounds, the frontier, facts are the agent's job and decisions are yours. `/grill-me` and `/grill-with-docs` are the two named ways in, and `/triage`, `/wayfinder` and `/improve-codebase-architecture` all run it internally. Reach for it directly only when you want the interview with no wrapper around it.
+- **`/resolving-merge-conflicts`** — work an in-progress merge or rebase conflict hunk by hunk, resolving by **intent** traced to each side's primary source rather than by picking lines, then finish the operation. It never runs `--abort`. Standalone and off every flow: reach for it when you are already mid-conflict.
+- **`/prototype`** — a small, throwaway program that answers one design question: does this state model feel right, or what should this UI look like. Throwaway is a constraint on how the code is written, not a promise to destroy it: the answer folds into the real code, and the prototype itself is kept as a **primary source** on a `prototype/<name>` branch out of main, pointed at from the implementation issue. It's the detour in step 2 of the main flow, but reach for it any time a design question is hard to settle on paper.
+- **`/research`** — delegate reading legwork to a **background agent**: it investigates a question against **primary sources**, then leaves a cited Markdown file in the repo. Keep working while it reads. The file it produces is something to take *into* the main flow at `/grill-with-docs` — research feeds the thinking, it doesn't replace it.
+- **`/to-questionnaire`** — when the thing blocking you isn't in your head or the codebase but in **someone else's**, this writes them a questionnaire to fill in. It's the inverse of `/grill-me`: instead of interviewing you about the subject, it interviews you about the **send** — who it's going to, what you need back — and aims the questions at the gap. What comes back is material for `/grill-with-docs` or `/to-spec`.
+- **`/wizard`** — for the steps only a **human** can take: provisioning infrastructure, setting up credentials or CI secrets, clicking through an unfamiliar third-party dashboard, running a one-off migration or cutover. It generates an interactive bash script that opens each URL, captures each value, and writes it into `.env` and GitHub secrets — so the procedure stops being something you re-explain to an agent every time. Model-invoked, so the agent reaches for it the moment it hits a wall only you can pass. If the agent could just do it itself, it should; this is for where a human is genuinely in the loop.
+- **`/wait-what`** — the corrective for a message that didn't land. Use it mid-conversation, inside any other skill, and the agent re-pitches what it just said with the context you were missing, in plain English, using the `CONTEXT.md` vocabulary. It works after the fact; `/grill-with-docs` is the upfront cure, because a shared language agreed early is what stops the jargon arriving at all.
+- **`/teach`** — learn a concept over multiple sessions, using the current directory as a stateful workspace.
+- **`/writing-for-agents`** — reference for writing documents agents consume: skills, AGENTS.md, pointed-at docs.
+
+## Precondition
+
+**`/setup-matt-pocock-skills`** — run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.
diff --git a/.agents/skills/ask-matt/agents/openai.yaml b/.agents/skills/ask-matt/agents/openai.yaml
new file mode 100644
index 00000000..5c60d51b
--- /dev/null
+++ b/.agents/skills/ask-matt/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Ask Matt"
+  short_description: "Find the right skill or workflow"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/caveman/SKILL.md b/.agents/skills/caveman/SKILL.md
deleted file mode 100644
index 85770a38..00000000
--- a/.agents/skills/caveman/SKILL.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-name: caveman
-description: >
-  Ultra-compressed communication mode. Cuts token usage ~75% by dropping
-  filler, articles, and pleasantries while keeping full technical accuracy.
-  Use when user says "caveman mode", "talk like caveman", "use caveman",
-  "less tokens", "be brief", or invokes /caveman.
----
-
-Respond terse like smart caveman. All technical substance stay. Only fluff die.
-
-## Persistence
-
-ACTIVE EVERY RESPONSE once triggered. No revert after many turns. No filler drift. Still active if unsure. Off only when user says "stop caveman" or "normal mode".
-
-## Rules
-
-Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). Abbreviate common terms (DB/auth/config/req/res/fn/impl). Strip conjunctions. Use arrows for causality (X -> Y). One word when one word enough.
-
-Technical terms stay exact. Code blocks unchanged. Errors quoted exact.
-
-Pattern: `[thing] [action] [reason]. [next step].`
-
-Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."
-Yes: "Bug in auth middleware. Token expiry check use `<` not `<=`. Fix:"
-
-### Examples
-
-**"Why React component re-render?"**
-
-> Inline obj prop -> new ref -> re-render. `useMemo`.
-
-**"Explain database connection pooling."**
-
-> Pool = reuse DB conn. Skip handshake -> fast under load.
-
-## Auto-Clarity Exception
-
-Drop caveman temporarily for: security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread, user asks to clarify or repeats question. Resume caveman after clear part done.
-
-Example -- destructive op:
-
-> **Warning:** This will permanently delete all rows in the `users` table and cannot be undone.
->
-> ```sql
-> DROP TABLE users;
-> ```
->
-> Caveman resume. Verify backup exist first.
diff --git a/.agents/skills/code-review/SKILL.md b/.agents/skills/code-review/SKILL.md
new file mode 100644
index 00000000..62a18e4c
--- /dev/null
+++ b/.agents/skills/code-review/SKILL.md
@@ -0,0 +1,89 @@
+---
+name: code-review
+description: Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
+---
+
+Two-axis review of the diff between `HEAD` and a fixed point the user supplies:
+
+- **Standards** — does the code conform to this repo's documented coding standards?
+- **Spec** — does the code faithfully implement the originating issue / spec?
+
+Both axes run as **parallel sub-agents** so they don't pollute each other's context, then this skill aggregates their findings.
+
+The issue tracker should have been provided to you — run `/setup-matt-pocock-skills` if `docs/agents/issue-tracker.md` is missing.
+
+## Process
+
+### 1. Pin the fixed point
+
+Whatever the user said is the fixed point — a commit SHA, branch name, tag, `main`, `HEAD~5`, etc. If they didn't specify one, ask for it.
+
+Capture the diff command once: `git diff <fixed-point>...HEAD` (three-dot, so the comparison is against the merge-base). Also note the list of commits via `git log <fixed-point>..HEAD --oneline`.
+
+Before going further, confirm the fixed point resolves (`git rev-parse <fixed-point>`) and the diff is non-empty. A bad ref or empty diff should fail here — not inside two parallel sub-agents.
+
+### 2. Identify the spec source
+
+Look for the originating spec, in this order:
+
+1. Issue references in the commit messages (`#123`, `Closes #45`, GitLab `!67`, etc.) — fetch via the workflow in `docs/agents/issue-tracker.md`.
+2. A path the user passed as an argument.
+3. A spec file under `docs/`, `specs/`, or `.scratch/` matching the branch name or feature.
+4. If nothing is found, ask the user where the spec is. If they say there isn't one, the **Spec** sub-agent will skip and report "no spec available".
+
+### 3. Identify the standards sources
+
+Anything in the repo that documents how code should be written, such as `CODING_STANDARDS.md` or `CONTRIBUTING.md`.
+
+On top of whatever the repo documents, the Standards axis always carries the **smell baseline** below — a fixed set of Fowler code smells (_Refactoring_, ch.3) that applies even when a repo documents nothing. Two rules bind it:
+
+- **The repo overrides.** A documented repo standard always wins; where it endorses something the baseline would flag, suppress the smell.
+- **Always a judgement call.** Each smell is a labelled heuristic ("possible Feature Envy"), never a hard violation — and, like any standard here, skip anything tooling already enforces.
+
+Each smell reads *what it is* → *how to fix*; match it against the diff:
+
+- **Mysterious Name** — a function, variable, or type whose name doesn't reveal what it does or holds. → rename it; if no honest name comes, the design's murky.
+- **Duplicated Code** — the same logic shape appears in more than one hunk or file in the change. → extract the shared shape, call it from both.
+- **Feature Envy** — a method that reaches into another object's data more than its own. → move the method onto the data it envies.
+- **Data Clumps** — the same few fields or params keep travelling together (a type wanting to be born). → bundle them into one type, pass that.
+- **Primitive Obsession** — a primitive or string standing in for a domain concept that deserves its own type. → give the concept its own small type.
+- **Repeated Switches** — the same `switch`/`if`-cascade on the same type recurs across the change. → replace with polymorphism, or one map both sites share.
+- **Shotgun Surgery** — one logical change forces scattered edits across many files in the diff. → gather what changes together into one module.
+- **Divergent Change** — one file or module is edited for several unrelated reasons. → split so each module changes for one reason.
+- **Speculative Generality** — abstraction, parameters, or hooks added for needs the spec doesn't have. → delete it; inline back until a real need shows.
+- **Message Chains** — long `a.b().c().d()` navigation the caller shouldn't depend on. → hide the walk behind one method on the first object.
+- **Middle Man** — a class or function that mostly just delegates onward. → cut it, call the real target direct.
+- **Refused Bequest** — a subclass or implementer that ignores or overrides most of what it inherits. → drop the inheritance, use composition.
+
+### 4. Spawn both sub-agents in parallel
+
+Send a single message with two `Agent` tool calls. Use the `general-purpose` subagent for both.
+
+**Standards sub-agent prompt** — include:
+
+- The full diff command and commit list.
+- The list of standards-source files you found in step 3, **plus the smell baseline from step 3** pasted in full — the sub-agent has no other access to it.
+- The brief: "Report — per file/hunk where relevant — (a) every place the diff violates a documented standard: cite the standard (file + the rule); and (b) any baseline smell you spot: name it and quote the hunk. Distinguish hard violations from judgement calls — documented-standard breaches can be hard, but baseline smells are always judgement calls, and a documented repo standard overrides the baseline. Skip anything tooling enforces. Under 400 words."
+
+**Spec sub-agent prompt** — include:
+
+- The diff command and commit list.
+- The path or fetched contents of the spec.
+- The brief: "Report: (a) requirements the spec asked for that are missing or partial; (b) behaviour in the diff that wasn't asked for (scope creep); (c) requirements that look implemented but where the implementation looks wrong. Quote the spec line for each finding. Under 400 words."
+
+If the spec is missing, skip the Spec sub-agent and note this in the final report.
+
+### 5. Aggregate
+
+Present the two reports under `## Standards` and `## Spec` headings, verbatim or lightly cleaned. Do **not** merge or rerank findings — the two axes are deliberately separate (see _Why two axes_).
+
+End with a one-line summary: total findings per axis, and the worst issue _within each axis_ (if any). Don't pick a single winner across axes — that's the reranking the separation exists to prevent.
+
+## Why two axes
+
+A change can pass one axis and fail the other:
+
+- Code that follows every standard but implements the wrong thing → **Standards pass, Spec fail.**
+- Code that does exactly what the issue asked but breaks the project's conventions → **Spec pass, Standards fail.**
+
+Reporting them separately stops one axis from masking the other.
diff --git a/.agents/skills/code-review/agents/openai.yaml b/.agents/skills/code-review/agents/openai.yaml
new file mode 100644
index 00000000..9076774b
--- /dev/null
+++ b/.agents/skills/code-review/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "Code Review"
+  short_description: "Review a diff on standards and spec"
diff --git a/.agents/skills/codebase-design/agents/openai.yaml b/.agents/skills/codebase-design/agents/openai.yaml
new file mode 100644
index 00000000..3180715e
--- /dev/null
+++ b/.agents/skills/codebase-design/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "Codebase Design"
+  short_description: "Vocabulary for deep-module design"
diff --git a/.agents/skills/diagnose/SKILL.md b/.agents/skills/diagnosing-bugs/SKILL.md
similarity index 70%
rename from .agents/skills/diagnose/SKILL.md
rename to .agents/skills/diagnosing-bugs/SKILL.md
index ed55bda2..f400de7c 100644
--- a/.agents/skills/diagnose/SKILL.md
+++ b/.agents/skills/diagnosing-bugs/SKILL.md
@@ -1,17 +1,17 @@
 ---
-name: diagnose
-description: Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
+name: diagnosing-bugs
+description: Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
 ---
 
-# Diagnose
+# Diagnosing Bugs
 
 A discipline for hard bugs. Skip phases only when explicitly justified.
 
-When exploring the codebase, use the project's domain glossary to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.
+When exploring the codebase, read `CONTEXT.md` (if it exists) to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.
 
 ## Phase 1 — Build a feedback loop
 
-**This is the skill.** Everything else is mechanical. If you have a fast, deterministic, agent-runnable pass/fail signal for the bug, you will find the cause — bisection, hypothesis-testing, and instrumentation all just consume that signal. If you don't have one, no amount of staring at code will save you.
+**This is the skill.** Everything else is mechanical. If you have a **tight** pass/fail signal for the bug — one that goes red on _this_ bug — you will find the cause; bisection, hypothesis-testing, and instrumentation all just consume it. If you don't have one, no amount of staring at code will save you.
 
 Spend disproportionate effort here. **Be aggressive. Be creative. Refuse to give up.**
 
@@ -30,15 +30,15 @@ Spend disproportionate effort here. **Be aggressive. Be creative. Refuse to give
 
 Build the right feedback loop, and the bug is 90% fixed.
 
-### Iterate on the loop itself
+### Tighten the loop
 
-Treat the loop as a product. Once you have _a_ loop, ask:
+Treat the loop as a product. Once you have _a_ loop, **tighten** it:
 
 - Can I make it faster? (Cache setup, skip unrelated init, narrow the test scope.)
 - Can I make the signal sharper? (Assert on the specific symptom, not "didn't crash".)
 - Can I make it more deterministic? (Pin time, seed RNG, isolate filesystem, freeze network.)
 
-A 30-second flaky loop is barely better than no loop. A 2-second deterministic loop is a debugging superpower.
+A 30-second flaky loop is barely better than no loop; a 2-second deterministic one is tight — a debugging superpower.
 
 ### Non-deterministic bugs
 
@@ -48,11 +48,20 @@ The goal is not a clean repro but a **higher reproduction rate**. Loop the trigg
 
 Stop and say so explicitly. List what you tried. Ask the user for: (a) access to whatever environment reproduces it, (b) a captured artifact (HAR file, log dump, core dump, screen recording with timestamps), or (c) permission to add temporary production instrumentation. Do **not** proceed to hypothesise without a loop.
 
-Do not proceed to Phase 2 until you have a loop you believe in.
+### Completion criterion — a tight loop that goes red
 
-## Phase 2 — Reproduce
+Phase 1 is done when the loop is **tight** and **red-capable**: you can name **one command** — a script path, a test invocation, a curl — that you have **already run at least once** (paste the invocation and its output), and that is:
 
-Run the loop. Watch the bug appear.
+- [ ] **Red-capable** — it drives the actual bug code path and asserts the **user's exact symptom**, so it can go red on this bug and green once fixed. Not "runs without erroring" — it must be able to _catch this specific bug_.
+- [ ] **Deterministic** — same verdict every run (flaky bugs: a pinned, high reproduction rate, per above).
+- [ ] **Fast** — seconds, not minutes.
+- [ ] **Agent-runnable** — you can run it unattended; a human in the loop only via `scripts/hitl-loop.template.sh`.
+
+If you catch yourself reading code to build a theory before this command exists, **stop — jumping straight to a hypothesis is the exact failure this skill prevents.** No red-capable command, no Phase 2.
+
+## Phase 2 — Reproduce + minimise
+
+Run the loop. Watch it go red — the bug appears.
 
 Confirm:
 
@@ -60,7 +69,15 @@ Confirm:
 - [ ] The failure is reproducible across multiple runs (or, for non-deterministic bugs, reproducible at a high enough rate to debug against).
 - [ ] You have captured the exact symptom (error message, wrong output, slow timing) so later phases can verify the fix actually addresses it.
 
-Do not proceed until you reproduce the bug.
+### Minimise
+
+Once it's red, shrink the repro to the **smallest scenario that still goes red**. Cut inputs, callers, config, data, and steps **one at a time**, re-running the loop after each cut — keep only what's load-bearing for the failure.
+
+Why bother: a minimal repro shrinks the hypothesis space in Phase 3 (fewer moving parts left to suspect) and becomes the clean regression test in Phase 5.
+
+Done when **every remaining element is load-bearing** — removing any one of them makes the loop go green.
+
+Do not proceed until you have reproduced **and** minimised.
 
 ## Phase 3 — Hypothesise
 
diff --git a/.agents/skills/diagnosing-bugs/agents/openai.yaml b/.agents/skills/diagnosing-bugs/agents/openai.yaml
new file mode 100644
index 00000000..a13a755a
--- /dev/null
+++ b/.agents/skills/diagnosing-bugs/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "Diagnosing Bugs"
+  short_description: "Diagnose hard bugs and regressions"
diff --git a/.agents/skills/diagnose/scripts/hitl-loop.template.sh b/.agents/skills/diagnosing-bugs/scripts/hitl-loop.template.sh
similarity index 100%
rename from .agents/skills/diagnose/scripts/hitl-loop.template.sh
rename to .agents/skills/diagnosing-bugs/scripts/hitl-loop.template.sh
diff --git a/.agents/skills/domain-modeling/agents/openai.yaml b/.agents/skills/domain-modeling/agents/openai.yaml
new file mode 100644
index 00000000..7f1522d2
--- /dev/null
+++ b/.agents/skills/domain-modeling/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "Domain Modeling"
+  short_description: "Build and sharpen a domain model"
diff --git a/.agents/skills/git-guardrails-claude-code/SKILL.md b/.agents/skills/git-guardrails-claude-code/SKILL.md
new file mode 100644
index 00000000..d943c682
--- /dev/null
+++ b/.agents/skills/git-guardrails-claude-code/SKILL.md
@@ -0,0 +1,95 @@
+---
+name: git-guardrails-claude-code
+description: Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
+---
+
+# Setup Git Guardrails
+
+Sets up a PreToolUse hook that intercepts and blocks dangerous git commands before Claude executes them.
+
+## What Gets Blocked
+
+- `git push` (all variants including `--force`)
+- `git reset --hard`
+- `git clean -f` / `git clean -fd`
+- `git branch -D`
+- `git checkout .` / `git restore .`
+
+When blocked, Claude sees a message telling it that it does not have authority to access these commands.
+
+## Steps
+
+### 1. Ask scope
+
+Ask the user: install for **this project only** (`.claude/settings.json`) or **all projects** (`~/.claude/settings.json`)?
+
+### 2. Copy the hook script
+
+The bundled script is at: [scripts/block-dangerous-git.sh](scripts/block-dangerous-git.sh)
+
+Copy it to the target location based on scope:
+
+- **Project**: `.claude/hooks/block-dangerous-git.sh`
+- **Global**: `~/.claude/hooks/block-dangerous-git.sh`
+
+Make it executable with `chmod +x`.
+
+### 3. Add hook to settings
+
+Add to the appropriate settings file:
+
+**Project** (`.claude/settings.json`):
+
+```json
+{
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/block-dangerous-git.sh"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+**Global** (`~/.claude/settings.json`):
+
+```json
+{
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "~/.claude/hooks/block-dangerous-git.sh"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+If the settings file already exists, merge the hook into existing `hooks.PreToolUse` array — don't overwrite other settings.
+
+### 4. Ask about customization
+
+Ask if user wants to add or remove any patterns from the blocked list. Edit the copied script accordingly.
+
+### 5. Verify
+
+Run a quick test:
+
+```bash
+echo '{"tool_input":{"command":"git push origin main"}}' | <path-to-script>
+```
+
+Should exit with code 2 and print a BLOCKED message to stderr.
diff --git a/.agents/skills/git-guardrails-claude-code/agents/openai.yaml b/.agents/skills/git-guardrails-claude-code/agents/openai.yaml
new file mode 100644
index 00000000..3f5d756f
--- /dev/null
+++ b/.agents/skills/git-guardrails-claude-code/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "Git Guardrails for Claude Code"
+  short_description: "Block dangerous git commands"
diff --git a/.agents/skills/git-guardrails-claude-code/scripts/block-dangerous-git.sh b/.agents/skills/git-guardrails-claude-code/scripts/block-dangerous-git.sh
new file mode 100755
index 00000000..c40b59cb
--- /dev/null
+++ b/.agents/skills/git-guardrails-claude-code/scripts/block-dangerous-git.sh
@@ -0,0 +1,25 @@
+#!/bin/bash
+
+INPUT=$(cat)
+COMMAND=$(echo "$INPUT" | jq -r '.tool_input.command')
+
+DANGEROUS_PATTERNS=(
+  "git push"
+  "git reset --hard"
+  "git clean -fd"
+  "git clean -f"
+  "git branch -D"
+  "git checkout \."
+  "git restore \."
+  "push --force"
+  "reset --hard"
+)
+
+for pattern in "${DANGEROUS_PATTERNS[@]}"; do
+  if echo "$COMMAND" | grep -qE "$pattern"; then
+    echo "BLOCKED: '$COMMAND' matches dangerous pattern '$pattern'. The user has prevented you from doing this." >&2
+    exit 2
+  fi
+done
+
+exit 0
diff --git a/.agents/skills/grill-me/SKILL.md b/.agents/skills/grill-me/SKILL.md
index bd04394c..9470cfcf 100644
--- a/.agents/skills/grill-me/SKILL.md
+++ b/.agents/skills/grill-me/SKILL.md
@@ -1,10 +1,7 @@
 ---
 name: grill-me
-description: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
+description: A relentless interview to sharpen a plan or design.
+disable-model-invocation: true
 ---
 
-Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
-
-Ask the questions one at a time.
-
-If a question can be answered by exploring the codebase, explore the codebase instead.
+Run a `/grilling` session.
diff --git a/.agents/skills/grill-me/agents/openai.yaml b/.agents/skills/grill-me/agents/openai.yaml
new file mode 100644
index 00000000..4d6fb0c7
--- /dev/null
+++ b/.agents/skills/grill-me/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Grill Me"
+  short_description: "Sharpen a plan through interview"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/grill-with-docs/ADR-FORMAT.md b/.agents/skills/grill-with-docs/ADR-FORMAT.md
deleted file mode 100644
index da7e78ec..00000000
--- a/.agents/skills/grill-with-docs/ADR-FORMAT.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# ADR Format
-
-ADRs live in `docs/adr/` and use sequential numbering: `0001-slug.md`, `0002-slug.md`, etc.
-
-Create the `docs/adr/` directory lazily — only when the first ADR is needed.
-
-## Template
-
-```md
-# {Short title of the decision}
-
-{1-3 sentences: what's the context, what did we decide, and why.}
-```
-
-That's it. An ADR can be a single paragraph. The value is in recording *that* a decision was made and *why* — not in filling out sections.
-
-## Optional sections
-
-Only include these when they add genuine value. Most ADRs won't need them.
-
-- **Status** frontmatter (`proposed | accepted | deprecated | superseded by ADR-NNNN`) — useful when decisions are revisited
-- **Considered Options** — only when the rejected alternatives are worth remembering
-- **Consequences** — only when non-obvious downstream effects need to be called out
-
-## Numbering
-
-Scan `docs/adr/` for the highest existing number and increment by one.
-
-## When to offer an ADR
-
-All three of these must be true:
-
-1. **Hard to reverse** — the cost of changing your mind later is meaningful
-2. **Surprising without context** — a future reader will look at the code and wonder "why on earth did they do it this way?"
-3. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons
-
-If a decision is easy to reverse, skip it — you'll just reverse it. If it's not surprising, nobody will wonder why. If there was no real alternative, there's nothing to record beyond "we did the obvious thing."
-
-### What qualifies
-
-- **Architectural shape.** "We're using a monorepo." "The write model is event-sourced, the read model is projected into Postgres."
-- **Integration patterns between contexts.** "Ordering and Billing communicate via domain events, not synchronous HTTP."
-- **Technology choices that carry lock-in.** Database, message bus, auth provider, deployment target. Not every library — just the ones that would take a quarter to swap out.
-- **Boundary and scope decisions.** "Customer data is owned by the Customer context; other contexts reference it by ID only." The explicit no-s are as valuable as the yes-s.
-- **Deliberate deviations from the obvious path.** "We're using manual SQL instead of an ORM because X." Anything where a reasonable reader would assume the opposite. These stop the next engineer from "fixing" something that was deliberate.
-- **Constraints not visible in the code.** "We can't use AWS because of compliance requirements." "Response times must be under 200ms because of the partner API contract."
-- **Rejected alternatives when the rejection is non-obvious.** If you considered GraphQL and picked REST for subtle reasons, record it — otherwise someone will suggest GraphQL again in six months.
diff --git a/.agents/skills/grill-with-docs/CONTEXT-FORMAT.md b/.agents/skills/grill-with-docs/CONTEXT-FORMAT.md
deleted file mode 100644
index ddfa247c..00000000
--- a/.agents/skills/grill-with-docs/CONTEXT-FORMAT.md
+++ /dev/null
@@ -1,77 +0,0 @@
-# CONTEXT.md Format
-
-## Structure
-
-```md
-# {Context Name}
-
-{One or two sentence description of what this context is and why it exists.}
-
-## Language
-
-**Order**:
-{A concise description of the term}
-_Avoid_: Purchase, transaction
-
-**Invoice**:
-A request for payment sent to a customer after delivery.
-_Avoid_: Bill, payment request
-
-**Customer**:
-A person or organization that places orders.
-_Avoid_: Client, buyer, account
-
-## Relationships
-
-- An **Order** produces one or more **Invoices**
-- An **Invoice** belongs to exactly one **Customer**
-
-## Example dialogue
-
-> **Dev:** "When a **Customer** places an **Order**, do we create the **Invoice** immediately?"
-> **Domain expert:** "No — an **Invoice** is only generated once a **Fulfillment** is confirmed."
-
-## Flagged ambiguities
-
-- "account" was used to mean both **Customer** and **User** — resolved: these are distinct concepts.
-```
-
-## Rules
-
-- **Be opinionated.** When multiple words exist for the same concept, pick the best one and list the others as aliases to avoid.
-- **Flag conflicts explicitly.** If a term is used ambiguously, call it out in "Flagged ambiguities" with a clear resolution.
-- **Keep definitions tight.** One sentence max. Define what it IS, not what it does.
-- **Show relationships.** Use bold term names and express cardinality where obvious.
-- **Only include terms specific to this project's context.** General programming concepts (timeouts, error types, utility patterns) don't belong even if the project uses them extensively. Before adding a term, ask: is this a concept unique to this context, or a general programming concept? Only the former belongs.
-- **Group terms under subheadings** when natural clusters emerge. If all terms belong to a single cohesive area, a flat list is fine.
-- **Write an example dialogue.** A conversation between a dev and a domain expert that demonstrates how the terms interact naturally and clarifies boundaries between related concepts.
-
-## Single vs multi-context repos
-
-**Single context (most repos):** One `CONTEXT.md` at the repo root.
-
-**Multiple contexts:** A `CONTEXT-MAP.md` at the repo root lists the contexts, where they live, and how they relate to each other:
-
-```md
-# Context Map
-
-## Contexts
-
-- [Ordering](./src/ordering/CONTEXT.md) — receives and tracks customer orders
-- [Billing](./src/billing/CONTEXT.md) — generates invoices and processes payments
-- [Fulfillment](./src/fulfillment/CONTEXT.md) — manages warehouse picking and shipping
-
-## Relationships
-
-- **Ordering → Fulfillment**: Ordering emits `OrderPlaced` events; Fulfillment consumes them to start picking
-- **Fulfillment → Billing**: Fulfillment emits `ShipmentDispatched` events; Billing consumes them to generate invoices
-- **Ordering ↔ Billing**: Shared types for `CustomerId` and `Money`
-```
-
-The skill infers which structure applies:
-
-- If `CONTEXT-MAP.md` exists, read it to find contexts
-- If only a root `CONTEXT.md` exists, single context
-- If neither exists, create a root `CONTEXT.md` lazily when the first term is resolved
-
-When multiple contexts exist, infer which one the current topic relates to. If unclear, ask.
diff --git a/.agents/skills/grill-with-docs/SKILL.md b/.agents/skills/grill-with-docs/SKILL.md
index 5ea0aa91..bed05d2b 100644
--- a/.agents/skills/grill-with-docs/SKILL.md
+++ b/.agents/skills/grill-with-docs/SKILL.md
@@ -1,88 +1,7 @@
 ---
 name: grill-with-docs
-description: Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
+description: A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
+disable-model-invocation: true
 ---
 
-<what-to-do>
-
-Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
-
-Ask the questions one at a time, waiting for feedback on each question before continuing.
-
-If a question can be answered by exploring the codebase, explore the codebase instead.
-
-</what-to-do>
-
-<supporting-info>
-
-## Domain awareness
-
-During codebase exploration, also look for existing documentation:
-
-### File structure
-
-Most repos have a single context:
-
-```
-/
-├── CONTEXT.md
-├── docs/
-│   └── adr/
-│       ├── 0001-event-sourced-orders.md
-│       └── 0002-postgres-for-write-model.md
-└── src/
-```
-
-If a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:
-
-```
-/
-├── CONTEXT-MAP.md
-├── docs/
-│   └── adr/                          ← system-wide decisions
-├── src/
-│   ├── ordering/
-│   │   ├── CONTEXT.md
-│   │   └── docs/adr/                 ← context-specific decisions
-│   └── billing/
-│       ├── CONTEXT.md
-│       └── docs/adr/
-```
-
-Create files lazily — only when you have something to write. If no `CONTEXT.md` exists, create one when the first term is resolved. If no `docs/adr/` exists, create it when the first ADR is needed.
-
-## During the session
-
-### Challenge against the glossary
-
-When the user uses a term that conflicts with the existing language in `CONTEXT.md`, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"
-
-### Sharpen fuzzy language
-
-When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."
-
-### Discuss concrete scenarios
-
-When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.
-
-### Cross-reference with code
-
-When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?"
-
-### Update CONTEXT.md inline
-
-When a term is resolved, update `CONTEXT.md` right there. Don't batch these up — capture them as they happen. Use the format in [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md).
-
-`CONTEXT.md` should be totally devoid of implementation details. Do not treat `CONTEXT.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.
-
-### Offer ADRs sparingly
-
-Only offer to create an ADR when all three are true:
-
-1. **Hard to reverse** — the cost of changing your mind later is meaningful
-2. **Surprising without context** — a future reader will wonder "why did they do it this way?"
-3. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons
-
-If any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](./ADR-FORMAT.md).
-
-</supporting-info>
+Run a `/grilling` session, using the `/domain-modeling` skill.
diff --git a/.agents/skills/grill-with-docs/agents/openai.yaml b/.agents/skills/grill-with-docs/agents/openai.yaml
new file mode 100644
index 00000000..5dbe2780
--- /dev/null
+++ b/.agents/skills/grill-with-docs/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Grill with Docs"
+  short_description: "Grill a design and write its docs"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/grilling/SKILL.md b/.agents/skills/grilling/SKILL.md
index fe3569db..95bd01ee 100644
--- a/.agents/skills/grilling/SKILL.md
+++ b/.agents/skills/grilling/SKILL.md
@@ -1,10 +1,22 @@
 ---
 name: grilling
-description: Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
+description: Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
 ---
 
-Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
+Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: every decision branches into the decisions that hang off it.
 
-Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
+Work the tree in **rounds**. The **frontier** is every decision whose prerequisites are already settled — the questions you can ask _now_ without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round.
 
-If a question can be answered by exploring the codebase, explore the codebase instead.
+Each question should be formatted like so:
+
+```
+❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
+
+➡️ <your recommended answer>
+```
+
+Each round the user answers reshapes the tree — settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a _later_ round, not this one.
+
+Finding _facts_ is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it — don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report — ask the rest of the frontier now. The _decisions_ are the user's — put each to them and wait.
+
+The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.
diff --git a/.agents/skills/grilling/agents/openai.yaml b/.agents/skills/grilling/agents/openai.yaml
new file mode 100644
index 00000000..ddbdb961
--- /dev/null
+++ b/.agents/skills/grilling/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "Grilling"
+  short_description: "Stress-test thinking a round of questions at a time"
diff --git a/.agents/skills/handoff/SKILL.md b/.agents/skills/handoff/SKILL.md
index 28bfb3ab..043d9e13 100644
--- a/.agents/skills/handoff/SKILL.md
+++ b/.agents/skills/handoff/SKILL.md
@@ -2,12 +2,15 @@
 name: handoff
 description: Compact the current conversation into a handoff document for another agent to pick up.
 argument-hint: "What will the next session be used for?"
+disable-model-invocation: true
 ---
 
-Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it to a path produced by `mktemp -t handoff-XXXXXX.md` (read the file before you write to it).
+Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.
 
-Suggest the skills to be used, if any, by the next session.
+Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
 
-Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
+Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
+
+Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
 
 If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
diff --git a/.agents/skills/handoff/agents/openai.yaml b/.agents/skills/handoff/agents/openai.yaml
new file mode 100644
index 00000000..6e1d8da1
--- /dev/null
+++ b/.agents/skills/handoff/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Handoff"
+  short_description: "Compact a conversation into a handoff"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/implement/SKILL.md b/.agents/skills/implement/SKILL.md
new file mode 100644
index 00000000..7a0b11f5
--- /dev/null
+++ b/.agents/skills/implement/SKILL.md
@@ -0,0 +1,15 @@
+---
+name: implement
+description: "Implement a piece of work based on a spec or set of tickets."
+disable-model-invocation: true
+---
+
+Implement the work described by the user in the spec or tickets.
+
+Use /tdd where possible, at pre-agreed seams.
+
+Run typechecking regularly, single test files regularly, and the full test suite once at the end.
+
+Once done, use /code-review to review the work.
+
+Commit your work to the current branch.
diff --git a/.agents/skills/implement/agents/openai.yaml b/.agents/skills/implement/agents/openai.yaml
new file mode 100644
index 00000000..f8794dc1
--- /dev/null
+++ b/.agents/skills/implement/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Implement"
+  short_description: "Build work from a spec or tickets"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/improve-codebase-architecture/DEEPENING.md b/.agents/skills/improve-codebase-architecture/DEEPENING.md
deleted file mode 100644
index ecaf5d7d..00000000
--- a/.agents/skills/improve-codebase-architecture/DEEPENING.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# Deepening
-
-How to deepen a cluster of shallow modules safely, given its dependencies. Assumes the vocabulary in [LANGUAGE.md](LANGUAGE.md) — **module**, **interface**, **seam**, **adapter**.
-
-## Dependency categories
-
-When assessing a candidate for deepening, classify its dependencies. The category determines how the deepened module is tested across its seam.
-
-### 1. In-process
-
-Pure computation, in-memory state, no I/O. Always deepenable — merge the modules and test through the new interface directly. No adapter needed.
-
-### 2. Local-substitutable
-
-Dependencies that have local test stand-ins (PGLite for Postgres, in-memory filesystem). Deepenable if the stand-in exists. The deepened module is tested with the stand-in running in the test suite. The seam is internal; no port at the module's external interface.
-
-### 3. Remote but owned (Ports & Adapters)
-
-Your own services across a network boundary (microservices, internal APIs). Define a **port** (interface) at the seam. The deep module owns the logic; the transport is injected as an **adapter**. Tests use an in-memory adapter. Production uses an HTTP/gRPC/queue adapter.
-
-Recommendation shape: *"Define a port at the seam, implement an HTTP adapter for production and an in-memory adapter for testing, so the logic sits in one deep module even though it's deployed across a network."*
-
-### 4. True external (Mock)
-
-Third-party services (Stripe, Twilio, etc.) you don't control. The deepened module takes the external dependency as an injected port; tests provide a mock adapter.
-
-## Seam discipline
-
-- **One adapter means a hypothetical seam. Two adapters means a real one.** Don't introduce a port unless at least two adapters are justified (typically production + test). A single-adapter seam is just indirection.
-- **Internal seams vs external seams.** A deep module can have internal seams (private to its implementation, used by its own tests) as well as the external seam at its interface. Don't expose internal seams through the interface just because tests use them.
-
-## Testing strategy: replace, don't layer
-
-- Old unit tests on shallow modules become waste once tests at the deepened module's interface exist — delete them.
-- Write new tests at the deepened module's interface. The **interface is the test surface**.
-- Tests assert on observable outcomes through the interface, not internal state.
-- Tests should survive internal refactors — they describe behaviour, not implementation. If a test has to change when the implementation changes, it's testing past the interface.
diff --git a/.agents/skills/improve-codebase-architecture/HTML-REPORT.md b/.agents/skills/improve-codebase-architecture/HTML-REPORT.md
new file mode 100644
index 00000000..17f6d2c7
--- /dev/null
+++ b/.agents/skills/improve-codebase-architecture/HTML-REPORT.md
@@ -0,0 +1,123 @@
+# HTML Report Format
+
+The architectural review is rendered as a single self-contained HTML file in the OS temp directory. Tailwind and Mermaid both come from CDNs. Mermaid handles graph-shaped diagrams reliably; hand-built divs and inline SVG handle the more editorial visuals (mass diagrams, cross-sections). Mix the two — don't lean on Mermaid for everything, it'll start to look generic.
+
+## Scaffold
+
+```html
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <title>Architecture review — {{repo name}}</title>
+    <script src="https://cdn.tailwindcss.com"></script>
+    <script type="module">
+      import mermaid from "https://cdn.jsdelivr.net/npm/mermaid@11/dist/mermaid.esm.min.mjs";
+      mermaid.initialize({ startOnLoad: true, theme: "neutral", securityLevel: "loose" });
+    </script>
+    <style>
+      /* small custom layer for things Tailwind doesn't cover cleanly:
+         dashed seam lines, hand-drawn-feeling arrow heads, etc. */
+      .seam { stroke-dasharray: 4 4; }
+      .leak { stroke: #dc2626; }
+      .deep { background: linear-gradient(135deg, #0f172a, #1e293b); }
+    </style>
+  </head>
+  <body class="bg-stone-50 text-slate-900 font-sans">
+    <main class="max-w-5xl mx-auto px-6 py-12 space-y-12">
+      <header>...</header>
+      <section id="candidates" class="space-y-10">...</section>
+      <section id="top-recommendation">...</section>
+    </main>
+  </body>
+</html>
+```
+
+## Header
+
+Repo name, date, and a compact legend: solid box = module, dashed line = seam, red arrow = leakage, thick dark box = deep module. No introduction paragraph — straight into the candidates.
+
+## Candidate card
+
+The diagrams carry the weight. Prose is sparse, plain, and uses the glossary terms (from the `/codebase-design` skill) without ceremony.
+
+Each candidate is one `<article>`:
+
+- **Title** — short, names the deepening (e.g. "Collapse the Order intake pipeline").
+- **Badge row** — recommendation strength (`Strong` = emerald, `Worth exploring` = amber, `Speculative` = slate), plus a tag for the dependency category (`in-process`, `local-substitutable`, `ports & adapters`, `mock`).
+- **Files** — monospaced list, `font-mono text-sm`.
+- **Before / After diagram** — the centrepiece. Two columns, side by side. See patterns below.
+- **Problem** — one sentence. What hurts.
+- **Solution** — one sentence. What changes.
+- **Wins** — bullets, ≤6 words each. e.g. "Tests hit one interface", "Pricing logic stops leaking", "Delete 4 shallow wrappers".
+- **ADR callout** (if applicable) — one line in an amber-tinted box.
+
+No paragraphs of explanation. If the diagram needs a paragraph to be understood, redraw the diagram.
+
+## Diagram patterns
+
+Pick the pattern that fits the candidate. Mix them. Don't make every diagram look the same — variety is part of the point.
+
+### Mermaid graph (the workhorse for dependencies / call flow)
+
+Use a Mermaid `flowchart` or `graph` when the point is "X calls Y calls Z, and look at the mess." Wrap it in a Tailwind-styled card so it doesn't feel parachuted in. Style with classDef to colour leakage edges red and the deep module dark. Sequence diagrams work well for "before: 6 round-trips; after: 1."
+
+```html
+<div class="rounded-lg border border-slate-200 bg-white p-4">
+  <pre class="mermaid">
+    flowchart LR
+      A[OrderHandler] --> B[OrderValidator]
+      B --> C[OrderRepo]
+      C -.leak.-> D[PricingClient]
+      classDef leak stroke:#dc2626,stroke-width:2px;
+      class C,D leak
+  </pre>
+</div>
+```
+
+### Hand-built boxes-and-arrows (when Mermaid's layout fights you)
+
+Modules as `<div>`s with borders and labels. Arrows as inline SVG `<line>` or `<path>` elements positioned absolutely over a relative container. Reach for this when you want the "after" diagram to feel like one thick-bordered deep module with greyed-out internals — Mermaid won't render that with the right weight.
+
+### Cross-section (good for layered shallowness)
+
+Stack horizontal bands (`h-12 border-l-4`) to show layers a call passes through. Before: 6 thin layers each doing nothing. After: 1 thick band labelled with the consolidated responsibility.
+
+### Mass diagram (good for "interface as wide as implementation")
+
+Two rectangles per module — one for interface surface area, one for implementation. Before: interface rectangle is nearly as tall as the implementation rectangle (shallow). After: interface rectangle is short, implementation rectangle is tall (deep).
+
+### Call-graph collapse
+
+Before: a tree of function calls rendered as nested boxes. After: the same tree collapsed into one box, with the now-internal calls shown faded inside it.
+
+## Style guidance
+
+- Lean editorial, not corporate-dashboard. Generous whitespace. Serif optional for headings (`font-serif` works well with stone/slate).
+- Colour sparingly: one accent (emerald or indigo) plus red for leakage and amber for warnings.
+- Keep diagrams ~320px tall so before/after sits comfortably side by side without scrolling.
+- Use `text-xs uppercase tracking-wider` for module labels inside diagrams — they should read as schematic, not as UI.
+- The only scripts are the Tailwind CDN and the Mermaid ESM import. The report is otherwise static — no app code, no interactivity beyond Mermaid's own rendering.
+
+## Top recommendation section
+
+One larger card. Candidate name, one sentence on why, anchor link to its card. That's it.
+
+## Tone
+
+Plain English, concise — but the architectural nouns and verbs come straight from the `/codebase-design` skill. Concision is not an excuse to drift.
+
+**Use exactly:** module, interface, implementation, depth, deep, shallow, seam, adapter, leverage, locality.
+
+**Never substitute:** component, service, unit (for module) · API, signature (for interface) · boundary (for seam) · layer, wrapper (for module, when you mean module).
+
+**Phrasings that fit the style:**
+
+- "Order intake module is shallow — interface nearly matches the implementation."
+- "Pricing leaks across the seam."
+- "Deepen: one interface, one place to test."
+- "Two adapters justify the seam: HTTP in prod, in-memory in tests."
+
+**Wins bullets** name the gain in glossary terms: *"locality: bugs concentrate in one module"*, *"leverage: one interface, N call sites"*, *"interface shrinks; implementation absorbs the wrappers"*. Don't write *"easier to maintain"* or *"cleaner code"* — those terms aren't in the glossary and don't earn their place.
+
+No hedging, no throat-clearing, no "it's worth noting that…". If a sentence could be a bullet, make it a bullet. If a bullet could be cut, cut it. If a term isn't in the `/codebase-design` glossary, reach for one that is before inventing a new one.
diff --git a/.agents/skills/improve-codebase-architecture/INTERFACE-DESIGN.md b/.agents/skills/improve-codebase-architecture/INTERFACE-DESIGN.md
deleted file mode 100644
index 3197723a..00000000
--- a/.agents/skills/improve-codebase-architecture/INTERFACE-DESIGN.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# Interface Design
-
-When the user wants to explore alternative interfaces for a chosen deepening candidate, use this parallel sub-agent pattern. Based on "Design It Twice" (Ousterhout) — your first idea is unlikely to be the best.
-
-Uses the vocabulary in [LANGUAGE.md](LANGUAGE.md) — **module**, **interface**, **seam**, **adapter**, **leverage**.
-
-## Process
-
-### 1. Frame the problem space
-
-Before spawning sub-agents, write a user-facing explanation of the problem space for the chosen candidate:
-
-- The constraints any new interface would need to satisfy
-- The dependencies it would rely on, and which category they fall into (see [DEEPENING.md](DEEPENING.md))
-- A rough illustrative code sketch to ground the constraints — not a proposal, just a way to make the constraints concrete
-
-Show this to the user, then immediately proceed to Step 2. The user reads and thinks while the sub-agents work in parallel.
-
-### 2. Spawn sub-agents
-
-Spawn 3+ sub-agents in parallel using the Agent tool. Each must produce a **radically different** interface for the deepened module.
-
-Prompt each sub-agent with a separate technical brief (file paths, coupling details, dependency category from [DEEPENING.md](DEEPENING.md), what sits behind the seam). The brief is independent of the user-facing problem-space explanation in Step 1. Give each agent a different design constraint:
-
-- Agent 1: "Minimize the interface — aim for 1–3 entry points max. Maximise leverage per entry point."
-- Agent 2: "Maximise flexibility — support many use cases and extension."
-- Agent 3: "Optimise for the most common caller — make the default case trivial."
-- Agent 4 (if applicable): "Design around ports & adapters for cross-seam dependencies."
-
-Include both [LANGUAGE.md](LANGUAGE.md) vocabulary and CONTEXT.md vocabulary in the brief so each sub-agent names things consistently with the architecture language and the project's domain language.
-
-Each sub-agent outputs:
-
-1. Interface (types, methods, params — plus invariants, ordering, error modes)
-2. Usage example showing how callers use it
-3. What the implementation hides behind the seam
-4. Dependency strategy and adapters (see [DEEPENING.md](DEEPENING.md))
-5. Trade-offs — where leverage is high, where it's thin
-
-### 3. Present and compare
-
-Present designs sequentially so the user can absorb each one, then compare them in prose. Contrast by **depth** (leverage at the interface), **locality** (where change concentrates), and **seam placement**.
-
-After comparing, give your own recommendation: which design you think is strongest and why. If elements from different designs would combine well, propose a hybrid. Be opinionated — the user wants a strong read, not a menu.
diff --git a/.agents/skills/improve-codebase-architecture/LANGUAGE.md b/.agents/skills/improve-codebase-architecture/LANGUAGE.md
deleted file mode 100644
index 530c2763..00000000
--- a/.agents/skills/improve-codebase-architecture/LANGUAGE.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# Language
-
-Shared vocabulary for every suggestion this skill makes. Use these terms exactly — don't substitute "component," "service," "API," or "boundary." Consistent language is the whole point.
-
-## Terms
-
-**Module**
-Anything with an interface and an implementation. Deliberately scale-agnostic — applies equally to a function, class, package, or tier-spanning slice.
-_Avoid_: unit, component, service.
-
-**Interface**
-Everything a caller must know to use the module correctly. Includes the type signature, but also invariants, ordering constraints, error modes, required configuration, and performance characteristics.
-_Avoid_: API, signature (too narrow — those refer only to the type-level surface).
-
-**Implementation**
-What's inside a module — its body of code. Distinct from **Adapter**: a thing can be a small adapter with a large implementation (a Postgres repo) or a large adapter with a small implementation (an in-memory fake). Reach for "adapter" when the seam is the topic; "implementation" otherwise.
-
-**Depth**
-Leverage at the interface — the amount of behaviour a caller (or test) can exercise per unit of interface they have to learn. A module is **deep** when a large amount of behaviour sits behind a small interface. A module is **shallow** when the interface is nearly as complex as the implementation.
-
-**Seam** _(from Michael Feathers)_
-A place where you can alter behaviour without editing in that place. The *location* at which a module's interface lives. Choosing where to put the seam is its own design decision, distinct from what goes behind it.
-_Avoid_: boundary (overloaded with DDD's bounded context).
-
-**Adapter**
-A concrete thing that satisfies an interface at a seam. Describes *role* (what slot it fills), not substance (what's inside).
-
-**Leverage**
-What callers get from depth. More capability per unit of interface they have to learn. One implementation pays back across N call sites and M tests.
-
-**Locality**
-What maintainers get from depth. Change, bugs, knowledge, and verification concentrate at one place rather than spreading across callers. Fix once, fixed everywhere.
-
-## Principles
-
-- **Depth is a property of the interface, not the implementation.** A deep module can be internally composed of small, mockable, swappable parts — they just aren't part of the interface. A module can have **internal seams** (private to its implementation, used by its own tests) as well as the **external seam** at its interface.
-- **The deletion test.** Imagine deleting the module. If complexity vanishes, the module wasn't hiding anything (it was a pass-through). If complexity reappears across N callers, the module was earning its keep.
-- **The interface is the test surface.** Callers and tests cross the same seam. If you want to test *past* the interface, the module is probably the wrong shape.
-- **One adapter means a hypothetical seam. Two adapters means a real one.** Don't introduce a seam unless something actually varies across it.
-
-## Relationships
-
-- A **Module** has exactly one **Interface** (the surface it presents to callers and tests).
-- **Depth** is a property of a **Module**, measured against its **Interface**.
-- A **Seam** is where a **Module**'s **Interface** lives.
-- An **Adapter** sits at a **Seam** and satisfies the **Interface**.
-- **Depth** produces **Leverage** for callers and **Locality** for maintainers.
-
-## Rejected framings
-
-- **Depth as ratio of implementation-lines to interface-lines** (Ousterhout): rewards padding the implementation. We use depth-as-leverage instead.
-- **"Interface" as the TypeScript `interface` keyword or a class's public methods**: too narrow — interface here includes every fact a caller must know.
-- **"Boundary"**: overloaded with DDD's bounded context. Say **seam** or **interface**.
diff --git a/.agents/skills/improve-codebase-architecture/SKILL.md b/.agents/skills/improve-codebase-architecture/SKILL.md
index 05984a60..b56969e9 100644
--- a/.agents/skills/improve-codebase-architecture/SKILL.md
+++ b/.agents/skills/improve-codebase-architecture/SKILL.md
@@ -1,38 +1,28 @@
 ---
 name: improve-codebase-architecture
-description: Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
+description: Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
+disable-model-invocation: true
 ---
 
 # Improve Codebase Architecture
 
 Surface architectural friction and propose **deepening opportunities** — refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability.
 
-## Glossary
+This command is _informed_ by the project's domain model and built on a shared design vocabulary:
 
-Use these terms exactly in every suggestion. Consistent language is the point — don't drift into "component," "service," "API," or "boundary." Full definitions in [LANGUAGE.md](LANGUAGE.md).
-
-- **Module** — anything with an interface and an implementation (function, class, package, slice).
-- **Interface** — everything a caller must know to use the module: types, invariants, error modes, ordering, config. Not just the type signature.
-- **Implementation** — the code inside.
-- **Depth** — leverage at the interface: a lot of behaviour behind a small interface. **Deep** = high leverage. **Shallow** = interface nearly as complex as the implementation.
-- **Seam** — where an interface lives; a place behaviour can be altered without editing in place. (Use this, not "boundary.")
-- **Adapter** — a concrete thing satisfying an interface at a seam.
-- **Leverage** — what callers get from depth.
-- **Locality** — what maintainers get from depth: change, bugs, knowledge concentrated in one place.
-
-Key principles (see [LANGUAGE.md](LANGUAGE.md) for the full list):
-
-- **Deletion test**: imagine deleting the module. If complexity vanishes, it was a pass-through. If complexity reappears across N callers, it was earning its keep.
-- **The interface is the test surface.**
-- **One adapter = hypothetical seam. Two adapters = real seam.**
-
-This skill is _informed_ by the project's domain model. The domain language gives names to good seams; ADRs record decisions the skill should not re-litigate.
+- Run the `/codebase-design` skill for the architecture vocabulary (**module**, **interface**, **depth**, **seam**, **adapter**, **leverage**, **locality**) and its principles (the deletion test, "the interface is the test surface", "one adapter = hypothetical seam, two = real"). Use these terms exactly in every suggestion — don't drift into "component," "service," "API," or "boundary."
+- The domain language in `CONTEXT.md` gives names to good seams; ADRs in `docs/adr/` record decisions this command should not re-litigate.
 
 ## Process
 
 ### 1. Explore
 
-Read the project's domain glossary and any ADRs in the area you're touching first.
+**Scope before you scan — YAGNI.** Deepening a module pays off by making future changes to it easier, so put extra weight on the parts of the codebase that have recently changed. Decide *where* to look before you look:
+
+- If the user named a direction — a module, a subsystem, a pain point — take it, and skip the inference below.
+- Otherwise, walk back a good stretch of the commit history (`git log --oneline`) to find the codebase's hot spots — the files and areas that keep coming up — and let those paths pull your attention first. If the changes are scattered with no clear hot spot, widen the net.
+
+Read the project's domain glossary (`CONTEXT.md`) and any ADRs in the area you're touching first.
 
 Then use the Agent tool with `subagent_type=Explore` to walk the codebase. Don't follow rigid heuristics — explore organically and note where you experience friction:
 
@@ -44,28 +34,38 @@ Then use the Agent tool with `subagent_type=Explore` to walk the codebase. Don't
 
 Apply the **deletion test** to anything you suspect is shallow: would deleting it concentrate complexity, or just move it? A "yes, concentrates" is the signal you want.
 
-### 2. Present candidates
+### 2. Present candidates as an HTML report
+
+Write a self-contained HTML file to the OS temp directory so nothing lands in the repo. Resolve the temp dir from `$TMPDIR`, falling back to `/tmp` (or `%TEMP%` on Windows), and write to `<tmpdir>/architecture-review-<timestamp>.html` so each run gets a fresh file. Open it for the user — `xdg-open <path>` on Linux, `open <path>` on macOS, `start <path>` on Windows — and tell them the absolute path.
+
+The report uses **Tailwind via CDN** for layout and styling, and **Mermaid via CDN** for diagrams where a graph/flow/sequence reliably communicates the structure. Mix Mermaid with hand-crafted CSS/SVG visuals — use Mermaid when relationships are graph-shaped (call graphs, dependencies, sequences), and hand-built divs/SVG when you want something more editorial (mass diagrams, cross-sections, collapse animations). Each candidate gets a **before/after visualisation**. Be visual.
 
-Present a numbered list of deepening opportunities. For each candidate:
+For each candidate, render a card with:
 
 - **Files** — which files/modules are involved
 - **Problem** — why the current architecture is causing friction
 - **Solution** — plain English description of what would change
-- **Benefits** — explained in terms of locality and leverage, and also in how tests would improve
+- **Benefits** — explained in terms of locality and leverage, and how tests would improve
+- **Before / After diagram** — side-by-side, custom-drawn, illustrating the shallowness and the deepening
+- **Recommendation strength** — one of `Strong`, `Worth exploring`, `Speculative`, rendered as a badge
+
+End the report with a **Top recommendation** section: which candidate you'd tackle first and why.
+
+**Use CONTEXT.md vocabulary for the domain, and the `/codebase-design` vocabulary for the architecture.** If `CONTEXT.md` defines "Order," talk about "the Order intake module" — not "the FooBarHandler," and not "the Order service."
 
-**Use CONTEXT.md vocabulary for the domain, and [LANGUAGE.md](LANGUAGE.md) vocabulary for the architecture.** If `CONTEXT.md` defines "Order," talk about "the Order intake module" — not "the FooBarHandler," and not "the Order service."
+**ADR conflicts**: if a candidate contradicts an existing ADR, only surface it when the friction is real enough to warrant revisiting the ADR. Mark it clearly in the card (e.g. a warning callout: _"contradicts ADR-0007 — but worth reopening because…"_). Don't list every theoretical refactor an ADR forbids.
 
-**ADR conflicts**: if a candidate contradicts an existing ADR, only surface it when the friction is real enough to warrant revisiting the ADR. Mark it clearly (e.g. _"contradicts ADR-0007 — but worth reopening because…"_). Don't list every theoretical refactor an ADR forbids.
+See [HTML-REPORT.md](HTML-REPORT.md) for the full HTML scaffold, diagram patterns, and styling guidance.
 
-Do NOT propose interfaces yet. Ask the user: "Which of these would you like to explore?"
+Do NOT propose interfaces yet. After the file is written, ask the user: "Which of these would you like to explore?"
 
 ### 3. Grilling loop
 
-Once the user picks a candidate, drop into a grilling conversation. Walk the design tree with them — constraints, dependencies, the shape of the deepened module, what sits behind the seam, what tests survive.
+Once the user picks a candidate, run the `/grilling` skill to walk the decision tree with them — constraints, dependencies, the shape of the deepened module, what sits behind the seam, what tests survive.
 
-Side effects happen inline as decisions crystallize:
+Side effects happen inline as decisions crystallize — run the `/domain-modeling` skill to keep the domain model current as you go:
 
-- **Naming a deepened module after a concept not in `CONTEXT.md`?** Add the term to `CONTEXT.md` — same discipline as `/grill-with-docs` (see [CONTEXT-FORMAT.md](../grill-with-docs/CONTEXT-FORMAT.md)). Create the file lazily if it doesn't exist.
+- **Naming a deepened module after a concept not in `CONTEXT.md`?** Add the term to `CONTEXT.md`. Create the file lazily if it doesn't exist.
 - **Sharpening a fuzzy term during the conversation?** Update `CONTEXT.md` right there.
-- **User rejects the candidate with a load-bearing reason?** Offer an ADR, framed as: _"Want me to record this as an ADR so future architecture reviews don't re-suggest it?"_ Only offer when the reason would actually be needed by a future explorer to avoid re-suggesting the same thing — skip ephemeral reasons ("not worth it right now") and self-evident ones. See [ADR-FORMAT.md](../grill-with-docs/ADR-FORMAT.md).
-- **Want to explore alternative interfaces for the deepened module?** See [INTERFACE-DESIGN.md](INTERFACE-DESIGN.md).
+- **User rejects the candidate with a load-bearing reason?** Offer an ADR, framed as: _"Want me to record this as an ADR so future architecture reviews don't re-suggest it?"_ Only offer when the reason would actually be needed by a future explorer to avoid re-suggesting the same thing — skip ephemeral reasons ("not worth it right now") and self-evident ones.
+- **Want to explore alternative interfaces for the deepened module?** Run the `/codebase-design` skill and use its design-it-twice parallel sub-agent pattern.
diff --git a/.agents/skills/improve-codebase-architecture/agents/openai.yaml b/.agents/skills/improve-codebase-architecture/agents/openai.yaml
new file mode 100644
index 00000000..706fdca0
--- /dev/null
+++ b/.agents/skills/improve-codebase-architecture/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Improve Codebase Architecture"
+  short_description: "Find and grill architecture improvements"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/prototype/LOGIC.md b/.agents/skills/prototype/LOGIC.md
index 526ecb18..5f5a3fd5 100644
--- a/.agents/skills/prototype/LOGIC.md
+++ b/.agents/skills/prototype/LOGIC.md
@@ -1,13 +1,15 @@
 # Logic Prototype
 
-A tiny interactive terminal app that lets the user drive a state model by hand. Use this when the question is about **business logic, state transitions, or data shape** — the kind of thing that looks reasonable on paper but only feels wrong once you push it through real cases.
+A single, self-contained HTML file — a **shareable demo** — that lets anyone drive a state model by clicking buttons. Use this when the question is about **business logic, state transitions, or data shape** — the kind of thing that looks reasonable on paper but only feels wrong once you push it through real cases.
+
+Because it's one file with nothing to install, you can hand it to a non-developer — a designer, a PM, a domain expert — and let them feel the model for themselves. So it speaks their language, not the code's.
 
 ## When this is the right shape
 
 - "I'm not sure if this state machine handles the edge case where X then Y."
 - "Does this data model actually let me represent the case where..."
 - "I want to feel out what the API should look like before writing it."
-- Anything where the user wants to **press buttons and watch state change**.
+- Anything where someone wants to **press buttons and watch state change**.
 
 If the question is "what should this look like" — wrong branch. Use [UI.md](UI.md).
 
@@ -15,17 +17,11 @@ If the question is "what should this look like" — wrong branch. Use [UI.md](UI
 
 ### 1. State the question
 
-Before writing code, write down what state model and what question you're prototyping. One paragraph, in the prototype's README or a comment at the top of the file. A logic prototype that answers the wrong question is pure waste — make the question explicit so it can be checked later, whether the user is watching now or returning to it AFK.
-
-### 2. Pick the language
-
-Use whatever the host project uses. If the project has no obvious runtime (e.g. a docs repo), ask.
-
-Match the project's existing conventions for tooling — don't add a new package manager or runtime just for the prototype.
+Before writing code, write down what state model and what question you're prototyping. One paragraph, at the top of the demo (in a visible intro, not just a comment). A logic prototype that answers the wrong question is pure waste — make the question explicit so it can be checked later, whether the user is watching now or returning to it AFK.
 
-### 3. Isolate the logic in a portable module
+### 2. Isolate the logic in a portable module
 
-Put the actual logic — the bit that's answering the question — behind a small, pure interface that could be lifted out and dropped into the real codebase later. The TUI around it is throwaway; the logic module shouldn't be.
+Put the actual logic — the bit that's answering the question — in a single `<script>` block written as a small, pure module that could be lifted out and dropped into the real codebase later. The page around it is throwaway; this module isn't.
 
 The right shape depends on the question:
 
@@ -34,46 +30,38 @@ The right shape depends on the question:
 - **A small set of pure functions** over a plain data type. Good when there's no implicit current state — just transformations.
 - **A class or module with a clear method surface** when the logic genuinely owns ongoing internal state.
 
-Pick whichever shape best fits the question being asked, *not* whichever is easiest to wire to a TUI. Keep it pure: no I/O, no terminal code, no `console.log` for control flow. The TUI imports it and calls into it; nothing flows the other direction.
-
-This is what makes the prototype useful past its own lifetime. When the question's been answered, the validated reducer / machine / function set can be lifted into the real module — the TUI shell gets deleted.
-
-### 4. Build the smallest TUI that exposes the state
-
-Build it as a **lightweight TUI** — on every tick, clear the screen (`console.clear()` / `print("\033[2J\033[H")` / equivalent) and re-render the whole frame. The user should always see one stable view, not an ever-growing scrollback.
-
-Each frame has two parts, in this order:
+Pick whichever shape best fits the question being asked, *not* whichever is easiest to wire to a page. Keep it pure: no DOM, no `document`, no button handlers reaching inside it. The page calls into it; nothing flows the other direction. This is what makes the prototype useful past its own lifetime: once the question's answered, the validated reducer / machine / function set lifts into the real module on its own.
 
-1. **Current state**, pretty-printed and diff-friendly (one field per line, or formatted JSON). Use **bold** for field names or section headers and **dim** for less important context (timestamps, IDs, derived values). Native ANSI escape codes are fine — `\x1b[1m` bold, `\x1b[2m` dim, `\x1b[0m` reset. No need to pull in a styling library unless one is already in the project.
-2. **Keyboard shortcuts**, listed at the bottom: `[a] add user  [d] delete user  [t] tick clock  [q] quit`. Bold the key, dim the description, or vice-versa — whatever reads cleanly.
+### 3. Build the shareable HTML file
 
-Behaviour:
+One file, plain HTML/CSS/JS — no framework, no bundler, no server, everything inline so it opens by double-click and survives being emailed around. Anyone should be able to run it by opening it.
 
-1. **Initialise state** — a single in-memory object/struct. Render the first frame on start.
-2. **Read one keystroke (or one line)** at a time, dispatch to a handler that mutates state.
-3. **Re-render** the full frame after every action — don't append, replace.
-4. **Loop until quit.**
+Write it for a non-developer. Every label is in **domain language**, not code — buttons and state read like the business, not the reducer. Explain in plain words what's happening.
 
-The whole frame should fit on one screen.
+Lay it out with a clean hierarchy, top to bottom:
 
-### 5. Make it runnable in one command
+1. **Title and one-line explanation** of what this demo lets you explore (the question from step 1).
+2. **Current state** — the full relevant state, rendered as a readable panel (labelled fields, not a raw JSON dump), re-rendered after every click so the change is visible. Where it helps a non-developer follow, call out what just changed.
+3. **Free-play buttons** — one button per action, always available, so anyone can poke at the model in any order. Each click dispatches its action and re-renders the state.
+4. **Guided walkthroughs** — a set of **scenarios**, one per tab. Each tab holds a short plain-language description of the scenario — the situation it sets up and what to watch for — and underneath it, the ordered **buttons to press** for that scenario. Each step is a real button: clicking it performs that action and moves to the next step. Starting a walkthrough resets to a known initial state so the scenario runs the same way every time.
 
-Add a script to the project's existing task runner (`package.json` scripts, `Makefile`, `justfile`, `pyproject.toml`). The user should run `pnpm run <prototype-name>` or equivalent — never need to remember a path.
+Choose scenarios that demonstrate the awkward cases — the happy path, a tricky edge case, an attempt at something that should be illegal — the ones hard to reason about on paper.
 
-If the host project has no task runner, just put the command at the top of the prototype's README.
+Keep it beautiful but restrained: clean typography, generous spacing, one accent colour. No animations, no gimmicks — nothing that competes with the state and the buttons.
 
-### 6. Hand it over
+### 4. Hand it over
 
-Give the user the run command. They'll drive it themselves; the interesting moments are when they say "wait, that shouldn't be possible" or "huh, I assumed X would be different" — those are the bugs in the _idea_, which is the whole point. If they want new actions added, add them. Prototypes evolve.
+Send them the file, or open it for them. They'll click through the walkthroughs and free-play whenever they get to it; the interesting moments are when they say "wait, that shouldn't be possible" or "huh, I assumed X would be different" — those are the bugs in the _idea_, which is the whole point. If they want new actions or a new scenario, add them. Prototypes evolve.
 
-### 7. Capture the answer
+### 5. Capture the answer and the prototype
 
-When the prototype has done its job, the answer to the question is the only thing worth keeping. If the user is around, ask what it taught them. If not, leave a `NOTES.md` next to the prototype so the answer can be filled in (or filled in by you, if you've watched the session) before the prototype gets deleted.
+Once the prototype has answered its question, capture the answer, then capture the prototype the way the [SKILL](SKILL.md) describes. The logic-specific mapping: the validated reducer / machine / function set lifts into the real module (the decision, absorbed); the HTML shell rides along to the throwaway branch that keeps the prototype as a primary source — and being one self-contained file, it stays trivially re-runnable there.
 
 ## Anti-patterns
 
 - **Don't add tests.** A prototype that needs tests is no longer a prototype.
-- **Don't wire it to the real database.** Use an in-memory store unless the question is specifically about persistence.
+- **Don't wire it to the real database.** Use in-memory state unless the question is specifically about persistence.
 - **Don't generalise.** No "what if we wanted to support X later." The prototype answers one question.
-- **Don't blur the logic and the TUI together.** If the reducer / state machine references `console.log`, prompts, or terminal escape codes, it's no longer portable. Keep the TUI as a thin shell over a pure module.
-- **Don't ship the TUI shell into production.** The shell is optimised for being driven by hand from a terminal. The logic module behind it is the bit worth keeping.
+- **Don't blur the logic and the page together.** If the pure module references the DOM, `document`, or button handlers, it's no longer liftable. Keep the page as a thin shell over a pure module.
+- **Don't reach for a framework, bundler, or server.** One file the recipient double-clicks; a React app or a dev server defeats "shareable".
+- **Don't ship the HTML shell into production.** The page is optimised for being clicked through by hand. The logic module behind it is the bit worth keeping.
diff --git a/.agents/skills/prototype/SKILL.md b/.agents/skills/prototype/SKILL.md
index 64f3e611..09457115 100644
--- a/.agents/skills/prototype/SKILL.md
+++ b/.agents/skills/prototype/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: prototype
-description: Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
+description: Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
 ---
 
 # Prototype
@@ -11,7 +11,7 @@ A prototype is **throwaway code that answers a question**. The question decides
 
 Identify which question is being answered — from the user's prompt, the surrounding code, or by asking if the user is around:
 
-- **"Does this logic / state model feel right?"** → [LOGIC.md](LOGIC.md). Build a tiny interactive terminal app that pushes the state machine through cases that are hard to reason about on paper.
+- **"Does this logic / state model feel right?"** → [LOGIC.md](LOGIC.md). Build a single shareable HTML file — free-play buttons plus tabbed guided walkthroughs — that pushes the state machine through cases that are hard to reason about on paper, and that a non-developer can drive.
 - **"What should this look like?"** → [UI.md](UI.md). Generate several radically different UI variations on a single route, switchable via a URL search param and a floating bottom bar.
 
 The two branches produce very different artifacts — getting this wrong wastes the whole prototype. If the question is genuinely ambiguous and the user isn't reachable, default to whichever branch better matches the surrounding code (a backend module → logic; a page or component → UI) and state the assumption at the top of the prototype.
@@ -19,12 +19,8 @@ The two branches produce very different artifacts — getting this wrong wastes
 ## Rules that apply to both
 
 1. **Throwaway from day one, and clearly marked as such.** Locate the prototype code close to where it will actually be used (next to the module or page it's prototyping for) so context is obvious — but name it so a casual reader can see it's a prototype, not production. For throwaway UI routes, obey whatever routing convention the project already uses; don't invent a new top-level structure.
-2. **One command to run.** Whatever the project's existing task runner supports — `pnpm <name>`, `python <path>`, `bun <path>`, etc. The user must be able to start it without thinking.
+2. **Trivial to run.** A UI prototype starts from one command in the project's task runner — `pnpm <name>`, `python <path>`, `bun <path>`, etc. A logic demo is a single HTML file the user double-clicks. Either way, no thinking required to start it.
 3. **No persistence by default.** State lives in memory. Persistence is the thing the prototype is _checking_, not something it should depend on. If the question explicitly involves a database, hit a scratch DB or a local file with a clear "PROTOTYPE — wipe me" name.
-4. **Skip the polish.** No tests, no error handling beyond what makes the prototype _runnable_, no abstractions. The point is to learn something fast and then delete it.
+4. **Skip the polish.** No tests, no error handling beyond what makes the prototype _runnable_, no abstractions. The point is to learn something fast.
 5. **Surface the state.** After every action (logic) or on every variant switch (UI), print or render the full relevant state so the user can see what changed.
-6. **Delete or absorb when done.** When the prototype has answered its question, either delete it or fold the validated decision into the real code — don't leave it rotting in the repo.
-
-## When done
-
-The _answer_ is the only thing worth keeping from a prototype. Capture it somewhere durable (commit message, ADR, issue, or a `NOTES.md` next to the prototype) along with the question it was answering. If the user is around, that capture is a quick conversation; if not, leave the placeholder so they (or you, on the next pass) can fill in the verdict before deleting the prototype.
+6. **Capture it when done.** Fold any validated decision into the real code, then capture the prototype itself as a **primary source**: commit it to a throwaway branch, out of main, and leave a context pointer to that branch on the implementation issue. Capture the answer too — the verdict and the question it settled — in the issue or a commit. The main branch keeps only the validated decision.
diff --git a/.agents/skills/prototype/UI.md b/.agents/skills/prototype/UI.md
index f3b6e640..76c0f601 100644
--- a/.agents/skills/prototype/UI.md
+++ b/.agents/skills/prototype/UI.md
@@ -97,12 +97,12 @@ Surface the URL (and the `?variant=` keys). The user will flip through whenever
 
 ### 6. Capture the answer and clean up
 
-Once a variant has won, write down which one and why (commit message, ADR, issue, or a `NOTES.md` next to the prototype if running AFK and the user hasn't responded yet). Then:
+Once a variant has won, capture the answer — which variant and why — then capture the prototype the way the [SKILL](SKILL.md) describes. Fold the winner into the real code and move the rest onto the throwaway branch, not into main:
 
-- **Sub-shape A** — delete the losing variants and the switcher; fold the winner into the existing page.
-- **Sub-shape B** — promote the winning variant to a real route, delete the throwaway route and the switcher.
+- **Sub-shape A** — fold the winner into the existing page; drop the losing variants and the switcher from main.
+- **Sub-shape B** — promote the winning variant to a real route; drop the throwaway route and the switcher from main.
 
-Don't leave variant components or the switcher lying around. They rot fast and confuse the next reader.
+The full set of variants is the primary source, so it lands on the throwaway branch, not the bin — variant components and the switcher left in the main branch rot fast and confuse the next reader.
 
 ## Anti-patterns
 
diff --git a/.agents/skills/prototype/agents/openai.yaml b/.agents/skills/prototype/agents/openai.yaml
new file mode 100644
index 00000000..1618b147
--- /dev/null
+++ b/.agents/skills/prototype/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "Prototype"
+  short_description: "Prototype to answer a design question"
diff --git a/.agents/skills/research/SKILL.md b/.agents/skills/research/SKILL.md
new file mode 100644
index 00000000..0ba594a0
--- /dev/null
+++ b/.agents/skills/research/SKILL.md
@@ -0,0 +1,12 @@
+---
+name: research
+description: Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
+---
+
+Spin up a **background agent** to do the research, so you keep working while it reads.
+
+Its job:
+
+1. Investigate the question against **primary sources** — official docs, source code, specs, first-party APIs — not a secondary write-up of them. Follow every claim back to the source that owns it.
+2. Write the findings to a single Markdown file, citing each claim's source.
+3. Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.
diff --git a/.agents/skills/research/agents/openai.yaml b/.agents/skills/research/agents/openai.yaml
new file mode 100644
index 00000000..e18b96ca
--- /dev/null
+++ b/.agents/skills/research/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "Research"
+  short_description: "Research from high-trust sources"
diff --git a/.agents/skills/resolving-merge-conflicts/SKILL.md b/.agents/skills/resolving-merge-conflicts/SKILL.md
new file mode 100644
index 00000000..aadb3fcb
--- /dev/null
+++ b/.agents/skills/resolving-merge-conflicts/SKILL.md
@@ -0,0 +1,14 @@
+---
+name: resolving-merge-conflicts
+description: "Use when you need to resolve an in-progress git merge/rebase conflict."
+---
+
+1. **See the current state** of the merge/rebase. Check git history, and the conflicting files.
+
+2. **Find the primary sources** for each conflict. Understand deeply why each change was made, and what the original intent was. Read the commit messages, check the PRs, check original issues/tickets.
+
+3. **Resolve each hunk.** Preserve both intents where possible. Where incompatible, pick the one matching the merge's stated goal and note the trade-off. Do **not** invent new behaviour. Always resolve; never `--abort`.
+
+4. Discover the project's **automated checks** and run them — typically typecheck, then tests, then format. Fix anything the merge broke.
+
+5. **Finish the merge/rebase.** Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.
diff --git a/.agents/skills/resolving-merge-conflicts/agents/openai.yaml b/.agents/skills/resolving-merge-conflicts/agents/openai.yaml
new file mode 100644
index 00000000..331ffb9d
--- /dev/null
+++ b/.agents/skills/resolving-merge-conflicts/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "Resolving Merge Conflicts"
+  short_description: "Resolve merge and rebase conflicts"
diff --git a/.agents/skills/setup-matt-pocock-skills/SKILL.md b/.agents/skills/setup-matt-pocock-skills/SKILL.md
index 1ebc6e14..4cbdd0f6 100644
--- a/.agents/skills/setup-matt-pocock-skills/SKILL.md
+++ b/.agents/skills/setup-matt-pocock-skills/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: setup-matt-pocock-skills
-description: Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
+description: Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
 disable-model-invocation: true
 ---
 
@@ -26,16 +26,18 @@ Look at the current repo to understand its starting state. Read whatever exists;
 - `docs/adr/` and any `src/*/docs/adr/` directories
 - `docs/agents/` — does this skill's prior output already exist?
 - `.scratch/` — sign that a local-markdown issue tracker convention is already in use
+- Is the `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in your available skills.) This decides whether Section B runs at all.
+- Monorepo signals — a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages/*` with its own `src/`. Present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.
 
 ### 2. Present findings and ask
 
-Summarise what's present and what's missing. Then walk the user through the three decisions **one at a time** — present a section, get the user's answer, then move to the next. Don't dump all three at once.
+Summarise what's present and what's missing. Then take the sections in order — one section, one answer, then the next.
 
-Assume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why these skills need it, what changes if they pick differently). Then show the choices and the default.
+Lead each section with the recommended answer so the user can accept it in a word. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when `triage` isn't installed, Section C when there's no monorepo).
 
 **Section A — Issue tracker.**
 
-> Explainer: The "issue tracker" is where issues live for this repo. Skills like `to-issues`, `triage`, `to-prd`, and `qa` read from and write to it — they need to know whether to call `gh issue create`, write a markdown file under `.scratch/`, or follow some other workflow you describe. Pick the place you actually track work for this repo.
+> Explainer: The "issue tracker" is where issues live for this repo. Skills like `to-tickets`, `triage`, and `to-spec` read from and write to it — they need to know whether to call `gh issue create`, write a markdown file under `.scratch/`, or follow some other workflow you describe. Pick the place you actually track work for this repo.
 
 Default posture: these skills were designed for GitHub. If a `git remote` points at GitHub, propose that. If a `git remote` points at GitLab (`gitlab.com` or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:
 
@@ -44,35 +46,26 @@ Default posture: these skills were designed for GitHub. If a `git remote` points
 - **Local markdown** — issues live as files under `.scratch/<feature>/` in this repo (good for solo projects or repos without a remote)
 - **Other** (Jira, Linear, etc.) — ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose
 
-**Section B — Triage label vocabulary.**
+Record the choice in `docs/agents/issue-tracker.md`. The GitHub and GitLab templates carry a "PRs as a request surface" flag, defaulted **off** — leave it off and don't raise it; a user who wants external PRs in the triage queue can flip the flag in the file later.
 
-> Explainer: When the `triage` skill processes an incoming issue, it moves it through a state machine — needs evaluation, waiting on reporter, ready for an AFK agent to pick up, ready for a human, or won't fix. To do that, it needs to apply labels (or the equivalent in your issue tracker) that match strings *you've actually configured*. If your repo already uses different label names (e.g. `bug:triage` instead of `needs-triage`), map them here so the skill applies the right ones instead of creating duplicates.
+**Section B — Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you) — an uninstalled skill needs no labels.
 
-The five canonical roles:
+If it is installed, ask exactly one question:
 
-- `needs-triage` — maintainer needs to evaluate
-- `needs-info` — waiting on reporter
-- `ready-for-agent` — fully specified, AFK-ready (an agent can pick it up with no human context)
-- `ready-for-human` — needs human implementation
-- `wontfix` — will not be actioned
+> Do you want to keep the default triage labels? (recommended: **yes**)
 
-Default: each role's string equals its name. Ask the user if they want to override any. If their issue tracker has no existing labels, the defaults are fine.
+The defaults are the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. On **yes**, write them as-is. Only if the user says no — usually because their tracker already uses other names (e.g. `bug:triage` for `needs-triage`) — collect the overrides so `triage` applies existing labels instead of creating duplicates.
 
-**Section C — Domain docs.**
+**Section C — Domain docs.** Default to **single-context** — one `CONTEXT.md` + `docs/adr/` at the repo root. This fits almost every repo; write it without asking.
 
-> Explainer: Some skills (`improve-codebase-architecture`, `diagnose`, `tdd`) read a `CONTEXT.md` file to learn the project's domain language, and `docs/adr/` for past architectural decisions. They need to know whether the repo has one global context or multiple (e.g. a monorepo with separate frontend/backend contexts) so they look in the right place.
-
-Confirm the layout:
-
-- **Single-context** — one `CONTEXT.md` + `docs/adr/` at the repo root. Most repos are this.
-- **Multi-context** — `CONTEXT-MAP.md` at the root pointing to per-context `CONTEXT.md` files (typically a monorepo).
+Offer **multi-context** — a root `CONTEXT-MAP.md` pointing to per-context `CONTEXT.md` files — only when exploration found monorepo signals. Then confirm which layout they want.
 
 ### 3. Confirm and edit
 
 Show the user a draft of:
 
 - The `## Agent skills` block to add to whichever of `CLAUDE.md` / `AGENTS.md` is being edited (see step 4 for selection rules)
-- The contents of `docs/agents/issue-tracker.md`, `docs/agents/triage-labels.md`, `docs/agents/domain.md`
+- The contents of `docs/agents/issue-tracker.md`, `docs/agents/domain.md`, and `docs/agents/triage-labels.md` (the last only when `triage` is installed)
 
 Let them edit before writing.
 
@@ -106,12 +99,14 @@ The block:
 [one-line summary of layout — "single-context" or "multi-context"]. See `docs/agents/domain.md`.
 ```
 
-Then write the three docs files using the seed templates in this skill folder as a starting point:
+Include the `### Triage labels` sub-block, and write `docs/agents/triage-labels.md`, only when `triage` is installed and Section B ran. When it isn't, both are omitted.
+
+Then write the docs files using the seed templates in this skill folder as a starting point:
 
 - [issue-tracker-github.md](./issue-tracker-github.md) — GitHub issue tracker
 - [issue-tracker-gitlab.md](./issue-tracker-gitlab.md) — GitLab issue tracker
 - [issue-tracker-local.md](./issue-tracker-local.md) — local-markdown issue tracker
-- [triage-labels.md](./triage-labels.md) — label mapping
+- [triage-labels.md](./triage-labels.md) — label mapping (only if `triage` is installed)
 - [domain.md](./domain.md) — domain doc consumer rules + layout
 
 For "other" issue trackers, write `docs/agents/issue-tracker.md` from scratch using the user's description.
diff --git a/.agents/skills/setup-matt-pocock-skills/agents/openai.yaml b/.agents/skills/setup-matt-pocock-skills/agents/openai.yaml
new file mode 100644
index 00000000..65a0da81
--- /dev/null
+++ b/.agents/skills/setup-matt-pocock-skills/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Setup Matt Pocock Skills"
+  short_description: "Configure a repo for the skills"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/setup-matt-pocock-skills/domain.md b/.agents/skills/setup-matt-pocock-skills/domain.md
index c97d6a6d..b548c538 100644
--- a/.agents/skills/setup-matt-pocock-skills/domain.md
+++ b/.agents/skills/setup-matt-pocock-skills/domain.md
@@ -8,7 +8,7 @@ How the engineering skills should consume this repo's domain documentation when
 - **`CONTEXT-MAP.md`** at the repo root if it exists — it points at one `CONTEXT.md` per context. Read each one relevant to the topic.
 - **`docs/adr/`** — read ADRs that touch the area you're about to work in. In multi-context repos, also check `src/<context>/docs/adr/` for context-scoped decisions.
 
-If any of these files don't exist, **proceed silently**. Don't flag their absence; don't suggest creating them upfront. The producer skill (`/grill-with-docs`) creates them lazily when terms or decisions actually get resolved.
+If any of these files don't exist, **proceed silently**. Don't flag their absence; don't suggest creating them upfront. The `/domain-modeling` skill (reached via `/grill-with-docs` and `/improve-codebase-architecture`) creates them lazily when terms or decisions actually get resolved.
 
 ## File structure
 
@@ -42,7 +42,7 @@ Multi-context repo (presence of `CONTEXT-MAP.md` at the root):
 
 When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in `CONTEXT.md`. Don't drift to synonyms the glossary explicitly avoids.
 
-If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for `/grill-with-docs`).
+If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for `/domain-modeling`).
 
 ## Flag ADR conflicts
 
diff --git a/.agents/skills/setup-matt-pocock-skills/issue-tracker-github.md b/.agents/skills/setup-matt-pocock-skills/issue-tracker-github.md
index cce77ecb..bf595e24 100644
--- a/.agents/skills/setup-matt-pocock-skills/issue-tracker-github.md
+++ b/.agents/skills/setup-matt-pocock-skills/issue-tracker-github.md
@@ -1,6 +1,6 @@
 # Issue tracker: GitHub
 
-Issues and PRDs for this repo live as GitHub issues. Use the `gh` CLI for all operations.
+Issues and specs for this repo live as GitHub issues. Use the `gh` CLI for all operations.
 
 ## Conventions
 
@@ -13,6 +13,18 @@ Issues and PRDs for this repo live as GitHub issues. Use the `gh` CLI for all op
 
 Infer the repo from `git remote -v` — `gh` does this automatically when run inside a clone.
 
+## Pull requests as a triage surface
+
+**PRs as a request surface: no.** _(Set to `yes` if this repo treats external PRs as feature requests; `/triage` reads this flag.)_
+
+When set to `yes`, PRs run through the same labels and states as issues, using the `gh pr` equivalents:
+
+- **Read a PR**: `gh pr view <number> --comments` and `gh pr diff <number>` for the diff.
+- **List external PRs for triage**: `gh pr list --state open --json number,title,body,labels,author,authorAssociation,comments` then keep only `authorAssociation` of `CONTRIBUTOR`, `FIRST_TIME_CONTRIBUTOR`, or `NONE` (drop `OWNER`/`MEMBER`/`COLLABORATOR`).
+- **Comment / label / close**: `gh pr comment`, `gh pr edit --add-label`/`--remove-label`, `gh pr close`.
+
+GitHub shares one number space across issues and PRs, so a bare `#42` may be either — resolve with `gh pr view 42` and fall back to `gh issue view 42`.
+
 ## When a skill says "publish to the issue tracker"
 
 Create a GitHub issue.
@@ -20,3 +32,14 @@ Create a GitHub issue.
 ## When a skill says "fetch the relevant ticket"
 
 Run `gh issue view <number> --comments`.
+
+## Wayfinding operations
+
+Used by `/wayfinder`. The **map** is a single issue with **child** issues as tickets.
+
+- **Map**: a single issue labelled `wayfinder:map`, holding the Notes / Decisions-so-far / Fog body. `gh issue create --label wayfinder:map`.
+- **Child ticket**: an issue linked to the map as a GitHub sub-issue (`gh api` on the sub-issues endpoint). Where sub-issues aren't enabled, add the child to a task list in the map body and put `Part of #<map>` at the top of the child body. Labels: `wayfinder:<type>` (`research`/`prototype`/`grilling`/`task`). Once claimed, the ticket is assigned to the driving dev.
+- **Blocking**: GitHub's **native issue dependencies** — the canonical, UI-visible representation. Add an edge with `gh api --method POST repos/<owner>/<repo>/issues/<child>/dependencies/blocked_by -F issue_id=<blocker-db-id>`, where `<blocker-db-id>` is the blocker's numeric **database id** (`gh api repos/<owner>/<repo>/issues/<n> --jq .id`, _not_ the `#number` or `node_id`). GitHub reports `issue_dependencies_summary.blocked_by` (open blockers only — the live gate). Where dependencies aren't available, fall back to a `Blocked by: #<n>, #<n>` line at the top of the child body. A ticket is unblocked when every blocker is closed.
+- **Frontier query**: list the map's open children (`gh issue list --state open`, scoped to the map's sub-issues / task list), drop any with an open blocker (`issue_dependencies_summary.blocked_by > 0`, or an open issue in the `Blocked by` line) or an assignee; first in map order wins.
+- **Claim**: `gh issue edit <n> --add-assignee @me` — the session's first write.
+- **Resolve**: `gh issue comment <n> --body "<answer>"`, then `gh issue close <n>`, then append a context pointer (gist + link) to the map's Decisions-so-far.
diff --git a/.agents/skills/setup-matt-pocock-skills/issue-tracker-gitlab.md b/.agents/skills/setup-matt-pocock-skills/issue-tracker-gitlab.md
index f54da955..95e49cbb 100644
--- a/.agents/skills/setup-matt-pocock-skills/issue-tracker-gitlab.md
+++ b/.agents/skills/setup-matt-pocock-skills/issue-tracker-gitlab.md
@@ -1,6 +1,6 @@
 # Issue tracker: GitLab
 
-Issues and PRDs for this repo live as GitLab issues. Use the [`glab`](https://gitlab.com/gitlab-org/cli) CLI for all operations.
+Issues and specs for this repo live as GitLab issues. Use the [`glab`](https://gitlab.com/gitlab-org/cli) CLI for all operations.
 
 ## Conventions
 
@@ -14,6 +14,18 @@ Issues and PRDs for this repo live as GitLab issues. Use the [`glab`](https://gi
 
 Infer the repo from `git remote -v` — `glab` does this automatically when run inside a clone.
 
+## Merge requests as a triage surface
+
+**MRs as a request surface: no.** _(Set to `yes` if this repo treats external merge requests as feature requests; `/triage` reads this flag.)_
+
+When set to `yes`, MRs run through the same labels and states as issues, using the `glab mr` equivalents:
+
+- **Read an MR**: `glab mr view <number> --comments` and `glab mr diff <number>` for the diff.
+- **List external MRs for triage**: `glab mr list -F json`, then keep only MRs whose author is not a project member/owner (a contributor's MR, not a maintainer's in-flight work).
+- **Comment / label / close**: `glab mr note`, `glab mr update --label`/`--unlabel`, `glab mr close`.
+
+Unlike GitHub, GitLab numbers issues and MRs separately, so `#42` is unambiguous once you know which surface the maintainer means.
+
 ## When a skill says "publish to the issue tracker"
 
 Create a GitLab issue.
@@ -21,3 +33,14 @@ Create a GitLab issue.
 ## When a skill says "fetch the relevant ticket"
 
 Run `glab issue view <number> --comments`.
+
+## Wayfinding operations
+
+Used by `/wayfinder`. The **map** is a single issue with **child** issues as tickets.
+
+- **Map**: a single issue labelled `wayfinder:map`, holding the Notes / Decisions-so-far / Fog body. `glab issue create --label wayfinder:map`. (On GitLab tiers with native epics, an epic may hold the map instead; a labelled issue works everywhere.)
+- **Child ticket**: an issue carrying `Part of #<map>` at the top of its description and labels `wayfinder:<type>` (`research`/`prototype`/`grilling`/`task`). Once claimed, the ticket is assigned to the driving dev.
+- **Blocking**: GitLab's **native blocking link** — the canonical, UI-visible representation. Add it with the `/blocked_by #<n>` quick action, posted as a note (`glab issue note <child> --message "/blocked_by #<blocker>"`). Native blocking links are a Premium/Ultimate feature; on the free tier (or where unavailable) fall back to a `Blocked by: #<n>, #<n>` line at the top of the description. A ticket is unblocked when every blocker is closed.
+- **Frontier query**: `glab issue list -F json` scoped to the map's children, drop any with an open blocker — a native `blocked_by` link to an open issue (`glab api projects/:id/issues/:iid/links`), or an open issue in the `Blocked by` line — or an assignee; first in map order wins.
+- **Claim**: `glab issue update <n> --assignee @me` — the session's first write.
+- **Resolve**: `glab issue note <n> --message "<answer>"`, then `glab issue close <n>`, then append a context pointer (gist + link) to the map's Decisions-so-far.
diff --git a/.agents/skills/setup-matt-pocock-skills/issue-tracker-local.md b/.agents/skills/setup-matt-pocock-skills/issue-tracker-local.md
index a2f08fb0..fbda5e04 100644
--- a/.agents/skills/setup-matt-pocock-skills/issue-tracker-local.md
+++ b/.agents/skills/setup-matt-pocock-skills/issue-tracker-local.md
@@ -1,12 +1,12 @@
 # Issue tracker: Local Markdown
 
-Issues and PRDs for this repo live as markdown files in `.scratch/`.
+Issues and specs for this repo live as markdown files in `.scratch/`.
 
 ## Conventions
 
 - One feature per directory: `.scratch/<feature-slug>/`
-- The PRD is `.scratch/<feature-slug>/PRD.md`
-- Implementation issues are `.scratch/<feature-slug>/issues/<NN>-<slug>.md`, numbered from `01`
+- The spec is `.scratch/<feature-slug>/spec.md`
+- Implementation issues are one file per ticket at `.scratch/<feature-slug>/issues/<NN>-<slug>.md`, numbered from `01` — never a single combined tickets file
 - Triage state is recorded as a `Status:` line near the top of each issue file (see `triage-labels.md` for the role strings)
 - Comments and conversation history append to the bottom of the file under a `## Comments` heading
 
@@ -17,3 +17,14 @@ Create a new file under `.scratch/<feature-slug>/` (creating the directory if ne
 ## When a skill says "fetch the relevant ticket"
 
 Read the file at the referenced path. The user will normally pass the path or the issue number directly.
+
+## Wayfinding operations
+
+Used by `/wayfinder`. The **map** is a file with one **child** file per ticket.
+
+- **Map**: `.scratch/<effort>/map.md` — the Notes / Decisions-so-far / Fog body.
+- **Child ticket**: `.scratch/<effort>/issues/NN-<slug>.md`, numbered from `01`, with the question in the body. A `Type:` line records the ticket type (`research`/`prototype`/`grilling`/`task`); a `Status:` line records `claimed`/`resolved`.
+- **Blocking**: a `Blocked by: NN, NN` line near the top. A ticket is unblocked when every file it lists is `resolved`.
+- **Frontier**: scan `.scratch/<effort>/issues/` for files that are open, unblocked, and unclaimed; first by number wins.
+- **Claim**: set `Status: claimed` and save before any work.
+- **Resolve**: append the answer under an `## Answer` heading, set `Status: resolved`, then append a context pointer (gist + link) to the map's Decisions-so-far in `map.md`.
diff --git a/.agents/skills/setup-matt-pocock-skills/triage-labels.md b/.agents/skills/setup-matt-pocock-skills/triage-labels.md
index 72b06c21..b716855d 100644
--- a/.agents/skills/setup-matt-pocock-skills/triage-labels.md
+++ b/.agents/skills/setup-matt-pocock-skills/triage-labels.md
@@ -1,20 +1,15 @@
 # Triage Labels
 
-The skills speak in terms of canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
+The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
 
-This repo uses the 8-state vocabulary owned by `unic-archon-dlc` (see `docs/agents/labels.md`). Note `rejected` is the canonical "will not be actioned" label here, **not** `wontfix`.
+| Label in mattpocock/skills | Label in our tracker | Meaning                                  |
+| -------------------------- | -------------------- | ---------------------------------------- |
+| `needs-triage`             | `needs-triage`       | Maintainer needs to evaluate this issue  |
+| `needs-info`               | `needs-info`         | Waiting on reporter for more information |
+| `ready-for-agent`          | `ready-for-agent`    | Fully specified, ready for an AFK agent  |
+| `ready-for-human`          | `ready-for-human`    | Requires human implementation            |
+| `wontfix`                  | `wontfix`            | Will not be actioned                     |
 
-| Role             | Label             | Meaning                                          |
-| ---------------- | ----------------- | ------------------------------------------------ |
-| Needs evaluation | `needs-triage`    | Maintainer needs to evaluate this issue          |
-| Needs info       | `needs-info`      | Waiting on reporter for more information         |
-| Needs specs      | `needs-specs`     | Enough info from reporter; ready to write a spec |
-| Ready for agent  | `ready-for-agent` | Fully specified, ready for an AFK agent          |
-| Ready for human  | `ready-for-human` | Requires human implementation                    |
-| Resolved         | `resolved`        | Implemented; ready for a PR                      |
-| Closed           | `closed`          | PR has been merged                               |
-| Won't fix        | `rejected`        | Will not be actioned (older skills call this role `wontfix`) |
-
-When a skill mentions a role (e.g. "apply the AFK-ready label", or the legacy `wontfix` role), use the corresponding label string from this table.
+When a skill mentions a role (e.g. "apply the AFK-ready triage label"), use the corresponding label string from this table.
 
 Edit the right-hand column to match whatever vocabulary you actually use.
diff --git a/.agents/skills/tdd/SKILL.md b/.agents/skills/tdd/SKILL.md
index 7a989411..ead7781d 100644
--- a/.agents/skills/tdd/SKILL.md
+++ b/.agents/skills/tdd/SKILL.md
@@ -1,109 +1,38 @@
 ---
 name: tdd
-description: Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
+description: Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
 ---
 
 # Test-Driven Development
 
-## Philosophy
+TDD is the red → green loop. This skill is the reference that makes that loop produce tests worth keeping: what a good test is, where tests go, the anti-patterns, and the rules of the loop. Every section applies on every cycle — consult them before and during the loop, not after.
 
-**Core principle**: Tests should verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't.
+When exploring the codebase, read `CONTEXT.md` (if it exists) so test names and interface vocabulary match the project's domain language, and respect ADRs in the area you're touching.
 
-**Good tests** are integration-style: they exercise real code paths through public APIs. They describe _what_ the system does, not _how_ it does it. A good test reads like a specification - "user can checkout with valid cart" tells you exactly what capability exists. These tests survive refactors because they don't care about internal structure.
+## What a good test is
 
-**Bad tests** are coupled to implementation. They mock internal collaborators, test private methods, or verify through external means (like querying a database directly instead of using the interface). The warning sign: your test breaks when you refactor, but behavior hasn't changed. If you rename an internal function and tests fail, those tests were testing implementation, not behavior.
+Tests verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't. A good test reads like a specification — "user can checkout with valid cart" tells you exactly what capability exists — and survives refactors because it doesn't care about internal structure.
 
 See [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines.
 
-## Anti-Pattern: Horizontal Slices
+## Seams — where tests go
 
-**DO NOT write all tests first, then all implementation.** This is "horizontal slicing" - treating RED as "write all tests" and GREEN as "write all code."
+A **seam** is the public boundary you test at: the interface where you observe behavior without reaching inside. Tests live at seams, never against internals.
 
-This produces **crap tests**:
+**Test only at pre-agreed seams.** Before writing any test, write down the seams under test and confirm them with the user. No test is written at an unconfirmed seam. You can't test everything — agreeing the seams up front is how testing effort lands on the critical paths and complex logic instead of every edge case.
 
-- Tests written in bulk test _imagined_ behavior, not _actual_ behavior
-- You end up testing the _shape_ of things (data structures, function signatures) rather than user-facing behavior
-- Tests become insensitive to real changes - they pass when behavior breaks, fail when behavior is fine
-- You outrun your headlights, committing to test structure before understanding the implementation
+Ask: "What's the public interface, and which seams should we test?"
 
-**Correct approach**: Vertical slices via tracer bullets. One test → one implementation → repeat. Each test responds to what you learned from the previous cycle. Because you just wrote the code, you know exactly what behavior matters and how to verify it.
+When the shape of that interface is itself in question — how deep the module is, where the seam belongs, what the interface should expose — use the `/codebase-design` skill for the vocabulary. It is the shared source of the module, interface, depth, seam, adapter, leverage and locality terms, and it is a reference to consult, not a session to run.
 
-```
-WRONG (horizontal):
-  RED:   test1, test2, test3, test4, test5
-  GREEN: impl1, impl2, impl3, impl4, impl5
+## Anti-patterns
 
-RIGHT (vertical):
-  RED→GREEN: test1→impl1
-  RED→GREEN: test2→impl2
-  RED→GREEN: test3→impl3
-  ...
-```
+- **Implementation-coupled** — mocks internal collaborators, tests private methods, or verifies through a side channel (querying the database instead of using the interface). The tell: the test breaks when you refactor but behavior hasn't changed.
+- **Tautological** — the assertion recomputes the expected value the way the code does (`expect(add(a, b)).toBe(a + b)`, a snapshot derived by hand the same way, a constant asserted equal to itself), so it passes by construction and can never disagree with the code. Expected values must come from an independent source of truth — a known-good literal, a worked example, the spec.
+- **Horizontal slicing** — writing all tests first, then all implementation. Bulk tests verify _imagined_ behavior: you test the _shape_ of things rather than user-facing behavior, the tests go insensitive to real changes, and you commit to test structure before understanding the implementation. Work in **vertical slices** instead — one test → one implementation → repeat, each test a **tracer bullet** that responds to what the last cycle taught you.
 
-## Workflow
+## Rules of the loop
 
-### 1. Planning
-
-When exploring the codebase, use the project's domain glossary so that test names and interface vocabulary match the project's language, and respect ADRs in the area you're touching.
-
-Before writing any code:
-
-- [ ] Confirm with user what interface changes are needed
-- [ ] Confirm with user which behaviors to test (prioritize)
-- [ ] Identify opportunities for [deep modules](deep-modules.md) (small interface, deep implementation)
-- [ ] Design interfaces for [testability](interface-design.md)
-- [ ] List the behaviors to test (not implementation steps)
-- [ ] Get user approval on the plan
-
-Ask: "What should the public interface look like? Which behaviors are most important to test?"
-
-**You can't test everything.** Confirm with the user exactly which behaviors matter most. Focus testing effort on critical paths and complex logic, not every possible edge case.
-
-### 2. Tracer Bullet
-
-Write ONE test that confirms ONE thing about the system:
-
-```
-RED:   Write test for first behavior → test fails
-GREEN: Write minimal code to pass → test passes
-```
-
-This is your tracer bullet - proves the path works end-to-end.
-
-### 3. Incremental Loop
-
-For each remaining behavior:
-
-```
-RED:   Write next test → fails
-GREEN: Minimal code to pass → passes
-```
-
-Rules:
-
-- One test at a time
-- Only enough code to pass current test
-- Don't anticipate future tests
-- Keep tests focused on observable behavior
-
-### 4. Refactor
-
-After all tests pass, look for [refactor candidates](refactoring.md):
-
-- [ ] Extract duplication
-- [ ] Deepen modules (move complexity behind simple interfaces)
-- [ ] Apply SOLID principles where natural
-- [ ] Consider what new code reveals about existing code
-- [ ] Run tests after each refactor step
-
-**Never refactor while RED.** Get to GREEN first.
-
-## Checklist Per Cycle
-
-```
-[ ] Test describes behavior, not implementation
-[ ] Test uses public interface only
-[ ] Test would survive internal refactor
-[ ] Code is minimal for this test
-[ ] No speculative features added
-```
+- **Red before green.** Write the failing test first, then only enough code to pass it. Don't anticipate future tests or add speculative features.
+- **One slice at a time.** One seam, one test, one minimal implementation per cycle.
+- **Refactoring is not part of the loop.** It belongs to the review stage (see the `code-review` skill), not the red → green implementation cycle.
diff --git a/.agents/skills/tdd/agents/openai.yaml b/.agents/skills/tdd/agents/openai.yaml
new file mode 100644
index 00000000..651b838a
--- /dev/null
+++ b/.agents/skills/tdd/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "TDD"
+  short_description: "Test-driven red-green-refactor"
diff --git a/.agents/skills/tdd/deep-modules.md b/.agents/skills/tdd/deep-modules.md
deleted file mode 100644
index 0d9720cf..00000000
--- a/.agents/skills/tdd/deep-modules.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# Deep Modules
-
-From "A Philosophy of Software Design":
-
-**Deep module** = small interface + lots of implementation
-
-```
-┌─────────────────────┐
-│   Small Interface   │  ← Few methods, simple params
-├─────────────────────┤
-│                     │
-│                     │
-│  Deep Implementation│  ← Complex logic hidden
-│                     │
-│                     │
-└─────────────────────┘
-```
-
-**Shallow module** = large interface + little implementation (avoid)
-
-```
-┌─────────────────────────────────┐
-│       Large Interface           │  ← Many methods, complex params
-├─────────────────────────────────┤
-│  Thin Implementation            │  ← Just passes through
-└─────────────────────────────────┘
-```
-
-When designing interfaces, ask:
-
-- Can I reduce the number of methods?
-- Can I simplify the parameters?
-- Can I hide more complexity inside?
diff --git a/.agents/skills/tdd/interface-design.md b/.agents/skills/tdd/interface-design.md
deleted file mode 100644
index a0a20ca4..00000000
--- a/.agents/skills/tdd/interface-design.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# Interface Design for Testability
-
-Good interfaces make testing natural:
-
-1. **Accept dependencies, don't create them**
-
-   ```typescript
-   // Testable
-   function processOrder(order, paymentGateway) {}
-
-   // Hard to test
-   function processOrder(order) {
-     const gateway = new StripeGateway();
-   }
-   ```
-
-2. **Return results, don't produce side effects**
-
-   ```typescript
-   // Testable
-   function calculateDiscount(cart): Discount {}
-
-   // Hard to test
-   function applyDiscount(cart): void {
-     cart.total -= discount;
-   }
-   ```
-
-3. **Small surface area**
-   - Fewer methods = fewer tests needed
-   - Fewer params = simpler test setup
diff --git a/.agents/skills/tdd/refactoring.md b/.agents/skills/tdd/refactoring.md
deleted file mode 100644
index 8a444392..00000000
--- a/.agents/skills/tdd/refactoring.md
+++ /dev/null
@@ -1,10 +0,0 @@
-# Refactor Candidates
-
-After TDD cycle, look for:
-
-- **Duplication** → Extract function/class
-- **Long methods** → Break into private helpers (keep tests on public interface)
-- **Shallow modules** → Combine or deepen
-- **Feature envy** → Move logic to where data lives
-- **Primitive obsession** → Introduce value objects
-- **Existing code** the new code reveals as problematic
diff --git a/.agents/skills/tdd/tests.md b/.agents/skills/tdd/tests.md
index ff22f809..7ab86479 100644
--- a/.agents/skills/tdd/tests.md
+++ b/.agents/skills/tdd/tests.md
@@ -59,3 +59,19 @@ test("createUser makes user retrievable", async () => {
   expect(retrieved.name).toBe("Alice");
 });
 ```
+
+**Tautological tests**: Expected value restates the implementation, so the test passes by construction.
+
+```typescript
+// BAD: Expected value is recomputed the way the code computes it
+test("calculateTotal sums line items", () => {
+  const items = [{ price: 10 }, { price: 5 }];
+  const expected = items.reduce((sum, i) => sum + i.price, 0);
+  expect(calculateTotal(items)).toBe(expected);
+});
+
+// GOOD: Expected value is an independent, known literal
+test("calculateTotal sums line items", () => {
+  expect(calculateTotal([{ price: 10 }, { price: 5 }])).toBe(15);
+});
+```
diff --git a/.agents/skills/teach/GLOSSARY-FORMAT.md b/.agents/skills/teach/GLOSSARY-FORMAT.md
new file mode 100644
index 00000000..9cae84c4
--- /dev/null
+++ b/.agents/skills/teach/GLOSSARY-FORMAT.md
@@ -0,0 +1,35 @@
+# GLOSSARY.md Format
+
+`GLOSSARY.md` is the canonical language for this teaching workspace. All explainers, exercises, and learning records should adhere to its terminology. Building it is itself part of learning: compressing a concept into a tight definition is evidence the user understands it.
+
+## Structure
+
+```md
+# {Topic} Glossary
+
+{One or two sentence description of the topic this glossary covers.}
+
+## Terms
+
+**Hypertrophy**:
+Muscle growth driven by mechanical tension and metabolic stress over repeated training sessions.
+_Avoid_: Bulking, getting big
+
+**Progressive overload**:
+Systematically increasing the demand on a muscle over time — via load, volume, or intensity.
+_Avoid_: Pushing harder, levelling up
+
+**RPE (Rate of Perceived Exertion)**:
+A 1–10 self-rating of how hard a set felt, where 10 is failure and 8 means two reps left in the tank.
+_Avoid_: Effort score, intensity rating
+```
+
+## Rules
+
+- **Add a term only when the user understands it.** The glossary is a record of compressed knowledge, not a dictionary the user reads to learn. If the user has just been introduced to a concept, wait until they can use it correctly before promoting it here.
+- **Be opinionated.** When several words exist for the same concept, pick the best one and list the rest as aliases to avoid. This is how language compresses.
+- **Keep definitions tight.** One or two sentences. Define what the term IS, not what it does or how to do it.
+- **Use the glossary's own terms inside definitions.** Once a term is in the glossary, prefer it everywhere — including inside other definitions. This is what makes complex terms easier to grasp later.
+- **Group under subheadings** when natural clusters emerge (e.g. `## Anatomy`, `## Programming`). A flat list is fine when terms cohere.
+- **Flag ambiguities explicitly.** If a term is used loosely in the wider field, note the resolution: "In this workspace, 'set' always means a working set — warm-ups are tracked separately."
+- **Revise as understanding deepens.** A definition the user wrote in week one may be wrong by week six. Update in place; do not leave stale entries.
diff --git a/.agents/skills/teach/LEARNING-RECORD-FORMAT.md b/.agents/skills/teach/LEARNING-RECORD-FORMAT.md
new file mode 100644
index 00000000..2faa7c98
--- /dev/null
+++ b/.agents/skills/teach/LEARNING-RECORD-FORMAT.md
@@ -0,0 +1,46 @@
+# Learning Record Format
+
+Learning records live in `./learning-records/` and use sequential numbering: `0001-slug.md`, `0002-slug.md`, etc. Create the directory lazily — only when the first record is written.
+
+They are the teaching equivalent of ADRs: they capture non-obvious lessons, key insights, and stated prior knowledge that will steer future sessions. They are used to calculate the zone of proximal development.
+
+## Template
+
+```md
+# {Short title of what was learned or established}
+
+{1-3 sentences: what was learned (or what prior knowledge was established), and why it matters for future sessions.}
+```
+
+That is the whole format. A learning record can be a single paragraph. The value is recording _that_ this is now known and _why_ it changes what to teach next — not in filling out sections.
+
+## Optional sections
+
+Only include these when they add genuine value. Most records won't need them.
+
+- **Status** frontmatter (`active | superseded by LR-NNNN`) — useful when an earlier understanding turns out to be wrong and is replaced.
+- **Evidence** — how the user demonstrated the understanding (a question answered, an exercise completed, prior experience cited). Useful when the claim might be revisited.
+- **Implications** — what this unlocks or rules out for future sessions. Worth recording when non-obvious.
+
+## Numbering
+
+Scan `./learning-records/` for the highest existing number and increment by one.
+
+## When to write a learning record
+
+Write one when any of these is true:
+
+1. **The user demonstrated genuine understanding of something non-trivial** — not just exposure, but evidence they can use the concept correctly. This sets a new floor for what to teach next.
+2. **The user disclosed prior knowledge** — "I already know X." Record it so future sessions don't re-teach it. Also record the _depth_ claimed.
+3. **A misconception was corrected** — the user previously believed something wrong and now sees why. These are high-value: they predict future stumbling blocks for related topics.
+4. **The mission shifted in response to learning** — the user discovered they cared about something different than they thought. Cross-link to [[MISSION.md]] and update it.
+
+### What does _not_ qualify
+
+- Material that was merely covered. Coverage is not learning. Wait for evidence.
+- Anything already captured tersely in [[GLOSSARY.md]] as a term definition. Don't duplicate.
+- Session-by-session activity logs. Learning records are not a journal — they are decision-grade insights.
+
+## Supersession
+
+When a later record contradicts an earlier one (the user's understanding deepened or corrected), mark the old record `Status: superseded by LR-NNNN` rather than deleting it. The history of how understanding evolved is itself useful signal.
diff --git a/.agents/skills/teach/MISSION-FORMAT.md b/.agents/skills/teach/MISSION-FORMAT.md
new file mode 100644
index 00000000..5dac184a
--- /dev/null
+++ b/.agents/skills/teach/MISSION-FORMAT.md
@@ -0,0 +1,31 @@
+# MISSION.md Format
+
+`MISSION.md` lives at the workspace root. It captures the _reason_ the user is learning this topic. Every teaching decision — what to teach next, which resources to surface, which exercises to design — should trace back to this document.
+
+## Template
+
+```md
+# Mission: {Topic}
+
+## Why
+{1-3 sentences. The concrete real-world goal the user is chasing. What changes in their life or work when they have this skill? Avoid abstract framings like "to understand X" — push for the underlying outcome.}
+
+## Success looks like
+- {A specific, observable thing the user will be able to do}
+- {Another specific thing}
+- {…}
+
+## Constraints
+- {Time, budget, prior commitments, learning preferences, anything that bounds the approach}
+
+## Out of scope
+- {Adjacent topics the user explicitly does not want to chase right now — protects the zone of proximal development}
+```
+
+## Rules
+
+- **One mission per workspace.** If the user wants to learn two unrelated things, that is two workspaces.
+- **Concrete over abstract.** "Run a half marathon by October" beats "get fitter." "Ship a Rust CLI to my team" beats "learn Rust."
+- **Push back on vagueness.** If the user cannot articulate why, interview them before writing anything. A bad mission is worse than no mission.
+- **Revise when reality shifts.** Missions change. When the user's goal moves, update this file — don't leave a stale mission steering future sessions.
+- **Keep it short.** If `MISSION.md` runs past a screen, it has stopped being a compass and started being a plan.
diff --git a/.agents/skills/teach/RESOURCES-FORMAT.md b/.agents/skills/teach/RESOURCES-FORMAT.md
new file mode 100644
index 00000000..c94aac6a
--- /dev/null
+++ b/.agents/skills/teach/RESOURCES-FORMAT.md
@@ -0,0 +1,32 @@
+# RESOURCES.md Format
+
+`RESOURCES.md` is the curated set of trusted sources for this topic. Knowledge for explainers should be drawn from here, not from parametric guesses. Wisdom comes from the communities listed here.
+
+## Structure
+
+```md
+# {Topic} Resources
+
+## Knowledge
+
+- [Book: _The Science and Practice of Strength Training_ — Zatsiorsky & Kraemer](https://example.com)
+  Foundational text on programming and adaptation. Use for: anything to do with periodisation, recovery, intensity zones.
+- [Article: "How Much Should I Train?" — Greg Nuckols (Stronger By Science)](https://example.com)
+  Evidence-based review of volume landmarks. Use for: weekly set targets per muscle group.
+
+## Wisdom (Communities)
+
+- [r/weightroom](https://reddit.com/r/weightroom)
+  High-signal subreddit, moderated against bro-science. Use for: programme critique, plateau troubleshooting.
+- Local: Tuesday strength class at {gym name}
+  Use for: real-time coaching feedback on lifts.
+```
+
+## Rules
+
+- **High-trust only.** Prefer primary sources, recognised experts, peer-reviewed work, and communities with strong moderation. If a resource is marketing dressed as education, leave it out.
+- **Annotate every entry.** A bare link is useless in three months. Add one line: what it covers and when to reach for it.
+- **Group by Knowledge / Wisdom.** Mirrors the philosophy in [SKILL.md](./SKILL.md). It is fine for a resource to appear in only one group.
+- **Surface gaps explicitly.** If no good resource exists for an area the mission needs, write a `## Gaps` section listing what is missing. This drives future search.
+- **Prune ruthlessly.** A resource that turned out to be wrong, shallow, or off-mission should be removed, not buried. Better five sharp sources than thirty mediocre ones.
+- **Record community preferences.** If the user has opted out of joining communities, note it here so future sessions don't keep proposing them.
diff --git a/.agents/skills/teach/SKILL.md b/.agents/skills/teach/SKILL.md
new file mode 100644
index 00000000..b1603e5a
--- /dev/null
+++ b/.agents/skills/teach/SKILL.md
@@ -0,0 +1,140 @@
+---
+name: teach
+description: Teach the user a new skill or concept, within this workspace.
+disable-model-invocation: true
+argument-hint: "What would you like to learn about?"
+---
+
+The user has asked you to teach them something. This is a stateful request - they intend to learn the topic over multiple sessions.
+
+## Teaching Workspace
+
+Treat the current directory as a teaching workspace. The state of their learning is captured in this directory in several files:
+
+- `MISSION.md`: A document capturing the _reason_ the user is interested in the topic. This should be used to ground all teaching. Use the format in [MISSION-FORMAT.md](./MISSION-FORMAT.md).
+- `./reference/*.html`: A directory of reference materials. These are the compressed learnings from the lessons - cheat sheets, reference algorithms, syntax, yoga poses, glossaries. They are the raw units of learning. They should be beautiful documents which print out well, and are designed for quick reference.
+- `RESOURCES.md`: A list of resources which can be explored to ground your teaching in contextual knowledge, or to acquire knowledge and wisdom. Use the format in [RESOURCES-FORMAT.md](./RESOURCES-FORMAT.md).
+- `./learning-records/*.md`: A directory of learning records, which capture what the user has learned. These are loosely equivalent to architectural decision records in software development - they capture non-obvious lessons and key insights that may need to be revised later, or drive future sessions. These should be used to calculate the zone of proximal development. They are titled `0001-<dash-case-name>.md`, where the number increments each time. Use the format in [LEARNING-RECORD-FORMAT.md](./LEARNING-RECORD-FORMAT.md).
+- `./lessons/*.html`: A directory of lessons. A **lesson** is a single, self-contained HTML output that teaches one tightly-scoped thing tied to the mission. This is the primary unit of teaching in this workspace.
+- `./assets/*`: Reusable **components** shared across lessons. See [Assets](#assets).
+- `NOTES.md`: A scratchpad for you to jot down user preferences, or working notes.
+
+## Philosophy
+
+To learn at a deep level, the user needs three things:
+
+- **Knowledge**, captured from high-quality, high-trust resources
+- **Skills**, acquired through highly-relevant interactive lessons devised by you, based on the knowledge
+- **Wisdom**, which comes from interacting with other learners and practitioners
+
+Before the `RESOURCES.md` is well-populated, your focus should be to find high-quality resources which will help the user acquire knowledge. Never trust your parametric knowledge.
+
+Some topics may require more skills than knowledge. Learning more about theoretical physics might be more knowledge-based. For yoga, more skills-based.
+
+### Fluency vs Storage Strength
+
+You should be careful to split between two types of learning:
+
+- **Fluency strength**: in-the-moment retrieval of knowledge
+- **Storage strength**: long-term retention of knowledge
+
+Fluency can give the user an illusory sense of mastery, but storage strength is the real goal. Try to design lessons which build long-term retention by desirable difficulty:
+
+- Using retrieval practice (recall from memory)
+- Spacing (distributing practice over time)
+- Interleaving (mixing up different but related topics in practice - for skills practice only)
+
+## Lessons
+
+A lesson is the main thing you produce — the unit in which knowledge and skills reach the user. Each lesson is one self-contained HTML file, saved to `./lessons/` and titled `0001-<dash-case-name>.html` where the number increments each time.
+
+A lesson should be **beautiful** — clean, readable typography and layout — since the user will return to these later to review. Think Tufte.
+
+The lesson should be short, and completable very quickly. Learners' working memory is very small, and we need to stay within it. But each lesson should give the user a single tangible win that they can build on. It should be directly tied to the mission, and should be in the user's zone of proximal development.
+
+If possible, open the lesson file for the user by running a CLI command.
+
+Each lesson should link via HTML anchors to other lessons and reference documents.
+
+Each lesson should recommend a primary source for the user to read or watch. This should be the most high-quality, high-trust resource you found on the topic.
+
+Each lesson should contain a reminder to ask followup questions to the agent. The agent is their teacher, and can assist with anything that's unclear.
+
+## Assets
+
+Lessons are built from reusable **components**, stored in `./assets/`: stylesheets, quiz widgets, simulators, diagram helpers — anything a second lesson could reuse.
+
+Reuse is the default, not the exception. Before authoring a lesson, read `./assets/` and build from the components already there. When a lesson needs something new and reusable, write it as a component in `./assets/` and link to it — never inline code a future lesson would duplicate.
+
+A shared stylesheet is the first component every workspace earns: every lesson links it, so the lessons look like one consistent course rather than a pile of one-offs. As the workspace grows, so should the component library.
+
+## The Mission
+
+Every lesson should be tied into the mission - the reason that the user is interested in learning about the topic.
+
+If the user is unclear about the mission, or the `MISSION.md` is not populated, your first job should be to question the user on why they want to learn this.
+
+Failing to understand the mission will mean knowledge acquisition is not grounded in real-world goals. Lessons will feel too abstract. You will have no way of judging what the user should do next.
+
+Missions may change as the user develops more skills and knowledge. This is normal - make sure to update the `MISSION.md` and add a learning record to capture the change. Confirm with the user before changing the mission.
+
+## Zone Of Proximal Development
+
+Each lesson, the user should always feel as if they are being challenged 'just enough'.
+
+The user may specify an exact thing they want to learn. If they don't, figure out their zone of proximal development by:
+
+- Reading their `learning-records`
+- Figuring out the right thing to teach them based on their mission
+- Teach the most relevant thing that fits in their zone of proximal development
+
+## Knowledge
+
+Lessons should be designed around a skill the user is going to learn. The knowledge in the lesson should be only what's required to acquire that skill. You teach the knowledge first, then get the user to practice the skills via an interactive feedback loop.
+
+Knowledge should first be gathered from trusted resources. Use `RESOURCES.md` to keep track of them. Lessons should be littered with citations - links to external resources to back up any claim made. This increases the trustworthiness of the lesson.
+
+For acquiring knowledge, difficulty is the enemy. It eats working memory you need for understanding.
+
+## Skills
+
+If knowledge is all about acquisition, skills are about durability and flexibility. Make the knowledge stick.
+
+For skill acquisition, difficulty is the tool. Effortful retrieval is what builds storage strength. Skills should be taught through interactive lessons. There are several tools at your disposal:
+
+- Interactive lessons, using quizzes and light in-browser tasks
+- Lessons which guide the user through a list of real-world steps to take (for instance, yoga poses)
+
+Each of these should be based on a **feedback loop**, where the user receives feedback on their performance. This feedback loop should be as tight as possible, giving feedback immediately - and ideally automatically.
+
+For quizzes, each answer should be exactly the same number of words (and characters, if possible). Don't give the user any clues about the answer through formatting.
+
+## Acquiring Wisdom
+
+Wisdom comes from true real-world interaction - testing your skills outside the learning environment.
+
+When the user asks a question that appears to require wisdom, your default posture should be to attempt to answer - but to ultimately delegate to a **community**.
+
+A community is a place (online or offline) where the user can test their skills in the real world. This might be a forum, a subreddit, a real-world class (budget permitting) or a local interest group.
+
+You should attempt to find high-reputation communities the user can join. If the user expresses a preference that they don't want to join a community, respect it.
+
+## Reference Documents
+
+While creating lessons, you should also create reference documents. Lessons can reference these documents - they are useful for tracking raw units of knowledge useful across lessons.
+
+Lessons will rarely be revisited later - reference documents will be. They should be the compressed essence of the lesson, in a format designed for quick reference.
+
+Some learning topics lend themselves to reference:
+
+- Syntax and code snippets for programming
+- Algorithms and flowcharts for processes
+- Yoga poses and sequences for yoga
+- Exercises and routines for fitness
+- Glossaries for any topic with its own nomenclature
+
+Glossaries, in particular, are an essential reference. Once one is created, it should be adhered to in every lesson.
+
+## `NOTES.md`
+
+The user will sometimes express preferences of how they want to be taught, or things you should keep in mind. This is the place to record those preferences, so you can refer back to them when designing lessons or working with the user.
diff --git a/.agents/skills/teach/agents/openai.yaml b/.agents/skills/teach/agents/openai.yaml
new file mode 100644
index 00000000..3452a850
--- /dev/null
+++ b/.agents/skills/teach/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Teach"
+  short_description: "Learn a concept in a guided workspace"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/to-issues/SKILL.md b/.agents/skills/to-issues/SKILL.md
deleted file mode 100644
index 9f6efbfe..00000000
--- a/.agents/skills/to-issues/SKILL.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-name: to-issues
-description: Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
----
-
-# To Issues
-
-Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
-
-The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
-
-## Process
-
-### 1. Gather context
-
-Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.
-
-### 2. Explore the codebase (optional)
-
-If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
-
-### 3. Draft vertical slices
-
-Break the plan into **tracer bullet** issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
-
-Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.
-
-<vertical-slice-rules>
-- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
-- A completed slice is demoable or verifiable on its own
-- Prefer many thin slices over few thick ones
-</vertical-slice-rules>
-
-### 4. Quiz the user
-
-Present the proposed breakdown as a numbered list. For each slice, show:
-
-- **Title**: short descriptive name
-- **Type**: HITL / AFK
-- **Blocked by**: which other slices (if any) must complete first
-- **User stories covered**: which user stories this addresses (if the source material has them)
-
-Ask the user:
-
-- Does the granularity feel right? (too coarse / too fine)
-- Are the dependency relationships correct?
-- Should any slices be merged or split further?
-- Are the correct slices marked as HITL and AFK?
-
-Iterate until the user approves the breakdown.
-
-### 5. Publish the issues to the issue tracker
-
-For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.
-
-Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
-
-<issue-template>
-## Parent
-
-A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).
-
-## What to build
-
-A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
-
-Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
-
-## Acceptance criteria
-
-- [ ] Criterion 1
-- [ ] Criterion 2
-- [ ] Criterion 3
-
-## Blocked by
-
-- A reference to the blocking ticket (if any)
-
-Or "None - can start immediately" if no blockers.
-
-</issue-template>
-
-Do NOT close or modify any parent issue.
diff --git a/.agents/skills/to-questionnaire/SKILL.md b/.agents/skills/to-questionnaire/SKILL.md
new file mode 100644
index 00000000..1423375b
--- /dev/null
+++ b/.agents/skills/to-questionnaire/SKILL.md
@@ -0,0 +1,53 @@
+---
+name: to-questionnaire
+description: Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
+disable-model-invocation: true
+---
+
+Turn something the user can't answer alone into a **questionnaire** — a Markdown document they hand to one person to fill in async, or fill out together over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.
+
+**Grill the send, not the subject.** Interview the user only about the _send_, which they can always answer: who it goes to, and what they need back. The questions in the document then target the **gap** between what the recipient knows and what the user needs.
+
+1. **Who is it going to?** Ask, in one exchange, the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user doesn't.
+
+2. **What do you need back?** Ask, in one exchange, the specific decisions or facts the user can't resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide.
+
+3. **Write the questionnaire.** Draft questions aimed at the gap from steps 1–2, following the Document structure below. Write it to `to-questionnaire-<slug>.md` in the current directory (slug from the topic) and report the path. Done when the file exists and every item the user named in step 2 is covered by a question.
+
+## Document structure
+
+Frame the document as a **discovery questionnaire**: the user lacks context, the recipient holds it. Order questions most-important-first — async means you may only get one pass — and group them under `##` headings by theme once there are more than a handful. Write it using the template below.
+
+<questionnaire-template>
+
+# <Questionnaire title>
+
+**Purpose:** why this questionnaire exists and the decision riding on it.
+
+**From:** <the user> — **To:** <the recipient> — **How your answers will be used:** <where they go>
+
+## Context
+
+One paragraph orienting a recipient who wasn't in the user's head. Enough to answer well, not a page.
+
+## How to answer
+
+Deadline and rough effort. Partial answers and "I don't know" are useful — flag anything you're unsure of rather than skipping it.
+
+## <Theme heading>
+
+One `##` section per theme. Under each, its questions, most-important-first. Every question is one idea — never compound — with an answer stub directly beneath, and a one-line _why this matters_ only where the question could be misread or invite a throwaway answer.
+
+<question-example>
+### What load is the system expected to handle at launch?
+
+_Why this matters: it decides whether we provision for burst traffic now or defer it._
+
+>
+</question-example>
+
+## Anything else?
+
+A closing catch-all: anything we didn't ask that we should know?
+
+</questionnaire-template>
diff --git a/.agents/skills/to-questionnaire/agents/openai.yaml b/.agents/skills/to-questionnaire/agents/openai.yaml
new file mode 100644
index 00000000..a58d1476
--- /dev/null
+++ b/.agents/skills/to-questionnaire/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "To Questionnaire"
+  short_description: "Front-load questions into a doc for someone to answer"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/to-prd/SKILL.md b/.agents/skills/to-spec/SKILL.md
similarity index 65%
rename from .agents/skills/to-prd/SKILL.md
rename to .agents/skills/to-spec/SKILL.md
index 47a01d4e..3fd64959 100644
--- a/.agents/skills/to-prd/SKILL.md
+++ b/.agents/skills/to-spec/SKILL.md
@@ -1,25 +1,24 @@
 ---
-name: to-prd
-description: Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
+name: to-spec
+description: Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
+disable-model-invocation: true
 ---
 
-This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
+This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user — just synthesize what you already know.
 
 The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
 
 ## Process
 
-1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
+1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
 
-2. Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.
+2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
 
-A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.
+Check with the user that these seams match their expectations.
 
-Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
+3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.
 
-3. Write the PRD using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.
-
-<prd-template>
+<spec-template>
 
 ## Problem Statement
 
@@ -67,10 +66,10 @@ A list of testing decisions that were made. Include:
 
 ## Out of Scope
 
-A description of the things that are out of scope for this PRD.
+A description of the things that are out of scope for this spec.
 
 ## Further Notes
 
 Any further notes about the feature.
 
-</prd-template>
+</spec-template>
diff --git a/.agents/skills/to-spec/agents/openai.yaml b/.agents/skills/to-spec/agents/openai.yaml
new file mode 100644
index 00000000..549e6f76
--- /dev/null
+++ b/.agents/skills/to-spec/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "To Spec"
+  short_description: "Turn a conversation into a spec"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/to-tickets/SKILL.md b/.agents/skills/to-tickets/SKILL.md
new file mode 100644
index 00000000..96deac51
--- /dev/null
+++ b/.agents/skills/to-tickets/SKILL.md
@@ -0,0 +1,105 @@
+---
+name: to-tickets
+description: Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
+disable-model-invocation: true
+---
+
+# To Tickets
+
+Break a plan, spec, or conversation into a set of **tickets** — tracer-bullet vertical slices, each declaring the tickets that **block** it.
+
+The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
+
+## Process
+
+### 1. Gather context
+
+Work from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.
+
+### 2. Explore the codebase (optional)
+
+If you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
+
+Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."
+
+### 3. Draft vertical slices
+
+Break the work into **tracer bullet** tickets.
+
+<vertical-slice-rules>
+
+- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer
+- A completed slice is demoable or verifiable on its own
+- Each slice is sized to fit in a single fresh context window
+- Any prefactoring should be done first
+
+</vertical-slice-rules>
+
+Give each ticket its **blocking edges** — the other tickets that must complete before it can start. A ticket with no blockers can start immediately.
+
+**Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change — rename a column, retype a shared symbol — whose **blast radius** fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as **expand–contract**. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket — green is promised only there.
+
+### 4. Quiz the user
+
+Present the proposed breakdown as a numbered list. For each ticket, show:
+
+- **Title**: short descriptive name
+- **Blocked by**: which other tickets (if any) must complete first
+- **What it delivers**: the end-to-end behaviour this ticket makes work
+
+Ask the user:
+
+- Does the granularity feel right? (too coarse / too fine)
+- Are the blocking edges correct — does each ticket only depend on tickets that genuinely gate it?
+- Should any tickets be merged or split further?
+
+Iterate until the user approves the breakdown.
+
+### 5. Publish the tickets to the configured tracker
+
+Publish the approved tickets. **How** depends on the tracker `/setup-matt-pocock-skills` configured — the tickets are the same either way, only the shape of the blocking edges changes:
+
+- **Local files** → write one file per ticket under `.scratch/<feature-slug>/issues/<NN>-<slug>.md`, numbered from `01` in dependency order (blockers first). Each file's "Blocked by" lists the numbers/titles it depends on. Use the per-ticket file template below — one ticket per file, never a single combined file.
+- **A real issue tracker (GitHub, Linear, …)** → publish one issue per ticket in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Use the platform's native blocking / sub-issue relationship where it has one; otherwise set each ticket's "Blocked by" to the blocking issues. Apply the `ready-for-agent` triage label unless instructed otherwise — the tickets are agent-grabbable by construction.
+
+Work the **frontier**: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.
+
+Do NOT close or modify any parent issue.
+
+<local-ticket-template>
+
+# <NN> — <Ticket title>
+
+**What to build:** the end-to-end behaviour this ticket makes work, from the user's perspective — not a layer-by-layer implementation list.
+
+**Blocked by:** the numbers/titles of the tickets that gate this one, or "None — can start immediately".
+
+**Status:** ready-for-agent
+
+- [ ] Acceptance criterion 1
+- [ ] Acceptance criterion 2
+
+</local-ticket-template>
+
+<issue-template>
+
+## Parent
+
+A reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).
+
+## What to build
+
+The end-to-end behaviour this ticket makes work, from the user's perspective — not layer-by-layer implementation.
+
+## Acceptance criteria
+
+- [ ] Criterion 1
+- [ ] Criterion 2
+
+## Blocked by
+
+- A reference to each blocking ticket, or "None — can start immediately".
+
+</issue-template>
+
+In either form, avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
diff --git a/.agents/skills/to-tickets/agents/openai.yaml b/.agents/skills/to-tickets/agents/openai.yaml
new file mode 100644
index 00000000..24605a5d
--- /dev/null
+++ b/.agents/skills/to-tickets/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "To Tickets"
+  short_description: "Split a plan into tracer-bullet tickets"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/triage/AGENT-BRIEF.md b/.agents/skills/triage/AGENT-BRIEF.md
index 2efecdfe..6535c9bd 100644
--- a/.agents/skills/triage/AGENT-BRIEF.md
+++ b/.agents/skills/triage/AGENT-BRIEF.md
@@ -1,6 +1,8 @@
 # Writing Agent Briefs
 
-An agent brief is a structured comment posted on a GitHub issue when it moves to `ready-for-agent`. It is the authoritative specification that an AFK agent will work from. The original issue body and discussion are context — the agent brief is the contract.
+An agent brief is a structured comment posted on a GitHub issue or PR when it moves to `ready-for-agent`. It is the authoritative specification that an AFK agent will work from. The original body and discussion are context — the agent brief is the contract.
+
+The brief states **what the agent should do**, which stretches to both surfaces: for an issue, that's building the change from nothing; for a PR, it's what's left to do *to the existing diff* — finish it, close gaps, address review points. Same principles either way; the PR example below shows the difference.
 
 ## Principles
 
@@ -143,6 +145,43 @@ checked for matches.
 - Bug reports (only enhancement rejections go to `.out-of-scope/`)
 ```
 
+### Good agent brief (PR)
+
+For a PR, "Current behavior" describes the state of the diff, and the brief asks the agent to finish or fix it rather than build from scratch.
+
+```markdown
+## Agent Brief
+
+**Category:** enhancement
+**Summary:** Finish the contributor's `--json` output flag for `triage list`
+
+**Current behavior:**
+The PR adds a `--json` flag that serializes the issue list to JSON. The happy
+path works and the diff matches the project's command structure. Two gaps
+remain: errors are still printed as human text (not JSON), and the new flag has
+no test coverage.
+
+**Desired behavior:**
+With `--json`, all output — including errors — is well-formed JSON on stdout,
+and the command's exit codes are unchanged. The existing human-readable output
+is untouched when the flag is absent.
+
+**Key interfaces:**
+- The command's error path should emit `{ "error": string }` under `--json`
+  instead of the plain-text error
+- Reuse the existing serializer the PR already added; don't introduce a second
+
+**Acceptance criteria:**
+- [ ] `triage list --json` emits valid JSON for both success and error cases
+- [ ] Exit codes match the non-JSON command
+- [ ] A test covers the `--json` success output and one error case
+- [ ] Default (non-JSON) output is byte-for-byte unchanged
+
+**Out of scope:**
+- Adding `--json` to any other command
+- Changing the JSON shape of the success payload the PR already defined
+```
+
 ### Bad agent brief
 
 ```markdown
diff --git a/.agents/skills/triage/OUT-OF-SCOPE.md b/.agents/skills/triage/OUT-OF-SCOPE.md
index cc8ea257..fc0e39f5 100644
--- a/.agents/skills/triage/OUT-OF-SCOPE.md
+++ b/.agents/skills/triage/OUT-OF-SCOPE.md
@@ -83,7 +83,11 @@ The maintainer may:
 
 ## When to write to `.out-of-scope/`
 
-Only when an **enhancement** (not a bug) is rejected as `wontfix`. The flow:
+Only when an **enhancement** (not a bug) is *rejected* as `wontfix`. This applies to enhancement PRs exactly as it does to issues — a rejected PR is recorded here so the same request doesn't return as fresh code.
+
+Do **not** write here when something is closed as `wontfix` because it's **already implemented**. That's a built feature, not a rejected one; recording it would poison the dedup checks with false rejections. Instead, the closing comment points to where the feature already lives.
+
+The flow:
 
 1. Maintainer decides a feature request is out of scope
 2. Check if a matching `.out-of-scope/` file already exists
diff --git a/.agents/skills/triage/SKILL.md b/.agents/skills/triage/SKILL.md
index 3dee68f9..e67b7bba 100644
--- a/.agents/skills/triage/SKILL.md
+++ b/.agents/skills/triage/SKILL.md
@@ -1,12 +1,15 @@
 ---
 name: triage
-description: Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
+description: Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
+disable-model-invocation: true
 ---
 
 # Triage
 
 Move issues on the project issue tracker through a small state machine of triage roles.
 
+If this repo treats external pull requests as a request surface (see the issue-tracker config), triage covers them too: **a PR is an issue with attached code** — same roles, same states, same machine, with a few deltas marked "for a PR" below. Resolve a bare `#42` to an issue or PR per the tracker config.
+
 Every comment or issue posted to the issue tracker during triage **must** start with this disclaimer:
 
 ```
@@ -33,6 +36,8 @@ Five **state** roles:
 - `ready-for-human` — needs human implementation
 - `wontfix` — will not be actioned
 
+For a PR, the same states read against the attached code: `ready-for-agent` means a brief is attached and an agent should take the next step on the diff; `ready-for-human` means it's ready for a human to merge.
+
 Every triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.
 
 These are canonical role names — the actual label strings used in the issue tracker may differ. The mapping should have been provided to you - run `/setup-matt-pocock-skills` if not.
@@ -44,7 +49,7 @@ State transitions: an unlabeled issue normally goes to `needs-triage` first; fro
 The maintainer invokes `/triage` and describes what they want in natural language. Interpret the request and act. Examples:
 
 - "Show me anything that needs my attention"
-- "Let's look at #42"
+- "Let's look at #42" (issue or PR)
 - "Move #42 to ready-for-agent"
 - "What's ready for agents to pick up?"
 
@@ -56,24 +61,28 @@ Query the issue tracker and present three buckets, oldest first:
 2. **`needs-triage`** — evaluation in progress.
 3. **`needs-info` with reporter activity since the last triage notes** — needs re-evaluation.
 
-Show counts and a one-line summary per issue. Let the maintainer pick.
+When PRs are in scope, include external PRs in these buckets and tag each line `[PR]` or `[issue]`. Discovery surfaces only *external* PRs (the tracker config defines who counts as external) — a collaborator's in-flight PR is not triage work. This filter is discovery-only; an explicitly named PR is always triaged regardless of author.
+
+Show counts and a one-line summary per item. Let the maintainer pick.
 
-## Triage a specific issue
+## Triage a specific issue or PR
 
-1. **Gather context.** Read the full issue (body, comments, labels, reporter, dates). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Read `.out-of-scope/*.md` and surface any prior rejection that resembles this issue.
+1. **Gather context.** Read the full issue or PR (body, comments, labels, author, dates; for a PR, the diff too). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Run two checks against the codebase: (a) **redundancy** — search for an existing implementation of the requested behavior by domain concept (not just the request's wording), and report where you looked. If found, it's an already-implemented `wontfix` (step 5). (b) **prior rejection** — read `.out-of-scope/*.md` and surface any that resembles this request.
 
-2. **Recommend.** Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the issue. Wait for direction.
+2. **Recommend.** Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the request — including whether it's already implemented. Wait for direction.
 
-3. **Reproduce (bugs only).** Before any grilling, attempt reproduction: read the reporter's steps, trace the relevant code, run tests or commands. Report what happened — successful repro with code path, failed repro, or insufficient detail (a strong `needs-info` signal). A confirmed repro makes a much stronger agent brief.
+3. **Verify the claim.** Before any grilling, check that the claim holds up. For a bug, reproduce it from the reporter's steps. For a PR, confirm the diff does what it claims — check it out, run the relevant tests or commands. Report what happened: confirmed (with code path), failed, or insufficient detail (a strong `needs-info` signal). A confirmed verification makes a much stronger agent brief.
 
-4. **Grill (if needed).** If the issue needs fleshing out, run a `/grill-with-docs` session.
+4. **Grill (if needed).** If the request needs fleshing out, run the `/grilling` and `/domain-modeling` skills together — grill it into shape a round of questions at a time, sharpening domain terms and updating `CONTEXT.md`/ADRs inline as decisions land.
 
 5. **Apply the outcome:**
    - `ready-for-agent` — post an agent brief comment ([AGENT-BRIEF.md](AGENT-BRIEF.md)).
    - `ready-for-human` — same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).
    - `needs-info` — post triage notes (template below).
-   - `wontfix` (bug) — polite explanation, then close.
-   - `wontfix` (enhancement) — write to `.out-of-scope/`, link to it from a comment, then close ([OUT-OF-SCOPE.md](OUT-OF-SCOPE.md)).
+   - `wontfix` — close, with the comment depending on *why*:
+     - **Already implemented** — the change already exists in the codebase. Point to where it lives; do **not** write to `.out-of-scope/` (that KB is for *rejected* requests, not built ones).
+     - **Rejected (bug)** — polite explanation, then close.
+     - **Rejected (enhancement)** — write to `.out-of-scope/`, link to it from a comment, then close ([OUT-OF-SCOPE.md](OUT-OF-SCOPE.md)).
    - `needs-triage` — apply the role. Optional comment if there's partial progress.
 
 ## Quick state override
@@ -100,4 +109,4 @@ Capture everything resolved during grilling under "established so far" so the wo
 
 ## Resuming a previous session
 
-If prior triage notes exist on the issue, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.
+If prior triage notes exist on the issue or PR, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.
diff --git a/.agents/skills/triage/agents/openai.yaml b/.agents/skills/triage/agents/openai.yaml
new file mode 100644
index 00000000..acb366cf
--- /dev/null
+++ b/.agents/skills/triage/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Triage"
+  short_description: "Move issues through triage roles"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/wait-what/SKILL.md b/.agents/skills/wait-what/SKILL.md
new file mode 100644
index 00000000..d493cfa8
--- /dev/null
+++ b/.agents/skills/wait-what/SKILL.md
@@ -0,0 +1,7 @@
+---
+name: wait-what
+description: Stop. That last message did not land — re-pitch it.
+disable-model-invocation: true
+---
+
+Wait — I don't understand where you've got to here. Re-pitch that: give me a little bit of context, talk in ASD-STE100 Simplified Technical English, and use the ubiquitous language from `CONTEXT.md`.
diff --git a/.agents/skills/wait-what/agents/openai.yaml b/.agents/skills/wait-what/agents/openai.yaml
new file mode 100644
index 00000000..ba77f1c9
--- /dev/null
+++ b/.agents/skills/wait-what/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Wait What"
+  short_description: "Re-pitch that — simpler, with the context I'm missing"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/wayfinder/SKILL.md b/.agents/skills/wayfinder/SKILL.md
new file mode 100644
index 00000000..e4984ed3
--- /dev/null
+++ b/.agents/skills/wayfinder/SKILL.md
@@ -0,0 +1,128 @@
+---
+name: wayfinder
+description: Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
+disable-model-invocation: true
+---
+
+A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the **destination** isn't visible yet. Wayfinding is about finding that way, not charging at the destination. This skill charts the way as a **shared map** on the repo's issue tracker, then works its **decision tickets** — questions whose resolution is a decision, not slices of a build to execute — one at a time until the route is clear.
+
+The destination varies per effort, and naming it is the first act of charting — it shapes every ticket. It might be a spec to hand off and iterate on, a decision to lock before planning starts, or a change made in place like a data-structure migration. The map is domain-agnostic — engineering work, course content, whatever fits the shape.
+
+## Plan, don't do
+
+Wayfinder is **planning** by default: each ticket resolves a decision, and the map is done when the way is clear — nothing left to decide before someone goes and does the thing. The pull to just do the work is usually the signal you've reached the edge of the map and it's time to hand off. An effort can override this in its **Notes** — carrying execution into the map itself — but absent that, produce decisions, not deliverables.
+
+## Refer by name
+
+Every map and ticket is an issue, so it has a **name** — its title. In everything the human reads — narration, the map's Decisions-so-far — refer to it by that name, never by a bare id, number, or slug. A wall of `#42, #43, #44` is illegible; names read at a glance. The id and URL don't vanish — a name wraps its link — but they ride _inside_ the name, never stand in for it.
+
+## The Map
+
+The map is a single issue on this repo's issue tracker, labelled `wayfinder:map` — the canonical artifact. Its tickets are child issues of the map.
+
+The map is an **index**, not a store. It lists the decisions made and points at the tickets that hold their detail; a decision lives in exactly one place — its ticket — so the map never restates it, only gists it and links.
+
+**Where the map, its child tickets, blocking, and frontier queries physically live is tracker-specific.** The issue tracker should have been provided to you — run `/setup-matt-pocock-skills` if not. Consult the tracker doc's "Wayfinding operations" section for how _this_ repo expresses them. If no tracker has been provided, default to the local-markdown tracker.
+
+### The map body
+
+The whole map at low resolution, loaded once per session. Open tickets are **not** listed — they are open child issues, found by query.
+
+```markdown
+## Destination
+
+<what reaching the end of this map looks like — the spec, decision, or change this effort is finding its way to. One or two lines; every session orients to it before choosing a ticket.>
+
+## Notes
+
+<domain; skills every session should consult; standing preferences for this effort>
+
+## Decisions so far
+
+<!-- the index — one line per closed ticket: enough to judge relevance, then zoom the link for the detail the ticket holds -->
+
+- [<closed ticket title>](link) — <one-line gist of the answer>
+
+## Not yet specified
+
+<!-- see "Fog of war": in-scope fog you can't ticket yet; graduates as the frontier advances -->
+
+## Out of scope
+
+<!-- see "Out of scope": work ruled beyond the destination; closed, never graduates -->
+```
+
+### Tickets
+
+Each ticket is a **child issue** of the map; the tracker's issue id is its identity. Its body is the question, sized to one 100K token agent session:
+
+```markdown
+## Question
+
+<the decision or investigation this ticket resolves>
+```
+
+Each ticket carries a `wayfinder:<type>` label — one of `research`, `prototype`, `grilling`, `task` (see [Ticket Types](#ticket-types)).
+
+A session **claims** a ticket by assigning it to the dev driving the map, **first**, before any work, so concurrent sessions skip it. That assignee _is_ the claim: an open, unassigned ticket is unclaimed.
+
+Blocking uses the tracker's **native** dependency relationship — essential because it renders the frontier _visually_ in the tracker's own UI, so the human sees what's takeable without opening the map. Only a tracker that lacks native blocking falls back to a body convention. A ticket is **unblocked** when every ticket blocking it is closed; the **frontier** is the open, unblocked, unclaimed children — the edge of the known.
+
+The answer isn't part of the body — it's recorded on resolution (see [Work through the map](#work-through-the-map)). Assets created while resolving a ticket are linked from the issue, not pasted in.
+
+## Ticket Types
+
+Every ticket is either **HITL** — human in the loop, worked _with_ a human who speaks for themselves — or **AFK**, driven by the agent alone. A HITL ticket only resolves through that live exchange; the agent never stands in for the human's side of it (a grilling agent that answers its own questions has broken this).
+
+- **Research** (AFK): Reading documentation, third-party APIs, or local resources like knowledge bases to surface a fact a decision waits on. Resolved by a `/research` **subagent**. Use when knowledge outside the current working directory is required.
+- **Prototype** (HITL): Raise the fidelity of the discussion by making a cheap, rough, concrete artifact to react to — an outline, a rough take, a stub, or UI/logic code via the /prototype skill. Links the prototype as an asset. Use when "how should it look" or "how should it behave" is the key question.
+- **Grilling** (HITL): Conversation. The default case. Always invoke the /grilling and /domain-modeling skills.
+- **Task** (HITL or AFK): Manual work that must happen before a _decision_ can be made — nothing to decide, prototype, or research, but the discussion is blocked until it's done. Signing up for a service so its API can be judged, provisioning access, moving data so its shape can be seen. This is the one type that _does_ rather than decides — and it earns its place by unblocking a decision, not by delivering the destination. The agent drives it alone where it can (AFK); otherwise it hands the human a precise checklist (HITL). Resolved when the work is done; the answer records what was done and any resulting facts (credentials location, new URLs, row counts) later tickets depend on.
+
+## Fog of war
+
+The map is _deliberately_ incomplete: don't chart what you can't yet see. Beyond the live tickets lies the **fog of war** — the dim view of decisions and investigations you can tell are coming but can't yet pin down, because they hang on questions still open. Resolving a ticket clears the fog ahead of it, graduating whatever's now specifiable into fresh tickets — one at a time, until the way to the destination is clear and no tickets remain.
+
+The map's **Not yet specified** section is where that dim view is written down: the suspected question, the area to revisit later. It's the undiscovered frontier _toward_ the destination — everything here is in scope, just not sharp enough to ticket. Write as loosely or as fully as the view allows; it doubles as a signpost for collaborators reading where the effort is headed.
+
+**Fog or ticket?** The test is whether you can state the question precisely now — _not_ whether you can answer it now.
+
+- **Ticket when** the question is already sharp — even if it's blocked and you can't act on it yet.
+- **Not yet specified when** you can't yet phrase it that sharply. Don't pre-slice the fog into ticket-sized pieces: it's coarser than a ticket, and one patch may graduate into several tickets, or none, once the frontier reaches it.
+
+**Not yet specified** excludes what's already decided (Decisions so far), what's already a live ticket, and what's out of scope (the next section).
+
+## Out of scope
+
+Fog only ever gathers _toward_ the destination. The destination fixes the scope, so work beyond it is **out of scope** — it isn't fog, and it doesn't belong in **Not yet specified**. It gets its own **Out of scope** section on the map: work you've consciously ruled out of _this_ effort. Scope, not sharpness, lands it here.
+
+Out-of-scope work never graduates — the frontier stops at the destination — so it returns only if the destination is redrawn, and then as a fresh effort, not a resumption.
+
+Ruling something out of scope is a scoping act, not a step on the route. When a ticket that already exists turns out to sit past the destination — mis-scoped in while charting, or exposed by a resolution — **close it** (a closed ticket is unambiguously off the frontier) and leave one line in the **Out of scope** section: the gist plus why it's out of scope, linking the closed ticket. It stays out of **Decisions so far**, which records the route actually walked — a scope boundary isn't a step on it.
+
+## Invocation
+
+Two modes. Either way, **never resolve more than one ticket per session** — with the exception of research tickets.
+
+### Chart the map
+
+User invokes with a loose idea.
+
+1. **Name the destination.** Run a `/grilling` and `/domain-modeling` session to pin down what this map is finding its way to — the spec, decision, or change. The destination fixes the scope, so it's settled first.
+2. **Map the frontier.** Grill again, **breadth-first** this time: fan out across the whole space rather than deep on any one thread, surfacing the open decisions and the first steps takeable now. **If this surfaces no fog** — the way to the destination is already clear, the whole journey small enough for one session — you don't need a map. Stop and ask the user how they'd like to proceed.
+3. **Create the map** (label `wayfinder:map`): Destination and Notes filled in, Decisions-so-far empty, the fog sketched into **Not yet specified**.
+4. **Create the tickets you can specify now** as child issues of the map — then wire blocking edges in a **second pass** (issues need ids before they can reference each other). Wiring sorts them into the frontier and the blocked; everything you can't yet specify stays in the fog — the **Not yet specified** section.
+5. **Fire the research subagents.** For each `research` ticket you just created, spin up a `/research` subagent to resolve it in parallel, capturing its findings on a throwaway `research/<name>` branch with a context pointer from the ticket.
+6. Stop — charting is one session's work; it hand-resolves nothing.
+
+### Work through the map
+
+User invokes with a map (URL or number). A ticket is **optional** — without one, you pick the next decision, not the user.
+
+1. Load the **map** — the low-res view, not every ticket body.
+2. Choose the ticket. If the user named one, use it. Otherwise take the first frontier ticket in order. **Claim it**: assign it to yourself before any work.
+3. Resolve it — **zoom as needed**: fetch the full body of any related or closed ticket on demand; invoke the skills the `## Notes` block names. If in doubt, use `/grilling` and `/domain-modeling`.
+4. Record the resolution: post the answer as a **resolution comment**, **close** the issue, and **append a context pointer** to the map's Decisions-so-far.
+5. Add newly-surfaced tickets (create-then-wire); graduate any fog the answer has made specifiable, clearing each graduated patch from **Not yet specified** so it lives only as its new ticket. If the answer reveals a ticket — this one or another — sits beyond the destination, **rule it out of scope** rather than resolving it on the route. If the decision invalidates other parts of the map, update or delete those tickets.
+
+The user may run unblocked tickets in parallel, so expect other sessions to be editing the tracker concurrently.
diff --git a/.agents/skills/wayfinder/agents/openai.yaml b/.agents/skills/wayfinder/agents/openai.yaml
new file mode 100644
index 00000000..b3754475
--- /dev/null
+++ b/.agents/skills/wayfinder/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Wayfinder"
+  short_description: "Map a large effort as decision tickets"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/wizard/SKILL.md b/.agents/skills/wizard/SKILL.md
new file mode 100644
index 00000000..7c42dbd2
--- /dev/null
+++ b/.agents/skills/wizard/SKILL.md
@@ -0,0 +1,44 @@
+---
+name: wizard
+description: Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
+---
+
+# Wizard
+
+A **wizard** is a bash script that walks a human, step by step, through a manual procedure that's tedious to do by hand and tedious to re-explain to an AI every time. It opens each URL, says exactly what to click and copy, captures the values, writes them where they belong (`.env`, GitHub secrets), confirms at every stage, and shows how much is left. It might configure third-party services, run a one-off migration, or move the project from one state to another.
+
+The delightful UX is already solved by [template.sh](template.sh) — progress with time-remaining, confirmation gates, cross-platform URL opening (including WSL), hidden secret entry, idempotent `.env` upserts, `gh secret`/`gh variable` writes, and a closing summary. **Your job is only to scope the procedure and author its stages.** The library above the `STAGES` marker is identical in every wizard; that consistency is the point — never hand-edit it.
+
+A wizard is ephemeral by default — built for one run, saved to a scratch or `scripts/` path, deleted when the job's done. Commit it only when the user wants a repeatable setup path that should live in the repo.
+
+## Process
+
+### 1. Scope the procedure
+
+Work out every manual step the human must take and every value that gets captured along the way. Read the repo first — don't ask cold:
+
+- For setup: `.env`, `.env.example`, `.env.*`, `README`, `docker-compose*`, framework config, and `.github/workflows/*` (every `secrets.*` / `vars.*` reference is a value the wizard must produce).
+- For a migration or transition: the current state, the target state, and the irreversible actions between them.
+
+Then show the user the ordered list of stages and the values each produces, and confirm — they may add, drop, or reorder.
+
+**Done when:** every stage is named in order, and for each captured value you know (a) where the human gets it, (b) where it's written (`.env`, a GitHub secret, both, or nowhere — some stages are pure actions), and (c) whether it's secret (hidden entry) or public.
+
+### 2. Map each stage's journey
+
+For each stage, write the precise path a human follows: which URL to open, what to do there, where a value is shown, which variable it fills — e.g. "Dashboard → Developers → API keys → Reveal test key → copy". Where you don't actually know the current UI or the exact command, say so and ask the user or check the docs — never invent steps that may not exist.
+
+**Done when:** every stage traces to concrete instructions a stranger could follow.
+
+### 3. Author the wizard
+
+Copy `template.sh` to the target path. Replace the example stage with one `stage` per step, in dependency order. Use the library helpers — `stage`, `say`/`step`, `open_url`, `ask`/`ask_secret`, `write_env`, `set_secret`/`set_var`, `pause`/`confirm` — and set `TOTAL_STAGES` and `TOTAL_MINUTES` to honest estimates (this drives the time-remaining display).
+
+Hold the bar the template sets: open the URL before asking for its value, use `ask_secret` for anything secret, `write_env` every persisted value, `set_secret` only the values CI actually needs, and `confirm` before any irreversible action. Each `stage` clears the screen so only the current step is visible — keep a stage to one focused task so nothing the human needs scrolls away. Don't touch the library above the marker.
+
+### 4. Verify and hand off
+
+- `bash -n <script>`; run `shellcheck` if available.
+- `chmod +x <script>`.
+- Don't run it end-to-end yourself — it opens browsers and blocks on human input. Trace it statically instead: every value from step 1 is captured and lands where step 1 said, and every `set_secret` name exactly matches a `secrets.*` reference in CI.
+- Tell the user how to run it. If it's a repeatable setup path, commit it and link it from the README so the next person runs the script instead of asking an AI.
diff --git a/.agents/skills/wizard/agents/openai.yaml b/.agents/skills/wizard/agents/openai.yaml
new file mode 100644
index 00000000..b601bdf3
--- /dev/null
+++ b/.agents/skills/wizard/agents/openai.yaml
@@ -0,0 +1,3 @@
+interface:
+  display_name: "Wizard"
+  short_description: "Generate an interactive setup wizard"
diff --git a/.agents/skills/wizard/template.sh b/.agents/skills/wizard/template.sh
new file mode 100644
index 00000000..95b7a6a6
--- /dev/null
+++ b/.agents/skills/wizard/template.sh
@@ -0,0 +1,211 @@
+#!/usr/bin/env bash
+#
+# A wizard — walks a human through a manual procedure step by step.
+# Generated by the /wizard skill.
+#
+# Everything above the "STAGES" marker is the wizard library: do not hand-edit
+# it. Author the per-step stages below the marker.
+
+set -euo pipefail
+
+# ──────────────────────────────────────────────────────────────────────────
+# Wizard library — delightful, consistent UX. Identical across every wizard.
+# ──────────────────────────────────────────────────────────────────────────
+
+if [[ -t 1 ]] && command -v tput >/dev/null 2>&1 && [[ "$(tput colors 2>/dev/null || echo 0)" -ge 8 ]]; then
+  BOLD=$(tput bold); DIM=$(tput dim); RESET=$(tput sgr0)
+  BLUE=$(tput setaf 4); GREEN=$(tput setaf 2); YELLOW=$(tput setaf 3); RED=$(tput setaf 1)
+else
+  BOLD=""; DIM=""; RESET=""; BLUE=""; GREEN=""; YELLOW=""; RED=""
+fi
+
+# Author sets these two at the top of the stages section.
+TOTAL_STAGES=0
+TOTAL_MINUTES=0
+
+_STAGE_INDEX=0
+_MINUTES_ELAPSED=0
+ENV_FILE="${ENV_FILE:-.env}"
+WRITTEN_ENV=()    # KEYs written to ENV_FILE this run
+WRITTEN_SECRET=() # secret NAMEs set this run
+SKIPPED=()        # things we couldn't do (e.g. gh missing)
+
+# _clear — wipe the terminal so only the current step is on screen. No-op when
+# output isn't a terminal, so piped logs stay readable.
+_clear() {
+  [[ -t 1 ]] || return 0
+  if command -v tput >/dev/null 2>&1; then tput clear; else printf '\033[2J\033[3J\033[H'; fi
+}
+
+# banner "Title" — opening frame: what this wizard does and how long it takes.
+banner() {
+  _clear
+  printf '\n%s%s  %s%s\n' "$BOLD" "$BLUE" "$1" "$RESET"
+  printf '%s  %s stages · about %s minutes%s\n\n' \
+    "$DIM" "$TOTAL_STAGES" "$TOTAL_MINUTES" "$RESET"
+  printf '%s  You drive the browser; this wizard tells you exactly what to do and\n' "$DIM"
+  printf '  captures the values you copy back. Stop any time with Ctrl-C and re-run\n'
+  printf '  later — it remembers values already saved.%s\n' "$RESET"
+  pause "Ready to start?"
+}
+
+# stage "Name" <minutes> — clear the screen, then announce a stage and show
+# progress + time remaining. Clearing keeps only the current step on screen.
+stage() {
+  _clear
+  _STAGE_INDEX=$((_STAGE_INDEX + 1))
+  local remaining=$((TOTAL_MINUTES - _MINUTES_ELAPSED))
+  (( remaining < 0 )) && remaining=0
+  _MINUTES_ELAPSED=$((_MINUTES_ELAPSED + ${2:-0}))
+  printf '\n%s%s▸ Stage %s/%s · %s%s  %s(~%s min left)%s\n' \
+    "$BOLD" "$BLUE" "$_STAGE_INDEX" "$TOTAL_STAGES" "$1" "$RESET" "$DIM" "$remaining" "$RESET"
+}
+
+# say "..." — a plain instruction line.
+say()  { printf '  %s\n' "$1"; }
+# step "..." — a numbered-feeling action the human takes in the browser.
+step() { printf '  %s•%s %s\n' "$BLUE" "$RESET" "$1"; }
+note() { printf '  %s%s%s\n' "$DIM" "$1" "$RESET"; }
+warn() { printf '  %s⚠ %s%s\n' "$YELLOW" "$1" "$RESET"; }
+
+# open_url URL — open in the human's browser, cross-platform incl. WSL.
+open_url() {
+  local url="$1"
+  printf '  %s↗ opening%s %s\n' "$GREEN" "$RESET" "$url"
+  { if   command -v wslview     >/dev/null 2>&1; then wslview "$url"
+    elif command -v explorer.exe >/dev/null 2>&1; then explorer.exe "$url"
+    elif command -v xdg-open    >/dev/null 2>&1; then xdg-open "$url"
+    elif command -v open        >/dev/null 2>&1; then open "$url"
+    else warn "couldn't open a browser — visit it manually: $url"; fi
+  } >/dev/null 2>&1 || warn "couldn't open a browser — visit it manually: $url"
+}
+
+# pause "msg" — wait for the human to confirm they've done the manual part.
+pause() {
+  printf '  %s%s%s ' "$DIM" "${1:-Press Enter to continue}" "$RESET"
+  read -r _ || true
+}
+
+# confirm "question" — y/N gate; returns success on yes.
+confirm() {
+  local reply=""
+  printf '  %s? %s [y/N] ' "$YELLOW" "$1"
+  read -r reply || true
+  [[ "$reply" =~ ^[Yy] ]]
+}
+
+# _existing KEY — current value of KEY in ENV_FILE, if any.
+_existing() {
+  [[ -f "$ENV_FILE" ]] || return 1
+  local line; line=$(grep -E "^${1}=" "$ENV_FILE" | tail -n1) || return 1
+  printf '%s' "${line#*=}"
+}
+
+# ask KEY "Prompt" — read a value into $KEY. Offers the existing .env value as
+# a default on re-runs (Enter keeps it). Visible input (non-secret).
+ask() {
+  local key="$1" prompt="$2" current input
+  current=$(_existing "$key" || true)
+  if [[ -n "$current" ]]; then
+    printf '  %s%s%s %s[Enter keeps current]%s ' "$BOLD" "$prompt" "$RESET" "$DIM" "$RESET"
+  else
+    printf '  %s%s%s ' "$BOLD" "$prompt" "$RESET"
+  fi
+  read -r input || true
+  [[ -z "$input" && -n "$current" ]] && input="$current"
+  printf -v "$key" '%s' "$input"
+}
+
+# ask_secret KEY "Prompt" — like ask, but input is hidden.
+ask_secret() {
+  local key="$1" prompt="$2" current input
+  current=$(_existing "$key" || true)
+  if [[ -n "$current" ]]; then
+    printf '  %s%s%s %s[Enter keeps current]%s ' "$BOLD" "$prompt" "$RESET" "$DIM" "$RESET"
+  else
+    printf '  %s%s%s ' "$BOLD" "$prompt" "$RESET"
+  fi
+  read -rs input || true
+  printf '\n'
+  [[ -z "$input" && -n "$current" ]] && input="$current"
+  printf -v "$key" '%s' "$input"
+}
+
+# write_env KEY VALUE — upsert KEY=VALUE into ENV_FILE (creates it; replaces
+# any existing line). Idempotent.
+write_env() {
+  local key="$1" value="$2" tmp
+  touch "$ENV_FILE"
+  tmp=$(mktemp)
+  grep -vE "^${key}=" "$ENV_FILE" > "$tmp" || true
+  printf '%s=%s\n' "$key" "$value" >> "$tmp"
+  mv "$tmp" "$ENV_FILE"
+  WRITTEN_ENV+=("$key")
+  printf '  %s✓ wrote%s %s → %s\n' "$GREEN" "$RESET" "$key" "$ENV_FILE"
+}
+
+# set_secret NAME VALUE — set a GitHub Actions repo secret via gh. Falls back
+# to a warning (and records it) if gh is unavailable or unauthenticated.
+set_secret() {
+  local name="$1" value="$2"
+  if command -v gh >/dev/null 2>&1 && gh auth status >/dev/null 2>&1; then
+    if printf '%s' "$value" | gh secret set "$name" >/dev/null 2>&1; then
+      WRITTEN_SECRET+=("$name")
+      printf '  %s✓ set%s GitHub secret %s\n' "$GREEN" "$RESET" "$name"
+      return
+    fi
+  fi
+  SKIPPED+=("GitHub secret $name (set it manually: gh secret set $name)")
+  warn "skipped GitHub secret $name — gh not ready; set it later"
+}
+
+# set_var NAME VALUE — set a GitHub Actions repo variable (non-secret).
+set_var() {
+  local name="$1" value="$2"
+  if command -v gh >/dev/null 2>&1 && gh auth status >/dev/null 2>&1; then
+    if gh variable set "$name" --body "$value" >/dev/null 2>&1; then
+      printf '  %s✓ set%s GitHub variable %s\n' "$GREEN" "$RESET" "$name"
+      return
+    fi
+  fi
+  SKIPPED+=("GitHub variable $name")
+  warn "skipped GitHub variable $name — gh not ready; set it later"
+}
+
+# finish — clear, then a closing summary of everything configured.
+finish() {
+  _clear
+  printf '\n%s%s  ✓ Setup complete%s\n' "$BOLD" "$GREEN" "$RESET"
+  (( ${#WRITTEN_ENV[@]} ))    && note "wrote ${#WRITTEN_ENV[@]} value(s) to $ENV_FILE: ${WRITTEN_ENV[*]}"
+  (( ${#WRITTEN_SECRET[@]} )) && note "set ${#WRITTEN_SECRET[@]} GitHub secret(s): ${WRITTEN_SECRET[*]}"
+  if (( ${#SKIPPED[@]} )); then
+    printf '\n'; warn "still to do by hand:"
+    for s in "${SKIPPED[@]}"; do note "  - $s"; done
+  fi
+  printf '\n'
+}
+
+# ──────────────────────────────────────────────────────────────────────────
+# STAGES — author this section. One stage() per step the human takes.
+# Replace the example below. Set the two totals to match the stages you write.
+# ──────────────────────────────────────────────────────────────────────────
+
+TOTAL_STAGES=1
+TOTAL_MINUTES=5
+
+banner "Stripe setup"
+
+# ── Example stage: replace with your real steps ───────────────────────────
+stage "Stripe — API keys" 5
+say "We'll grab your Stripe test keys and store them for local dev + CI."
+open_url "https://dashboard.stripe.com/test/apikeys"
+step "On the API keys page, copy the Publishable key (starts pk_test_)."
+ask STRIPE_PUBLISHABLE_KEY "Paste the publishable key:"
+step "Click 'Reveal test key' on the Secret key row, then copy it."
+ask_secret STRIPE_SECRET_KEY "Paste the secret key:"
+write_env STRIPE_PUBLISHABLE_KEY "$STRIPE_PUBLISHABLE_KEY"
+write_env STRIPE_SECRET_KEY "$STRIPE_SECRET_KEY"
+set_secret STRIPE_SECRET_KEY "$STRIPE_SECRET_KEY"   # CI needs this one
+# ──────────────────────────────────────────────────────────────────────────
+
+finish
diff --git a/.agents/skills/write-a-skill/SKILL.md b/.agents/skills/write-a-skill/SKILL.md
deleted file mode 100644
index 7339c8a3..00000000
--- a/.agents/skills/write-a-skill/SKILL.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-name: write-a-skill
-description: Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
----
-
-# Writing Skills
-
-## Process
-
-1. **Gather requirements** - ask user about:
-   - What task/domain does the skill cover?
-   - What specific use cases should it handle?
-   - Does it need executable scripts or just instructions?
-   - Any reference materials to include?
-
-2. **Draft the skill** - create:
-   - SKILL.md with concise instructions
-   - Additional reference files if content exceeds 500 lines
-   - Utility scripts if deterministic operations needed
-
-3. **Review with user** - present draft and ask:
-   - Does this cover your use cases?
-   - Anything missing or unclear?
-   - Should any section be more/less detailed?
-
-## Skill Structure
-
-```
-skill-name/
-├── SKILL.md           # Main instructions (required)
-├── REFERENCE.md       # Detailed docs (if needed)
-├── EXAMPLES.md        # Usage examples (if needed)
-└── scripts/           # Utility scripts (if needed)
-    └── helper.js
-```
-
-## SKILL.md Template
-
-```md
----
-name: skill-name
-description: Brief description of capability. Use when [specific triggers].
----
-
-# Skill Name
-
-## Quick start
-
-[Minimal working example]
-
-## Workflows
-
-[Step-by-step processes with checklists for complex tasks]
-
-## Advanced features
-
-[Link to separate files: See [REFERENCE.md](REFERENCE.md)]
-```
-
-## Description Requirements
-
-The description is **the only thing your agent sees** when deciding which skill to load. It's surfaced in the system prompt alongside all other installed skills. Your agent reads these descriptions and picks the relevant skill based on the user's request.
-
-**Goal**: Give your agent just enough info to know:
-
-1. What capability this skill provides
-2. When/why to trigger it (specific keywords, contexts, file types)
-
-**Format**:
-
-- Max 1024 chars
-- Write in third person
-- First sentence: what it does
-- Second sentence: "Use when [specific triggers]"
-
-**Good example**:
-
-```
-Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when user mentions PDFs, forms, or document extraction.
-```
-
-**Bad example**:
-
-```
-Helps with documents.
-```
-
-The bad example gives your agent no way to distinguish this from other document skills.
-
-## When to Add Scripts
-
-Add utility scripts when:
-
-- Operation is deterministic (validation, formatting)
-- Same code would be generated repeatedly
-- Errors need explicit handling
-
-Scripts save tokens and improve reliability vs generated code.
-
-## When to Split Files
-
-Split into separate files when:
-
-- SKILL.md exceeds 100 lines
-- Content has distinct domains (finance vs sales schemas)
-- Advanced features are rarely needed
-
-## Review Checklist
-
-After drafting, verify:
-
-- [ ] Description includes triggers ("Use when...")
-- [ ] SKILL.md under 100 lines
-- [ ] No time-sensitive info
-- [ ] Consistent terminology
-- [ ] Concrete examples included
-- [ ] References one level deep
diff --git a/.agents/skills/writing-for-agents/SKILL-MECHANICS.md b/.agents/skills/writing-for-agents/SKILL-MECHANICS.md
new file mode 100644
index 00000000..c28e3bf0
--- /dev/null
+++ b/.agents/skills/writing-for-agents/SKILL-MECHANICS.md
@@ -0,0 +1,22 @@
+# Skill mechanics
+
+The skill-specific branch of [`writing-for-agents`](SKILL.md): what changes when the document is a skill — frontmatter, the invocation choice, and router skills. Everything else about writing it is the universal reference in `SKILL.md`.
+
+## Invocation
+
+Two choices, trading the two loads:
+
+- A **model-invoked** skill keeps a `description`, so the agent can fire it autonomously — and other skills can reach it. You can still type its name: model-invocation always _includes_ user reach; a description only ever adds agent discovery, never removes the human's. The description is the skill's top-level context pointer, forced to stay loaded at all times — permanent context load in exchange for discoverability. A model-invoked skill whose content is all reference is also one home for shared reference: another skill can invoke it, so reference needed by several skills lives in one place. Mechanics: omit `disable-model-invocation`, and write a model-facing description carrying the trigger branches (the pointer-writing rules in `SKILL.md` apply in full).
+- A **user-invoked** skill strips the description from the agent's reach: only the human typing its name can invoke it, and no other skill can. Zero context load, but it spends cognitive load — you are the index that must remember it exists. Mechanics: set `disable-model-invocation: true`; the `description` becomes human-facing — a one-line summary, trigger lists stripped.
+
+Pick model-invocation only when the agent must reach the skill on its own, or another skill must. If it only ever fires by hand, make it user-invoked and pay no context load.
+
+Shared reference that two user-invoked skills both need can live in neither — with no descriptions, neither can fire the other. Push it to a plain file outside the skill system: external reference any skill can point at.
+
+## Splitting by invocation
+
+The invocation cut of splitting (the sequence cut lives in `SKILL.md`): split off a model-invoked skill when you have a distinct leading word that should trigger it on its own — a trigger word you actually use in your prompts — or another skill must reach it. You pay context load for the new always-loaded description, so that independent reach has to be worth it.
+
+## Router skills
+
+When user-invoked skills multiply past what you can remember, that piled-up cognitive load is cured by a **router skill**: one user-invoked skill that names the others and when to reach for each, so the human has one skill to remember instead of many. It can only hint, never fire them: user-invoked skills have no description, so nothing but the human can reach them.
diff --git a/.agents/skills/writing-for-agents/SKILL.md b/.agents/skills/writing-for-agents/SKILL.md
new file mode 100644
index 00000000..c059d48c
--- /dev/null
+++ b/.agents/skills/writing-for-agents/SKILL.md
@@ -0,0 +1,81 @@
+---
+name: writing-for-agents
+description: Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
+---
+
+Reference for writing any document an agent consumes — a skill, an `AGENTS.md` / `CLAUDE.md`, a doc reached by a pointer. The packaging differs; the writing does not: the same levers make each one predictable — the agent taking the same _process_ every run, not producing the same output.
+
+When the document you're writing is a skill, read [`SKILL-MECHANICS.md`](SKILL-MECHANICS.md) for frontmatter, invocation choice, and router skills.
+
+## Context pointers
+
+A **context pointer** is a reference held in the agent's context that names some out-of-context material and encodes the condition for reaching it. A skill's description is one; a line in `AGENTS.md` naming a doc is the same object. The pointer's _wording_, not its target, decides when the agent reaches the material — and how reliably. A must-have target behind a weakly worded pointer is a variance bug: sharpen the wording first, and inline the material only if sharpening fails.
+
+A pointer does two jobs — state what the material is, and list the **branches** that should trigger reaching it (a branch is a distinct case the document handles, so different runs take different paths through it). Every word of an always-loaded pointer costs on every turn, so it earns even harder pruning than the body:
+
+- **Front-load the leading word** — the pointer is where it does its triggering work.
+- **One trigger per branch.** Synonyms that rename a single branch are one branch written twice; collapse them and keep only genuinely distinct branches.
+- **Cut identity the body already carries.**
+
+## The two loads
+
+Every document and pointer you add spends one of two budgets:
+
+- **Context load** — the cost of always-loaded material on the agent's window: an `AGENTS.md` line, a skill description, anything sitting in context every turn, spending tokens and attention whether or not it fires.
+- **Cognitive load** — the cost on the human: which documents exist and when to reach for each. The human is the index. Not a cost to minimise — it is the price of human agency; spend it where human judgement matters, remove it where it does not.
+
+Material reached only through a pointer escapes context load at the price of the pointer's own line; material with no pointer at all rides entirely on cognitive load.
+
+## Information hierarchy
+
+A document is built from two content types — **steps** (the ordered actions the agent performs) and **reference** (definitions, rules, facts consulted on demand) — that mix freely: all steps (a recipe), all reference (a review's rules, this skill), or both. The core decision is where each piece sits on the **information hierarchy**, a ladder ranked by how immediately the agent needs the material:
+
+1. **In-file step** — the primary tier: what the agent does, in order.
+2. **In-file reference** — consulted on demand. Often a legitimately flat peer-set (every rule of a review on one rung) — a fine arrangement, not a smell.
+3. **Disclosed reference** — pushed out into a separate file, reached by a context pointer, loaded only when the pointer fires. Spans a sibling file in the same folder through fully external reference that lives anywhere and any document can point at.
+
+Push too little down and the top bloats; push too much and you hide material the agent actually needs. That tension is the whole decision.
+
+**Progressive disclosure** is the move down the ladder — out of the main file and behind a pointer — so the top stays legible. Not primarily a token optimisation: it is how the hierarchy is protected. Branching is the cleanest disclosure test: inline what every branch needs, and push behind a pointer what only some branches reach. When a document has steps, in-file reference that should be disclosed buries them and turns attending to them into a coin-flip — a variance lever, not just a legibility one.
+
+**Co-location** is the within-file companion: where the ladder decides _how far down_ a piece sits, co-location decides _what sits beside it_ once there. Keep a concept's definition, rules, and caveats under one heading rather than scattered, so reading one part brings its neighbours with it. The test: the document should read like documentation written for the agent — grouped material reads that way; scattered material does not. (Distinct from duplication: that repeats one meaning in two places; scattering fragments one meaning across many.)
+
+**Sprawl** is the failure mode here: a document simply too long, even when every line is live and unique. Attention thins across the excess, and every extra line is one more to keep relevant. The cure is the ladder: disclose reference behind pointers, and split by branch or sequence so each path carries only what it needs.
+
+## Steps and completion criteria
+
+Every step ends on a **completion criterion** — the condition that tells the agent the work is done. Two properties make it a lever:
+
+- **Clarity** — can the agent tell done from not-done? A vague bound ("understanding reached") invites **premature completion**: ending the step before it is genuinely done, attention slipping to _being done_. The visible steps still ahead — the **post-completion steps** — supply the pull; the criterion's clarity is the resistance. Defend in order: **sharpen the bound first** (local and cheap); only if it is irreducibly fuzzy _and_ you observe the rush, hide the later steps by splitting the sequence — and hiding only works across a real context boundary (a hand-off or a subagent dispatch; an inline call leaves the later steps in context and clears nothing).
+- **Demand** — how much it requires. "Every modified model accounted for" forces thorough work where "produce a change list" does not. Demand drives **legwork** — the digging the agent does within the work, latent in the wording rather than written as its own step — and it is not step-bound: "every rule applied" binds a body of flat reference just as "every step done" binds a sequence, which is how an all-reference document still carries an exhaustiveness bar.
+
+The strongest criteria are both checkable and exhaustive.
+
+## When to split
+
+Splitting one document into two spends one of the two loads, so split only when the cut earns it:
+
+- **By sequence** — split a run of steps where the post-completion steps tempt the agent to rush the one in front of it. Keeping them out of view drives more legwork on the current task. Beware the reverse: merging sequences exposes each step's later steps to what follows, inviting premature completion.
+- **By invocation** — skill-specific: see [`SKILL-MECHANICS.md`](SKILL-MECHANICS.md).
+
+## Leading words
+
+A **leading word** is a compact concept already living in the model's pretraining that the agent thinks with while running the document (_lesson_, _fog of war_, _tracer bullets_). Repeated as a token, never as a sentence, it accumulates a distributed definition and anchors a whole region of behaviour in the fewest tokens, by recruiting priors the model already holds. Coining your own works if you define it clearly, but a made-up word recruits no priors — you pay in definition tokens what a pretrained word gives free; reach for an existing word first.
+
+It anchors twice. In the body, _execution_: the agent reaches for the same behaviour every time the word appears, and inside flat reference it focuses attention on a class of thing to look for. In a pointer, _invocation_: when the same word lives in your prompts, your docs, and your codebase, the agent links that shared language to the material and reaches it more reliably.
+
+Hunt for opportunities to refactor with leading words. A triad spelled out at three sites, a pointer spending a sentence to gesture at one idea — each is a passage begging to collapse into a single token:
+
+- "fast, deterministic, low-overhead" → _tight_ (a _tight_ loop).
+- "a loop you believe in" → _red_ — a fuzzy gate becomes a binary observable state (the loop goes _red_ on the bug, or it doesn't).
+
+You win twice: fewer tokens, and a sharper hook for the agent to hang its thinking on. Assume every document is carrying restatements that leading words retire — go find them.
+
+**Negation** is the failure mode beside this lever: steering by prohibition drags the forbidden behaviour into context and makes it _more_ available, not less. _Don't think of an elephant_, and the elephant is all there is; the negation is a weak modifier the strongly-activated concept overruns, so the ban half-reads as an instruction to do the thing. Prompt the **positive** — state the target behaviour ("write one-line comments") so the banned one is never spoken. A prohibition earns its place only as a hard guardrail you cannot phrase positively; even then, pair it with the positive target so attention lands on what to do.
+
+## Pruning
+
+- Keep each meaning in a **single source of truth**: one authoritative place, so changing the behaviour is a one-place edit. **Duplication** — the same meaning in more than one place — costs maintenance and tokens, and inflates a meaning's prominence on the ladder past its real rank. (The accidental inverse of a leading word, which repeats a token on purpose, never the meaning.)
+- The **environment** is a source of truth too — `package.json` scripts, config files, the directory layout, `--help` output — and a document that restates it is a **cache**: a copy of a lookup, earning its load only when the lookup is expensive. Cache what the agent cannot find by looking: the unwritten convention, the reason behind a choice, the gotcha no config confesses. Leave the one-file, one-command lookups to the environment, where they cannot go stale.
+- Check every line for **relevance**: does it still bear on what the document does? A line loses relevance by never bearing on the task (mere exposition, or a branch that should be disclosed) or by going stale as the behaviour or world it describes changes. Shorter documents are easier to keep relevant. Without a pruning discipline the default fate is **sediment**: stale layers that settle because adding feels safe and removing feels risky, until you must core down through them to find what is still live.
+- Hunt **no-ops** sentence by sentence: an instruction the model already obeys by default pays load to say nothing. The test — does it change behaviour versus the default? — is model-relative, not reader-relative: two people disagreeing about a no-op disagree about the default, and settle it by running the document, not by debate. When a sentence fails, delete the whole sentence rather than trim words from it. The test also grades leading words: a word too weak to beat the default (_be thorough_ when the agent is already thorough-ish) is a no-op, and the fix is a stronger word (_relentless_), not a different technique.
diff --git a/.agents/skills/writing-for-agents/agents/openai.yaml b/.agents/skills/writing-for-agents/agents/openai.yaml
new file mode 100644
index 00000000..d677a13f
--- /dev/null
+++ b/.agents/skills/writing-for-agents/agents/openai.yaml
@@ -0,0 +1,5 @@
+interface:
+  display_name: "Writing Great Skills"
+  short_description: "Principles for predictable skills"
+policy:
+  allow_implicit_invocation: false
diff --git a/.agents/skills/zoom-out/SKILL.md b/.agents/skills/zoom-out/SKILL.md
deleted file mode 100644
index 1e7a5dc7..00000000
--- a/.agents/skills/zoom-out/SKILL.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-name: zoom-out
-description: Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
-disable-model-invocation: true
----
-
-I don't know this area of code well. Go up a layer of abstraction. Give me a map of all the relevant modules and callers, using the project's domain glossary vocabulary.
diff --git a/.archon/commands/unic-dlc-build.md b/.archon/commands/unic-dlc-build.md
deleted file mode 100644
index 95ef3f38..00000000
--- a/.archon/commands/unic-dlc-build.md
+++ /dev/null
@@ -1,59 +0,0 @@
-# /unic-dlc-build
-
-Execute the TDD build workflow for a planning session, enforcing red → green per issue.
-
-## Usage
-
-```
-/unic-dlc-build <slug>
-```
-
-Where `<slug>` is the session identifier used when you ran `/unic-dlc-plan`. The generated
-`.archon/workflows/build-<slug>.yaml` must already exist (produced by the `yaml-gen` node in plan).
-
-## What this command does
-
-1. **Slopcheck gate** — before any implementation begins, scans `package.json` (and other
-   manifest files) for packages introduced since the last commit. Each new package is checked
-   against the npm registry. Packages that fail the check are flagged `[ASSUMED]` and require
-   explicit human approval before the build can continue.
-
-   Registry check strategy (in order of preference):
-
-   - Python `slopcheck` tool (GSD's slopsquatting gate) if available on `PATH`
-   - npm registry HEAD request fallback
-   - If neither is available: all new packages are treated as `[ASSUMED]` (strict default)
-
-   To bypass slopcheck for known-safe cases: `SLOPCHECK_BYPASS=1 /unic-dlc-build <slug>`
-
-2. **Generated build workflow** — executes `.archon/workflows/build-<slug>.yaml` which was
-   produced by the `yaml-gen` node in `/unic-dlc-plan`. The generated workflow:
-   - Issues a `code-red` node per issue: writes FAILING acceptance tests
-   - Issues a `code-green` node per issue: writes minimum implementation to pass those tests
-   - Enforces `code-red` before `code-green` within each issue via `depends_on` edges
-   - Runs independent issues' `code-red` (and `code-green`) phases in parallel
-
-## Prerequisites
-
-- `/unic-dlc-plan <slug>` must have been run and the plan PR approved
-- `.archon/workflows/build-<slug>.yaml` must exist
-- `.archon/unic-dlc.config.json` must be present (created by the install hook)
-
-## TDD contract
-
-Every issue in the build goes through:
-
-```
-RED:   code-red-<id>   → write failing acceptance tests
-GREEN: code-green-<id> → write minimum implementation to pass those tests
-```
-
-No `code-green` node may run before its corresponding `code-red` node completes.
-Independent issues run their `code-red` and `code-green` phases in parallel,
-giving the fastest possible end-to-end build time.
-
-## Runs
-
-```
-archon workflow run unic-dlc-build --input slug=<slug>
-```
diff --git a/.archon/commands/unic-dlc-cleanup.md b/.archon/commands/unic-dlc-cleanup.md
deleted file mode 100644
index 36497ac2..00000000
--- a/.archon/commands/unic-dlc-cleanup.md
+++ /dev/null
@@ -1,61 +0,0 @@
-# /unic-dlc-cleanup
-
-Post-merge cleanup for a planning session: architecture review, ADR consolidation, and a
-triage pass to refresh project state.
-
-## Usage
-
-```
-/unic-dlc-cleanup <slug>
-```
-
-Where `<slug>` is the session identifier used throughout the plan → build → qa cycle.
-
-## What this command does
-
-1. **`arch-review` node** — reads `docs/workflow/<slug>/PRD.md` (intent) and
-   `docs/workflow/<slug>/report.md` (technical outcome) alongside the changed code.
-   Detects three categories of drift:
-
-   - **Technical drift**: too-shallow modules, tight coupling, leaky abstractions.
-   - **Intent drift**: delivered behaviour that diverges from the PRD; silently dropped
-     acceptance criteria; scope creep added during build.
-   - **Deepening opportunities**: modules that could hide more complexity behind their
-     current interface.
-
-   Output: `docs/workflow/<slug>/arch-review.md`
-
-2. **`adr-consolidation` interactive node** — presents each proposed ADR individually for
-   human approval. Sources:
-
-   - "Decisions Made" section of `report.md`
-   - "Accept as ADR" items from `arch-review.md`
-
-   Each ADR is shown with Context, Decision, and Consequences. The user accepts (A),
-   rejects (R), or edits (E) each candidate. Only accepted ADRs are written to `docs/adr/`.
-
-3. **`run-triage` node** — invokes the shared triage workflow by name via
-   `archon workflow run unic-dlc-triage`. No triage logic is duplicated in the cleanup
-   workflow. This produces `HANDOFF.md` and updates `docs/workflow/ROADMAP.md` exactly
-   once per cleanup run.
-
-## Prerequisites
-
-- The build and QA cycles for `<slug>` must be complete (build PR merged, QA approved)
-- `docs/workflow/<slug>/PRD.md` and `docs/workflow/<slug>/report.md` must exist
-- `.archon/unic-dlc.config.json` must be present
-
-## Outputs
-
-| File                                  | Description                                     |
-| ------------------------------------- | ----------------------------------------------- |
-| `docs/workflow/<slug>/arch-review.md` | Architecture review with drift findings         |
-| `docs/adr/NNNN-*.md`                  | Accepted ADRs (one file per accepted candidate) |
-| `HANDOFF.md`                          | Updated handoff snapshot (from triage)          |
-| `docs/workflow/ROADMAP.md`            | Updated project phase (from triage)             |
-
-## Runs
-
-```
-archon workflow run unic-dlc-cleanup --input slug=<slug>
-```
diff --git a/.archon/commands/unic-dlc-explore.md b/.archon/commands/unic-dlc-explore.md
deleted file mode 100644
index 29ba263e..00000000
--- a/.archon/commands/unic-dlc-explore.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-description: Run the unic-archon-dlc explore workflow — parallel research across stack, features, architecture, and pitfalls, then synthesize into docs/workflow/<slug>/findings.md
----
-
-# /unic-dlc-explore
-
-Runs the `explore` workflow: four parallel research agents investigate the project from different angles, then a synthesize node combines their findings into a single `findings.md` document.
-
-## When to use
-
-- At the start of a new feature or investigation to build a shared mental model.
-- When onboarding to an unfamiliar project or module.
-- Before writing a spec, to surface pitfalls and architecture constraints early.
-- Any time you want a structured snapshot of what the project is, what it does, and where the risks are.
-
-## What it produces
-
-- **`docs/workflow/<slug>/findings.md`** — five sections:
-  - **Stack** — runtime, package manager, toolchain
-  - **Features** — shipped capabilities, in-progress work, planned features
-  - **Architecture** — directory structure, design patterns, ADR decisions, cross-platform constraints
-  - **Pitfalls** — TODOs, untested modules, CI issues, HANDOFF.md blockers
-  - **Integrated Brief** — 3-5 sentence synthesis with the highest-impact next step
-
-## Usage
-
-```sh
-archon workflow run unic-dlc-explore --input slug=<slug>
-```
-
-Or invoke from Claude Code:
-
-```
-/unic-dlc-explore <slug>
-```
-
-Replace `<slug>` with a short identifier for this exploration (e.g. `auth-refactor`, `v2-planning`).
-
-## Workflow structure
-
-```
-research-stack  ──┐
-research-features ─┤
-                   ├──▶  synthesize  ──▶  findings.md
-research-architecture ─┤
-research-pitfalls ──┘
-```
-
-All four research nodes are independent and run in parallel. The `synthesize` node depends on all four and writes the final output.
-
-## Inspiration
-
-- Parallel research pattern from the Archon workflow specification.
-- This plugin's `lib/findings-writer.mjs` handles idempotent directory and file creation.
diff --git a/.archon/commands/unic-dlc-plan.md b/.archon/commands/unic-dlc-plan.md
deleted file mode 100644
index a659f25e..00000000
--- a/.archon/commands/unic-dlc-plan.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-description: Run the unic-archon-dlc plan workflow — adversarial spec interview, PRD synthesis, and human PR gate
----
-
-# /unic-dlc-plan
-
-Runs the `plan` workflow: loads project context and prior research, runs an adversarial interview to surface requirements and decisions, synthesises the transcript into a structured PRD, and opens a PR for human review before proceeding.
-
-## When to use
-
-- After `/unic-dlc-explore` to turn research findings into a formal PRD.
-- When starting a new feature and you want to stress-test assumptions before writing specs.
-- Any time you need a structured `PRD.md` that captures problem, solution, stories, decisions, and scope.
-
-## What it produces
-
-- **`docs/workflow/<slug>/PRD.md`** — seven sections: Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, Further Notes.
-- **`docs/adr/NNNN-<slug>.md`** — one or more ADR files for non-obvious decisions surfaced during the interview (written live, confirmed by user).
-- **PR** targeting `develop` — pauses until approved. Rejection returns control to the adversarial interview for refinement.
-
-## Usage
-
-```sh
-archon workflow run unic-dlc-plan --input slug=<slug>
-```
-
-Or invoke from Claude Code:
-
-```
-/unic-dlc-plan <slug>
-```
-
-Replace `<slug>` with a short identifier for this planning session (e.g. `auth-refactor`, `v2-planning`).
-
-## Options
-
-Set `workflow.discuss_mode` in `.archon/unic-dlc.config.json` to control the interview style:
-
-| Value                 | Behaviour                                                                |
-| --------------------- | ------------------------------------------------------------------------ |
-| `interview` (default) | One focused, adversarial question per turn; probes deeply                |
-| `assumptions`         | Surfaces all implicit assumptions upfront, then confirms or refutes each |
-
-## Workflow structure
-
-```
-load-context ──▶ specs (loop) ──▶ to-prd ──▶ prd-gate (interactive)
-                     ▲                              │
-                     └──────── rejected ────────────┘
-```
-
-- `load-context` reads CONTEXT.md, CONTEXT-MAP.md, all ADRs, and findings.md (if present).
-- `specs` runs the adversarial interview; writes ADRs live for confirmed decisions.
-- `to-prd` synthesises the interview transcript into PRD.md.
-- `prd-gate` validates all 7 sections, opens a PR, and waits for human approval.
-
-## Inspiration
-
-- The `grill-with-docs` skill — adversarial interview pattern against the domain model.
-- The `to-prd` skill — structured PRD synthesis from conversation context.
-- Archon PR-gate pattern for human-in-the-loop workflow checkpoints.
diff --git a/.archon/commands/unic-dlc-qa.md b/.archon/commands/unic-dlc-qa.md
deleted file mode 100644
index f44bfbee..00000000
--- a/.archon/commands/unic-dlc-qa.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-description: Run the unic-archon-dlc QA workflow — e2e tests, coverage gate, UAT checklist, and merge
----
-
-# /unic-dlc-qa
-
-Runs the `qa` workflow: executes end-to-end tests, enforces the coverage threshold, walks through
-a UAT checklist derived from the PRD's acceptance criteria, and merges the PR once the human approves.
-
-## When to use
-
-- After `/unic-dlc-build <slug>` is complete and the build PR has been reviewed and approved.
-- When you want a structured QA gate before merging a feature branch.
-- Any time you need to confirm that acceptance criteria are met before shipping.
-
-## What it produces
-
-- **e2e results** — pass/fail output from the command configured in `e2e_command`.
-- **Coverage report** — pass/fail against the `coverage_threshold` set in `.archon/unic-dlc.config.json`.
-- **UAT checklist** — numbered acceptance criteria from `docs/workflow/<slug>/PRD.md`, presented alongside build coverage evidence.
-- **Merged PR** — once UAT is approved, the PR is merged via the configured tracker CLI and the feature branch is cleaned up (Gitflow only).
-
-## Usage
-
-```sh
-archon workflow run unic-dlc-qa --input slug=<slug>
-```
-
-Or invoke from Claude Code:
-
-```
-/unic-dlc-qa <slug>
-```
-
-Replace `<slug>` with the same identifier used in `/unic-dlc-plan` and `/unic-dlc-build`.
-
-## Prerequisites
-
-- `/unic-dlc-build <slug>` must have been run and the build PR approved.
-- `.archon/unic-dlc.config.json` must be present (created by the install hook).
-- `e2e_command` must be set in the config. If not, run `archon install --reconfigure` to set it.
-- The current branch must have an open PR targeting `develop` (for the merge step).
-
-## Workflow structure
-
-```
-e2e  ──▶  coverage-gate  ──▶  uat-gate (interactive)  ──▶  merge
-```
-
-- `e2e` — reads `e2e_command` from config; fails fast with a helpful message if it is not set.
-- `coverage-gate` — runs `pnpm test --coverage`; parses the output to compare against `coverage_threshold`. Skipped if no threshold is configured.
-- `uat-gate` — presents the numbered UAT checklist; waits for APPROVE or REJECT from the human.
-- `merge` — merges the PR via the tracker CLI (gh / az / manual instructions for jira and local-markdown); deletes the feature branch on Gitflow.
-
-## Configuration reference
-
-All settings are read from `.archon/unic-dlc.config.json`:
-
-| Field                | Type   | Default     | Description                                                              |
-| -------------------- | ------ | ----------- | ------------------------------------------------------------------------ |
-| `e2e_command`        | string | —           | Shell command to run e2e tests (e.g. `"pnpm test:e2e"`)                  |
-| `coverage_threshold` | number | —           | Minimum coverage % required (e.g. `80`). Omit to skip the gate.          |
-| `tracker`            | string | `"github"`  | Issue tracker: `github`, `ado`, `jira`, `local-markdown`                 |
-| `branching`          | string | `"gitflow"` | Branch strategy: `gitflow` (delete feature branch) or `github-flow`      |
-| `pr_strategy`        | string | `"squash"`  | GitHub merge style: `squash` or `merge` (used for `github` tracker only) |
-
-## UAT interaction
-
-The `uat-gate` node pauses and asks for your decision:
-
-- Type **`APPROVE`** to proceed to merge.
-- Type **`REJECT AC-N`** (e.g. `REJECT AC-3`) to flag a failing criterion. The workflow halts and you are returned to address the issue before re-running.
-
-## Runs
-
-```
-archon workflow run unic-dlc-qa --input slug=<slug>
-```
diff --git a/.archon/commands/unic-dlc-review.md b/.archon/commands/unic-dlc-review.md
deleted file mode 100644
index 3f016f28..00000000
--- a/.archon/commands/unic-dlc-review.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-description: Run the unic-archon-dlc self-contained code review workflow — four aspects, structured findings, single PR comment, idempotent re-run
----
-
-# /unic-dlc-review
-
-Runs the `review` workflow: analyses the current PR diff across four review aspects
-(code quality, test coverage, silent failures, type design), then posts — or updates — a
-single structured comment on the PR.
-
-**No runtime dependency on pr-review-toolkit or any other plugin.**
-All review logic is self-contained in `.archon/workflows/unic-dlc-review.yaml`.
-
-## When to use
-
-- After opening a PR and before requesting human review.
-- As a final quality gate before merging.
-- Re-run it after addressing feedback — it will **update** the prior comment rather than
-  posting a duplicate.
-
-## What it produces
-
-A single structured PR comment (or updated comment on re-run) with four sections:
-
-1. **Code quality** — readability, naming, function length, project-convention adherence
-2. **Test coverage adequacy** — exercises public interfaces, output-focused assertions, no
-   internal-collaborator mocks
-3. **Silent failure patterns** — swallowed exceptions, empty catch blocks, fallbacks that
-   hide bugs
-4. **Type design quality** — encapsulation, invariants in types, illegal-state-unrepresentable
-   patterns
-
-Each section lists specific findings with `file:line` references, or an explicit
-"No findings." line if nothing was detected.
-
-## Usage
-
-```sh
-archon workflow run unic-dlc-review
-```
-
-Or invoke from Claude Code:
-
-```
-/unic-dlc-review
-```
-
-No arguments needed. The workflow reads `.archon/unic-dlc.config.json` to determine the
-tracker and the current open PR.
-
-## Workflow structure
-
-```
-code-review  ──▶  structured comment posted / updated on PR
-```
-
-Single-node DAG. The node reads CLAUDE.md / AGENTS.md for project conventions, runs the
-four review aspects, and calls the tracker adapter to post or update the comment.
-
-## Re-run behaviour
-
-When you run `/unic-dlc-review` again on the same PR:
-
-- The workflow searches for a prior comment whose body contains the sentinel marker
-  `<!-- unic-dlc-review -->`.
-- If found, it **updates** that comment in-place.
-- If not found, it creates a new comment.
-
-This prevents duplicate review threads accumulating over multiple runs.
-
-## Inspiration
-
-- `apps/claude-code/pr-review/` — multi-aspect analysis structure, compact finding
-  schema (`severity / filePath / startLine / endLine / title / body`), re-review
-  detection via sentinel, and the discipline of posting a single summary comment rather
-  than many inline threads.
-- Matt Pocock's review skill
-  (https://github.com/mattpocock/skills/blob/main/skills/in-progress/review/SKILL.md) —
-  aspect-driven review structure, explicit "no findings" lines, and the principle that
-  every run should produce actionable output even when everything looks good.
-- This plugin's `lib/tracker-adapter.mjs` — used to post or update the comment via the
-  configured tracker backend (github / ado / jira / local-markdown).
diff --git a/.archon/commands/unic-dlc-triage.md b/.archon/commands/unic-dlc-triage.md
deleted file mode 100644
index e0eb8ad2..00000000
--- a/.archon/commands/unic-dlc-triage.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-description: Run the unic-archon-dlc triage workflow — produces HANDOFF.md and updates ROADMAP.md
----
-
-# /unic-dlc-triage
-
-Runs the `triage` workflow: reads current issue states from the configured tracker, reconciles them against `docs/workflow/ROADMAP.md`, and produces `HANDOFF.md` at the repo root.
-
-## When to use
-
-- After a session boundary to resume cleanly in a fresh context.
-- As the final step of the `/unic-dlc-cleanup` workflow (reused by the cleanup DAG).
-- Any time you want a status snapshot of open issues, blockers, and recent decisions.
-
-## What it produces
-
-- **`HANDOFF.md`** (repo root) — four sections: current phase, open issues by state, blockers, recent decisions.
-- **`docs/workflow/ROADMAP.md`** — created on first run; phase status updated on each run. Human-edited sections are preserved.
-
-## Usage
-
-```sh
-archon workflow run unic-dlc-triage
-```
-
-Or invoke from Claude Code:
-
-```
-/unic-dlc-triage
-```
-
-## Inspiration
-
-- Matt Pocock skills repo — `/triage` skill pattern.
-- This plugin's `docs/agents/` files (written by the install hook) provide the domain context consumed by the triage prompt nodes.
diff --git a/.archon/ralph/00-setup-slash-command/prd.md b/.archon/ralph/00-setup-slash-command/prd.md
deleted file mode 100644
index de6c057a..00000000
--- a/.archon/ralph/00-setup-slash-command/prd.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# 00. Setup slash command
-
-- Priority: P1
-- Effort: M
-- Version impact: minor (replaces the manual install path with a first-class slash command)
-- Depends on: —
-- Touches: `commands/setup.md` (new), `lib/install-runner.mjs` (new), `lib/archon-check.mjs` (new), `hooks/install.mjs` (deleted), `.claude-plugin/plugin.json`, `README.md`, `CHANGELOG.md`, `docs/adr/0001-setup-as-slash-command.md`, `docs/adr/README.md` (new), `docs/plans/README.md` (new), `CONTEXT.md` (already updated)
-
-## Context
-
-The plugin advertises a slash-command-first install flow (`README.md:135` shows `/unic-dlc-install`) but no slash commands exist at the plugin root yet. The current entry point is `hooks/install.mjs`, a readline script declared under `"hooks": { "install": ... }` in `plugin.json` — but Claude Code does not auto-execute install hooks, so users must run `node ${CLAUDE_PLUGIN_ROOT}/hooks/install.mjs` from a terminal. That path is undocumented in the README and not the experience users expect after installing a Claude Code plugin.
-
-This spec ships the first real slash command for unic-archon-dlc and the precedent for the other six workflow commands when they migrate from `.archon/commands/` (Archon workflow templates) to actual Claude Code slash commands. The architectural shape — slash command delegates to a pure lib module, no terminal CLI wrapper — is locked by [ADR-0001](../adr/0001-setup-as-slash-command.md).
-
-## Current behaviour
-
-- `hooks/install.mjs` exists as an interactive readline script with four behaviours: fresh-install (ask all), partial-fill (ask missing only), already-configured (print and exit), and `--reconfigure` (re-prompt all).
-- The script runs `checkArchon()` first (preflight + known-incompatible-versions warning) and exits with code 1 on missing binary.
-- It calls `exploreProject()` to auto-detect git remote, then `loadConfig()` for any existing config, then prompts with `node:readline/promises`.
-- After collection it writes `.archon/unic-dlc.config.json`, calls `writeAgentDocs()` to generate `docs/agents/*.md`, and calls `updateAgentSkillsBlock()` to merge a marker-delimited `## Agent skills` block into `CLAUDE.md`.
-- `plugin.json` declares `"hooks": { "install": "hooks/install.mjs" }`. Claude Code does not execute this hook on plugin install.
-- No `commands/` directory exists at the plugin root; no slash command is registered for the plugin.
-- The README's quick-start advertises `/unic-dlc-install` — this command does not exist.
-
-## Target behaviour
-
-- A `commands/setup.md` slash command exists and is invoked as `/unic-archon-dlc:setup`.
-- The command conducts the configuration conversation (tracker / branching / e2e command); it does not write files directly.
-- Filesystem writes are delegated to `lib/install-runner.mjs`, exporting `runInstall(projectDir, partialAnswers)`. The function merges `{ ...defaults, ...existing, ...partialAnswers }` (matching `hooks/install.mjs:146`), enforces the mandatory-fields invariant after merge (throws a typed error if absent), and writes config + agent docs + CLAUDE.md block in the same order and with the same per-step error semantics as the existing hook.
-- Archon preflight is performed by `lib/archon-check.mjs`, exporting a pure `checkArchon()` returning `{ ok: true, version } | { ok: false, code: 'enoent' | 'incompatible' | 'other', message }`. No `process.exit`. The slash command runs this first and bails with the friendly message on `ok: false`.
-- Idempotency follows the hybrid model from the design grilling: fresh→ask-all; partial→ask-only-missing; full + no args→print summary and exit; `setup reconfigure`→re-prompt-all; `setup <free-form intent>`→targeted tweak via conversational interpretation.
-- `hooks/install.mjs` is deleted; the `"hooks"` field is removed from `plugin.json`.
-- `README.md` quick-start references `/unic-archon-dlc:setup`, not `/unic-dlc-install`.
-- `CHANGELOG.md` has an `Added` / `Removed` entry under `[Unreleased]`.
-
-## Affected files
-
-| File                           | Change                                                                                                                                                                                                                                                                |
-| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `commands/setup.md`            | New. Thin orchestrator markdown: argument parse, archon preflight, config discovery, conversational prompting, `runInstall` invocation, friendly result rendering.                                                                                                    |
-| `lib/install-runner.mjs`       | New. Extract the post-prompt body of `hooks/install.mjs:128–187` into `runInstall(projectDir, partialAnswers)`. Pure with respect to user input; performs I/O on disk only. Includes `repo_layout` detection (from `detectRepoLayout`) and the default labels lookup. |
-| `lib/archon-check.mjs`         | New. Extract `hooks/install.mjs:44–67` into a result-returning function. Move `INCOMPATIBLE_ARCHON_VERSIONS` into the module.                                                                                                                                         |
-| `test/install-runner.test.mjs` | New. Covers fresh / partial / full / reconfigure paths; mandatory-field enforcement; merge precedence.                                                                                                                                                                |
-| `test/archon-check.test.mjs`   | New. Covers `enoent`, version OK, version-incompatible, generic error.                                                                                                                                                                                                |
-| `hooks/install.mjs`            | Delete.                                                                                                                                                                                                                                                               |
-| `.claude-plugin/plugin.json`   | Remove the `"hooks"` field.                                                                                                                                                                                                                                           |
-| `README.md`                    | Replace `/unic-dlc-install` (and its surrounding paragraph at lines 131–140) with `/unic-archon-dlc:setup`. Drop mentions of "install hook"; describe the slash command.                                                                                              |
-| `CHANGELOG.md`                 | `Added: /unic-archon-dlc:setup slash command.` `Removed: hooks/install.mjs and "hooks" field from plugin.json.`                                                                                                                                                       |
-| `docs/adr/README.md`           | New. Index file listing ADR-0001.                                                                                                                                                                                                                                     |
-| `docs/plans/README.md`         | New. Index file listing this spec.                                                                                                                                                                                                                                    |
-| `CONTEXT.md`                   | Already updated with Setup, Claude Code slash command, and Archon workflow command template entries.                                                                                                                                                                  |
-
-## Implementation steps
-
-1. **Extract `lib/archon-check.mjs`.** Copy the body of `checkArchon()`, replace `process.exit(1)` with a returned result object, move `INCOMPATIBLE_ARCHON_VERSIONS` into the module. Add `test/archon-check.test.mjs` covering the four result branches via a stubbable `execFileSync`.
-2. **Extract `lib/install-runner.mjs`.** Move the merge logic (`hooks/install.mjs:135–187`) into `runInstall(projectDir, partialAnswers)`. The function does _not_ prompt and does _not_ call `checkArchon` — both are the slash command's responsibility. It reads existing config via `loadConfig`, performs the merge, validates mandatory fields, writes config, calls `writeAgentDocs`, calls `updateAgentSkillsBlock`. Returns `{ ok: true, configPath, wroteDocs, wroteClaudeMd } | { ok: false, stage, message }`. Add `test/install-runner.test.mjs`.
-3. **Write `commands/setup.md`.** The markdown should: parse `$ARGUMENTS` for `reconfigure` or free-form intent; run `checkArchon` and bail with the friendly message on failure; call `exploreProject` and `loadConfig` to discover state; branch on (existing-config × arguments) per the hybrid idempotency table; collect any needed answers via conversational prompts; call `runInstall(cwd, answers)`; print the success summary or the staged-error message. Reference ADR-0001 in a one-line note at the top.
-4. **Delete `hooks/install.mjs`.** Remove the file. There is no migration shim — the readline path was never documented in the README.
-5. **Remove `"hooks"` from `.claude-plugin/plugin.json`.**
-6. **Update `README.md`.** Replace the quick-start `/unic-dlc-install` block with a `/unic-archon-dlc:setup` block. Remove references to "install hook" elsewhere in the file.
-7. **Add `CHANGELOG.md` entries** under `[Unreleased]`.
-8. **Create the two index files** (`docs/adr/README.md`, `docs/plans/README.md`) so the directories have discoverable contents.
-
-## Verification
-
-- `pnpm --filter unic-archon-dlc test` passes (covers both new lib modules).
-- `pnpm typecheck` passes (no JSDoc regressions).
-- `pnpm ci:check` passes (Biome + Prettier).
-- Manual smoke test in a clean target project:
-  - `/unic-archon-dlc:setup` on a fresh project → asks three questions → `.archon/unic-dlc.config.json`, `docs/agents/*.md`, and `CLAUDE.md` `## Agent skills` block all present.
-  - `/unic-archon-dlc:setup` re-run with full config → prints current values, exits without writing.
-  - `/unic-archon-dlc:setup reconfigure` → re-prompts all three questions, overwrites config.
-  - `/unic-archon-dlc:setup` with `archon` removed from PATH → friendly "archon not on PATH" message, no partial writes.
-  - `/unic-archon-dlc:setup change branching to github-flow` (full config existing) → updates one field, leaves others, writes config.
-
-## Acceptance criteria
-
-- `commands/setup.md` exists and is the only documented entry point for configuring the plugin.
-- `hooks/install.mjs` no longer exists.
-- `plugin.json` has no `hooks` field.
-- `lib/install-runner.mjs` and `lib/archon-check.mjs` exist with tests, both pass.
-- The merge precedence in `runInstall` is `defaults < existing < partialAnswers`, matching the deleted hook byte-for-byte for that block.
-- `runInstall` throws a typed error (not `process.exit`) when mandatory fields are missing after merge.
-- `checkArchon` returns a result object (not `process.exit`) for every branch.
-- README quick-start references `/unic-archon-dlc:setup`.
-- CHANGELOG has `Added` and `Removed` entries.
-- ADR-0001 is referenced from `commands/setup.md` and `docs/adr/README.md`.
-
-## Out of scope
-
-- Migrating `.archon/commands/*` (Archon workflow templates) into Claude Code slash commands at `commands/`. Separate spec.
-- Wiring archon preflight into workflow commands. ADR-0001 explicitly leaves preflight in setup only.
-- `.gitignore` changes for `.archon/`. Config is team config and presumed committed; transient state lives under `$ARTIFACTS_DIR`.
-- A non-interactive CLI wrapper around `runInstall()` for CI/scripted use. If a future caller needs it, a 5-line `bin/setup-cli.mjs` is trivial; do not pre-build for it.
-- Changing the slash command name later (e.g. `:configure` or `:init`). Locked in ADR-0001 / Q4 of the grilling session.
diff --git a/.archon/ralph/setup-slash-command/prd.json b/.archon/ralph/setup-slash-command/prd.json
deleted file mode 100644
index 540dbbe8..00000000
--- a/.archon/ralph/setup-slash-command/prd.json
+++ /dev/null
@@ -1,111 +0,0 @@
-{
-  "project": "unic-archon-dlc",
-  "branchName": "ralph/setup-slash-command",
-  "prdFile": "prd.md",
-  "description": "Replace hooks/install.mjs with a proper /unic-archon-dlc:setup slash command backed by pure lib modules",
-  "userStories": [
-    {
-      "id": "US-001",
-      "title": "Create lib/archon-check.mjs with result-object API and tests",
-      "description": "As a slash command author, I want a pure `checkArchon()` function that returns a result object so that I can handle all archon preflight outcomes without process.exit",
-      "acceptanceCriteria": [
-        "File `lib/archon-check.mjs` exists and exports a named `checkArchon()` function",
-        "Return type is `{ ok: true, version: string } | { ok: false, code: 'enoent' | 'incompatible' | 'other', message: string }`",
-        "`INCOMPATIBLE_ARCHON_VERSIONS` constant lives in this module (moved from hooks/install.mjs:24)",
-        "No `process.exit()` call anywhere in the module",
-        "File `test/archon-check.test.mjs` exists covering: enoent branch, version OK branch, incompatible version branch, generic error branch",
-        "Tests use node:test + node:assert/strict pattern matching existing test files",
-        "execFileSync is stubbable (injected or mocked) so tests do not require archon on PATH",
-        "`pnpm --filter unic-archon-dlc test` passes",
-        "`pnpm --filter unic-archon-dlc typecheck` passes"
-      ],
-      "technicalNotes": "Extract from hooks/install.mjs:44–67. Replace process.exit(1) with return { ok: false, code: ..., message: ... }. For incompatible version, return { ok: false, code: 'incompatible', message: ... } rather than warn-and-continue (warning becomes the slash command's responsibility). Follow lib/config-loader.mjs discriminated union pattern. Test isolation: pass execFileSync as a parameter or use module mocking via node:test mock.module().",
-      "dependsOn": [],
-      "priority": 1,
-      "passes": true,
-      "notes": "Implemented in iteration 1. Files: lib/archon-check.mjs, test/archon-check.test.mjs, package.json (test script)."
-    },
-    {
-      "id": "US-002",
-      "title": "Create lib/install-runner.mjs with runInstall() and tests",
-      "description": "As a slash command author, I want a pure `runInstall(projectDir, partialAnswers)` function so that file I/O is separated from user interaction and independently testable",
-      "acceptanceCriteria": [
-        "File `lib/install-runner.mjs` exists and exports a named `runInstall(projectDir, partialAnswers)` function",
-        "Return type is `{ ok: true, configPath: string, wroteDocs: boolean, wroteClaudeMd: boolean } | { ok: false, stage: 'validate' | 'config' | 'docs' | 'claude-md', message: string }`",
-        "Merge precedence is `defaults < existing < partialAnswers` (matching hooks/install.mjs:145–155 exactly)",
-        "Mandatory fields validated after merge: missing `tracker`, `pr_strategy`, or `branching` returns `{ ok: false, stage: 'validate', message: ... }` — no throw, no process.exit",
-        "`detectRepoLayout(projectDir)` logic (hooks/install.mjs:73–75) is inlined or re-exported from this module",
-        "Function calls `loadConfig`, `getDefaultLabels`, `writeAgentDocs`, `updateAgentSkillsBlock` in the same order as the hook (hooks/install.mjs:128–187)",
-        "Function does NOT call `checkArchon()` — that is the slash command's responsibility",
-        "Function does NOT prompt — no readline or user-input logic",
-        "File `test/install-runner.test.mjs` exists covering: fresh install (all defaults), partial fill (only missing fields updated), full config (no changes), reconfigure (partialAnswers overwrite existing), mandatory-field missing after merge returns validate error",
-        "Tests use tmpdir() isolation matching test/setup-explorer.test.mjs:11 pattern",
-        "`pnpm --filter unic-archon-dlc test` passes",
-        "`pnpm --filter unic-archon-dlc typecheck` passes"
-      ],
-      "technicalNotes": "Extract hooks/install.mjs:128–187 into runInstall(). The function signature is runInstall(projectDir: string, partialAnswers: Partial<Config>): RunInstallResult. Move detectRepoLayout from hooks/install.mjs:73–75 to this module. Import loadConfig from lib/config-loader.mjs, getDefaultLabels from lib/labels-config.mjs, writeAgentDocs + updateAgentSkillsBlock from lib/agent-docs-writer.mjs, exploreProject from lib/setup-explorer.mjs. For tests: write a real tmpdir project with a fake CLAUDE.md to satisfy writeAgentDocs/updateAgentSkillsBlock — or pass stubs for the write helpers if using dependency injection.",
-      "dependsOn": [],
-      "priority": 2,
-      "passes": true,
-      "notes": "Implemented in iteration 2. Files: lib/install-runner.mjs, test/install-runner.test.mjs, package.json (test script)."
-    },
-    {
-      "id": "US-003",
-      "title": "Create commands/setup.md slash command",
-      "description": "As a developer who installed unic-archon-dlc, I want to run `/unic-archon-dlc:setup` so that I can configure the plugin through a conversational interface in Claude Code",
-      "acceptanceCriteria": [
-        "File `commands/setup.md` exists at the plugin root",
-        "Command is invocable as `/unic-archon-dlc:setup` (filename matches plugin naming convention)",
-        "First line or header references ADR-0001 (`docs/adr/0001-setup-as-slash-command.md`)",
-        "Command parses `$ARGUMENTS` for `reconfigure` keyword and free-form intent strings",
-        "Command calls `checkArchon()` from `lib/archon-check.mjs` first; on `ok: false` prints the `message` and stops — no partial writes",
-        "Command calls `exploreProject()` and `loadConfig()` to discover current config state",
-        "Idempotency branches: fresh → ask all three; partial → ask missing only; full + no args → print summary and exit; full + reconfigure → re-prompt all; full + free-form → targeted tweak",
-        "Command calls `runInstall(cwd, answers)` from `lib/install-runner.mjs` for all write operations",
-        "On success: prints `unic-archon-dlc configured.` plus key/value summary",
-        "On `runInstall` failure: prints the staged error message from the result object",
-        "Plugin.json `commands` field references `commands/setup.md` (or the commands dir is auto-scanned — verify against plugin.json schema)"
-      ],
-      "technicalNotes": "commands/setup.md is a Claude Code slash command markdown file — it contains the prompt/instructions that Claude executes. It is not a Node.js script. Reference the hybrid idempotency table from the spec. Import path for lib modules: the slash command runs in the Claude Code agent context; it calls the lib modules via JS imports using the plugin root path. Check how other Claude Code plugins wire commands to lib (look at pr-review plugin for command patterns). The `plugin.json` may need a `commands` field added — check current schema against `.claude-plugin/plugin.json`.",
-      "dependsOn": ["US-001", "US-002"],
-      "priority": 3,
-      "passes": true,
-      "notes": "Implemented in iteration 3. Files: commands/setup.md."
-    },
-    {
-      "id": "US-004",
-      "title": "Delete hooks/install.mjs and remove \"hooks\" field from plugin.json",
-      "description": "As a maintainer, I want the obsolete hook removed so that there is one documented entry point and no dead code",
-      "acceptanceCriteria": [
-        "`hooks/install.mjs` no longer exists",
-        "`.claude-plugin/plugin.json` has no `hooks` field",
-        "`.claude-plugin/plugin.json` remains valid JSON with all other fields intact",
-        "`pnpm --filter unic-archon-dlc test` passes (no test imports hooks/install.mjs)",
-        "`pnpm --filter unic-archon-dlc typecheck` passes"
-      ],
-      "technicalNotes": "Delete hooks/install.mjs. Edit .claude-plugin/plugin.json to remove the `\"hooks\": { \"install\": \"hooks/install.mjs\" }` field. Verify that detectTracker() and deducePrStrategy() exported from hooks/install.mjs are either not imported anywhere else or have been copied into install-runner.mjs (US-002). Check test/ for any test importing from '../hooks/install.mjs' — there are existing hook tests (test/install-helpers.test.mjs, test/install-agent-docs.test.mjs, test/install-claude-md.test.mjs) that must be reviewed.",
-      "dependsOn": ["US-003"],
-      "priority": 4,
-      "passes": true,
-      "notes": "Implemented in iteration 4. Files: lib/install-runner.mjs (added detectTracker/deducePrStrategy), test/install-helpers.test.mjs (updated import), .claude-plugin/plugin.json (removed hooks field), deleted hooks/install.mjs."
-    },
-    {
-      "id": "US-005",
-      "title": "Update README.md quick-start and CHANGELOG.md",
-      "description": "As a developer reading the README, I want the quick-start to reference the real slash command so that I can get started without confusion",
-      "acceptanceCriteria": [
-        "README.md lines 129–136 no longer reference `/unic-dlc-install`",
-        "README.md quick-start shows `/unic-archon-dlc:setup` as the Step 1 command",
-        "README.md has no remaining references to `hooks/install.mjs` or 'install hook'",
-        "CHANGELOG.md has an `Added` entry: `Added /unic-archon-dlc:setup slash command` under `[Unreleased]`",
-        "CHANGELOG.md has a `Removed` entry: `Removed hooks/install.mjs and hooks field from plugin.json` under `[Unreleased]`",
-        "`pnpm --filter unic-archon-dlc verify:changelog` passes"
-      ],
-      "technicalNotes": "README.md quick-start is at lines 129–158. The Step 1 block (lines 129–136) advertises /unic-dlc-install — replace with /unic-archon-dlc:setup and rewrite the surrounding paragraph to describe the slash command flow. Also check lines 162–185 (configuration reference) for any install hook references. CHANGELOG.md should follow the existing format — check the current entries to match the style. The verify:changelog script checks for a properly dated [Unreleased] section.",
-      "dependsOn": ["US-003"],
-      "priority": 5,
-      "passes": true,
-      "notes": "Implemented in iteration 5. Files: README.md (quick-start updated), CHANGELOG.md (Added and Removed entries under [Unreleased])."
-    }
-  ]
-}
diff --git a/.archon/ralph/setup-slash-command/prd.md b/.archon/ralph/setup-slash-command/prd.md
deleted file mode 100644
index 02c6fc96..00000000
--- a/.archon/ralph/setup-slash-command/prd.md
+++ /dev/null
@@ -1,158 +0,0 @@
-# Setup Slash Command — Product Requirements
-
-## Overview
-
-**Problem**: The plugin advertises `/unic-dlc-install` in the README quick-start but no slash command exists. The real entry point is `hooks/install.mjs`, a readline terminal script that Claude Code never auto-executes. Users who install the plugin and try the advertised command get nothing. The hook is also undiscoverable — it requires running `node ${CLAUDE_PLUGIN_ROOT}/hooks/install.mjs` from a terminal, a path documented nowhere in the README.
-
-**Solution**: Ship `commands/setup.md` as the first-class entry point invoked as `/unic-archon-dlc:setup`. Extract the post-prompt write logic into `lib/install-runner.mjs` and the archon preflight into `lib/archon-check.mjs` — both pure, testable, and reused by the slash command. Delete the hook and remove it from `plugin.json`.
-
-**Branch**: `ralph/setup-slash-command`
-
----
-
-## Goals & Success
-
-### Primary Goal
-
-Replace the undiscoverable readline hook with a proper Claude Code slash command that users can invoke directly from Claude Code after installing the plugin.
-
-### Success Metrics
-
-| Metric               | Target                              | How Measured                                            |
-| -------------------- | ----------------------------------- | ------------------------------------------------------- |
-| Slash command exists | `/unic-archon-dlc:setup` registered | `commands/setup.md` present + referenced in plugin.json |
-| Hook deleted         | `hooks/install.mjs` absent          | File no longer exists                                   |
-| Tests pass           | All new lib tests green             | `pnpm --filter unic-archon-dlc test`                    |
-| Type-check clean     | Zero JSDoc regressions              | `pnpm typecheck`                                        |
-| README accurate      | Quick-start references new command  | Lines 129–136 updated                                   |
-
-### Non-Goals (Out of Scope)
-
-- Migrating `.archon/commands/*` to Claude Code slash commands — separate spec
-- Wiring archon preflight into workflow commands — ADR-0001 leaves preflight in setup only
-- Non-interactive CLI wrapper around `runInstall()` — trivial to add later if needed
-- Changing the slash command name (locked in ADR-0001)
-- `.gitignore` changes for `.archon/` — config is team config, presumed committed
-
----
-
-## User & Context
-
-### Target User
-
-- **Who**: Developer adding unic-archon-dlc to a project for the first time
-- **Role**: Team lead or senior dev setting up the AI development lifecycle
-- **Current Pain**: Installs the plugin, sees `/unic-dlc-install` in the README, types it in Claude Code, gets nothing. Falls back to reading the README more carefully and finds no terminal path documented.
-
-### User Journey
-
-1. **Trigger**: Developer installs `unic-archon-dlc` via Claude Code plugin marketplace and reads the README quick-start
-2. **Action**: Types `/unic-archon-dlc:setup` in Claude Code
-3. **Outcome**: Claude conducts a short 3-question configuration conversation, writes `.archon/unic-dlc.config.json`, generates `docs/agents/*.md`, and merges the `## Agent skills` block into `CLAUDE.md`
-
----
-
-## UX Requirements
-
-### Interaction Model
-
-Slash command with optional argument:
-
-- `/unic-archon-dlc:setup` — detect state; ask only missing fields (fresh: all three; partial: missing ones; full config: print summary and exit)
-- `/unic-archon-dlc:setup reconfigure` — re-prompt all three mandatory fields
-- `/unic-archon-dlc:setup <free-form intent>` — targeted conversational tweak (e.g. "change branching to github-flow")
-
-### States to Handle
-
-| State               | Description                                | Behavior                                   |
-| ------------------- | ------------------------------------------ | ------------------------------------------ |
-| Fresh               | No `.archon/unic-dlc.config.json`          | Ask all three mandatory fields             |
-| Partial             | Config exists but missing mandatory fields | Ask only missing fields                    |
-| Full + no args      | All mandatory fields present               | Print current values, exit without writing |
-| Full + reconfigure  | User passed `reconfigure`                  | Re-prompt all three fields, overwrite      |
-| Full + free-form    | User passed intent string                  | Conversational targeted tweak              |
-| Archon missing      | `archon` not on PATH                       | Friendly error message, no partial writes  |
-| Archon incompatible | Known bad version                          | Warning message, proceed                   |
-
----
-
-## Technical Context
-
-### Patterns to Follow
-
-- **Result-object error handling**: `lib/config-loader.mjs` — returns `{ error, … } | ValidConfig`, never throws for expected failure branches
-- **Three-tier merge**: `hooks/install.mjs:145–155` — `{ ...defaults, ...existing, ...partialAnswers }` then labels appended
-- **JS module pattern**: `lib/setup-explorer.mjs` — `// @ts-check`, named exports, JSDoc types, no default export
-- **Test pattern**: `test/setup-explorer.test.mjs:1–36` — `node:test`, `node:assert/strict`, `tmpdir()` + `Date.now()` isolation, one assertion per behavior
-- **Discriminated union test**: check `'error' in result` before destructuring (see `test/config-loader.test.mjs`)
-
-### Types & Interfaces
-
-```javascript
-// lib/archon-check.mjs — new result type
-/** @typedef {{ ok: true, version: string }} ArchonOk */
-/** @typedef {{ ok: false, code: 'enoent' | 'incompatible' | 'other', message: string }} ArchonFail */
-/** @typedef {ArchonOk | ArchonFail} ArchonCheckResult */
-
-// lib/install-runner.mjs — new result type
-/** @typedef {{ ok: true, configPath: string, wroteDocs: boolean, wroteClaudeMd: boolean }} RunInstallOk */
-/** @typedef {{ ok: false, stage: 'validate' | 'config' | 'docs' | 'claude-md', message: string }} RunInstallFail */
-/** @typedef {RunInstallOk | RunInstallFail} RunInstallResult */
-
-// Existing types consumed by install-runner
-// - TrackerBackend: 'github' | 'ado' | 'jira' | 'local-markdown' (lib/tracker-adapter.mjs)
-// - loadConfig(): ValidConfig | { error: string } (lib/config-loader.mjs)
-// - getDefaultLabels(tracker): Labels (lib/labels-config.mjs)
-// - writeAgentDocs(projectDir, config): void (lib/agent-docs-writer.mjs)
-// - updateAgentSkillsBlock(projectDir): void (lib/agent-docs-writer.mjs)
-// - exploreProject(projectDir): ProjectSnapshot (lib/setup-explorer.mjs)
-```
-
-### Architecture Notes
-
-- `lib/archon-check.mjs` must not call `process.exit()` — returns a result object for every branch including ENOENT
-- `lib/install-runner.mjs` must not prompt or call `checkArchon` — the slash command owns both
-- Mandatory fields after merge: `tracker`, `pr_strategy`, `branching` — missing any must return `{ ok: false, stage: 'validate', message: … }` not throw
-- `repo_layout` detection uses `detectRepoLayout()` from `hooks/install.mjs:73–75` — moves into `install-runner.mjs`
-- `detectTracker()` and `deducePrStrategy()` are also in `hooks/install.mjs:30–41` — the slash command calls them directly or they stay in the hook file until it's deleted; copy to install-runner or keep inline in the slash command
-
----
-
-## Implementation Summary
-
-### Story Overview
-
-| ID     | Title                                                              | Priority | Dependencies   |
-| ------ | ------------------------------------------------------------------ | -------- | -------------- |
-| US-001 | Create `lib/archon-check.mjs` with result-object API and tests     | 1        | —              |
-| US-002 | Create `lib/install-runner.mjs` with `runInstall()` and tests      | 2        | —              |
-| US-003 | Create `commands/setup.md` slash command                           | 3        | US-001, US-002 |
-| US-004 | Delete `hooks/install.mjs` and remove `"hooks"` from `plugin.json` | 4        | US-003         |
-| US-005 | Update `README.md` quick-start and `CHANGELOG.md`                  | 5        | US-003         |
-
-### Dependency Graph
-
-```
-US-001 (archon-check lib + tests)
-    ↘
-      US-003 (commands/setup.md) → US-004 (delete hook) → US-005 (docs)
-    ↗
-US-002 (install-runner lib + tests)
-```
-
----
-
-## Validation Requirements
-
-Every story must pass:
-
-- [ ] Type-check: `pnpm --filter unic-archon-dlc typecheck`
-- [ ] Lint: `pnpm check`
-- [ ] Tests: `pnpm --filter unic-archon-dlc test`
-- [ ] Format: `pnpm format`
-
----
-
-_Source spec_: `apps/claude-code/unic-archon-dlc/docs/plans/00-setup-slash-command.md`
-_ADR_: `apps/claude-code/unic-archon-dlc/docs/adr/0001-setup-as-slash-command.md`
-_Generated_: 2026-05-20T00:00:00Z
diff --git a/.archon/ralph/setup-slash-command/progress.txt b/.archon/ralph/setup-slash-command/progress.txt
deleted file mode 100644
index c020d3db..00000000
--- a/.archon/ralph/setup-slash-command/progress.txt
+++ /dev/null
@@ -1,150 +0,0 @@
-## Codebase Patterns
-
-### detectTracker/deducePrStrategy now live in lib/install-runner.mjs
-- **Where**: `lib/install-runner.mjs:1–18`
-- **Pattern**: These helper functions were moved from hooks/install.mjs when the hook was deleted. Tests import them from `../lib/install-runner.mjs`.
-
-### Test script is an explicit file list (not a glob)
-- **Where**: `apps/claude-code/unic-archon-dlc/package.json:13`
-- **Pattern**: The `test` script lists every test file explicitly. New test files must be appended to this list.
-- **Example**: `"test": "node --test test/foo.test.mjs test/bar.test.mjs"`
-
-### ExecFn injection pattern for testability
-- **Where**: `lib/archon-check.mjs`
-- **Pattern**: Pass `execFileSync` as an optional parameter with `typeof execFileSync` cast to a simpler `ExecFn` typedef to avoid TypeScript overload complexity. Tests inject a stub returning a string; production code falls back to the real import.
-- **Example**: `export function checkArchon(execFn = (execFileSync)) { ... }`
-
-### Biome import sort order: node: builtins first, then relative
-- **Where**: `test/archon-check.test.mjs`
-- **Pattern**: Biome enforces alphabetical sort within each import group. Named exports must also be sorted alphabetically (e.g. `{ checkArchon, INCOMPATIBLE_ARCHON_VERSIONS }`).
-
----
-
-## 2026-05-20 — US-001: Create lib/archon-check.mjs with result-object API and tests
-
-**Status**: PASSED
-**Files changed**:
-- `lib/archon-check.mjs` — new module with checkArchon() and INCOMPATIBLE_ARCHON_VERSIONS
-- `test/archon-check.test.mjs` — 5 tests covering all result branches
-- `package.json` — added test/archon-check.test.mjs to test script
-
-**Acceptance criteria verified**:
-- [x] File `lib/archon-check.mjs` exists and exports a named `checkArchon()` function
-- [x] Return type is `{ ok: true, version: string } | { ok: false, code: 'enoent' | 'incompatible' | 'other', message: string }`
-- [x] `INCOMPATIBLE_ARCHON_VERSIONS` constant lives in this module
-- [x] No `process.exit()` call anywhere in the module
-- [x] File `test/archon-check.test.mjs` exists covering: enoent branch, version OK branch, incompatible version branch, generic error branch
-- [x] Tests use node:test + node:assert/strict pattern
-- [x] execFn is stubbable (injected parameter with default)
-- [x] `pnpm --filter unic-archon-dlc test` passes (108 tests, 0 failures)
-- [x] `pnpm --filter unic-archon-dlc typecheck` passes
-
-**Learnings**:
-- `typeof execFileSync` parameter type causes TS2345 errors because overload resolution fails in stubs — use a simpler `ExecFn` typedef instead
-- Biome enforces named import alphabetical order; `INCOMPATIBLE_ARCHON_VERSIONS` must come after `checkArchon`
-- The test script is an explicit file list — every new test file must be added to package.json
-
----
-
-## 2026-05-20 — US-002: Create lib/install-runner.mjs with runInstall() and tests
-
-**Status**: PASSED
-**Files changed**:
-- `lib/install-runner.mjs` — new module with detectRepoLayout() and runInstall(), DEFAULTS constant, discriminated union result type
-- `test/install-runner.test.mjs` — 5 tests covering all merge/validate/write branches
-- `package.json` — added test/install-runner.test.mjs to test script
-
-**Acceptance criteria verified**:
-- [x] File `lib/install-runner.mjs` exists and exports `runInstall(projectDir, partialAnswers)`
-- [x] Return type is `RunInstallOk | RunInstallFail` discriminated union
-- [x] Merge precedence: defaults < existing < partialAnswers (spread order in `merged`)
-- [x] Mandatory fields validated after merge; missing returns `{ ok: false, stage: 'validate', message }`
-- [x] `detectRepoLayout(projectDir)` inlined and exported from this module
-- [x] Calls `loadConfig`, `getDefaultLabels`, `writeAgentDocs`, `updateAgentSkillsBlock` in hook order
-- [x] Does NOT call `checkArchon()` or prompt
-- [x] `test/install-runner.test.mjs` exists with 5 tests
-- [x] Tests use `tmpdir()` + `Date.now()` isolation
-- [x] `pnpm --filter unic-archon-dlc test` passes (113 tests, 0 failures)
-- [x] `pnpm --filter unic-archon-dlc typecheck` passes
-
-**Learnings**:
-- `loadConfig` returns `ConfigError` if ANY mandatory field is missing — existing partial configs (missing mandatory fields) are silently treated as empty (`{}`)
-- "Partial fill" test case: existing has all mandatory fields + optional `model_profile: 'fast'`; partialAnswers adds `e2e_command`. Both survive merge.
-- `labels` computed after validation (when `merged.tracker` is guaranteed present)
-- `!(f in merged)` pattern used for validation (consistent with config-loader.mjs, avoids `unknown` type issues)
-
----
-
-## 2026-05-20 — US-003: Create commands/setup.md slash command
-
-**Status**: PASSED
-**Files changed**:
-- `commands/setup.md` — new /unic-archon-dlc:setup slash command (131 lines)
-
-**Acceptance criteria verified**:
-- [x] File `commands/setup.md` exists at the plugin root
-- [x] Command is invocable as `/unic-archon-dlc:setup` (filename + plugin name convention)
-- [x] First content references ADR-0001 (`docs/adr/0001-setup-as-slash-command.md`)
-- [x] Command parses `$ARGUMENTS` for `reconfigure` keyword and free-form intent
-- [x] Command calls `checkArchon()` first; on `ok: false` prints message and stops
-- [x] Command calls `exploreProject()` and `loadConfig()` to discover config state
-- [x] All idempotency branches covered (fresh/partial/full+default/full+reconfigure/full+intent)
-- [x] Command calls `runInstall(cwd, answers)` for all write operations
-- [x] On success: prints `unic-archon-dlc configured.` plus summary
-- [x] On failure: prints `result.message` from RunInstallFail
-- [x] Plugin.json commands dir is auto-scanned (verified: pr-review has no `commands` field in plugin.json and commands work)
-- [x] `pnpm --filter unic-archon-dlc test` passes (113 tests, 0 failures)
-- [x] `pnpm --filter unic-archon-dlc typecheck` passes
-- [x] `pnpm check` passes (Biome + Prettier)
-
-**Learnings**:
-- Commands dir is auto-scanned by Claude Code — no `commands` field needed in plugin.json (verified against pr-review plugin)
-- Prettier reformats markdown code blocks with different indent/spacing; run `pnpm format` after creating new .md files
-- CLAUDE_PLUGIN_ROOT env var is used inside bash heredocs to import lib modules at runtime
-
----
-
-## 2026-05-20 — US-005: Update README.md quick-start and CHANGELOG.md
-
-**Status**: PASSED
-**Files changed**:
-- `README.md` — replaced `/unic-dlc-install` with `/unic-archon-dlc:setup`; changed "install hook" to "setup command" in two places
-- `CHANGELOG.md` — added `Added` and `Removed` entries under `[Unreleased]`
-
-**Acceptance criteria verified**:
-- [x] README.md lines 129–136 no longer reference `/unic-dlc-install`
-- [x] README.md quick-start shows `/unic-archon-dlc:setup` as the Step 1 command
-- [x] README.md has no remaining references to `hooks/install.mjs` or 'install hook'
-- [x] CHANGELOG.md has an `Added` entry under `[Unreleased]`
-- [x] CHANGELOG.md has a `Removed` entry under `[Unreleased]`
-- [x] `pnpm --filter unic-archon-dlc verify:changelog` passes
-
-**Learnings**:
-- verify:changelog structural check requires `### Breaking`, `### Added`, `### Fixed` in `[Unreleased]`; `### Removed` is optional and accepted
-- The diff-based version-bump gate uses repo-root-relative paths from `git diff --name-only`, so GUARDED path regexes (e.g. `/^commands\/.+\.md$/`) do NOT match monorepo paths — the gate does not trigger for plugin subdir changes
-
----
-
-## 2026-05-20 — US-004: Delete hooks/install.mjs and remove "hooks" field from plugin.json
-
-**Status**: PASSED
-**Files changed**:
-- `lib/install-runner.mjs` — added detectTracker() and deducePrStrategy() (moved from hooks/install.mjs)
-- `test/install-helpers.test.mjs` — updated import from `../hooks/install.mjs` to `../lib/install-runner.mjs`
-- `.claude-plugin/plugin.json` — removed `"hooks"` field
-- `hooks/install.mjs` — deleted
-
-**Acceptance criteria verified**:
-- [x] `hooks/install.mjs` no longer exists
-- [x] `.claude-plugin/plugin.json` has no `hooks` field
-- [x] `.claude-plugin/plugin.json` remains valid JSON with all other fields intact
-- [x] `pnpm --filter unic-archon-dlc test` passes (113 tests, 0 failures)
-- [x] `pnpm --filter unic-archon-dlc typecheck` passes
-- [x] `pnpm check` passes (Biome + Prettier)
-
-**Learnings**:
-- `detectTracker` and `deducePrStrategy` were exported from hooks/install.mjs and tested in install-helpers.test.mjs — they must be moved to lib/install-runner.mjs before deleting the hook
-- `detectRepoLayout` was already moved to lib/install-runner.mjs in US-002
-- Stage deleted files explicitly: `git add path/to/deleted-file`
-
----
diff --git a/.archon/unic-dlc.config.json b/.archon/unic-dlc.config.json
deleted file mode 100644
index 65b6b78e..00000000
--- a/.archon/unic-dlc.config.json
+++ /dev/null
@@ -1,37 +0,0 @@
-{
-  "model_profile": "balanced",
-  "tdd_mode": true,
-  "nyquist_validation": true,
-  "slopsquatting_gate": true,
-  "tracker": "github",
-  "pr_strategy": "merge",
-  "branching": "gitflow",
-  "e2e_command": null,
-  "repo_layout": "multi-context",
-  "labels": {
-    "state": {
-      "needs-triage": "needs-triage",
-      "needs-info": "needs-info",
-      "needs-specs": "needs-specs",
-      "ready-for-agent": "ready-for-agent",
-      "ready-for-human": "ready-for-human",
-      "resolved": "resolved",
-      "closed": "closed",
-      "rejected": "rejected"
-    },
-    "type": {
-      "feature": "feature",
-      "bug": "bug",
-      "spike": "spike",
-      "tech-debt": "tech-debt",
-      "docs": "docs",
-      "release": "release"
-    },
-    "priority": {
-      "p0": "p0",
-      "p1": "p1",
-      "p2": "p2",
-      "p3": "p3"
-    }
-  }
-}
diff --git a/.archon/unic-dlc.config.yaml b/.archon/unic-dlc.config.yaml
deleted file mode 100644
index 40f051e5..00000000
--- a/.archon/unic-dlc.config.yaml
+++ /dev/null
@@ -1,67 +0,0 @@
-project:
-  name: unic-agents-plugins
-  repo_layout: multi-context
-  branching: gitflow
-  pr_strategy: merge
-tracker:
-  type: github
-  access:
-    mcp: null
-    cli: gh
-  coords:
-    owner: unic
-    repo: unic-agents-plugins
-docs:
-  type: markdown
-  publish: false
-  access:
-    mcp: null
-    cli: null
-design:
-  type: none
-  access:
-    mcp: null
-repos: []
-templates:
-  prd: null
-  issue: null
-  bug: null
-classification:
-  labels:
-    state:
-      needs-triage: needs-triage
-      needs-info: needs-info
-      needs-specs: needs-specs
-      ready-for-agent: ready-for-agent
-      ready-for-human: ready-for-human
-      resolved: resolved
-      closed: closed
-      rejected: rejected
-    type:
-      feature: feature
-      bug: bug
-      spike: spike
-      tech-debt: tech-debt
-      docs: docs
-      release: release
-    priority:
-      p0: p0
-      p1: p1
-      p2: p2
-      p3: p3
-gates:
-  build: hitl
-  qa: hitl
-  pr-review: hitl
-  explore: hitl
-build:
-  fresh_context_red_green: true
-  tdd_mode: true
-  nyquist_validation: true
-  slopsquatting_gate: true
-  e2e_command: null
-  coverage_threshold: null
-estimations: off
-artifacts_dir: workflows
-model_profile: balanced
-methods: {}
diff --git a/.archon/workflows/unic-dlc-build.yaml b/.archon/workflows/unic-dlc-build.yaml
deleted file mode 100644
index 37bc35fc..00000000
--- a/.archon/workflows/unic-dlc-build.yaml
+++ /dev/null
@@ -1,365 +0,0 @@
-name: unic-dlc-build
-description: >
-  TDD build execution wrapper: slopcheck gate → generated per-slug build workflow.
-  Each issue goes red (failing tests) before green (passing implementation).
-  Independent issues run in parallel; chained issues run in dependency order.
-
-inputs:
-  slug:
-    description: Planning session identifier — matches the slug used in /unic-dlc-plan.
-    required: true
-
-nodes:
-  - id: slopcheck
-    name: Slopcheck — Verify New Packages
-    type: bash
-    runtime: bun
-    depends_on: []
-    script: |
-      #!/usr/bin/env node
-      // @ts-check
-      import { execFileSync } from 'node:child_process'
-      import { existsSync, readFileSync } from 'node:fs'
-      import { join } from 'node:path'
-      import { classifyPackages, parseNewPackages } from './lib/slopcheck.mjs'
-
-      const projectDir = process.cwd()
-      const pkgPath = join(projectDir, 'package.json')
-
-      if (!existsSync(pkgPath)) {
-        console.log('slopcheck: no package.json found, skipping.')
-        process.exit(0)
-      }
-
-      // Get the previous package.json from HEAD (if in a git repo)
-      let prevDeps = {}
-      try {
-        const prev = execFileSync('git', ['show', 'HEAD:package.json'], { cwd: projectDir, encoding: 'utf8' })
-        const parsed = JSON.parse(prev)
-        prevDeps = { ...parsed.dependencies, ...parsed.devDependencies }
-      } catch {
-        // Not in a git repo or no HEAD — treat all current packages as new (strictest)
-        console.log('slopcheck: cannot read HEAD:package.json, treating all packages as new.')
-      }
-
-      const current = JSON.parse(readFileSync(pkgPath, 'utf8'))
-      const currentDeps = { ...current.dependencies, ...current.devDependencies }
-      const newPkgs = parseNewPackages(prevDeps, currentDeps)
-
-      if (newPkgs.length === 0) {
-        console.log('slopcheck: no new packages detected. ✓')
-        process.exit(0)
-      }
-
-      console.log(`slopcheck: found ${newPkgs.length} new package(s): ${newPkgs.join(', ')}`)
-
-      // Determine registry check strategy
-      let registryFn = null
-
-      // Strategy 1: Python slopcheck tool
-      try {
-        execFileSync('slopcheck', ['--version'], { encoding: 'utf8' })
-        registryFn = async (/** @type {string} */ name) => {
-          try {
-            execFileSync('slopcheck', ['check', name], { encoding: 'utf8' })
-            return true
-          } catch {
-            return false
-          }
-        }
-        console.log('slopcheck: using Python slopcheck tool.')
-      } catch {
-        // Python tool not on PATH, try npm registry HEAD check
-        try {
-          const { default: https } = await import('node:https')
-          registryFn = (/** @type {string} */ name) =>
-            new Promise((resolve) => {
-              const encoded = encodeURIComponent(name).replace(/^%40/, '@')
-              const req = https.request(
-                { hostname: 'registry.npmjs.org', path: `/${encoded}`, method: 'HEAD' },
-                (res) => resolve(res.statusCode === 200),
-              )
-              req.on('error', () => resolve(false))
-              req.setTimeout(5000, () => {
-                req.destroy()
-                resolve(false)
-              })
-              req.end()
-            })
-          console.log('slopcheck: using npm registry HEAD check fallback.')
-        } catch {
-          console.log('slopcheck: no registry check available — all new packages treated as [ASSUMED].')
-        }
-      }
-
-      const verdicts = await classifyPackages(newPkgs, registryFn)
-      const assumed = verdicts.filter((v) => v.assumed)
-
-      if (assumed.length === 0) {
-        console.log('slopcheck: all new packages verified in registry. ✓')
-        process.exit(0)
-      }
-
-      console.log('\nslopcheck: [ASSUMED] packages require human verification:')
-      for (const pkg of assumed) {
-        console.log(`  ⚠  ${pkg.name} — not found in registry or unverifiable`)
-        console.log(`     checkpoint:human-verify — approve or reject this package before install continues`)
-      }
-      console.log(
-        '\nslopcheck: halting build. Resolve the above packages (remove them, pin a real version,',
-      )
-      console.log('or run the build with SLOPCHECK_BYPASS=1 to accept assumed packages explicitly.')
-
-      if (!process.env.SLOPCHECK_BYPASS) {
-        process.exit(1)
-      }
-
-  - id: run-build
-    name: Execute Generated Build Workflow
-    type: prompt
-    depends_on: [slopcheck]
-    prompt: |
-      You are running the unic-archon-dlc build workflow — run-build node.
-
-      The slopcheck gate has passed. Now execute the generated build workflow for this slug.
-
-      The generated workflow is at: .archon/workflows/build-{{ inputs.slug }}.yaml
-
-      Actions:
-      1. Verify that .archon/workflows/build-{{ inputs.slug }}.yaml exists.
-         If it does not exist, print:
-           "build-{{ inputs.slug }}.yaml not found. Run /unic-dlc-plan {{ inputs.slug }} first to generate it."
-         and halt.
-
-      2. Invoke the generated workflow via Archon by name:
-         Run: archon workflow run unic-dlc-build-{{ inputs.slug }} --input slug={{ inputs.slug }}
-
-         The generated workflow contains:
-           - code-red-<id> nodes: write FAILING acceptance tests per issue
-           - code-green-<id> nodes: write minimum implementation to pass those tests
-           - Dependency edges enforce: red before green within each issue
-           - Independent issues run code-red (and code-green) in parallel
-
-      3. After the workflow completes, print:
-         "build-{{ inputs.slug }} complete. All issues have been implemented following red→green discipline."
-
-      TDD rules enforced by the generated DAG:
-        - Never write implementation before writing failing tests.
-        - code-green nodes write ONLY enough code to pass the current tests.
-        - No speculative features, no extra abstractions.
-        - If a code-green node fails (tests still failing after implementation), pause and
-          ask the user whether to retry or flag the issue for human review.
-
-  - id: verification
-    name: Verification — Test Suite, Stubs, Wiring
-    type: bash
-    runtime: bun
-    depends_on: [run-build]
-    script: |
-      #!/usr/bin/env node
-      // @ts-check
-      import { readFileSync, readdirSync, statSync } from 'node:fs'
-      import { join, extname } from 'node:path'
-      import { execFileSync } from 'node:child_process'
-      import { detectStubs } from './lib/stub-detector.mjs'
-
-      const slug = process.env.ARCHON_INPUT_SLUG
-      if (!slug) {
-        console.error('verification: ARCHON_INPUT_SLUG is not set')
-        process.exit(1)
-      }
-
-      let exitCode = 0
-
-      // 1. Run the test suite
-      console.log('\n=== verification: running test suite ===')
-      try {
-        execFileSync('pnpm', ['test'], { stdio: 'inherit' })
-        console.log('verification: tests PASSED ✓')
-      } catch {
-        console.error('verification: tests FAILED ✗')
-        exitCode = 1
-      }
-
-      // 2. Detect stub patterns in changed source files
-      console.log('\n=== verification: checking for stub patterns ===')
-      let changedFiles = []
-      try {
-        const diff = execFileSync('git', ['diff', '--name-only', 'HEAD'], { encoding: 'utf8' })
-        changedFiles = diff.split('\n').filter(Boolean).filter(f => /\.(mjs|js|ts|py|rb|go|rs)$/.test(f))
-      } catch {
-        console.log('verification: cannot read git diff, skipping stub check.')
-      }
-
-      const stubFindings = []
-      for (const file of changedFiles) {
-        try {
-          const src = readFileSync(file, 'utf8')
-          const stubs = detectStubs(src)
-          for (const s of stubs) stubFindings.push({ file, ...s })
-        } catch { /* file deleted or unreadable */ }
-      }
-
-      if (stubFindings.length > 0) {
-        console.error(`verification: found ${stubFindings.length} stub pattern(s):`)
-        for (const f of stubFindings) {
-          console.error(`  ${f.file}:${f.line}  [${f.pattern}]  ${f.text}`)
-        }
-        exitCode = 1
-      } else {
-        console.log('verification: no stub patterns detected ✓')
-      }
-
-      // 3. Check coverage threshold
-      const configPath = '.archon/unic-dlc.config.json'
-      let coverageThreshold = null
-      try {
-        const cfg = JSON.parse(readFileSync(configPath, 'utf8'))
-        coverageThreshold = cfg.coverage_threshold ?? null
-      } catch { /* config absent */ }
-
-      if (coverageThreshold !== null) {
-        console.log(`\n=== verification: checking coverage threshold (${coverageThreshold}%) ===`)
-        try {
-          execFileSync('pnpm', ['test', '--coverage'], { stdio: 'inherit' })
-        } catch {
-          console.error(`verification: coverage check failed (threshold: ${coverageThreshold}%)`)
-          exitCode = 1
-        }
-      }
-
-      process.exit(exitCode)
-
-  - id: goals-check
-    name: Goals-Check — PRD Coverage Matrix
-    type: prompt
-    depends_on: [verification]
-    prompt: |
-      You are running the unic-archon-dlc build workflow — goals-check node.
-
-      Goal: produce a coverage matrix that maps every acceptance criterion from the PRD
-      to implementation evidence (file paths and test names). Any criterion without evidence
-      is "MISSING" and fails this node.
-
-      ## Step 1 — Load the PRD and issues
-
-      Read docs/workflow/{{ inputs.slug }}/PRD.md in full.
-      Read docs/workflow/{{ inputs.slug }}/issues.json and parse the issues array.
-
-      Extract every acceptance criterion from:
-        - Each user story in the PRD's "User Stories" section (format: "As a ... I want ...")
-        - Each issue's `acceptance_criteria` array in issues.json
-
-      Deduplicate criteria that appear in both (match by meaning, not exact text).
-
-      ## Step 2 — Find implementation evidence
-
-      For each criterion, search the codebase for:
-        - Source files that implement the described behaviour (file paths with function/class names)
-        - Test files that assert this criterion passes (test names, file:line references)
-
-      Use your knowledge of the changed files from the just-completed build to focus the search.
-
-      ## Step 3 — Build the coverage matrix
-
-      Format the matrix as a Markdown table:
-
-        | Criterion | Evidence | Status |
-        |-----------|----------|--------|
-        | <criterion text> | <file:line or test name> | ✓ COVERED / ✗ MISSING |
-
-      Rules:
-        - A criterion is COVERED if at least one test asserts it AND at least one source file
-          implements it.
-        - A criterion is MISSING if either the test or the implementation is absent.
-
-      ## Step 4 — Report and fail if any MISSING
-
-      If any rows are MISSING:
-        Print: "goals-check: FAILED — N criterion/criteria without coverage."
-        List the missing criteria.
-        The workflow will return control to `verification` after the report step.
-
-      If all criteria are COVERED:
-        Print: "goals-check: PASSED — all acceptance criteria covered. ✓"
-
-      Store the matrix as `{{ matrix }}` for use in the report node.
-
-  - id: report
-    name: Report — Consolidate Build Outcomes
-    type: prompt
-    depends_on: [goals-check]
-    prompt: |
-      You are running the unic-archon-dlc build workflow — report node.
-
-      Goal: write docs/workflow/{{ inputs.slug }}/report.md consolidating all build outcomes.
-
-      ## Required sections (exactly five)
-
-      ### 1. What Was Built
-      A high-level summary (3-5 bullets) of the issues that were implemented in this build cycle.
-      Reference each issue id and title.
-
-      ### 2. Goals-Check Coverage Matrix
-      Paste the coverage matrix produced by the goals-check node verbatim.
-
-      ### 3. Test Outcomes
-      - Pass/fail counts from the test run.
-      - Coverage numbers if available.
-      - Any flaky or skipped tests.
-
-      ### 4. Decisions Made
-      Bullet list of technical decisions made during implementation that should be recorded.
-      For each decision, propose an ADR filename (docs/adr/NNNN-<slug>.md) if the decision
-      is significant enough to warrant one. Write the ADR inline for review.
-
-      ### 5. Tech Debt Flagged
-      Bullet list of items deferred during this build (stub patterns that were accepted,
-      known limitations, shortcuts taken under time pressure). These items feed into
-      the cleanup workflow (slice 13).
-
-      ## Output
-
-      Write the report to docs/workflow/{{ inputs.slug }}/report.md.
-      Print: "report written to docs/workflow/{{ inputs.slug }}/report.md"
-
-      If goals-check returned any MISSING criteria, include a note in the "What Was Built"
-      section: "⚠ goals-check found N uncovered criteria — see matrix below."
-
-  - id: build-pr-gate
-    name: Build PR Gate — Human Review
-    type: interactive
-    fresh_context: true
-    depends_on: [report]
-    prompt: |
-      You are running the unic-archon-dlc build workflow — build-pr-gate node.
-
-      The implementation, goals-check matrix, and report are ready for human review.
-
-      Actions:
-      1. Stage all changed source and test files plus the report:
-         - All files changed during the build (git status --short)
-         - docs/workflow/{{ inputs.slug }}/report.md
-         - Any ADR files proposed in the report (docs/adr/NNNN-*.md that are new)
-      2. Open a PR targeting the develop branch with:
-         - Title: "build({{ inputs.slug }}): implementation"
-         - Body:
-           ## Summary
-           - TDD implementation for `{{ inputs.slug }}` session
-           - Goals-check matrix: all criteria covered (or: N criteria missing — see report)
-           - report.md attached
-
-           ## Review Checklist
-           - [ ] All acceptance criteria have implementation evidence
-           - [ ] No TODO / FIXME stubs left in implementation code
-           - [ ] Test coverage meets configured threshold
-           - [ ] Tech debt section in report.md is accurate
-           - [ ] Proposed ADRs (if any) are ready to record
-      3. Pause and wait for human review.
-         - If the PR is **approved** and merged:
-           Print: "Build PR gate passed."
-           Exit.
-         - If the PR is **rejected** or changes are requested:
-           Print: "Build PR gate: changes requested. Returning to verification."
-           Return control to the verification node for another pass.
-           Do NOT restart the full build (only re-verify and re-report).
diff --git a/.archon/workflows/unic-dlc-cleanup.yaml b/.archon/workflows/unic-dlc-cleanup.yaml
deleted file mode 100644
index 7cbc946e..00000000
--- a/.archon/workflows/unic-dlc-cleanup.yaml
+++ /dev/null
@@ -1,158 +0,0 @@
-name: unic-dlc-cleanup
-description: >
-  Post-merge cleanup: architecture review, ADR consolidation, then triage rerun.
-  Catches technical and intent drift, locks architectural decisions, and refreshes
-  project state via the shared triage workflow.
-
-inputs:
-  slug:
-    description: Planning session identifier — matches the slug from the completed build cycle.
-    required: true
-
-nodes:
-  - id: arch-review
-    name: Architecture Review — Drift Detection
-    type: prompt
-    depends_on: []
-    prompt: |
-      You are running the unic-archon-dlc cleanup workflow — arch-review node.
-
-      Goal: compare what was intended (PRD) against what was shipped (report + code) and
-      surface any drift before the project moves on.
-
-      ## Step 1 — Load context
-
-      Read the following files in full:
-        - docs/workflow/{{ inputs.slug }}/PRD.md         (intent)
-        - docs/workflow/{{ inputs.slug }}/report.md      (technical outcome)
-        - docs/workflow/{{ inputs.slug }}/issues.json    (issue breakdown)
-
-      Also read the list of changed files from the build:
-        Run: git diff --name-only HEAD~1 HEAD
-        (or adapt the range if HEAD~1 is not the merge commit)
-
-      For each changed source file, read its content.
-
-      ## Step 2 — Detect technical drift
-
-      Review the shipped code against architectural best practices:
-
-        - **Too-shallow modules**: functions or classes that are mere pass-throughs with no
-          real logic (a deep module hides complexity behind a small interface — the inverse is
-          the anti-pattern here).
-        - **Tight coupling**: direct imports of internal implementation details across module
-          boundaries; callers that know about the internals of their dependencies.
-        - **Leaky abstractions**: functions that expose internal data structures, require
-          callers to know about implementation order, or have error modes that only make sense
-          if you understand the internals.
-
-      For each issue found, note: file path, line(s), problem description, suggested fix.
-
-      ## Step 3 — Detect intent drift
-
-      Compare the PRD's user stories and acceptance criteria against the implementation:
-
-        - Delivered behaviour that diverges from what the PRD describes (not the same as tech
-          debt — this is wrong behaviour, not merely imperfect code).
-        - Acceptance criteria from the PRD that were silently dropped or narrowed during build.
-        - Features added during build that were not in the PRD (scope creep).
-
-      For each issue found, note: PRD section referenced, what was described vs what was
-      delivered, recommended action (fix now / create follow-up issue / accept as ADR).
-
-      ## Step 4 — Identify deepening opportunities
-
-      List at least one module that could be deepened to hide more complexity behind its
-      current interface — or explicitly state "No deepening opportunities identified."
-
-      ## Step 5 — Write arch-review.md
-
-      Write docs/workflow/{{ inputs.slug }}/arch-review.md with the following sections:
-
-        ## Architecture Review — {{ inputs.slug }}
-
-        ### Technical Drift
-        <findings or "No technical drift detected.">
-
-        ### Intent Drift
-        <findings or "No intent drift detected.">
-
-        ### Deepening Opportunities
-        <at least one suggestion, or "None identified.">
-
-        ### Summary
-        CLEAN | ISSUES FOUND (with count)
-
-      Print: "arch-review written to docs/workflow/{{ inputs.slug }}/arch-review.md"
-
-  - id: adr-consolidation
-    name: ADR Consolidation — Per-ADR Approval Gate
-    type: interactive
-    fresh_context: true
-    depends_on: [arch-review]
-    prompt: |
-      You are running the unic-archon-dlc cleanup workflow — adr-consolidation node.
-
-      Goal: review every architectural decision recorded during the build cycle and get
-      explicit human approval before writing any ADR to docs/adr/.
-
-      ## Step 1 — Collect ADR candidates
-
-      Gather decisions from:
-        1. `docs/workflow/{{ inputs.slug }}/report.md` — "Decisions Made" section
-        2. `docs/workflow/{{ inputs.slug }}/arch-review.md` — any decisions surfaced during review
-           (e.g. "accept as ADR" items from intent drift findings)
-        3. Any inline ADR drafts written by the build workflow nodes
-
-      For each candidate, present it in this format:
-
-        ---
-        ADR Candidate N of M
-        Proposed file: docs/adr/NNNN-<slug>.md
-        Status: [Proposed]
-        Context: <one paragraph — what situation prompted this decision>
-        Decision: <one sentence — what was decided>
-        Consequences: <bullet list — trade-offs accepted>
-        ---
-
-        Accept (A) / Reject (R) / Edit (E)?
-
-      ## Step 2 — Gate each ADR individually
-
-      Wait for the user to respond with A, R, or E for each candidate:
-        - **A (Accept)**: write the ADR to docs/adr/NNNN-<slug>.md using the next
-          available NNNN (check existing files in docs/adr/).
-          Print: "ADR written: docs/adr/NNNN-<slug>.md"
-        - **R (Reject)**: skip this candidate.
-          Print: "ADR skipped: <title>"
-        - **E (Edit)**: show the ADR draft again and allow the user to revise the
-          Context, Decision, or Consequences fields. Re-present for A/R after edits.
-
-      ## Step 3 — Summary
-
-      After all candidates are processed, print:
-
-        adr-consolidation complete.
-        Accepted: N | Rejected: M | Edited then accepted: K
-        Files written: (list of docs/adr/NNNN-*.md paths, or "none")
-
-  - id: run-triage
-    name: Run Triage — Refresh Project State
-    type: bash
-    runtime: bun
-    depends_on: [adr-consolidation]
-    script: |
-      #!/usr/bin/env node
-      // Reuse the shared triage workflow — no duplicate triage logic in cleanup.
-      // triage produces HANDOFF.md and updates ROADMAP.md exactly once per run.
-      import { execFileSync } from 'node:child_process'
-
-      try {
-        execFileSync('archon', ['workflow', 'run', 'unic-dlc-triage'], {
-          stdio: 'inherit',
-          env: { ...process.env },
-        })
-      } catch (err) {
-        console.error('run-triage: archon workflow run failed:', err.message)
-        process.exit(1)
-      }
diff --git a/.archon/workflows/unic-dlc-explore.yaml b/.archon/workflows/unic-dlc-explore.yaml
deleted file mode 100644
index a112c5dd..00000000
--- a/.archon/workflows/unic-dlc-explore.yaml
+++ /dev/null
@@ -1,210 +0,0 @@
-name: unic-dlc-explore
-description: Parallel research across four dimensions, then synthesize findings into docs/workflow/<slug>/findings.md.
-
-inputs:
-  slug:
-    description: Short identifier for this exploration (used as the findings directory name under docs/workflow/).
-    required: true
-
-nodes:
-  - id: research-stack
-    name: Research Stack
-    type: prompt
-    depends_on: []
-    prompt: |
-      You are running the unic-archon-dlc explore workflow — research-stack node.
-
-      Goal: understand the technology stack of this project.
-
-      1. Read package.json (root and any workspace members listed in pnpm-workspace.yaml).
-      2. Note the runtime, package manager, module system, and key devDependencies.
-      3. Check .nvmrc or .node-version for the pinned Node.js version.
-      4. Look for any framework, test runner, linter, or build tool references.
-      5. Output a concise Markdown summary under the heading "## Stack Findings" covering:
-         - Runtime version
-         - Package manager
-         - Module system (CJS/ESM)
-         - Key frameworks / libraries
-         - Toolchain (lint, format, type-check, test)
-
-  - id: research-features
-    name: Research Features
-    type: prompt
-    depends_on: []
-    prompt: |
-      You are running the unic-archon-dlc explore workflow — research-features node.
-
-      Goal: identify the key features and capabilities of this project.
-
-      1. Read README.md (if present) for a high-level feature list.
-      2. Scan docs/plans/ and docs/issues/ for feature specs and issue slugs.
-      3. Inspect any CHANGELOG.md files for shipped feature entries.
-      4. Look at exported function names in lib/*.mjs to infer capabilities.
-      5. Output a concise Markdown summary under the heading "## Features Findings" covering:
-         - Core capabilities already shipped
-         - In-progress or planned features (from specs/issues)
-         - Any notable user-facing commands or workflows
-
-  - id: research-architecture
-    name: Research Architecture
-    type: prompt
-    depends_on: []
-    prompt: |
-      You are running the unic-archon-dlc explore workflow — research-architecture node.
-
-      Goal: understand the structural and architectural decisions of this project.
-
-      1. Read CONTEXT.md (if present) for the domain model and layering decisions.
-      2. Read docs/adr/ entries (newest five by filename) for recorded decisions.
-      3. Examine the directory tree: lib/, test/, hooks/, .archon/, and any packages/.
-      4. Identify patterns: pure functions vs. stateful modules, DAG/workflow orchestration, plugin conventions.
-      5. Note any cross-platform constraints (Windows, macOS, Linux) visible in the code.
-      6. Output a concise Markdown summary under the heading "## Architecture Findings" covering:
-         - Directory structure and module responsibilities
-         - Key design patterns and conventions
-         - Recorded decisions from ADRs
-         - Cross-platform or portability constraints
-
-  - id: research-pitfalls
-    name: Research Pitfalls
-    type: prompt
-    depends_on: []
-    prompt: |
-      You are running the unic-archon-dlc explore workflow — research-pitfalls node.
-
-      Goal: surface known pitfalls, edge cases, and areas of technical debt.
-
-      1. Search for TODO, FIXME, HACK, and XXX comments across all source files.
-      2. Look for error-handling gaps: try/catch blocks that swallow errors, unhandled promise rejections.
-      3. Check CI configuration (.github/workflows/ or .gitlab-ci.yml) for flaky or skipped jobs.
-      4. Inspect test coverage: are there lib modules with no corresponding test file?
-      5. Read the most recent HANDOFF.md (if present) for documented blockers.
-      6. Output a concise Markdown summary under the heading "## Pitfalls Findings" covering:
-         - Known bugs or TODOs in the code
-         - Untested modules or coverage gaps
-         - CI issues or flaky behaviours
-         - Blockers from the latest HANDOFF.md
-
-  - id: synthesize
-    name: Synthesize Findings
-    type: prompt
-    depends_on: [research-stack, research-features, research-architecture, research-pitfalls]
-    prompt: |
-      You are running the unic-archon-dlc explore workflow — synthesize node.
-
-      You have four research outputs from the parallel nodes:
-        - research-stack    → "## Stack Findings"
-        - research-features → "## Features Findings"
-        - research-architecture → "## Architecture Findings"
-        - research-pitfalls → "## Pitfalls Findings"
-
-      Additionally:
-        - The user's stated intent for this exploration is captured in the `slug` workflow input.
-        - Read CONTEXT.md at the project root if it exists — it contains the canonical domain vocabulary.
-        - If this is a monorepo, also read CONTEXT-MAP.md at the repo root.
-
-      Your job:
-      1. Call initFindingsDir(projectDir, slug) to create docs/workflow/<slug>/ (idempotent).
-      2. Call writeFindingsMd(findingsDir, { stack, features, architecture, pitfalls, brief }) where:
-         - `stack`, `features`, `architecture`, `pitfalls` are the respective findings summaries
-           (strip the "## … Findings" heading and keep only the body text).
-         - `brief` is a new 3-5 sentence "Integrated Brief" that synthesises all four dimensions
-           into a single coherent narrative, highlighting the most important insight from each,
-           surfacing any cross-cutting concerns, and recommending the single highest-impact next step.
-      3. Print: "Explore complete. Findings written to docs/workflow/<slug>/findings.md"
-
-  - id: prototype
-    name: Prototype Experiments
-    type: prompt
-    depends_on: [synthesize]
-    prompt: |
-      You are running the unic-archon-dlc explore workflow — prototype node.
-
-      Goal: design and evaluate one or more experiments that test the key unknowns
-      identified in the findings, then record a verdict for each.
-
-      Inputs available:
-        - `slug` workflow input (the exploration identifier)
-        - docs/workflow/<slug>/findings.md (written by the synthesize node)
-
-      Steps:
-      1. Read docs/workflow/<slug>/findings.md.
-      2. From the Integrated Brief and Pitfalls section identify 1-3 concrete unknowns
-         worth spiking. For each unknown, design a minimal experiment:
-           - Give it a short descriptive title.
-           - Describe what you would build or measure.
-           - Reason through what outcome is most likely given the existing evidence.
-           - Assign exactly ONE verdict: VALIDATED, INVALIDATED, or PARTIAL.
-             · VALIDATED  — the approach is confirmed viable; evidence is sufficient.
-             · INVALIDATED — the approach is ruled out; a blocker was found.
-             · PARTIAL    — the approach shows promise but requires follow-up work.
-           - Write 2-4 sentences of supporting evidence or reasoning.
-      3. Call appendSpikeVerdicts(findingsDir, verdicts) from lib/spike-verdicts.mjs,
-         passing an array of { title, verdict, notes } objects.
-         This appends a "## Spike verdicts" section to findings.md.
-      4. Print: "Prototype complete. <N> verdict(s) written to docs/workflow/<slug>/findings.md"
-
-  - id: code-preserve-gate
-    name: Spike Branch Gate
-    type: interactive
-    fresh_context: true
-    depends_on: [prototype]
-    prompt: |
-      You are running the unic-archon-dlc explore workflow — code-preserve-gate node.
-
-      Goal: decide whether to preserve any spike code on a dedicated branch.
-
-      Ask the user exactly this question:
-        "Should I preserve this spike code on a branch? (yes/no)"
-
-      If the user answers YES (or y):
-        1. Derive a branch name: spike/<slug>  (e.g. spike/auth-refresh).
-        2. Run: git checkout -b spike/<slug>
-        3. Stage and commit any unstaged files related to this spike:
-             git add -A
-             git commit -m "spike(<slug>): preserve prototype code from explore workflow"
-        4. Print: "Spike code committed on branch spike/<slug>."
-
-      If the user answers NO (or n):
-        1. Leave the worktree unchanged — do NOT stage or commit anything.
-        2. Print: "Spike code discarded. Worktree left clean."
-
-  - id: create-spike-ticket
-    name: Create Spike Ticket
-    type: prompt
-    depends_on: [code-preserve-gate]
-    prompt: |
-      You are running the unic-archon-dlc explore workflow — create-spike-ticket node.
-
-      Goal: create (or update) a spike ticket in the configured tracker.
-
-      Inputs available:
-        - `slug` workflow input
-        - docs/workflow/<slug>/findings.md (contains the ## Spike verdicts section)
-
-      Steps:
-      1. Read docs/workflow/<slug>/findings.md.
-      2. Call parseSpikeVerdicts(content) from lib/spike-verdicts.mjs to extract verdicts.
-      3. Build a one-line verdict summary, e.g.:
-           "1 VALIDATED, 1 INVALIDATED, 1 PARTIAL"
-      4. Load the tracker configuration with loadConfig(projectDir) from lib/config-loader.mjs.
-         Use config.tracker (defaults to 'github' if absent).
-      5. Load labels with getDefaultLabels(tracker) from lib/labels-config.mjs.
-      6. Check whether a spike ticket for this slug already exists:
-           - GitHub:         gh issue list --label spike --search "<slug>" --json number,title
-           - local-markdown: check for docs/issues/<slug>-spike/index.md
-           - Other trackers: search by title containing slug.
-      7a. If NO existing ticket:
-           Call buildCreateCommand(tracker, title, 'spike', 'p2', labels) where
-           title = "Spike: <slug> — <one-line verdict summary>".
-           The body should include:
-             - Link to docs/workflow/<slug>/findings.md
-             - The full ## Spike verdicts section text
-           Execute or print the generated command.
-      7b. If ticket EXISTS:
-           Call buildUpdateCommand(tracker, issueId, 'needs-triage', labels)
-           and additionally update the body to append the new verdict summary.
-           Execute or print the generated command.
-      8. Print one of:
-           "Spike ticket created: <title>"
-           "Spike ticket updated: <issueId>"
diff --git a/.archon/workflows/unic-dlc-plan.yaml b/.archon/workflows/unic-dlc-plan.yaml
deleted file mode 100644
index 5c79b155..00000000
--- a/.archon/workflows/unic-dlc-plan.yaml
+++ /dev/null
@@ -1,421 +0,0 @@
-name: unic-dlc-plan
-description: >
-  Adversarial spec interview → PRD synthesis → human PR gate.
-  Produces docs/workflow/<slug>/PRD.md and optional ADR entries.
-
-inputs:
-  slug:
-    description: Short identifier for this planning session (used as the workflow directory name under docs/workflow/).
-    required: true
-
-nodes:
-  - id: load-context
-    name: Load Context
-    type: prompt
-    depends_on: []
-    prompt: |
-      You are running the unic-archon-dlc plan workflow — load-context node.
-
-      Goal: build a rich shared context before the adversarial interview begins.
-
-      1. Read CONTEXT.md at the project root if it exists. Note the domain vocabulary, key entities, and any established conventions.
-      2. Read CONTEXT-MAP.md at the repo root if it exists (present in monorepos). Note which sub-project this workflow targets.
-      3. Read all ADR files in docs/adr/ (sorted by filename). For each, note the decision title and outcome.
-      4. If docs/workflow/{{ inputs.slug }}/findings.md exists, read it. Note the Integrated Brief and any surfaced pitfalls.
-      5. Output a structured context summary with the following headings:
-         ## Domain Model
-         (key entities and vocabulary from CONTEXT.md)
-         ## Established Decisions
-         (list of ADRs: filename → one-line summary)
-         ## Prior Research
-         (Integrated Brief from findings.md, or "No findings.md for this slug." if absent)
-
-  - id: specs
-    name: Adversarial Spec Interview
-    type: loop
-    depends_on: [load-context]
-    prompt: |
-      You are running the unic-archon-dlc plan workflow — specs (adversarial interview) node.
-
-      Context already loaded in load-context:
-        - Domain vocabulary and entities
-        - Established ADR decisions
-        - Prior research findings (if any)
-
-      Discuss mode: {{ workflow.discuss_mode | default('interview') }}
-        - "interview"    → ask one open-ended question at a time; probe deeply; challenge assumptions
-        - "assumptions"  → surface all implicit assumptions upfront, then confirm or refute each
-
-      Interview guidelines:
-      1. If discuss_mode is "assumptions": enumerate every assumption you can identify about the
-         problem space, proposed solution, constraints, and acceptance criteria before asking questions.
-         For each assumption, ask the user to confirm, refute, or refine it.
-         If discuss_mode is "interview": ask one focused, adversarial question at a time.
-         Do not ask multiple questions in a single turn.
-      2. For every non-obvious architectural or process decision that emerges, propose an ADR entry:
-         - Suggest a filename following the pattern docs/adr/NNNN-<short-slug>.md
-         - Draft the ADR inline (Status, Context, Decision, Consequences)
-         - Write it live to docs/adr/NNNN-<short-slug>.md if the user confirms
-         - Use the next available NNNN by checking existing files in docs/adr/
-      3. Continue until the user signals they are done (e.g. "done", "that's enough", "proceed").
-      4. Before exiting, produce a structured interview transcript summary:
-         ## Interview Summary
-         (3-5 bullet points capturing the key decisions and constraints surfaced)
-         ## ADRs Produced
-         (list of any ADR files written during this session, or "None.")
-
-  - id: to-prd
-    name: Synthesise PRD
-    type: prompt
-    depends_on: [specs]
-    prompt: |
-      You are running the unic-archon-dlc plan workflow — to-prd node.
-
-      You have:
-        - The context summary from load-context (domain model, ADRs, prior research)
-        - The interview transcript summary and ADRs produced from the specs node
-        - The workflow slug: {{ inputs.slug }}
-
-      Your job: synthesise all of the above into a structured PRD.
-
-      1. Call writePrd(projectDir, slug, sections) where sections has exactly these keys:
-         - problemStatement: 2-4 sentences describing the pain or gap being addressed
-         - solution: 2-4 sentences describing the proposed approach at a high level
-         - userStories: a bulleted list of "As a <role>, I want <capability>, so that <benefit>." stories (at least 3)
-         - implementationDecisions: bullet list of key technical choices; reference ADR filenames where applicable
-         - testingDecisions: bullet list of testing strategy choices (framework, coverage targets, edge cases to cover)
-         - outOfScope: bullet list of explicitly excluded items to prevent scope creep
-         - furtherNotes: any open questions, dependencies, or items to revisit after v1
-
-      2. The resulting file must be docs/workflow/{{ inputs.slug }}/PRD.md.
-      3. Print: "PRD written to docs/workflow/{{ inputs.slug }}/PRD.md"
-
-  - id: prd-gate
-    name: PRD Human Gate
-    type: interactive
-    fresh_context: true
-    depends_on: [to-prd]
-    prompt: |
-      You are running the unic-archon-dlc plan workflow — prd-gate (first human PR gate) node.
-
-      The PRD and any new ADRs are ready for human review.
-
-      Actions:
-      1. Run validatePrdSections(content) on the PRD.md content to confirm all 7 sections are present.
-         If any sections are missing, list them and offer to fix them before opening the PR.
-      2. Stage the following files for a new PR:
-         - docs/workflow/{{ inputs.slug }}/PRD.md
-         - Any ADR files written during the specs node (docs/adr/NNNN-*.md that are new or modified)
-      3. Open a PR targeting the develop branch with:
-         - Title: "plan({{ inputs.slug }}): PRD and ADRs"
-         - Body:
-           ## Summary
-           - PRD for `{{ inputs.slug }}` workflow session
-           - Lists any new or updated ADR files
-           - Includes all 7 required PRD sections
-
-           ## Review Checklist
-           - [ ] Problem Statement clearly describes the pain or gap
-           - [ ] Solution is specific and implementable
-           - [ ] User Stories cover the primary use cases
-           - [ ] Implementation Decisions reference relevant ADRs
-           - [ ] Testing Decisions are concrete and actionable
-           - [ ] Out of Scope prevents scope creep
-           - [ ] Further Notes captures open questions
-      4. Pause and wait for human review.
-         - If the PR is **approved** and merged: print "PRD gate passed. Proceeding." and exit.
-         - If the PR is **rejected** or changes are requested: print "PRD gate: changes requested. Returning to specs."
-           Then return control to the specs node so the interview can be resumed or refined.
-
-  - id: to-issues
-    name: Decompose PRD into Issues
-    type: prompt
-    depends_on: [prd-gate]
-    prompt: |
-      You are running the unic-archon-dlc plan workflow — to-issues node.
-
-      Goal: decompose the approved PRD into independently-deliverable, vertically-sliced issues and
-      publish them to the tracker in dependency order.
-
-      ## Step 1 — Read the PRD
-
-      Read docs/workflow/{{ inputs.slug }}/PRD.md in full.
-
-      ## Step 2 — Decompose into vertical slices
-
-      Produce a draft list of issues. Each issue MUST have all of the following fields:
-
-        - id          : short kebab-case identifier unique within this file (e.g. "issue-01")
-        - title       : one-line description of the deliverable
-        - type        : one of: feature | bug | spike | tech-debt | docs
-        - priority    : one of: p0 | p1 | p2 | p3
-        - blocked_by  : array of IDs in *this* file that must ship first (empty array if independent)
-        - acceptance_criteria : non-empty array of statements that can each be demonstrated independently
-        - summary     : one short paragraph describing the work
-
-      Rules for good vertical slices:
-        - Each slice delivers observable user value on its own (or unblocks a slice that does).
-        - Slices are as small as possible while still being independently deployable/demonstrable.
-        - No slice should duplicate work covered by another slice.
-        - blocked_by must form a DAG — no cycles.
-
-      ## Step 3 — Validation loop (iterate until approved)
-
-      Present the breakdown to the user as a numbered list in this format:
-        <number>. [<type>/<priority>] <title>
-           blocked_by: <comma-separated IDs, or "none">
-           summary: <summary>
-           acceptance_criteria:
-             - <criterion 1>
-             - …
-
-      Then ask: "Validate this breakdown, or tell me which issues to split, merge, or relabel."
-
-      Iterate — apply requested changes and re-present — until the user approves explicitly
-      (e.g. replies "approved", "looks good", "proceed").
-
-      ## Step 4 — Validate schema before publishing
-
-      Before publishing, call validateIssue(issue) on every issue in the list.
-      If any issue fails validation, list the errors and fix them before proceeding.
-      Call sortByDependency(issues) to obtain the publication order.
-      If a circular dependency is detected, surface it to the user and ask them to resolve it.
-
-      ## Step 5 — Publish to tracker in dependency order
-
-      Load the tracker configuration from .archon/unic-dlc.config.json (field: tracker).
-      For each issue in sorted order:
-        1. Call buildCreateCommand(tracker, issue.title, issue.type, issue.priority, labels) to generate
-           the CLI command.
-        2. Print the command.
-        3. Execute the command (or, if in dry-run mode, skip execution and print "[dry-run]").
-
-      ## Step 6 — Write issues.json
-
-      Call buildIssuesJson(issues) and write the result to docs/workflow/{{ inputs.slug }}/issues.json.
-      Print: "issues.json written to docs/workflow/{{ inputs.slug }}/issues.json"
-
-  - id: nyquist-map
-    name: Nyquist Map — Attach Test Commands
-    type: prompt
-    depends_on: [to-issues]
-    prompt: |
-      You are running the unic-archon-dlc plan workflow — nyquist-map node.
-
-      Goal: for every issue in the just-published list, decide the exact shell command (or flag as
-      planned) that will verify the issue is done. This ensures every issue is testable before
-      implementation begins.
-
-      ## Step 1 — Load issues
-
-      Read docs/workflow/{{ inputs.slug }}/issues.json and parse the issues array.
-
-      ## Step 2 — Attach test commands
-
-      For each issue, determine the most appropriate verification command:
-
-        - If a concrete, runnable test command exists (e.g. `pnpm test`, `pnpm --filter <name> test`,
-          a specific test file path, or an integration check script), set:
-            test_command: "<exact shell command>"
-
-        - If no test exists yet (e.g. the issue creates new untested functionality, or the test itself
-          is the deliverable of another issue), set:
-            test_command_planned: true
-
-      Guidelines:
-        - Prefer the most specific command that exercises only the acceptance criteria of that issue.
-        - A `test_command_planned: true` is not a failure — it signals that a test must be written as
-          part of implementing that issue.
-        - Do NOT set both test_command and test_command_planned on the same issue.
-        - If the issue's type is 'docs' or 'spike', set test_command_planned: true unless a linting
-          or build check is meaningful.
-
-      ## Step 3 — Update issues.json
-
-      Merge the test_command / test_command_planned fields into each issue object.
-      Call buildIssuesJson(updatedIssues) and overwrite docs/workflow/{{ inputs.slug }}/issues.json.
-      Print a summary table:
-
-        Issue ID     | Test command / planned
-        -------------|--------------------------------------
-        issue-01     | pnpm --filter my-plugin test
-        issue-02     | [planned]
-        …
-
-      Print: "nyquist-map complete. issues.json updated with test commands."
-
-  - id: plan-checker
-    name: Plan Checker — Validate Issue Plan
-    type: loop
-    depends_on: [nyquist-map]
-    prompt: |
-      You are running the unic-archon-dlc plan workflow — plan-checker node.
-
-      Goal: validate the issue plan across four dimensions before generating the build YAML.
-      Max 3 iterations. Escalate immediately to the human gate if the issue count does not
-      decrease between consecutive iterations (stall detection).
-
-      ## Step 1 — Load issues
-
-      Read docs/workflow/{{ inputs.slug }}/issues.json and parse the issues array.
-      Track: iteration number (start at 1), previous issue count (start at -1).
-
-      ## Step 2 — Stall detection
-
-      If iteration > 1 AND current issue count >= previous issue count:
-        Print: "plan-checker: stall detected (issue count did not decrease). Escalating to human gate."
-        Exit the loop and proceed to yaml-gen.
-
-      If iteration > 3:
-        Print: "plan-checker: max iterations reached. Escalating to human gate."
-        Exit the loop and proceed to yaml-gen.
-
-      ## Step 3 — Validate four dimensions
-
-      ### 3.1 Consistency
-        - Collect all `blocked_by` values across all issues.
-        - Check that every referenced ID exists in the issue list.
-        - Orphaned references: IDs in `blocked_by` that don't exist in the list.
-        - Check that every acceptance criterion from every PRD user story is covered by
-          at least one issue's acceptance_criteria.
-        - Report: list of orphaned references; list of uncovered PRD criteria.
-
-      ### 3.2 Completeness
-        - For every issue, verify all mandatory fields are present and non-empty:
-          id, title, type, priority, blocked_by, acceptance_criteria, summary.
-        - acceptance_criteria must be a non-empty array.
-        - Report: list of issues with missing or empty mandatory fields.
-
-      ### 3.3 Decision coverage
-        - Read CONTEXT.md at the project root (if present). Extract trackable decisions
-          (sentences or bullet points that describe a binding technical or process choice).
-        - Read the interview transcript summary produced by the specs node (look for
-          "## Interview Summary" in the workflow session's notes or the specs node output).
-        - For each trackable decision, check whether at least one issue references or
-          addresses it (in title, summary, or acceptance_criteria).
-        - Report: list of unaddressed decisions.
-
-      ### 3.4 Nyquist compliance
-        - Check each issue for either `test_command` (string) or `test_command_planned: true`.
-        - Issues missing both fields fail this check.
-        - Report: list of issues without test coverage mapping.
-
-      ## Step 4 — Build the validation report
-
-      Produce a structured report:
-
-        ## plan-checker Report (iteration {{ loop.iteration }})
-
-        ### Consistency
-        <orphaned references or "✓ No orphaned references">
-        <uncovered PRD criteria or "✓ All PRD criteria covered">
-
-        ### Completeness
-        <missing fields per issue or "✓ All issues have required fields">
-
-        ### Decision Coverage
-        <unaddressed decisions or "✓ All trackable decisions addressed">
-
-        ### Nyquist Compliance
-        <issues missing test mapping or "✓ All issues have test_command or test_command_planned">
-
-        ### Summary
-        <overall PASS or FAIL with counts>
-
-      Write the report to docs/workflow/{{ inputs.slug }}/plan-checker-report.md
-      (overwrite on each iteration).
-
-      ## Step 5 — Act on the report
-
-      If all four dimensions PASS:
-        Print: "plan-checker: all checks passed. Proceeding to yaml-gen."
-        Exit the loop.
-
-      Otherwise:
-        Present the report to the user.
-        Ask: "Which issues should I fix? (Or type 'accept' to proceed despite failures.)"
-        If the user types 'accept':
-          Print: "plan-checker: user accepted failures. Proceeding."
-          Exit the loop.
-        Otherwise:
-          Apply the requested fixes to issues.json.
-          Increment iteration counter and loop again.
-
-  - id: yaml-gen
-    name: YAML Gen — Build Workflow Generator
-    type: bash
-    runtime: bun
-    depends_on: [plan-checker]
-    script: |
-      #!/usr/bin/env node
-      // @ts-check
-      import { readFileSync, writeFileSync, mkdirSync } from 'node:fs'
-      import { join } from 'node:path'
-      import { buildYaml } from './lib/dag-builder.mjs'
-
-      const slug = process.env.ARCHON_INPUT_SLUG
-      if (!slug) {
-        console.error('yaml-gen: ARCHON_INPUT_SLUG is not set')
-        process.exit(1)
-      }
-
-      const issuesPath = join('docs', 'workflow', slug, 'issues.json')
-      let issues
-      try {
-        issues = JSON.parse(readFileSync(issuesPath, 'utf8'))
-      } catch (err) {
-        console.error(`yaml-gen: cannot read ${issuesPath}: ${err.message}`)
-        process.exit(1)
-      }
-
-      let yaml
-      try {
-        yaml = buildYaml(slug, issues)
-      } catch (err) {
-        console.error(`yaml-gen: ${err.message}`)
-        process.exit(1)
-      }
-
-      const outDir = join('.archon', 'workflows')
-      mkdirSync(outDir, { recursive: true })
-      const outPath = join(outDir, `build-${slug}.yaml`)
-      writeFileSync(outPath, yaml)
-      console.log(`yaml-gen: build workflow written to ${outPath}`)
-
-  - id: plan-pr-gate
-    name: Plan PR Gate — Human Review
-    type: interactive
-    fresh_context: true
-    depends_on: [yaml-gen]
-    prompt: |
-      You are running the unic-archon-dlc plan workflow — plan-pr-gate (second human PR gate) node.
-
-      The issue plan and build workflow are ready for human review.
-
-      Actions:
-      1. Stage the following files for a new PR:
-         - docs/workflow/{{ inputs.slug }}/issues.json
-         - docs/workflow/{{ inputs.slug }}/plan-checker-report.md
-         - .archon/workflows/build-{{ inputs.slug }}.yaml
-      2. Open a PR targeting the develop branch with:
-         - Title: "plan({{ inputs.slug }}): issue plan and build workflow"
-         - Body:
-           ## Summary
-           - Issue plan for `{{ inputs.slug }}` ({{ issues | length }} issues)
-           - plan-checker validation report attached
-           - Auto-generated `build-{{ inputs.slug }}.yaml` Archon workflow
-
-           ## Review Checklist
-           - [ ] All issues are independently deliverable vertical slices
-           - [ ] Dependency order is correct (no orphaned blocked_by references)
-           - [ ] Every issue has a test command or is marked test_command_planned
-           - [ ] build-{{ inputs.slug }}.yaml parallel/serial structure looks correct
-           - [ ] plan-checker report shows no critical failures (or failures are intentional)
-      3. Pause and wait for human review.
-         - If the PR is **approved** and merged:
-           Print: "Plan PR gate passed. Build workflow ready at .archon/workflows/build-{{ inputs.slug }}.yaml"
-           Exit.
-         - If the PR is **rejected** or changes are requested:
-           Print: "Plan PR gate: changes requested. Returning to plan-checker for another validation pass."
-           Return control to the plan-checker node so validation can be re-run on the updated plan.
-           Do NOT return to to-issues (no full re-decomposition).
diff --git a/.archon/workflows/unic-dlc-qa.yaml b/.archon/workflows/unic-dlc-qa.yaml
deleted file mode 100644
index dcf50f18..00000000
--- a/.archon/workflows/unic-dlc-qa.yaml
+++ /dev/null
@@ -1,361 +0,0 @@
-name: unic-dlc-qa
-description: >
-  QA workflow: e2e test execution → coverage gate → UAT checklist → merge.
-  Runs after the build workflow is complete and the build PR has been approved.
-
-inputs:
-  slug:
-    description: Planning session identifier — matches the slug used in /unic-dlc-plan and /unic-dlc-build.
-    required: true
-
-nodes:
-  - id: e2e
-    name: End-to-End Tests
-    type: bash
-    runtime: bun
-    depends_on: []
-    script: |
-      #!/usr/bin/env node
-      // @ts-check
-      import { execFileSync } from 'node:child_process'
-      import { existsSync, readFileSync } from 'node:fs'
-      import { join } from 'node:path'
-
-      const projectDir = process.cwd()
-      const configPath = join(projectDir, '.archon', 'unic-dlc.config.json')
-
-      if (!existsSync(configPath)) {
-        console.error('e2e: .archon/unic-dlc.config.json not found.')
-        console.error('Run the install hook first: archon install')
-        process.exit(1)
-      }
-
-      const config = JSON.parse(readFileSync(configPath, 'utf8'))
-      const e2eCommand = config.e2e_command ?? null
-
-      if (!e2eCommand) {
-        console.error('e2e: e2e_command is not configured.')
-        console.error('')
-        console.error('To set it, run the install hook with --reconfigure:')
-        console.error('  archon install --reconfigure')
-        console.error('and provide a value for "e2e_command" (e.g. "pnpm test:e2e" or "npx playwright test").')
-        process.exit(1)
-      }
-
-      const parts = e2eCommand.trim().split(/\s+/)
-      const cmd = parts[0]
-      const args = parts.slice(1)
-
-      console.log(`e2e: running → ${e2eCommand}`)
-      console.log('')
-
-      try {
-        execFileSync(cmd, args, { cwd: projectDir, stdio: 'inherit' })
-        console.log('')
-        console.log('e2e: PASSED ✓')
-      } catch {
-        console.error('')
-        console.error('e2e: FAILED ✗')
-        process.exit(1)
-      }
-
-  - id: coverage-gate
-    name: Coverage Gate
-    type: bash
-    runtime: bun
-    depends_on: [e2e]
-    script: |
-      #!/usr/bin/env node
-      // @ts-check
-      import { execFileSync } from 'node:child_process'
-      import { existsSync, readFileSync } from 'node:fs'
-      import { join } from 'node:path'
-
-      const projectDir = process.cwd()
-      const configPath = join(projectDir, '.archon', 'unic-dlc.config.json')
-
-      let coverageThreshold = null
-      if (existsSync(configPath)) {
-        const config = JSON.parse(readFileSync(configPath, 'utf8'))
-        coverageThreshold = config.coverage_threshold ?? null
-      }
-
-      if (coverageThreshold === null) {
-        console.log('coverage-gate: no coverage_threshold configured — skipping.')
-        console.log('To enable, add "coverage_threshold": <number> to .archon/unic-dlc.config.json.')
-        process.exit(0)
-      }
-
-      console.log(`coverage-gate: threshold is ${coverageThreshold}%`)
-      console.log('coverage-gate: running test suite with coverage...')
-      console.log('')
-
-      // Run tests with coverage; capture output to parse coverage percentage
-      let coverageOutput = ''
-      let failed = false
-      try {
-        coverageOutput = execFileSync('pnpm', ['test', '--coverage'], {
-          cwd: projectDir,
-          encoding: 'utf8',
-          stdio: ['inherit', 'pipe', 'pipe'],
-        })
-        process.stdout.write(coverageOutput)
-      } catch (/** @type {any} */ err) {
-        if (err.stdout) process.stdout.write(err.stdout)
-        if (err.stderr) process.stderr.write(err.stderr)
-        coverageOutput = (err.stdout ?? '') + (err.stderr ?? '')
-        failed = true
-      }
-
-      // Attempt to extract a coverage percentage from the output.
-      // Handles common formats: "All files | 87.5 |", "Stmts: 87.5%", "87.5% statements"
-      const percentMatch =
-        coverageOutput.match(/All files\s*\|\s*([\d.]+)/) ??
-        coverageOutput.match(/Stmts\s*[:\|]\s*([\d.]+)/) ??
-        coverageOutput.match(/([\d.]+)%\s+statements/i)
-
-      if (percentMatch) {
-        const actual = parseFloat(percentMatch[1])
-        if (actual < coverageThreshold) {
-          console.error(`\ncoverage-gate: FAILED (${actual}% < threshold ${coverageThreshold}%)`)
-          process.exit(1)
-        }
-        console.log(`\ncoverage-gate: PASSED (${actual}%)`)
-      } else if (failed) {
-        // Could not parse percentage but the command failed
-        console.error(`\ncoverage-gate: FAILED (test suite exited non-zero; threshold ${coverageThreshold}%)`)
-        process.exit(1)
-      } else {
-        // Command passed but no parseable percentage — treat as passed with a warning
-        console.log(`\ncoverage-gate: PASSED (coverage % could not be parsed; threshold ${coverageThreshold}%)`)
-      }
-
-  - id: uat-gate
-    name: UAT Gate — Acceptance Checklist
-    type: interactive
-    fresh_context: true
-    depends_on: [coverage-gate]
-    prompt: |
-      You are running the unic-archon-dlc QA workflow — uat-gate node.
-
-      Goal: walk through the UAT checklist derived from the PRD's acceptance criteria alongside
-      the e2e results, then get human sign-off before the merge step proceeds.
-
-      ## Step 1 — Load artefacts
-
-      1. Read `docs/workflow/{{ inputs.slug }}/PRD.md`.
-         Extract all acceptance criteria. They are typically found in:
-           - Each "User Story" block as sub-bullet "Acceptance criteria:" lists.
-           - A top-level "## Acceptance Criteria" section if present.
-         Number each criterion sequentially: AC-1, AC-2, …
-
-      2. Check whether `docs/workflow/{{ inputs.slug }}/report.md` exists and read it if so.
-         The report contains the goals-check coverage matrix and test outcomes from the build phase.
-
-      ## Step 2 — Present the UAT checklist
-
-      Print the following header:
-
-        === UAT Checklist for {{ inputs.slug }} ===
-
-      Then for each acceptance criterion:
-
-        AC-N: <criterion text>
-          Evidence: <matching row from coverage matrix, or "not recorded">
-          [ ] Verified by human
-
-      Follow the list with:
-
-        e2e result: PASSED  (or FAILED — see e2e node output above)
-        Coverage:   PASSED  (or SKIPPED / FAILED — see coverage-gate output above)
-
-      ## Step 3 — Ask for sign-off
-
-      Ask the user:
-        "Please review each item above and confirm:
-         1. All acceptance criteria are verified (tick each [ ] mentally or note any failures).
-         2. You approve this build for merge.
-
-         Type APPROVE to continue to the merge step.
-         Type REJECT <AC-N> to flag a failing checklist item — I will return control to whoever
-         owns that item for remediation."
-
-      ## Step 4 — Act on the response
-
-      If the user types APPROVE (case-insensitive):
-        Print: "uat-gate: APPROVED. Proceeding to merge."
-
-      If the user types REJECT <AC-N> (or REJECT with any text):
-        Print: "uat-gate: REJECTED — {{ user response }}."
-        Print: "Returning control. Address the failing criterion and re-run /unic-dlc-qa {{ inputs.slug }} to retry."
-        Halt the workflow (do not proceed to the merge node).
-
-  - id: verify-pr-base
-    name: Verify PR Base Branch
-    type: bash
-    runtime: bun
-    depends_on: [uat-gate]
-    script: |
-      #!/usr/bin/env node
-      // @ts-check
-      import { readFileSync } from 'node:fs'
-      import { execFileSync } from 'node:child_process'
-
-      let config = {}
-      try {
-        config = JSON.parse(readFileSync('.archon/unic-dlc.config.json', 'utf8'))
-      } catch {
-        console.error('verify-pr-base: cannot read .archon/unic-dlc.config.json')
-        process.exit(1)
-      }
-
-      const tracker = config.tracker ?? 'github'
-      const branching = config.branching ?? 'gitflow'
-      const expectedBase = branching === 'gitflow' ? 'develop' : 'main'
-
-      if (tracker === 'github') {
-        let actualBase
-        try {
-          const out = execFileSync('gh', ['pr', 'view', '--json', 'baseRefName'], { encoding: 'utf8' })
-          actualBase = JSON.parse(out).baseRefName
-        } catch (err) {
-          console.error(`verify-pr-base: cannot query PR base — ${err.message}`)
-          process.exit(1)
-        }
-        if (actualBase !== expectedBase) {
-          console.error(
-            `verify-pr-base: PR targets "${actualBase}" but expected "${expectedBase}" (branching: ${branching}).`,
-          )
-          console.error('  Retarget the PR before merging.')
-          process.exit(1)
-        }
-        console.log(`verify-pr-base: PR base is "${actualBase}" ✓`)
-      } else if (tracker === 'ado') {
-        let actualBase
-        try {
-          const out = execFileSync('az', ['repos', 'pr', 'show', '--output', 'json'], { encoding: 'utf8' })
-          actualBase = JSON.parse(out).targetRefName?.replace('refs/heads/', '')
-        } catch (err) {
-          console.error(`verify-pr-base: cannot query ADO PR — ${err.message}`)
-          process.exit(1)
-        }
-        if (actualBase !== expectedBase) {
-          console.error(
-            `verify-pr-base: PR targets "${actualBase}" but expected "${expectedBase}" (branching: ${branching}).`,
-          )
-          process.exit(1)
-        }
-        console.log(`verify-pr-base: PR base is "${actualBase}" ✓`)
-      } else {
-        // Jira / local-markdown — no CLI to query PR base
-        console.log(
-          `verify-pr-base: tracker "${tracker}" does not support PR base verification. Skipping (warning only).`,
-        )
-      }
-
-  - id: merge
-    name: Merge PR
-    type: bash
-    runtime: bun
-    depends_on: [verify-pr-base]
-    script: |
-      #!/usr/bin/env node
-      // @ts-check
-      import { execFileSync } from 'node:child_process'
-      import { existsSync, readFileSync } from 'node:fs'
-      import { join } from 'node:path'
-
-      const projectDir = process.cwd()
-      const configPath = join(projectDir, '.archon', 'unic-dlc.config.json')
-
-      if (!existsSync(configPath)) {
-        console.error('merge: .archon/unic-dlc.config.json not found.')
-        process.exit(1)
-      }
-
-      const config = JSON.parse(readFileSync(configPath, 'utf8'))
-      const tracker = config.tracker ?? 'github'
-      const branching = config.branching ?? 'gitflow'
-      const prStrategy = config.pr_strategy ?? 'squash'
-      const slug = process.env.ARCHON_INPUT_SLUG ?? ''
-
-      console.log(`merge: tracker=${tracker}, branching=${branching}, pr_strategy=${prStrategy}`)
-      console.log('')
-
-      // Merge via the configured tracker
-      switch (tracker) {
-        case 'github': {
-          const mergeFlag = prStrategy === 'merge' ? '--merge' : '--squash'
-          console.log(`merge: running gh pr merge ${mergeFlag}`)
-          try {
-            execFileSync('gh', ['pr', 'merge', mergeFlag], { cwd: projectDir, stdio: 'inherit' })
-            console.log('merge: PR merged successfully via GitHub CLI.')
-          } catch {
-            console.error('merge: gh pr merge failed. Ensure you are on a feature branch with an open PR.')
-            process.exit(1)
-          }
-          break
-        }
-
-        case 'ado': {
-          console.log('merge: running az repos pr update --status completed')
-          try {
-            execFileSync('az', ['repos', 'pr', 'update', '--status', 'completed'], {
-              cwd: projectDir,
-              stdio: 'inherit',
-            })
-            console.log('merge: PR completed successfully via Azure DevOps CLI.')
-          } catch {
-            console.error('merge: az repos pr update failed. Ensure the Azure DevOps PR is open and the CLI is authenticated.')
-            process.exit(1)
-          }
-          break
-        }
-
-        case 'jira':
-          console.log('Merge via Jira: transition the linked PR to Done manually.')
-          console.log('  1. Open the Jira issue linked to this feature.')
-          console.log('  2. Transition it to "Done" (or "In Review → Done" depending on your board).')
-          console.log('  3. Merge the corresponding PR in your VCS provider.')
-          break
-
-        case 'local-markdown':
-          console.log('Merge: update Status in issues to resolved.')
-          console.log(`  Edit docs/issues/<slug>/index.md and set: Status: resolved`)
-          console.log('  Then commit and push the change manually.')
-          break
-
-        default:
-          console.log(`merge: unknown tracker "${tracker}". Merge the PR manually in your tracker.`)
-          break
-      }
-
-      // Delete feature branch after merge when using Gitflow
-      if (branching === 'gitflow' && (tracker === 'github' || tracker === 'ado')) {
-        console.log('')
-        console.log('merge: Gitflow — deleting feature branch...')
-        try {
-          // Determine current branch name
-          const currentBranch = execFileSync('git', ['rev-parse', '--abbrev-ref', 'HEAD'], {
-            cwd: projectDir,
-            encoding: 'utf8',
-          }).trim()
-
-          if (currentBranch.startsWith('feature/')) {
-            // Switch to develop before deleting
-            execFileSync('git', ['checkout', 'develop'], { cwd: projectDir, stdio: 'inherit' })
-            execFileSync('git', ['branch', '-d', currentBranch], { cwd: projectDir, stdio: 'inherit' })
-            console.log(`merge: feature branch "${currentBranch}" deleted. ✓`)
-          } else {
-            console.log(`merge: current branch "${currentBranch}" is not a feature branch — skipping delete.`)
-          }
-        } catch {
-          console.log('merge: could not delete feature branch automatically — delete it manually if needed.')
-        }
-      } else if (branching !== 'gitflow') {
-        console.log('')
-        console.log('merge: github-flow — leaving branch cleanup to GitHub (auto-delete on merge).')
-      }
-
-      console.log('')
-      console.log(`merge: QA workflow for "${slug}" complete. ✓`)
diff --git a/.archon/workflows/unic-dlc-review.yaml b/.archon/workflows/unic-dlc-review.yaml
deleted file mode 100644
index b085baa3..00000000
--- a/.archon/workflows/unic-dlc-review.yaml
+++ /dev/null
@@ -1,239 +0,0 @@
-name: unic-dlc-review
-description: >
-  Self-contained code review across four aspects — code quality, test coverage adequacy,
-  silent failure patterns, and type design quality. Posts (or updates) a single structured
-  comment on the current PR via the configured tracker adapter.
-  No runtime dependency on pr-review-toolkit or any other plugin.
-
-nodes:
-  - id: code-review
-    name: Code Review — Four Aspects
-    type: prompt
-    depends_on: []
-    prompt: |
-      You are running the unic-archon-dlc review workflow — code-review node.
-
-      ## Setup
-
-      1. Read `.archon/unic-dlc.config.json` to determine:
-         - `tracker` (github | ado | jira | local-markdown; default: github)
-         - `branching` strategy if present
-
-      2. Read project conventions from whichever file exists (in order):
-         - `CLAUDE.md`
-         - `AGENTS.md`
-         - `.claude/CLAUDE.md`
-         Note all style rules, naming conventions, tab/space preferences, and
-         explicit "do not" rules.
-
-      3. Identify the current open PR:
-         - github: `gh pr view --json number,title,body,headRefName`
-         - ado:    `az repos pr list --status active --output json | head -1`
-         - local-markdown: use the most recent `docs/workflow/*/report.md` as the review target
-         Store `PR_ID` (issue/PR number or identifier) and `PR_TITLE`.
-
-      4. Compute the diff to review:
-         - github / ado / local-markdown:
-           `git diff origin/$(git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null | sed 's|.*/||' || echo main)...HEAD`
-         - If the above fails, fall back to: `git diff HEAD~1...HEAD`
-         Store the result as `DIFF_TEXT`.
-
-      5. List all source files touched in the diff:
-         `git diff --name-only origin/$(git symbolic-ref --short HEAD 2>/dev/null)...HEAD 2>/dev/null || git diff --name-only HEAD~1`
-         Store as `CHANGED_FILES` (newline-separated list).
-
-      6. Read each file in `CHANGED_FILES` in full (skip deleted files).
-
-      ---
-
-      ## Aspect 1 — Code Quality
-
-      Analyse the diff and changed file contents for:
-      - **Readability**: Is each function easy to understand in isolation?
-      - **Naming**: Do variable, function, and module names communicate intent without
-        needing comments?
-      - **Function length**: Are any functions longer than ~40 lines? Could they be split?
-      - **Project-convention adherence**: Check against the rules you read from CLAUDE.md /
-        AGENTS.md. Examples include tab vs. space indentation, quote style, semicolons,
-        trailing commas, explicit returns, early returns over nested conditionals.
-
-      For each problem found, record a finding in this exact format:
-        - `file:line — [code-quality] <one-line description>`
-
-      If no problems are found, record:
-        - `No findings.`
-
-      Store all findings under the heading `### Code Quality`.
-
-      ---
-
-      ## Aspect 2 — Test Coverage Adequacy
-
-      Locate test files in `CHANGED_FILES` or in `test/`, `tests/`, `__tests__/`,
-      `*.test.*`, `*.spec.*` directories. For each changed source module, check whether:
-
-      - Tests exercise the module through its **public interface** (exported functions),
-        not internal helpers.
-      - Assertions verify **outputs and side-effects**, not internal state or call counts
-        on internal collaborators.
-      - No internal collaborators are mocked — only true external boundaries (network,
-        disk, third-party CLIs) should be mocked.
-      - Every exported function has at least one happy-path test and at least one
-        edge-case or error-path test.
-
-      For each gap found, record a finding:
-        - `file:line — [test-coverage] <one-line description>`
-
-      If no gaps are found, record:
-        - `No findings.`
-
-      Store all findings under the heading `### Test Coverage Adequacy`.
-
-      ---
-
-      ## Aspect 3 — Silent Failure Patterns
-
-      Scan the diff for patterns that swallow errors and hide bugs:
-
-      - **Empty catch blocks**: `catch { }` or `catch (e) { /* ignored */ }`
-      - **Swallowed exceptions**: `catch` that logs but does not rethrow, return a default,
-        or propagate the error to the caller.
-      - **Silent fallbacks**: `?? defaultValue` or `|| fallback` on values that should
-        never be absent — where the fallback masks a missing configuration or corrupt state.
-      - **Unhandled promise rejections**: `.then(…)` without `.catch(…)` or `await` outside
-        try/catch in async functions.
-      - **Ignored return values**: calling a function whose return value signals an error
-        or state change, then discarding it.
-
-      For each pattern found, record a finding:
-        - `file:line — [silent-failure] <one-line description>`
-
-      If no patterns are found, record:
-        - `No findings.`
-
-      Store all findings under the heading `### Silent Failure Patterns`.
-
-      ---
-
-      ## Aspect 4 — Type Design Quality
-
-      Analyse type annotations, JSDoc types, or TypeScript types introduced or changed
-      in the diff:
-
-      - **Encapsulation**: Are types narrow enough to prevent invalid usage? Or are they
-        overly broad (e.g. `string` where a union literal would be more precise)?
-      - **Invariants in types**: Do types encode business rules? E.g. a `NonEmptyArray<T>`
-        instead of `T[]` where empty is invalid.
-      - **Illegal-state-unrepresentable**: Are there mutually exclusive fields that could
-        be unified into a discriminated union? Are there optional fields that should be
-        required, or vice-versa?
-      - **JSDoc completeness** (for `.mjs` / `// @ts-check` files): Are all exported
-        function parameters and return types annotated?
-
-      For each weakness found, record a finding:
-        - `file:line — [type-design] <one-line description>`
-
-      If no weaknesses are found, record:
-        - `No findings.`
-
-      Store all findings under the heading `### Type Design Quality`.
-
-      ---
-
-      ## Compose the review comment
-
-      Assemble a Markdown comment with this exact structure:
-
-      ```
-      <!-- unic-dlc-review -->
-      ## unic-dlc-review
-
-      > PR: <PR_TITLE>
-
-      ### Code Quality
-      <findings or "No findings.">
-
-      ### Test Coverage Adequacy
-      <findings or "No findings.">
-
-      ### Silent Failure Patterns
-      <findings or "No findings.">
-
-      ### Type Design Quality
-      <findings or "No findings.">
-
-      ---
-      *Generated by unic-archon-dlc · re-run `/unic-dlc-review` to update this comment.*
-      ```
-
-      The `<!-- unic-dlc-review -->` HTML comment at the very first line is the sentinel
-      used for update detection. Do not remove or alter it.
-
-      Store the assembled Markdown as `REVIEW_BODY`.
-
-      ---
-
-      ## Post or update the comment
-
-      Search for an existing review comment on this PR:
-
-      **github:**
-      ```
-      gh pr view "$PR_ID" --json comments --jq '.comments[] | select(.body | startswith("<!-- unic-dlc-review -->")) | .databaseId'
-      ```
-      If a comment ID is found (call it `EXISTING_ID`):
-        Update: `gh api repos/{owner}/{repo}/issues/comments/$EXISTING_ID -X PATCH -f body="$REVIEW_BODY"`
-        Print:  "review: updated existing comment $EXISTING_ID on PR #$PR_ID"
-      If no comment exists:
-        Create: `gh pr comment "$PR_ID" --body "$REVIEW_BODY"`
-        Print:  "review: posted new comment on PR #$PR_ID"
-
-      **ado:**
-      Fetch threads: `az repos pr thread list --id "$PR_ID" --output json`
-      Search for a thread whose first comment starts with `<!-- unic-dlc-review -->`.
-      If found (`THREAD_ID`, `COMMENT_ID`):
-        Update: `az repos pr thread comment update --id "$PR_ID" --thread-id "$THREAD_ID" --comment-id "$COMMENT_ID" --content "$REVIEW_BODY"`
-        Print:  "review: updated existing thread $THREAD_ID on PR $PR_ID"
-      If not found:
-        Create: `az repos pr thread create --id "$PR_ID" --comment "$REVIEW_BODY"`
-        Print:  "review: posted new thread on PR $PR_ID"
-
-      **local-markdown:**
-      Look for `docs/workflow/<slug>/review-comment.md` (where slug is the most recent
-      workflow directory under docs/workflow/).
-      If it exists:
-        Overwrite the file with `REVIEW_BODY`.
-        Print: "review: updated docs/workflow/<slug>/review-comment.md"
-      If it does not exist:
-        Write `REVIEW_BODY` to `docs/workflow/<slug>/review-comment.md`.
-        Print: "review: created docs/workflow/<slug>/review-comment.md"
-
-      **jira:**
-      Search for a comment whose body starts with `<!-- unic-dlc-review -->`:
-        `jira issue comment list "$PR_ID" --output json`
-      If found (`COMMENT_ID`):
-        `jira issue comment update "$PR_ID" "$COMMENT_ID" --body "$REVIEW_BODY"`
-        Print: "review: updated existing comment $COMMENT_ID on issue $PR_ID"
-      If not found:
-        `jira issue comment add "$PR_ID" --body "$REVIEW_BODY"`
-        Print: "review: posted new comment on issue $PR_ID"
-
-      ---
-
-      ## Summary
-
-      After posting or updating, print a human-readable summary:
-
-      ```
-      unic-dlc-review complete.
-
-      Aspects reviewed: Code Quality · Test Coverage Adequacy · Silent Failure Patterns · Type Design Quality
-      PR: <PR_TITLE> (<PR_ID>)
-      Action: <created | updated> review comment
-
-      Findings:
-        Code Quality:           <N finding(s) | No findings>
-        Test Coverage Adequacy: <N finding(s) | No findings>
-        Silent Failure Patterns: <N finding(s) | No findings>
-        Type Design Quality:    <N finding(s) | No findings>
-      ```
diff --git a/.archon/workflows/unic-dlc-triage.yaml b/.archon/workflows/unic-dlc-triage.yaml
deleted file mode 100644
index 6134ee6d..00000000
--- a/.archon/workflows/unic-dlc-triage.yaml
+++ /dev/null
@@ -1,47 +0,0 @@
-name: unic-dlc-triage
-description: Read current issue states and produce a HANDOFF.md status snapshot.
-
-nodes:
-  - id: read-state
-    name: Read Issue States
-    type: prompt
-    depends_on: []
-    prompt: |
-      You are running the unic-archon-dlc triage workflow.
-
-      1. Read .archon/unic-dlc.config.json to determine the configured tracker and branching strategy.
-      2. Read docs/workflow/ROADMAP.md if it exists; note the last-updated phase.
-      3. List all issues from the configured tracker using the appropriate CLI:
-         - github: `gh issue list --json number,title,labels,state`
-         - ado:    `az boards work-item list --query "[*].{id:id,title:fields.\"System.Title\",state:fields.\"System.State\"}"`
-         - jira:   `jira issue list --output json`
-         - local-markdown: Read docs/issues/**/index.md and parse Status: lines
-      4. Group issues by their canonical state label.
-      5. Identify blockers: issues whose blocked_by references are still open.
-      6. List the five most recent ADR files in docs/adr/ (by filename order).
-      7. Determine the current lifecycle phase from ROADMAP.md or "unknown" if absent.
-      8. Output a JSON object with shape:
-         {
-           "phase": "<phase>",
-           "openIssues": { "<state>": ["<title>", ...] },
-           "blockers": ["<blocker description>", ...],
-           "recentDecisions": ["<adr-filename>", ...]
-         }
-
-  - id: produce-handoff
-    name: Produce HANDOFF.md
-    type: prompt
-    depends_on: [read-state]
-    prompt: |
-      Using the JSON snapshot from read-state:
-
-      1. Write HANDOFF.md at the repo root with exactly four sections:
-         ## Current Phase — the phase value
-         ## Open Issues by State — issues grouped by state label
-         ## Blockers — open issues whose blockers are still unresolved
-         ## Recent Decisions — ADR filenames from docs/adr/
-
-      2. Call updateRoadmap() to refresh docs/workflow/ROADMAP.md with the current phase.
-         The ROADMAP.md uses marker-delimited auto-generated regions — do not overwrite human content.
-
-      3. Print a short summary: "Triage complete. HANDOFF.md written. ROADMAP.md updated."
diff --git a/.claude/commands/archon-rollout.md b/.claude/commands/archon-rollout.md
index 80d6d4db..8c142b7c 100644
--- a/.claude/commands/archon-rollout.md
+++ b/.claude/commands/archon-rollout.md
@@ -121,7 +121,7 @@ Monitor signals: `LIMIT` (Claude usage cap tripped mid-run — external, re-run
 
 ## Standing rules (always apply)
 
-1. **Branch from `develop`, PR to `develop`.** Always pass `--branch feature/<scope>/<issue#>-<slug>` (derived in Step 1). Follow Gitflow's two-prefix model: develop-targeting work (features **and** bugs) is `feature/`; `hotfix/` is reserved for fixes branched off `main`. Never `fix/`, never target `main`. The Gitflow _topology_ is owned by `docs/agents/branching.md` (auto-generated, do not edit); the `<scope>/<issue#>-<slug>` naming _within_ the `feature/` namespace is owned by this command.
+1. **Branch from `develop`, PR to `develop`.** Always pass `--branch feature/<scope>/<issue#>-<slug>` (derived in Step 1). Follow Gitflow's two-prefix model: develop-targeting work (features **and** bugs) is `feature/`; `hotfix/` is reserved for fixes branched off `main`. Never `fix/`, never target `main`. The Gitflow _topology_ is owned by the "Git branching (Gitflow)" section of the root `AGENTS.md`; the `<scope>/<issue#>-<slug>` naming _within_ the `feature/` namespace is owned by this command.
 2. **Foundation on `develop` first** (Step 2). Never dispatch a dependent before its contract is on `develop`.
 3. **Clean-slate for `unic-pr-review`.** Issues scoped to `apps/claude-code/unic-pr-review/` share no code/prompts/fixtures/dependency with `apps/claude-code/pr-review/` (deprecated, hook-protected by `.claude/hooks/block-pr-review.mjs`). Put the clean-slate clause in those dispatch prompts verbatim. Other scopes are exempt.
 4. **`verify:changelog` merge-gate.** Guarded-file PRs need a version bump + CHANGELOG bullet or CI fails. If a rollout itself introduces/tightens this gate, merge that PR **last**.
diff --git a/.claude/skills/ask-matt b/.claude/skills/ask-matt
new file mode 120000
index 00000000..414cf8dd
--- /dev/null
+++ b/.claude/skills/ask-matt
@@ -0,0 +1 @@
+../../.agents/skills/ask-matt
\ No newline at end of file
diff --git a/.claude/skills/caveman b/.claude/skills/caveman
deleted file mode 120000
index 9016aac9..00000000
--- a/.claude/skills/caveman
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/caveman
\ No newline at end of file
diff --git a/.claude/skills/code-review b/.claude/skills/code-review
new file mode 120000
index 00000000..2d88efdf
--- /dev/null
+++ b/.claude/skills/code-review
@@ -0,0 +1 @@
+../../.agents/skills/code-review
\ No newline at end of file
diff --git a/.claude/skills/codebase-design b/.claude/skills/codebase-design
new file mode 120000
index 00000000..08b466eb
--- /dev/null
+++ b/.claude/skills/codebase-design
@@ -0,0 +1 @@
+../../.agents/skills/codebase-design
\ No newline at end of file
diff --git a/.claude/skills/diagnose b/.claude/skills/diagnose
deleted file mode 120000
index 7d4b7c9e..00000000
--- a/.claude/skills/diagnose
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/diagnose
\ No newline at end of file
diff --git a/.claude/skills/diagnosing-bugs b/.claude/skills/diagnosing-bugs
new file mode 120000
index 00000000..b2134fff
--- /dev/null
+++ b/.claude/skills/diagnosing-bugs
@@ -0,0 +1 @@
+../../.agents/skills/diagnosing-bugs
\ No newline at end of file
diff --git a/.claude/skills/domain-modeling b/.claude/skills/domain-modeling
new file mode 120000
index 00000000..e672a60c
--- /dev/null
+++ b/.claude/skills/domain-modeling
@@ -0,0 +1 @@
+../../.agents/skills/domain-modeling
\ No newline at end of file
diff --git a/.claude/skills/git-guardrails-claude-code b/.claude/skills/git-guardrails-claude-code
new file mode 120000
index 00000000..769e7013
--- /dev/null
+++ b/.claude/skills/git-guardrails-claude-code
@@ -0,0 +1 @@
+../../.agents/skills/git-guardrails-claude-code
\ No newline at end of file
diff --git a/.claude/skills/grilling b/.claude/skills/grilling
new file mode 120000
index 00000000..e7124527
--- /dev/null
+++ b/.claude/skills/grilling
@@ -0,0 +1 @@
+../../.agents/skills/grilling
\ No newline at end of file
diff --git a/.claude/skills/implement b/.claude/skills/implement
new file mode 120000
index 00000000..e429be8a
--- /dev/null
+++ b/.claude/skills/implement
@@ -0,0 +1 @@
+../../.agents/skills/implement
\ No newline at end of file
diff --git a/.claude/skills/research b/.claude/skills/research
new file mode 120000
index 00000000..7a555b65
--- /dev/null
+++ b/.claude/skills/research
@@ -0,0 +1 @@
+../../.agents/skills/research
\ No newline at end of file
diff --git a/.claude/skills/resolving-merge-conflicts b/.claude/skills/resolving-merge-conflicts
new file mode 120000
index 00000000..4d75390e
--- /dev/null
+++ b/.claude/skills/resolving-merge-conflicts
@@ -0,0 +1 @@
+../../.agents/skills/resolving-merge-conflicts
\ No newline at end of file
diff --git a/.claude/skills/teach b/.claude/skills/teach
new file mode 120000
index 00000000..83977359
--- /dev/null
+++ b/.claude/skills/teach
@@ -0,0 +1 @@
+../../.agents/skills/teach
\ No newline at end of file
diff --git a/.claude/skills/to-issues b/.claude/skills/to-issues
deleted file mode 120000
index d7287a2e..00000000
--- a/.claude/skills/to-issues
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/to-issues
\ No newline at end of file
diff --git a/.claude/skills/to-prd b/.claude/skills/to-prd
deleted file mode 120000
index 3e4d639f..00000000
--- a/.claude/skills/to-prd
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/to-prd
\ No newline at end of file
diff --git a/.claude/skills/to-questionnaire b/.claude/skills/to-questionnaire
new file mode 120000
index 00000000..ace7bf6c
--- /dev/null
+++ b/.claude/skills/to-questionnaire
@@ -0,0 +1 @@
+../../.agents/skills/to-questionnaire
\ No newline at end of file
diff --git a/.claude/skills/to-spec b/.claude/skills/to-spec
new file mode 120000
index 00000000..1fa4ba2a
--- /dev/null
+++ b/.claude/skills/to-spec
@@ -0,0 +1 @@
+../../.agents/skills/to-spec
\ No newline at end of file
diff --git a/.claude/skills/to-tickets b/.claude/skills/to-tickets
new file mode 120000
index 00000000..2cd91dd7
--- /dev/null
+++ b/.claude/skills/to-tickets
@@ -0,0 +1 @@
+../../.agents/skills/to-tickets
\ No newline at end of file
diff --git a/.claude/skills/verify-spec/SKILL.md b/.claude/skills/verify-spec/SKILL.md
index e121f3ab..03ff1e77 100644
--- a/.claude/skills/verify-spec/SKILL.md
+++ b/.claude/skills/verify-spec/SKILL.md
@@ -19,6 +19,8 @@ Verify that all acceptance criteria in a spec file are satisfied by the current
 
 ## Locating the spec file
 
+**Scope limit: this skill reads spec _files_ only.** Since upstream v1.1, `/to-spec` publishes the spec as a GitHub issue and writes no file, so a Feature specced that way has nothing here to verify. Say so plainly — "this Feature's spec is a GitHub issue, which this skill cannot read yet" — rather than reporting no match, which reads as a missing spec.
+
 Spec files live in `docs/issues/` as `<slug>/PRD.md`. Completed vertical-slice sub-tasks live under `docs/issues/<slug>/done/NN-title.md`.
 
 Search in order:
diff --git a/.claude/skills/wait-what b/.claude/skills/wait-what
new file mode 120000
index 00000000..a959f0c7
--- /dev/null
+++ b/.claude/skills/wait-what
@@ -0,0 +1 @@
+../../.agents/skills/wait-what
\ No newline at end of file
diff --git a/.claude/skills/wayfinder b/.claude/skills/wayfinder
new file mode 120000
index 00000000..05ec1ca6
--- /dev/null
+++ b/.claude/skills/wayfinder
@@ -0,0 +1 @@
+../../.agents/skills/wayfinder
\ No newline at end of file
diff --git a/.claude/skills/wizard b/.claude/skills/wizard
new file mode 120000
index 00000000..d4bc4d11
--- /dev/null
+++ b/.claude/skills/wizard
@@ -0,0 +1 @@
+../../.agents/skills/wizard
\ No newline at end of file
diff --git a/.claude/skills/write-a-skill b/.claude/skills/write-a-skill
deleted file mode 120000
index 8e09e460..00000000
--- a/.claude/skills/write-a-skill
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/write-a-skill
\ No newline at end of file
diff --git a/.claude/skills/writing-for-agents b/.claude/skills/writing-for-agents
new file mode 120000
index 00000000..90df1558
--- /dev/null
+++ b/.claude/skills/writing-for-agents
@@ -0,0 +1 @@
+../../.agents/skills/writing-for-agents
\ No newline at end of file
diff --git a/.claude/skills/zoom-out b/.claude/skills/zoom-out
deleted file mode 120000
index f2b07f6c..00000000
--- a/.claude/skills/zoom-out
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/zoom-out
\ No newline at end of file
diff --git a/AGENTS.md b/AGENTS.md
index c887a735..ced5baea 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -27,7 +27,6 @@ docs/
 ├── agents/                   # Agent skill documentation
 ├── inbox/                    # Retired idea-capture notes (historical)
 ├── issues/                   # Grilled and scoped feature issues
-├── plans/                    # Retired spec files (historical)
 ├── process/                  # Process and workflow guides
 └── research/                 # Research notes and explorations
 ```
@@ -98,6 +97,8 @@ Use package scope: `feat(auto-format): …`, `fix(pr-review): …`, `chore(relea
 
 **Never commit directly to `main` or `develop`.** Always go through a PR.
 
+PRs merge with a merge commit, never a squash — the release flow reads `develop → main` merges.
+
 Bugs are not a separate prefix: a `bug` issue that targets `develop` uses `feature/` (the prefix encodes PR topology, not change kind). Archon-dispatched branches add a scope sub-namespace: `feature/<scope>/<issue#>-<slug>`, where `<scope>` is the area label with its tier stripped (`app:unic-pr-review` → `unic-pr-review`, `repo` → `repo`). The `/archon-rollout` command owns the full derivation rule.
 
 ## Release flow
@@ -120,7 +121,9 @@ To ship a new plugin version:
 
 ## Feature-driven development
 
-New work enters through the issue tracker as Features. Use `/tdd` to implement individual issues, or `unic-dlc-build` (via `unic-archon-dlc`) once the harness is set up in this repo.
+New work enters through the issue tracker as Features. Plan with `/wayfinder` when the work is too big for one agent session, or `/grill-with-docs` when it fits in one; then `/to-spec` → `/to-tickets` → `/archon-rollout`. Use `/tdd` and `/implement` for individual issues.
+
+`unic-archon-dlc` is **not** installed here — this repo builds it, it does not run it. See [ADR-0033](docs/adr/0033-de-dogfood-unic-archon-dlc.md).
 
 ## Do not add
 
@@ -145,9 +148,9 @@ Issues live in GitHub Issues at `unic/unic-agents-plugins` (planned migration to
 
 ### Type & area labels
 
-**Type** (kind of issue): `feature`, `bug`, `spike`, `tech-debt`, `docs`, `release`. See `docs/agents/labels.md` (auto-generated by `unic-archon-dlc`; `release` is a repo-local addition in `.archon/unic-dlc.config.json`).
+**Type** (kind of issue): `feature`, `bug`, `spike`, `tech-debt`, `docs`, `release`. See `docs/agents/labels.md`, which is now the only home for the repo-local `release` type.
 
-**Area** (which app/package): `app:<plugin>` one per app, `pkg:<package>` one per workspace package, and `repo` for monorepo-wide / cross-cutting work. The area tier is a repo convention: hand-applied, owned by neither `unic-archon-dlc` nor Matt's skills, and a candidate for future archon adoption. See [`CONTEXT-MAP.md`](CONTEXT-MAP.md) and [ADR-0032](docs/adr/0032-label-taxonomy.md).
+**Area** (which app/package): `app:<plugin>` one per app, `pkg:<package>` one per workspace package, and `repo` for monorepo-wide / cross-cutting work. Hand-applied. See [`CONTEXT-MAP.md`](CONTEXT-MAP.md) and [ADR-0032](docs/adr/0032-label-taxonomy.md).
 
 ### Domain docs
 
@@ -155,12 +158,48 @@ Multi-context repo: Per-plugin `CONTEXT.md` files live under `apps/claude-code/<
 
 ## Agent skills
 
-<!-- unic-archon-dlc:begin -->
-<!-- AUTO-GENERATED by unic-archon-dlc — do not edit; re-run `/unic-archon-dlc:setup` to regenerate. -->
+Matt Pocock's skills ([`mattpocock/skills`](https://github.com/mattpocock/skills)) are the agent-skill driver for this repo, installed via `npx skills` and pinned in `skills-lock.json`. See [ADR-0033](docs/adr/0033-de-dogfood-unic-archon-dlc.md).
+
+- [issue-tracker.md](docs/agents/issue-tracker.md) — `gh` conventions, PR triage surface, wayfinding operations
+- [triage-labels.md](docs/agents/triage-labels.md) — canonical triage role → this repo's state label
+- [labels.md](docs/agents/labels.md) — four-tier label taxonomy: state, type, priority, area
+- [domain.md](docs/agents/domain.md) — multi-context layout, `CONTEXT.md` and ADR locations
+- [feature-runner.md](docs/agents/feature-runner.md) — AFK invocation of the feature runner
+
+### Who owns which files
+
+| Path                                             | Owner                        | Rule                                                                                                                                         |
+| ------------------------------------------------ | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| `.agents/skills/**`                              | Upstream `mattpocock/skills` | **Never hand-edit.** Every `npx skills add` overwrites it; edits die silently                                                                |
+| `.claude/skills/<name>` symlinks                 | `npx skills`                 | Managed. `skills remove` leaves the `.agents/skills/` source directory behind, so pair it with `git rm -r`                                   |
+| `.claude/skills/{archon,new-plugin,verify-spec}` | This repo                    | Real directories, repo-authored. `npx skills` does not manage them — never remove them while pruning vendored skills                         |
+| `skills-lock.json`                               | `npx skills`                 | Never hand-edit — the hashes are computed                                                                                                    |
+| `docs/agents/*.md`                               | This repo                    | Hand-maintained, no generator. Do **not** run `/setup-matt-pocock-skills`: it reverts `triage-labels.md` to a five-role `wontfix` vocabulary |
+
+### Upgrading
+
+Selection policy: all of `skills/engineering/` and `skills/productivity/`, `skills/misc/` by explicit justification, never `skills/in-progress/`.
+
+Two entries the policy needs to name explicitly:
+
+- **`misc/git-guardrails-claude-code`** is the one `misc/` entry installed. Justification: it is the only vendored skill that installs a repo-local safety hook, so it belongs where the repo is. Read the caveat below before wiring it up.
+- **`setup-matt-pocock-skills` stays installed but must never run.** It is the reference `docs/agents/*.md` was hand-authored from, which is why it is kept. A run reverts `docs/agents/triage-labels.md` to the five-role `wontfix` vocabulary. Four installed skills tell an agent to invoke it when a tracker or label mapping looks missing — `triage`, `wayfinder`, `to-spec`, `to-tickets`. Those files exist and are correct here, so that condition is never met: if a skill asks for them, read `docs/agents/`, do not run the setup skill.
+
+```sh
+npx skills@latest add mattpocock/skills -a claude-code -y -s <name> -s <name> …
+npx skills@latest remove -s <name> -s <name> … -a claude-code -y
+```
+
+Three traps the CLI sets:
+
+- **Target `-a claude-code`, never `-a '*'`.** The wildcard installs a second, frontmatter-rewritten copy of every skill into a top-level `agent/skills/` tree for foreign agents, which then drifts from `.agents/skills/`. `remove` rejects `-a '*'` outright.
+- **`-s` takes repeated flags, not a comma list.** `-s a,b,c` reports "no matching skills found" and exits 0.
+- **`remove` is 2-for-3.** It cleans the `.claude/skills/<name>` symlink and the lockfile entry but leaves `.agents/skills/<name>/` behind. Pair every removal with `git rm -r .agents/skills/<name>`.
+
+Upstream renames and deletes skills between releases, and nothing prunes. After upgrading, diff the installed set against the upstream tree and remove what no longer exists there.
+
+### Vendored hook caveat: `git-guardrails-claude-code` needs `jq`
+
+`.agents/skills/git-guardrails-claude-code/scripts/block-dangerous-git.sh` reads its `PreToolUse` payload with `jq` and does not check that the read worked. Without `jq` on the hook runner's `PATH` it exits 0 — which the hook protocol means as **allow** — so a `git push --force` passes while the transcript looks identical to a successful block. Its own verification step tests only the matching-command path, so installing it appears to confirm protection that is conditional on `jq`.
 
-- [issue-tracker.md](docs/agents/issue-tracker.md) — issue tracker backend, CLI, create/update conventions
-- [labels.md](docs/agents/labels.md) — three-tier label taxonomy: state, type, priority
-- [branching.md](docs/agents/branching.md) — branching strategy, branch names, PR targets
-- [domain.md](docs/agents/domain.md) — single-context vs multi-context, CONTEXT.md and ADR locations
-- [workflow.md](docs/agents/workflow.md) — seven workflow phases, artifact outputs, docs/workflow/ paths
-<!-- unic-archon-dlc:end -->
+Before wiring this hook into `.claude/settings.json`, confirm `jq` resolves for the hook runner, then test the negative path: pipe a payload in with `jq` off the `PATH` and expect a **non-zero** exit. The fix belongs upstream — `.agents/skills/**` is never hand-edited here, so a local patch dies on the next `npx skills add`.
diff --git a/CONTEXT-MAP.md b/CONTEXT-MAP.md
index 605a2cbd..b59f5fdc 100644
--- a/CONTEXT-MAP.md
+++ b/CONTEXT-MAP.md
@@ -25,13 +25,13 @@ Shared packages each map to a `pkg:` area label.
 
 ## Area labels
 
-The issue tracker carries a fourth label tier, **area**, alongside the archon-owned state / type / priority tiers documented in [`docs/agents/labels.md`](docs/agents/labels.md):
+The issue tracker carries a fourth label tier, **area**, alongside the state / type / priority tiers documented in [`docs/agents/labels.md`](docs/agents/labels.md):
 
 - `app:<plugin>`: one per plugin context above
 - `pkg:<package>`: one per workspace package above
 - `repo`: monorepo-wide / cross-cutting work that belongs to no single app or package (e.g. CI, workspace tooling, cross-plugin refactors)
 
-This tier is a repo convention: hand-applied and maintained here, not generated by `unic-archon-dlc` or by Matt's skills. See [ADR-0032](docs/adr/0032-label-taxonomy.md).
+All four tiers are repo conventions: hand-applied and maintained here, generated by nothing. State, type and priority were `unic-archon-dlc`-owned until it was de-dogfooded — see [ADR-0032](docs/adr/0032-label-taxonomy.md) and its [2026-08 amendment](docs/adr/0032-label-taxonomy.md#amendment-2026-08), plus [ADR-0033](docs/adr/0033-de-dogfood-unic-archon-dlc.md).
 
 ## Relationships
 
diff --git a/CONTEXT.md b/CONTEXT.md
index ca762a57..844016f0 100644
--- a/CONTEXT.md
+++ b/CONTEXT.md
@@ -21,11 +21,11 @@ A versioned, tagged snapshot of a single Plugin published to `main`. A per-Plugi
 _Avoid_: deploy, publish, version bump
 
 **Feature**:
-A self-contained unit of work tracked as a directory under `docs/issues/<slug>/`, containing a PRD and numbered implementation issues. The atomic input to the Feature Runner.
-_Avoid_: ticket, epic, story
+A self-contained unit of work, tracked as a spec Issue on the GitHub tracker with one child Issue per ticket. A Feature that keeps a durable markdown artefact set also has a `docs/issues/<slug>/` directory, created by hand — no skill generates one. The atomic input to the Feature Runner.
+_Avoid_: ticket (a ticket is one Issue within a Feature), epic, story
 
 **Feature Runner**:
-The skill that implements a Feature's issues end-to-end in one worktree, branch, and pull request. Backed by `unic-dlc-build`.
+Whatever implements a Feature's Issues end-to-end in one worktree, branch, and pull request. Two run here: a developer driving `/tdd` or `/implement`, and `/archon-rollout` dispatching the native `archon-fix-github-issue` workflow per Issue. Not `unic-dlc-build` — that Box ships to Consumers and does not run against this monorepo ([ADR-0033](docs/adr/0033-de-dogfood-unic-archon-dlc.md)).
 _Avoid_: issue runner, queue runner
 
 **Consumer**:
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 87d6331e..c6d7ba0b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -2,7 +2,7 @@
 
 This monorepo uses a Feature-driven development workflow. For the full lifecycle — from idea capture through grilling, PRD, issues, execution, and QA — see **[`docs/process/development-workflow.md`](docs/process/development-workflow.md)**.
 
-New features and fixes are tracked as Features in the issue tracker under `docs/issues/<slug>/`. Implementation is done manually using `/tdd` for individual issues; the **Feature Runner** (`unic-dlc-build`, shipped by `unic-archon-dlc`) is the long-term AFK runner once it is wired into this repo (see [ADR-0009](apps/claude-code/unic-archon-dlc/docs/adr/0009-retire-ralph-adopt-archon-runner.md)).
+New features and fixes are tracked as Features in the GitHub issue tracker; a Feature that keeps a durable file set also gets a `docs/issues/<slug>/` directory. Implementation runs either by hand with `/tdd` or `/implement` per issue, or AFK via `/archon-rollout`, which dispatches the native `archon-fix-github-issue` workflow per issue and respects the `## Blocked by` tree.
 
 ## Cross-cutting standards
 
@@ -73,9 +73,9 @@ pnpm install
 All work enters through the issue tracker as a Feature. The recommended flow:
 
 1. Capture the idea — open a GitHub Issue directly, or run `/triage` to walk it through the state machine.
-2. Grill the design with `/grill-me` or `/grill-with-docs` until the problem and solution are clear.
-3. Create a PRD and issues with `/to-prd` → `/to-issues`.
-4. Implement each issue manually with `/tdd`. (AFK execution via `unic-dlc-build` will replace this step once the harness is wired in — see [ADR-0009](apps/claude-code/unic-archon-dlc/docs/adr/0009-retire-ralph-adopt-archon-runner.md) and [ADR-0010](apps/claude-code/unic-archon-dlc/docs/adr/0010-retire-implement-feature-skill.md).)
+2. Chart the work. If it is too big for one agent session, run `/wayfinder`: it maps the open decisions as a `wayfinder:map` issue with child tickets and resolves them one at a time. If it fits in one session, grill it with `/grill-me` or `/grill-with-docs` instead.
+3. Create a spec and tickets with `/to-spec` → `/to-tickets`.
+4. Implement each issue with `/tdd` or `/implement`, or dispatch a chain of `ready-for-agent` issues with `/archon-rollout`.
 5. Open a PR targeting `develop`.
 
 See [`docs/process/development-workflow.md`](docs/process/development-workflow.md) for the full 8-phase lifecycle.
diff --git a/ONBOARDING.md b/ONBOARDING.md
index 77670356..66a79a89 100644
--- a/ONBOARDING.md
+++ b/ONBOARDING.md
@@ -17,13 +17,14 @@ Top Skills & Commands:
 - `/grill-with-docs` ████████████████████ 22x/month
 - `/triage` ██████████████░░░░░░ 15x/month
 - `/archon` ████████████░░░░░░░░ 13x/month
-- `/to-issues` ████████░░░░░░░░░░░░ 9x/month
+- `/to-tickets` ████████░░░░░░░░░░░░ 9x/month
 - `/tdd` ██████░░░░░░░░░░░░░░ 7x/month
 - `/plugin-dev:skill-development` █████░░░░░░░░░░░░░░░ 6x/month
 - `/skills` █████░░░░░░░░░░░░░░░ 6x/month
 - `/archon-rollout` ████░░░░░░░░░░░░░░░░ 5x/month
-- `/to-prd` ████░░░░░░░░░░░░░░░░ 5x/month
-- `/zoom-out` ████░░░░░░░░░░░░░░░░ 5x/month
+- `/to-spec` ████░░░░░░░░░░░░░░░░ 5x/month
+
+Counts are historical. `/to-tickets` and `/to-spec` carry the counts of `/to-issues` and `/to-prd`, which upstream renamed at v1.1.
 
 Top MCP Servers:
 
@@ -43,15 +44,16 @@ Top MCP Servers:
 
 ### Skills to Know About
 
-- [ ] /grill-with-docs — adversarial grilling of a plan against the project's domain model and ADRs, updating CONTEXT.md/ADRs inline as decisions firm up. The team's most-used skill: it stress-tests PR findings and locks designs before any code is written.
-- [ ] /triage — moves issues through the 8-state triage workflow; the default for "where do I stand" on open issues and prepping work for an AFK agent.
+- [ ] /grill-with-docs — adversarial grilling of a plan against the project's domain model and ADRs, updating CONTEXT.md/ADRs inline as decisions firm up. The team's most-used skill: it stress-tests PR findings and locks designs before any code is written. At upstream v1.1 it thinned to a composition of `/grilling` + `/domain-modeling`, and hands the bigger jobs to `/wayfinder`.
+- [ ] /wayfinder — the other half of that split, and where upstream moved the planning weight. Charts work too big for one agent session as a `wayfinder:map` issue with child decision tickets, blocked by GitHub's native issue dependencies, and works the frontier one ticket at a time. Reach for it when `/grill-with-docs` would run out of context.
+- [ ] /triage — moves issues through the 8-state triage workflow; the default for "where do I stand" on open issues and the on-ramp for raw work. It is no longer a gate after `/to-tickets` — that approval happens inside the skill.
 - [ ] /archon — runs AI workflows in isolated git worktrees for parallel development; the basis of the team's custom delivery harness.
 - [ ] /archon-rollout — dispatches `archon-fix-github-issue` per issue respecting the dependency tree, with standing guardrails and a deduped monitor; the team's way of shipping a chain of ready-for-agent issues.
-- [ ] /to-issues — breaks a plan or PRD into independently-grabbable issues using tracer-bullet vertical slices.
-- [ ] /to-prd — turns the current conversation into a PRD and publishes it to the issue tracker.
+- [ ] /to-tickets — breaks a spec into independently-grabbable issues using tracer-bullet vertical slices. Replaced `/to-issues` at upstream v1.1.
+- [ ] /to-spec — turns the current conversation into a spec and publishes it to the issue tracker. Replaced `/to-prd` at upstream v1.1.
 - [ ] /tdd — test-first red-green-refactor loop for building features and fixing bugs.
+- [ ] /implement — takes a ticket from spec to working code.
 - [ ] /plugin-dev:skill-development — guidance for authoring and improving Claude Code skills.
-- [ ] /zoom-out — step back and orient on a tangle of changes or untracked files.
 - [ ] /unic-pr-review:review-pr — multi-agent Azure DevOps PR review (intent checking, Confidence-scored Findings, interactive Approval Loop); the v2 successor to the deprecated `pr-review` plugin.
 - [ ] /unic-spec-review:review-spec — adversarial eleven-agent review of Confluence web specs (plus Figma and live-system sources), posting selected Findings back as Confluence comments.
 
@@ -61,7 +63,7 @@ Top MCP Servers:
 - **Run the verification loop before pushing.** `pnpm ci:check` (not just `pnpm format` — Biome's import sorting is not auto-fixed by `format`), then `pnpm test` and `pnpm typecheck`. CI runs all three OSes × Node 22/24, so check cross-platform assumptions (use `node:path`/`node:fs`, not shell commands).
 - **Versioning is scripted.** Bump with `pnpm --filter <plugin> bump <patch|minor|major>` — never hand-edit `marketplace.json`. CHANGELOG headers must be `## [X.Y.Z] — YYYY-MM-DD`, and `verify:changelog` gates any PR that touches guarded files (commands, scripts, `plugin.json`, plugin `README.md`).
 - **Never create or delete `LICENSE` files** — the maintainer manages those by hand in every package.
-- **Spec-first delivery.** Work flows `/grill-with-docs` → `/to-prd` → `/to-issues` → `/archon-rollout`. Only `ready-for-agent` issues with locked acceptance criteria get dispatched to an agent.
+- **Spec-first delivery.** Work flows `/wayfinder` (or `/grill-with-docs` when it fits in one session) → `/to-spec` → `/to-tickets` → `/archon-rollout`. `/to-tickets` publishes `ready-for-agent` tickets only after you approve its breakdown in-session — that approval is the only gate before an agent picks the work up, so read the acceptance criteria there. `/to-spec` labels the spec issue the same way, and that one is not implementable: check an Issue has `## What to build` before dispatching it.
 - **Trust CI on GitHub, not an agent's self-report.** When an Archon run reports "all green / mergeable," confirm with `gh pr checks <n>` before merging — the run summary and its exit code can both mislead.
 
 ## Get Started
diff --git a/README.md b/README.md
index 6f3980d1..7ab8cdd1 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ Then install individual plugins:
 
 ## Development
 
-**Prerequisites:** Node.js ≥ 22 (see `.nvmrc` for the recommended version), pnpm ≥ 10, Claude Code CLI (for Ralph).
+**Prerequisites:** Node.js ≥ 22 (see `.nvmrc` for the recommended version), pnpm ≥ 10.
 
 ```sh
 pnpm install                           # install all workspace deps
@@ -56,7 +56,7 @@ packages/
 └── release-tools/        # @unic/release-tools — bump/tag/verify scripts
 docs/
 ├── adr/                  # Architectural Decision Records
-├── agents/               # Agent skill documentation (issue-tracker, labels, branching, domain, workflow)
+├── agents/               # Agent skill documentation (indexed in AGENTS.md § Agent skills)
 ├── inbox/                # Retired idea-capture notes (historical)
 ├── issues/               # Grilled and scoped feature issues
 ├── process/              # Process and workflow guides
diff --git a/apps/claude-code/unic-archon-dlc/AGENTS.md b/apps/claude-code/unic-archon-dlc/AGENTS.md
index 8efc47aa..c28c772d 100644
--- a/apps/claude-code/unic-archon-dlc/AGENTS.md
+++ b/apps/claude-code/unic-archon-dlc/AGENTS.md
@@ -69,7 +69,7 @@ Load-bearing invariants. These either originate in a Plugin ADR or are policy de
 - **`/improve-architecture` is a skill that composes Matt's method and owns ADR superseding.** The off-line, on-demand arch-health box is a **command/skill** (its core is a design grilling loop that needs the live conversation — [ADR-0017](docs/adr/0017-container-follows-structural-need.md)), not an Archon workflow. It **composes `improve-codebase-architecture` verbatim** (technical drift + deepening HTML report + `/grilling` loop, with `/codebase-design` vocabulary + `/domain-modeling`) and **earns its place** ([ADR-0021](docs/adr/0021-earns-its-place-compose-verbatim.md)) by adding three DLC layers the raw skill lacks: an **intent-drift** pass (PRD stories/ACs vs shipped), a **durable `arch-review.md`** artifact under `<artifacts_dir>/` ([ADR-0015](docs/adr/0015-workflows-slug-artifact-home.md)), and an **ADR-consolidation gate with superseding**. Two modes: `<slug>` → intent-grounded against that build session; no-arg → repo-wide sweep (dated artifact, intent-drift skipped). Superseding works across **both ADR homes** (plugin-local + repo-root), never deletes an ADR (old status → `Superseded by ADR-NNNN`, index updated in the matching `README.md`). Config load is **lenient** (off-line, touches no tracker); **no new config key**, no `lib/` change, no auto-hook (PLAN #8). It does **not** touch the legacy `unic-dlc-cleanup.yaml` — that is `/cleanup`'s (step 11) scope. See [ADR-0027](docs/adr/0027-improve-architecture-skill-superseding.md).
 - **`/cleanup` is the repo-global operational janitor — a report-first command, not an Archon workflow.** It prunes the debris a lifecycle accumulates: merged/stale worktrees, stale branches/PRs, and stale `<artifacts_dir>/<slug>/` dirs. It **composes** Archon's own `archon isolation list` / `archon isolation cleanup [days] [--merged] [--include-closed]` / `archon complete <branch>` for worktree/branch lifecycle and the configured tracker (`tracker.access`, MCP-first/CLI-fallback) for PR/branch state — never a `tracker-adapter` lib (dissolved). It is a **command** because it mutates sibling worktrees/branches/PRs and so cannot run inside an isolated worktree ([ADR-0017](docs/adr/0017-container-follows-structural-need.md)). It **defaults to a report-only dry-run and never auto-deletes**: pruning needs `--apply` plus an explicit **per-category** confirmation, and `cleanup.dry_run: true` (the shipped default) keeps even `--apply` in report mode until overridden. A slug dir is prunable **only if** its PR/branch is merged or closed (`cleanup.prune_slug_dirs` defaults `false`); slug-dir pruning skips any dir containing a `LICENSE` (repo policy). It reads the new `cleanup` config block (`stale_days`/`dry_run`/`prune_slug_dirs`); config load is lenient (off-line). This step **retired** the legacy `unic-dlc-cleanup.yaml` + command stub, whose arch-review + ADR-consolidation content moved to `/improve-architecture` ([ADR-0027](docs/adr/0027-improve-architecture-skill-superseding.md)). See [ADR-0028](docs/adr/0028-cleanup-operational-janitor.md).
 - **`/explore` is the off-line, optional research + AFK-spike on-ramp — an Archon workflow whose `findings.md` is the `/specs` baton.** Never required; a precursor to `/specs` (PLAN #3/#8). The pipeline (bootstrap → guard → four parallel research nodes, each reading the `research` Method for its primary-source citation discipline (#281) → synthesize → spike → spike-ticket → spike-branch-gate → preserve-spike) writes `<artifacts_dir>/<slug>/findings.md`, where the **Integrated Brief** carries three explicitly-named lenses — **Domain Model / Established Decisions / Prior Research** — that `/specs`' load-context reads verbatim (the tightened handoff contract). The `spike` node is **AFK** (build/measure where feasible, else reason → VALIDATED/INVALIDATED/PARTIAL verdicts); **interactive prototyping stays Matt's `/prototype` skill**, referenced but never invoked (nodes have no live conversation — [ADR-0017](docs/adr/0017-container-follows-structural-need.md)). The `spike-branch-gate` is a config-gated `approval:` node (`gates.explore`, HITL default): APPROVE preserves the spike on `spike/<slug>`, AFK skips it (worktree left for `/cleanup`); the **spike ticket is filed before the gate** (composing the tracker + `classification.labels`, never a `tracker-adapter`/`labels-config` lib) so the durable output survives a discard. Every node is a self-contained prompt node — no plugin-`lib/` import ([ADR-0023](docs/adr/0023-build-generic-red-green-refactor-loop.md) §5); this step dissolved `findings-writer` + `spike-verdicts` and added no config key. See [ADR-0029](docs/adr/0029-explore-research-spike-onramp.md).
-- **Dogfooding note.** This monorepo has had Setup run against it; the generated artefacts live under [`docs/agents/`](../../../docs/agents/) at the repo root and are managed by the marker-delimited block in the root [`AGENTS.md`](../../../AGENTS.md). Those files describe the target two-axis architecture (see [ADR-0016](docs/adr/0016-dlc-thin-process-layer.md)–[ADR-0018](docs/adr/0018-generic-core-config-compose.md)) with the tracker as the single source of truth, and should be treated as the canonical agent guidance for this repo, not as a current-practice snapshot.
+- **This monorepo is not a Consumer.** `/unic-archon-dlc:setup` must never run against it. An earlier dogfooding run left generated artefacts under `docs/agents/` and a marker-delimited block in the root `AGENTS.md`, which collided with `setup-matt-pocock-skills` over the same paths — the collision this Plugin's own `/triage` doctrine forbids. Both were removed and `docs/agents/*.md` is now hand-owned by the repo; Matt's skills are its only agent-skill driver. Test the Plugin against a scratch Consumer clone instead. See [root ADR-0033](../../../docs/adr/0033-de-dogfood-unic-archon-dlc.md).
 
 ## External dependencies
 
diff --git a/apps/claude-code/unic-confluence/CONTRIBUTING.md b/apps/claude-code/unic-confluence/CONTRIBUTING.md
index f7f2b0ef..318ba8a8 100644
--- a/apps/claude-code/unic-confluence/CONTRIBUTING.md
+++ b/apps/claude-code/unic-confluence/CONTRIBUTING.md
@@ -18,7 +18,7 @@ pnpm install
 
 ## Planning
 
-All work starts as a GitHub Issue in [unic/unic-agents-plugins](https://github.com/unic/unic-agents-plugins/issues). Open or claim an issue there before touching code. See [`docs/agents/workflow.md`](../../../../docs/agents/workflow.md) in the repo root for the full seven-phase workflow (triage → specs → implementation → PR → release).
+All work starts as a GitHub Issue in [unic/unic-agents-plugins](https://github.com/unic/unic-agents-plugins/issues). Open or claim an issue there before touching code. See [`docs/process/development-workflow.md`](../../../docs/process/development-workflow.md) in the repo root for the full workflow (triage → specs → implementation → PR → release).
 
 ## Implementing
 
diff --git a/docs/adr/0032-label-taxonomy.md b/docs/adr/0032-label-taxonomy.md
index 31578126..38773755 100644
--- a/docs/adr/0032-label-taxonomy.md
+++ b/docs/adr/0032-label-taxonomy.md
@@ -1,6 +1,6 @@
 # 0032. Issue label taxonomy: state, type, priority, and a repo-owned area tier
 
-**Status:** Accepted (2026-06)
+**Status:** Accepted (2026-06); ownership amended 2026-08, see [Amendment](#amendment-2026-08)
 
 ## Context
 
@@ -79,3 +79,38 @@ were kept, since Dependabot auto-applies and recreates them.
   vocabulary and revert `docs/agents/triage-labels.md` to the 5-role/`wontfix`
   set. Re-aligning `SKILL.md` was left out of scope because it is a vendored skill
   an upstream update could overwrite; reconcile it by hand if you re-run the skill.
+
+## Amendment (2026-08)
+
+The four-tier taxonomy above stands unchanged. Its **ownership** does not.
+
+[ADR-0033](0033-de-dogfood-unic-archon-dlc.md) uninstalls `unic-archon-dlc` from this
+monorepo, which reverses the Context above on one point: `unic-archon-dlc` is **not** "the
+tool that stays" here, and `setup-matt-pocock-skills` is **not** being phased out — it is
+the surviving driver. The collision the Context describes is resolved by removing a
+generator, not by picking a winner between two.
+
+Four amendments follow:
+
+1. **Tiers 1-3 are repo-owned.** State, type and priority were owned by
+   `unic-archon-dlc` and generated into `docs/agents/labels.md`. That file is now
+   hand-maintained, so all four tiers sit on the same footing: the repo owns them, and
+   `docs/agents/labels.md` is the record. Its "three-tier" wording — flagged above as
+   auto-generated and not to be hand-edited — is corrected to four.
+2. **`release` has one home.** The type was a repo-local override in
+   `.archon/unic-dlc.config.json`, which is deleted. `docs/agents/labels.md` is now its only
+   record.
+3. **`wayfinder:*` is a fifth, tool-scoped namespace, outside the four tiers.**
+   `wayfinder:map` marks a map issue; `wayfinder:{research,prototype,grilling,task}` type a
+   child ticket. `/wayfinder` owns their lifecycle, so they are excluded from the
+   one-per-tier discipline the four tiers follow and from any future generator's remit.
+   Documented under
+   [`docs/agents/issue-tracker.md` § Wayfinding operations](../agents/issue-tracker.md#wayfinding-operations).
+4. **The "do not re-run `/setup-matt-pocock-skills`" warning is resolved by never
+   re-running it.** Upstream v1.1 still declares five canonical roles using `wontfix`, so
+   the destructive behaviour described above is unchanged. `docs/agents/*.md` is instead
+   authored by hand from that skill's templates. The reconciled reference doc the warning
+   points at, `.agents/skills/setup-matt-pocock-skills/triage-labels.md`, is no longer
+   maintained: `.agents/skills/**` is upstream-owned and every `npx skills add` overwrites
+   it — which is how that reconciliation was silently lost in 2026-08. The 8-state mapping
+   lives in `docs/agents/triage-labels.md` only.
diff --git a/docs/adr/0033-de-dogfood-unic-archon-dlc.md b/docs/adr/0033-de-dogfood-unic-archon-dlc.md
new file mode 100644
index 00000000..3bf57ba5
--- /dev/null
+++ b/docs/adr/0033-de-dogfood-unic-archon-dlc.md
@@ -0,0 +1,95 @@
+# 0033. De-dogfood `unic-archon-dlc`: one agent-skill driver, not two
+
+**Status:** Accepted (2026-08)
+
+## Context
+
+This monorepo ran two agent-skill setup systems against itself at the same time.
+
+`unic-archon-dlc` had its `/setup` run here as dogfooding. That generated
+`docs/agents/{branching,domain,issue-tracker,labels,workflow}.md`, each carrying a
+DO-NOT-EDIT header, plus a marker-delimited `## Agent skills` block in the root
+`AGENTS.md`. `setup-matt-pocock-skills` writes three of those same paths and the same
+`AGENTS.md` section. Two generators, one set of files.
+
+The plugin's own doctrine already ruled the arrangement out. From
+`apps/claude-code/unic-archon-dlc/AGENTS.md`, on `/triage`:
+
+> […] injects `classification.labels` from `.archon/unic-dlc.config.yaml` as the single
+> source of truth and **forbids reading Matt's `docs/agents/triage-labels.md` /
+> `issue-tracker.md`**, so labels can't drift from what `/tickets` + `/build` read.
+> Consequently `setup-matt-pocock-skills` is **not** a Plugin dependency.
+
+A repo running both is precisely the drift that doctrine exists to prevent. The damage was
+already visible:
+
+- `docs/agents/workflow.md` documented the **retired** seven-workflow generation
+  (`explore → plan → build → qa → cleanup → triage`), superseded by the box-set redesign
+  months earlier.
+- `docs/agents/issue-tracker.md` cited `lib/tracker-adapter.mjs`, a module that was
+  dissolved.
+- `.archon/` tracked fourteen dead `unic-dlc-*` artefacts and two `unic-dlc.config.*`
+  files, while the workflows actually in use were never committed.
+- `/wayfinder`, new at upstream v1.1, reads a **Wayfinding operations** section from the
+  tracker doc. The DLC-generated copy has no such section, so the skill could not work
+  here at all.
+
+[ADR-0032](0032-label-taxonomy.md) resolved the same collision the other way in 2026-06:
+`unic-archon-dlc` was "the tool that stays" and `setup-matt-pocock-skills` was "being
+phased out". That was correct when the plugin was also this repo's local driver. The
+redesign since then (ADR-0030–0032, plugin-local) turned it into a _product_ with a
+vendored Method bundle pinned to an upstream tag, shipped to Consumer repos. Its
+configuration surface now belongs to those Consumers, not to the workshop that builds it.
+
+## Decision
+
+**`unic-archon-dlc` is a product built in this repo, not a driver run against it.**
+
+1. `/unic-archon-dlc:setup` must never run against this monorepo. Test the plugin against a
+   scratch Consumer clone.
+2. `setup-matt-pocock-skills` — that is, Matt Pocock's skills at `.agents/skills/`, pinned
+   in `skills-lock.json` — is the sole agent-skill driver here.
+3. `docs/agents/*.md` is **repo-owned and hand-maintained**. No generator writes it. The
+   DO-NOT-EDIT headers are gone.
+4. `/setup-matt-pocock-skills` is **not** re-run either, despite now owning the territory:
+   upstream still declares five canonical triage roles using `wontfix`, so a re-run would
+   revert `docs/agents/triage-labels.md` to a vocabulary this repo does not use. The
+   warning ADR-0032 raised about this is resolved by never re-running the skill, not by
+   reconciling it after the fact. Files it would have written are authored by hand from its
+   templates.
+5. `.agents/skills/**` remains **upstream-owned**: never hand-edit it. Every
+   `npx skills add` overwrites the tree, so an edit there dies silently — which is exactly
+   how this repo lost its 8-state reconciliation of `triage-labels.md` once already.
+
+Removed: seven `.archon/commands/unic-dlc-*.md`, seven `.archon/workflows/unic-dlc-*.yaml`,
+`.archon/unic-dlc.config.json`, `.archon/unic-dlc.config.yaml`, `.archon/ralph/`,
+`docs/agents/workflow.md`, `docs/agents/branching.md`, and the plugin's "Dogfooding note"
+doctrine. `.archon/config.yaml` survives — that is Archon's own project config, not the
+plugin's.
+
+## Consequences
+
+- **The label taxonomy loses its generator.** Tiers 1-3 were "owned by `unic-archon-dlc`";
+  they are now repo-owned and documented by hand in `docs/agents/labels.md`. See the
+  amendment on [ADR-0032](0032-label-taxonomy.md).
+- **`release` has one home.** The repo-local `release` type lived as an override in
+  `.archon/unic-dlc.config.json`, which is deleted. `docs/agents/labels.md` is now the only
+  record of it.
+- **`/wayfinder` becomes usable.** `docs/agents/issue-tracker.md` is hand-authored from
+  upstream's v1.1 GitHub template, including the Wayfinding operations section. All three
+  moving parts are verified live rather than assumed: GitHub sub-issues, native issue
+  dependencies, and the five `wayfinder:*` labels, created by hand on 2026-08-05. No
+  body-convention fallback is needed. Nothing maintains those labels and `/wayfinder` does
+  not create a missing one, so the tracker doc treats their presence as a prerequisite to
+  check rather than a fact to trust — a versioned document cannot enforce tracker state.
+- **The plugin's `/setup` gap is now visible rather than papered over.** It generates a
+  tracker doc it under-fills — no wayfinding section — which a real Consumer will hit.
+  Fixing that is plugin work, tracked separately; this repo no longer masks it with a
+  hand-seeded file.
+- **Losing dogfooding costs coverage.** No Consumer-shaped repo exercises `/setup` on every
+  change any more, and that is a real regression in confidence. It is the price of a
+  coherent single driver here; the replacement is a scratch clone, which needs discipline
+  rather than a generated artefact nobody re-reads.
+- **Branch and workflow facts consolidate into `AGENTS.md`.** `docs/agents/branching.md`
+  duplicated the Gitflow table verbatim; `workflow.md` described a generation that no
+  longer exists. Both are deleted rather than re-homed.
diff --git a/docs/adr/README.md b/docs/adr/README.md
index 5fd3f100..ea888103 100644
--- a/docs/adr/README.md
+++ b/docs/adr/README.md
@@ -31,3 +31,5 @@ Numbers are assigned in the order decisions were recorded, not by importance.
 
 - Never delete an ADR.
 - If a decision is superseded, update the original status to `Superseded by ADR-NNNN` and create a new ADR.
+- If the decision still stands but a detail of it changes — ownership, scope, a named tool — **amend in place** instead. Append a dated `## Amendment (YYYY-MM)` section, leave Context and Decision untouched so the original record survives, and extend the status line: `**Status:** Accepted (YYYY-MM); <what> amended YYYY-MM, see [Amendment](#amendment-yyyy-mm)`. [ADR-0032](0032-label-taxonomy.md) is the worked example.
+- Pick by subject, not by size: a change to the same subject amends, a change of subject gets its own ADR. [ADR-0033](0033-de-dogfood-unic-archon-dlc.md) is a new record precisely because de-dogfooding is not a label-taxonomy decision, even though it reversed one clause of ADR-0032.
diff --git a/docs/agents/branching.md b/docs/agents/branching.md
deleted file mode 100644
index 375005a5..00000000
--- a/docs/agents/branching.md
+++ /dev/null
@@ -1,30 +0,0 @@
-<!--
-  AUTO-GENERATED by unic-archon-dlc — DO NOT EDIT BY HAND.
-  Source: apps/claude-code/unic-archon-dlc/lib/agent-docs-writer.mjs
-  Regenerate: re-run `/unic-archon-dlc:setup` (or call `runInstall()` from `lib/install-runner.mjs`).
-  This file describes the unic-archon-dlc target workflow; the current driver
-  in any given Consumer repo may differ.
--->
-
-# Branching Strategy
-
-Configured by unic-archon-dlc.
-
-## Strategy: Gitflow
-
-| Branch type | Pattern          | PR target          |
-| ----------- | ---------------- | ------------------ |
-| Production  | `main`           | —                  |
-| Integration | `develop`        | —                  |
-| Feature     | `feature/<name>` | `develop`          |
-| Hotfix      | `hotfix/<name>`  | `main` + `develop` |
-
-## Default branch names
-
-- **Main branch:** `main`
-- **Integration branch:** `develop`
-- **Feature branch prefix:** `feature/`
-
-## PR conventions
-
-All PRs target `develop`. Merge strategy: `merge`.
diff --git a/docs/agents/domain.md b/docs/agents/domain.md
index 5fc42a08..45751c3a 100644
--- a/docs/agents/domain.md
+++ b/docs/agents/domain.md
@@ -1,14 +1,6 @@
-<!--
-  AUTO-GENERATED by unic-archon-dlc — DO NOT EDIT BY HAND.
-  Source: apps/claude-code/unic-archon-dlc/lib/agent-docs-writer.mjs
-  Regenerate: re-run `/unic-archon-dlc:setup` (or call `runInstall()` from `lib/install-runner.mjs`).
-  This file describes the unic-archon-dlc target workflow; the current driver
-  in any given Consumer repo may differ.
--->
-
 # Domain
 
-Configured by unic-archon-dlc.
+Repo-owned. Hand-maintained — no generator writes this file.
 
 ## Repository layout: multi-context
 
diff --git a/docs/agents/feature-runner.md b/docs/agents/feature-runner.md
index 3c4307ba..cc7f234e 100644
--- a/docs/agents/feature-runner.md
+++ b/docs/agents/feature-runner.md
@@ -1,17 +1,21 @@
 # Feature Runner
 
+Repo-owned. Hand-maintained — no generator writes this file.
+
 The **Feature Runner** is the concept of a runner that implements a Feature's issues end-to-end in one worktree, branch, and pull request — see root `CONTEXT.md`.
 
-## Current state
+## The two runners
+
+- **By hand — `/tdd` or `/implement` per issue.** The developer works each `ready-for-agent` issue, respects `## Blocked by` order ([ADR-0007](../../apps/claude-code/unic-archon-dlc/docs/adr/0007-blocked-by-canonical-sequencing.md)), marks the issue `resolved`, and opens a PR targeting `develop`.
+- **AFK — `/archon-rollout`.** Dispatches the native `archon-fix-github-issue` workflow per issue, each in its own worktree, respecting the dependency tree. Every run lands its own PR targeting `develop`.
 
-- **Current default — manual `/tdd` per issue.** Until the AFK runner is wired into this repo, the developer drives `/tdd` against each `ready-for-agent` issue, respects `## Blocked by` order ([ADR-0007](../../apps/claude-code/unic-archon-dlc/docs/adr/0007-blocked-by-canonical-sequencing.md)), marks the issue `resolved`, and opens a PR targeting `develop` once the feature's issues are done.
-- **Long-term AFK runner — `unic-dlc-build`.** Shipped by `unic-archon-dlc` (also developed in this monorepo). See [ADR-0009](../../apps/claude-code/unic-archon-dlc/docs/adr/0009-retire-ralph-adopt-archon-runner.md) for the retirement of `ralph-orchestrator` and [ADR-0010](../../apps/claude-code/unic-archon-dlc/docs/adr/0010-retire-implement-feature-skill.md) for the retirement of the interim `/implement-feature` skill that briefly filled this role.
+`unic-dlc-build` (shipped by `unic-archon-dlc`) is **not** a runner here. That plugin is built in this monorepo for Consumer repos and is deliberately not installed against this one — see [ADR-0033](../adr/0033-de-dogfood-unic-archon-dlc.md). For the history it replaced, see [ADR-0009](../../apps/claude-code/unic-archon-dlc/docs/adr/0009-retire-ralph-adopt-archon-runner.md) (retiring `ralph-orchestrator`) and [ADR-0010](../../apps/claude-code/unic-archon-dlc/docs/adr/0010-retire-implement-feature-skill.md) (retiring the interim `/implement-feature` skill).
 
 ## What survives across runners
 
 Regardless of which runner executes a Feature, these conventions hold:
 
-- Issues live at `docs/issues/<slug>/NN-*.md` with the `## What to build` / `## Acceptance criteria` format.
+- A ticket carries the `## What to build` / `## Acceptance criteria` shape, whether it lives as a GitHub issue (what `/to-tickets` publishes) or as `docs/issues/<slug>/NN-*.md` for a Feature that keeps a durable file set.
 - `## Blocked by` is the canonical execution-order signal ([ADR-0007](../../apps/claude-code/unic-archon-dlc/docs/adr/0007-blocked-by-canonical-sequencing.md)). Numeric filename prefixes are a UX convenience, not a contract.
 - Each Feature ships as a single PR targeting `develop`. Issues are marked `resolved` on implementation and `closed` after the PR merges.
 
diff --git a/docs/agents/issue-tracker.md b/docs/agents/issue-tracker.md
index 404d77f5..34a3bf67 100644
--- a/docs/agents/issue-tracker.md
+++ b/docs/agents/issue-tracker.md
@@ -1,34 +1,92 @@
-<!--
-  AUTO-GENERATED by unic-archon-dlc — DO NOT EDIT BY HAND.
-  Source: apps/claude-code/unic-archon-dlc/lib/agent-docs-writer.mjs
-  Regenerate: re-run `/unic-archon-dlc:setup` (or call `runInstall()` from `lib/install-runner.mjs`).
-  This file describes the unic-archon-dlc target workflow; the current driver
-  in any given Consumer repo may differ.
--->
+# Issue tracker: GitHub
 
-# Issue Tracker: github
+Repo-owned. Hand-maintained — no generator writes this file. See [ADR-0033](../adr/0033-de-dogfood-unic-archon-dlc.md).
 
-Configured by unic-archon-dlc.
+Issues and specs for this repo live as GitHub issues at [`unic/unic-agents-plugins`](https://github.com/unic/unic-agents-plugins/issues) (a migration to Azure DevOps is planned, not scheduled). Use the `gh` CLI for all operations.
 
-## Backend
+## Conventions
 
-**Tracker:** `github`
-**PR strategy:** `merge`
+- **Create an issue**: `gh issue create --title "..." --body "..."`. Use a heredoc for multi-line bodies.
+- **Read an issue**: `gh issue view <number> --comments` for a human read — it prints tab-delimited text, **not** JSON, so it cannot be piped to `jq`. For anything programmatic ask for the fields: `gh issue view <number> --json title,body,labels,comments,state --jq '{title, state, labels: [.labels[].name], body, comments: [.comments[].body]}'`.
+- **List issues**: `gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'` with appropriate `--label` and `--state` filters.
+- **Comment on an issue**: `gh issue comment <number> --body "..."`
+- **Apply / remove labels**: `gh issue edit <number> --add-label "..."` / `--remove-label "..."`
+- **Close**: `gh issue close <number> --comment "..."`
 
-## Create a new issue
+Infer the repo from `git remote -v` — `gh` does this automatically when run inside a clone.
 
-```sh
-gh issue create --title "<title>" --label "<label>"
-```
+Labels: state, type, priority and area are documented in [`labels.md`](labels.md). A skill's canonical triage _role_ maps onto the state tier via [`triage-labels.md`](triage-labels.md) — this repo runs an 8-state vocabulary and uses `rejected`, never `wontfix`.
+
+## Pull requests as a triage surface
+
+**PRs as a request surface: yes.**
+
+PRs run through the same labels and states as issues, using the `gh pr` equivalents:
+
+- **Read a PR**: `gh pr view <number> --comments` and `gh pr diff <number>` for the diff.
+- **List external PRs for triage**: `gh pr list --state open --json number,title,body,labels,author,authorAssociation,comments` then keep only `authorAssociation` of `CONTRIBUTOR`, `FIRST_TIME_CONTRIBUTOR`, or `NONE` (drop `OWNER`/`MEMBER`/`COLLABORATOR`).
+- **Comment / label / close**: `gh pr comment`, `gh pr edit --add-label`/`--remove-label`, `gh pr close`.
+
+GitHub shares one number space across issues and PRs, so a bare `#42` may be either — resolve with `gh pr view 42` and fall back to `gh issue view 42`.
+
+## When a skill says "publish to the issue tracker"
+
+Create a GitHub issue.
+
+## When a skill says "fetch the relevant ticket"
+
+Run `gh issue view <number> --comments`.
+
+## Wayfinding operations
 
-## Update issue state
+Used by `/wayfinder`. The **map** is a single issue with **child** issues as tickets. Both endpoints below are enabled on this repo — sub-issues and native issue dependencies — so neither body-convention fallback applies here.
+
+The five `wayfinder:*` labels exist on the tracker — `map` plus the four ticket types — created by hand on 2026-08-05. Nothing maintains them and `/wayfinder` does not create a missing one, so treat their presence as a **prerequisite to verify, not a fact to trust**: this file is versioned and the tracker is not, so a deleted label or a fresh fork will disagree with it. Check with `gh label list --search wayfinder`, and create whatever is missing:
 
 ```sh
-gh issue edit <number> --add-label "<label>"
+gh label create wayfinder:map       --description "Wayfinder map: the index issue for one effort" --color 5319E7
+gh label create wayfinder:research  --description "Wayfinder ticket: investigate against primary sources" --color BFD4F2
+gh label create wayfinder:prototype --description "Wayfinder ticket: build a throwaway to answer it" --color BFD4F2
+gh label create wayfinder:grilling  --description "Wayfinder ticket: decide it by grilling" --color BFD4F2
+gh label create wayfinder:task      --description "Wayfinder ticket: do the thing" --color BFD4F2
 ```
 
-## Conventions
+**Every sub-issue and dependency endpoint below takes the issue's numeric database id, never its `#number` and never its `node_id`.** Read it once per issue and reuse it: `gh api repos/<owner>/<repo>/issues/<n> --jq .id`.
+
+- **Map**: a single issue labelled `wayfinder:map`, holding the Destination / Notes / Decisions-so-far / Fog body. `gh issue create --label wayfinder:map`.
+- **Child ticket**: create the issue, then link it to the map as a GitHub sub-issue:
+
+  ```sh
+  gh issue create --title "<question>" --body "…" --label "wayfinder:<type>"
+  gh api --method POST repos/<owner>/<repo>/issues/<map>/sub_issues -F sub_issue_id=<child-db-id>
+  ```
+
+  `<type>` is one of `research`, `prototype`, `grilling`, `task`. Once claimed, the ticket is assigned to the driving dev.
+
+  The `sub_issues` POST returns the **parent** issue, not the child, so its `.number` is not confirmation that the link landed. Verify by listing: `gh api repos/<owner>/<repo>/issues/<map>/sub_issues --jq '.[].number'`.
+
+- **Blocking**: GitHub's **native issue dependencies** — the canonical, UI-visible representation:
+
+  ```sh
+  gh api --method POST repos/<owner>/<repo>/issues/<child>/dependencies/blocked_by -F issue_id=<blocker-db-id>
+  ```
+
+  GitHub reports `issue_dependencies_summary.blocked_by` — open blockers only, which is the live gate. A ticket is unblocked when every blocker is closed.
+
+- **Frontier query**: `gh issue list` has **no** sub-issue filter, so read the children from the map and check each one:
+
+  ```sh
+  gh api repos/<owner>/<repo>/issues/<map>/sub_issues \
+    --jq '.[] | select(.state == "open" and (.assignee | not)) | .number' |
+  while read -r n; do
+    gh api "repos/<owner>/<repo>/issues/$n" \
+      --jq 'select(.issue_dependencies_summary.blocked_by == 0) | "\(.number) \(.title)"'
+  done
+  ```
+
+  The result is the frontier: open, unassigned, unblocked. First in map order wins.
+
+- **Claim**: `gh issue edit <n> --add-assignee @me` — the session's first write.
+- **Resolve**: `gh issue comment <n> --body "<answer>"`, then `gh issue close <n>`, then append a context pointer (gist + link) to the map's Decisions-so-far.
 
-- Issue state is tracked via labels matching the canonical triage vocabulary (see `docs/agents/labels.md`).
-- Dependency links use the tracker's native "blocked by" field; for local-markdown, use a `## Blocked by` heading.
-- The tracker adapter (`lib/tracker-adapter.mjs`) translates canonical label names to tracker strings at write time.
+`wayfinder:*` labels sit outside the four-tier taxonomy — `/wayfinder` owns their lifecycle. See the [ADR-0032 amendment](../adr/0032-label-taxonomy.md#amendment-2026-08).
diff --git a/docs/agents/labels.md b/docs/agents/labels.md
index 78527776..272c3eee 100644
--- a/docs/agents/labels.md
+++ b/docs/agents/labels.md
@@ -1,44 +1,37 @@
-<!--
-  AUTO-GENERATED by unic-archon-dlc — DO NOT EDIT BY HAND.
-  Source: apps/claude-code/unic-archon-dlc/lib/agent-docs-writer.mjs
-  Regenerate: re-run `/unic-archon-dlc:setup` (or call `runInstall()` from `lib/install-runner.mjs`).
-  This file describes the unic-archon-dlc target workflow; the current driver
-  in any given Consumer repo may differ.
--->
-
 # Labels
 
-Three-tier taxonomy for `github`. Canonical names are used inside workflows; the tracker adapter maps them to tracker strings at write time.
-
-## State labels
-
-| Canonical       | Tracker string  |
-| --------------- | --------------- |
-| needs-triage    | needs-triage    |
-| needs-info      | needs-info      |
-| needs-specs     | needs-specs     |
-| ready-for-agent | ready-for-agent |
-| ready-for-human | ready-for-human |
-| resolved        | resolved        |
-| closed          | closed          |
-| rejected        | rejected        |
-
-## Type labels
-
-| Canonical | Tracker string |
-| --------- | -------------- |
-| feature   | feature        |
-| bug       | bug            |
-| spike     | spike          |
-| tech-debt | tech-debt      |
-| docs      | docs           |
-| release   | release        |
-
-## Priority labels
-
-| Canonical | Tracker string |
-| --------- | -------------- |
-| p0        | p0             |
-| p1        | p1             |
-| p2        | p2             |
-| p3        | p3             |
+Repo-owned. Hand-maintained — no generator writes this file. See [ADR-0032](../adr/0032-label-taxonomy.md).
+
+Four tiers on the GitHub tracker: **state**, **type**, **priority** and **area**. Canonical names are what skills speak; on this tracker they are also the literal label strings, so no mapping is needed. `docs/agents/triage-labels.md` maps a skill's canonical triage _role_ onto the state tier, which is where the two vocabularies differ.
+
+`wayfinder:*` labels sit outside these tiers — `/wayfinder` owns their lifecycle. Five exist: `wayfinder:map` and the four ticket types (`research`, `prototype`, `grilling`, `task`). They were created by hand and nothing maintains them; see [Wayfinding operations](issue-tracker.md#wayfinding-operations).
+
+## State (8)
+
+One per issue. `rejected` is canonical here, **not** `wontfix`.
+
+`needs-triage` → `needs-info` → `needs-specs` → `ready-for-agent` / `ready-for-human` → `resolved` → `closed`, or `rejected` at any point.
+
+## Type (6)
+
+One per issue: `feature`, `bug`, `spike`, `tech-debt`, `docs`, `release`.
+
+`release` is repo-local. It was added as an override in `.archon/unic-dlc.config.json`, which no longer exists — this file is now its only home.
+
+## Priority (4)
+
+One per issue: `p0`, `p1`, `p2`, `p3`.
+
+## Area (one per app or package)
+
+- `app:<plugin>` — one per app under `apps/claude-code/`
+- `pkg:<package>` — one per workspace package under `packages/`
+- `repo` — monorepo-wide or cross-cutting work
+
+One exception: `app:unic-ticket-specification` has no directory under `apps/claude-code/` — the plugin was specified but never built. Keep the label; one issue carries it, and deleting a label strips it from every issue that has it. `app:pr-review` does have a directory, deliberately tagging the deprecated v1 plugin's 30 historical issues.
+
+Hand-applied. The context each area label maps to is listed in [`CONTEXT-MAP.md`](../../CONTEXT-MAP.md).
+
+## Kept for tooling
+
+`dependencies` and `javascript` are Dependabot's. It auto-applies and recreates them, so leave them alone.
diff --git a/docs/agents/triage-labels.md b/docs/agents/triage-labels.md
index 41cb06d8..eb7a30e2 100644
--- a/docs/agents/triage-labels.md
+++ b/docs/agents/triage-labels.md
@@ -1,16 +1,42 @@
 # Triage Labels
 
-The skills speak in terms of triage roles. This file maps those roles to the label strings used in this repo's issue tracker.
-
-| Role             | Label             | Meaning                                          |
-| ---------------- | ----------------- | ------------------------------------------------ |
-| Needs evaluation | `needs-triage`    | Maintainer needs to evaluate this issue          |
-| Needs info       | `needs-info`      | Waiting on reporter for more information         |
-| Needs specs      | `needs-specs`     | Enough info from reporter; ready to write a spec |
-| Ready for agent  | `ready-for-agent` | Fully specified, ready for an AFK agent          |
-| Ready for human  | `ready-for-human` | Requires human implementation                    |
-| Resolved         | `resolved`        | Implemented; ready for a PR                      |
-| Closed           | `closed`          | PR has been merged                               |
-| Rejected         | `rejected`        | Will not be actioned                             |
-
-When a skill mentions a role (e.g. "apply the AFK-ready label"), use the corresponding label string from this table.
+Repo-owned. Hand-maintained — no generator writes this file.
+
+`/triage` speaks in **canonical roles**. This file maps every role it can name onto the label strings this repo actually uses. Left column entries are the skill's literal role names, so a lookup never needs interpretation. The full tracker taxonomy is in [`labels.md`](labels.md).
+
+## Category roles
+
+| Canonical role | Label in this repo | Note                                                                                                                                                                |
+| -------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `bug`          | `bug`              | —                                                                                                                                                                   |
+| `enhancement`  | `feature`          | This repo has no `enhancement` label. **Never create one** — [ADR-0032](../adr/0032-label-taxonomy.md) merged 48 `enhancement` issues into `feature` and deleted it |
+
+The type tier carries four more labels no canonical role names — `spike`, `tech-debt`, `docs`, `release`. Apply them directly when they fit better than `feature`.
+
+## State roles
+
+| Canonical role    | Label in this repo | Meaning                                  |
+| ----------------- | ------------------ | ---------------------------------------- |
+| `needs-triage`    | `needs-triage`     | Maintainer needs to evaluate this issue  |
+| `needs-info`      | `needs-info`       | Waiting on reporter for more information |
+| `ready-for-agent` | `ready-for-agent`  | Fully specified, ready for an AFK agent  |
+| `ready-for-human` | `ready-for-human`  | Requires human implementation            |
+| `wontfix`         | `rejected`         | Will not be actioned                     |
+
+**`rejected` is this repo's label, never `wontfix`.** The skill's canonical role keeps the older name; the label does not.
+
+## Repo-only states
+
+Three more state labels exist that no canonical role names. They extend the skill's five-state machine rather than replacing it — `/triage` will not apply them on its own, so set them by hand or by whichever command owns that transition.
+
+`ready-for-agent` has a second author: `/to-spec` and `/to-tickets` apply it themselves on publish, after you approve their output in-session. Treat that label as final — do not re-triage freshly published tickets.
+
+It carries two different meanings depending on which issue holds it. On a **ticket** from `/to-tickets` it means an agent may implement this. On the **spec issue** from `/to-spec` it means the spec is settled — the body is user stories, with no `## What to build` and no `## Blocked by` edges, so it is not implementable. Check the shape, not just the label, before dispatching.
+
+| Label         | Meaning                                         | Sits between                 |
+| ------------- | ----------------------------------------------- | ---------------------------- |
+| `needs-specs` | Enough info from the reporter; ready for a spec | `needs-info` → `ready-for-*` |
+| `resolved`    | Implemented; ready for a PR                     | `ready-for-*` → `closed`     |
+| `closed`      | PR has been merged                              | after `resolved`             |
+
+Full order: `needs-triage` → `needs-info` → `needs-specs` → `ready-for-agent` / `ready-for-human` → `resolved` → `closed`, with `rejected` reachable at any point.
diff --git a/docs/agents/workflow.md b/docs/agents/workflow.md
deleted file mode 100644
index 529496be..00000000
--- a/docs/agents/workflow.md
+++ /dev/null
@@ -1,29 +0,0 @@
-<!--
-  AUTO-GENERATED by unic-archon-dlc — DO NOT EDIT BY HAND.
-  Source: apps/claude-code/unic-archon-dlc/lib/agent-docs-writer.mjs
-  Regenerate: re-run `/unic-archon-dlc:setup` (or call `runInstall()` from `lib/install-runner.mjs`).
-  This file describes the unic-archon-dlc target workflow; the current driver
-  in any given Consumer repo may differ.
--->
-
-# Workflow Phases
-
-unic-archon-dlc ships seven Archon workflow YAML DAGs. Six are lifecycle phases (explore → plan → build → qa → cleanup → triage) that produce persistent artifacts committed to `docs/workflow/<slug>/`. The `review` workflow is on-demand and posts (or updates) a structured review on the current PR via the configured tracker backend.
-
-| Phase   | Command                    | Artifact outputs                                                                                              |
-| ------- | -------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| explore | `/unic-dlc-explore <slug>` | `docs/workflow/<slug>/findings.md`                                                                            |
-| plan    | `/unic-dlc-plan <slug>`    | `docs/workflow/<slug>/PRD.md`, `issues.json`, `build-<slug>.yaml`                                             |
-| build   | `/unic-dlc-build <slug>`   | `docs/workflow/<slug>/report.md`                                                                              |
-| qa      | `/unic-dlc-qa <slug>`      | merged PR                                                                                                     |
-| cleanup | `/unic-dlc-cleanup <slug>` | `docs/workflow/<slug>/arch-review.md`                                                                         |
-| triage  | `/unic-dlc-triage`         | `HANDOFF.md`, `docs/workflow/ROADMAP.md`                                                                      |
-| review  | `/unic-dlc-review`         | PR comment (github/ado/jira) or `docs/workflow/<slug>/review-comment.md` (local-markdown); idempotent re-runs |
-
-## State separation
-
-| Layer                        | Storage                          | Who owns it       |
-| ---------------------------- | -------------------------------- | ----------------- |
-| Transient workflow state     | `$ARTIFACTS_DIR` (Archon native) | Archon runtime    |
-| Persistent project artifacts | `docs/workflow/<slug>/`          | Committed to repo |
-| Issue / ticket tracking      | Configured tracker               | Tracker backend   |
diff --git a/docs/process/ai-development.md b/docs/process/ai-development.md
index d5e95c5f..cc8f7efd 100644
--- a/docs/process/ai-development.md
+++ b/docs/process/ai-development.md
@@ -6,19 +6,21 @@ This guide explains the mental model behind the AI-development workflow, the arc
 
 ## 1. The Feature Runner
 
-A **Feature Runner** is the skill that implements a Feature's issues end-to-end in one worktree, branch, and pull request (see root `CONTEXT.md`).
+A **Feature Runner** is whatever implements a Feature's Issues end-to-end in one worktree, branch, and pull request (see root `CONTEXT.md`).
 
-New work enters as a GitHub Issue — the canonical tracker for state and ownership (see [docs/agents/issue-tracker.md](../agents/issue-tracker.md)). Once an idea is grilled into a Feature, `/to-prd` and `/to-issues` materialise a `docs/issues/<slug>/` directory with the PRD and the numbered ticket files the Feature Runner reads. GitHub Issues remain the source of truth for triage state; `docs/issues/<slug>/` is the markdown artifact set that captures the grilled scope. Not every GitHub Issue becomes a Feature directory (small fixes never need one).
+New work enters as a GitHub Issue — the canonical tracker for state and ownership (see [docs/agents/issue-tracker.md](../agents/issue-tracker.md)). Once an idea is charted into a Feature, `/to-spec` publishes the spec as an issue and `/to-tickets` publishes one issue per ticket, linked by GitHub's native sub-issue and blocking relationships.
 
-|                       | Feature Runner                                             |
-| --------------------- | ---------------------------------------------------------- |
-| **Input**             | `docs/issues/<slug>/NN-*.md` Issue                         |
-| **Format**            | Descriptive: `## What to build` + `## Acceptance criteria` |
-| **Worker**            | `/tdd`                                                     |
-| **Completion marker** | `Status: resolved` in issue file                           |
-| **Branch**            | `feature/<name>` (or `feature/afk/<slug>` when AFK)        |
+`docs/issues/<slug>/` directories hold the markdown artifact set for Features that want durable file-based tickets — `PRD.md` plus numbered ticket files a Feature Runner can read. Since upstream v1.1 **no skill generates them**; create one by hand when a Feature needs it. Most work lives in GitHub Issues alone.
 
-`unic-dlc-build` (shipped by `unic-archon-dlc`) is the long-term Feature Runner — see [ADR-0009](../../apps/claude-code/unic-archon-dlc/docs/adr/0009-retire-ralph-adopt-archon-runner.md) and [ADR-0010](../../apps/claude-code/unic-archon-dlc/docs/adr/0010-retire-implement-feature-skill.md). Until it is wired into this repo, the runner is **the developer driving `/tdd` manually**, one issue at a time. Infrastructure work (CI, tooling, packages) and product work (plugin features) both enter through the issue tracker — the split is in the issue content, not in which runner handles it.
+|                       | Feature Runner                                                          |
+| --------------------- | ----------------------------------------------------------------------- |
+| **Input**             | A `ready-for-agent` GitHub issue, or `docs/issues/<slug>/NN-*.md`       |
+| **Format**            | Descriptive: `## What to build` + `## Acceptance criteria`              |
+| **Worker**            | `/tdd` or `/implement`                                                  |
+| **Completion marker** | `resolved` label on the Issue, or `Status: resolved` in the ticket file |
+| **Branch**            | `feature/<name>`, or `feature/<scope>/<issue#>-<slug>` AFK              |
+
+Two runners operate here: **the developer driving `/tdd` or `/implement`** one issue at a time, and **`/archon-rollout`** dispatching the native `archon-fix-github-issue` workflow per issue for AFK runs. `unic-dlc-build` (shipped by `unic-archon-dlc`) is not one of them — that plugin is built here for Consumer repos and deliberately not installed against this one, see [ADR-0033](../adr/0033-de-dogfood-unic-archon-dlc.md). Infrastructure work (CI, tooling, packages) and product work (plugin features) both enter through the issue tracker — the split is in the issue content, not in which runner handles it.
 
 ---
 
@@ -29,15 +31,15 @@ Every piece of work passes through a pipeline before an agent executes it. Each
 ```
 GitHub Issue / /triage  ← raw capture, no review required
        ↓
-/grill-with-docs        ← human reviews every branch of the design tree
-       ↓
-/to-prd                 ← human reviews the synthesized PRD
+/wayfinder              ← human resolves one decision ticket per session
+  or /grill-with-docs    (single-session work: human reviews every branch)
        ↓
-/to-issues              ← human reviews the vertical slice breakdown
+/to-spec                ← human approves the seams, then it publishes
        ↓
-/triage                 ← human moves issues to ready-for-agent
+/to-tickets             ← human approves the breakdown, then it publishes
+                           `ready-for-agent` — this is the last checkpoint
        ↓
-/tdd  (or unic-dlc-build, when wired up)  ← execution
+/tdd or /implement      ← execution, or /archon-rollout for a chain
 ```
 
 The pipeline is load-bearing. The quality of the execution at the bottom depends entirely on the quality of the decisions captured at each stage above it. A vague acceptance criterion that slips through triage will produce a vague implementation. Under manual `/tdd` you can still catch it interactively; under AFK execution there is no human in the loop until PR review.
@@ -48,11 +50,11 @@ The pipeline is load-bearing. The quality of the execution at the bottom depends
 
 `/tdd` is interactive by default: its planning phase asks the user to confirm interface changes and approve which behaviours to test before writing any code. When `/tdd` is run interactively, that conversation is where most ambiguity is eliminated.
 
-In AFK mode (the future `unic-dlc-build` path) there is no user to ask. The issue's `## Acceptance criteria` replaces that conversation. The planning phase is not skipped — it must have been completed during the grilling and issue-writing stages.
+In AFK mode (an `/archon-rollout` dispatch) there is no user to ask. The issue's `## Acceptance criteria` replaces that conversation. The planning phase is not skipped — it must have been completed during the grilling and issue-writing stages.
 
 This means there is a direct line between **grilling quality → PRD quality → issue acceptance criteria quality → implementation correctness**. If any link in that chain is weak, the agent produces a _correct-but-wrong_ implementation: code that satisfies the literal issue description but diverges from what you actually intended.
 
-The grilling session (`/grill-with-docs`) is where that chain is forged. It is not a formality — it is the point at which ambiguity is eliminated and architectural constraints are identified. Skipping or shortcutting it shifts the cost downstream, where it is much more expensive to recover from.
+Phase 2 is where that chain is forged — `/wayfinder` across sessions, or `/grill-with-docs` within one. It is not a formality: it is the point at which ambiguity is eliminated and architectural constraints are identified. Skipping or shortcutting it shifts the cost downstream, where it is much more expensive to recover from.
 
 ---
 
@@ -79,15 +81,15 @@ An issue's `## Acceptance criteria` is doing two jobs: it is the definition of d
 - [ ] Tests pass
 ```
 
-The `to-issues` skill produces acceptance criteria — but an agent authors them. They are then reviewed by you before the issue reaches `ready-for-agent`. That review is the last human checkpoint before AFK execution. Use it.
+The `to-tickets` skill produces acceptance criteria — but an agent authors them. You review them **inside the skill**, while it iterates on the breakdown with you. It publishes only once you approve, and the `ready-for-agent` label it applies is that approval. Nothing downstream re-checks, so this in-session review is the last human checkpoint before AFK execution. Use it.
 
-If an issue's acceptance criteria are too vague to verify without judgment, the issue is not `ready-for-agent`. Send it back to `needs-specs`.
+If an issue's acceptance criteria are too vague to verify without judgment, do not approve the breakdown. Send the ticket back for rework in the same session, or once published, relabel it `needs-specs`.
 
 ---
 
 ## 5. Dependency ordering
 
-Issues produced by `to-issues` are named with a numeric prefix (`01-`, `02-`, etc.) for human readability. The numbers usually reflect dependency order because `to-issues` publishes blockers first. But **numerical order is not the execution contract**.
+`to-tickets` publishes blockers first, so issue numbers usually ascend in dependency order — and in its local-file mode, filenames carry an explicit `01-`, `02-` prefix for readability. Either way, **that order is not the execution contract**.
 
 The `## Blocked by` field in each issue is the canonical dependency signal — see [ADR-0007](../../apps/claude-code/unic-archon-dlc/docs/adr/0007-blocked-by-canonical-sequencing.md). Any Feature Runner (manual or AFK) must respect `## Blocked by` over filename order. If they conflict, the runner halts rather than proceeding silently in the wrong order — because a wrong execution order means downstream issues inherit a broken foundation.
 
@@ -101,13 +103,13 @@ The dependency graph also reveals which issues are parallelisable (those with no
 
 `CONTEXT.md` and `docs/adr/` are not documentation you write once and forget. They are the vocabulary and constraint layer that every agent reads before writing code. Their quality directly affects the quality of every execution — manual or AFK.
 
-**Update CONTEXT.md** when a new domain term is introduced or an existing term is redefined. `/grill-with-docs` does this automatically during a grilling session — terms resolved during grilling are written into CONTEXT.md inline. If a term surfaces outside a grilling session, add it manually.
+**Update CONTEXT.md** when a new domain term is introduced or an existing term is redefined. `/grill-with-docs` does this inline, because it composes `/domain-modeling` — terms resolved during the session are written into CONTEXT.md as they land. A `/wayfinder` map does it per decision ticket, in whichever session resolves that ticket. If a term surfaces outside either, add it manually or run `/domain-modeling` on its own.
 
 **Write an ADR** when a decision is: (a) hard to reverse, (b) surprising without context, and (c) the result of a real trade-off with considered alternatives. An ADR that just restates the obvious adds noise and dilutes the ones that matter.
 
 **Never let ADRs drift.** An ADR that no longer reflects the codebase is worse than no ADR — it misdirects the agent. If a decision is superseded, update the original ADR's status to `Superseded by ADR-NNNN` and write the new one.
 
-The commits from your grilling sessions carry this context forward. When `unic-dlc-build` later runs AFK, recent commits are part of the context input precisely because grilling sessions modify CONTEXT.md and ADRs — those changes land in commits and the agent needs the ideation trail, not just the final file state.
+The commits from your grilling sessions carry this context forward. When an AFK run picks the work up, recent commits are part of the context input precisely because grilling sessions modify CONTEXT.md and ADRs — those changes land in commits and the agent needs the ideation trail, not just the final file state.
 
 ---
 
diff --git a/docs/process/development-workflow.md b/docs/process/development-workflow.md
index 27c1155e..9749ae28 100644
--- a/docs/process/development-workflow.md
+++ b/docs/process/development-workflow.md
@@ -10,59 +10,81 @@ Not every phase is required for every piece of work. A typo fix can go straight
 
 When an idea surfaces mid-conversation or mid-task, capture it without breaking flow by opening a GitHub Issue directly (or running `/triage` and letting it walk the idea through the state machine).
 
-GitHub Issues are the canonical tracker (see [docs/agents/issue-tracker.md](../agents/issue-tracker.md)) — they hold raw ideas, bug reports, and triage state. Features that get grilled additionally pick up a `docs/issues/<slug>/` directory in Phase 5, where `/to-prd` and `/to-issues` write the PRD and ticket files the Feature Runner consumes. Not every GitHub Issue grows into a Feature directory — small fixes stay as plain GitHub Issues.
+GitHub Issues are the canonical tracker (see [docs/agents/issue-tracker.md](../agents/issue-tracker.md)) — they hold raw ideas, bug reports, triage state, and from Phase 5 onward the spec and its tickets. A Feature that wants a durable markdown artefact set also gets a `docs/issues/<slug>/` directory, created by hand; most work never needs one.
 
-If you already have enough context to start grilling immediately, skip capture and go straight to Phase 2.
+If you already have enough context to start charting immediately, skip capture and go straight to Phase 2.
 
-## Phase 2 — Grill the idea
+## Phase 2 — Chart the work
 
-Before writing a PRD or spec, reach shared understanding with the agent:
+Before writing a spec, reach shared understanding with the agent. Pick the tool by how much there is to decide:
 
 ```
-/grill-with-docs
+/wayfinder          # too much to plan in one agent session
+/grill-with-docs    # fits in one session, touches domain concepts
+/grill-me           # fits in one session, no domain vocabulary at stake
 ```
 
-Use `/grill-with-docs` when the topic involves domain concepts — it is designed to update `CONTEXT.md` and ADRs alongside the grilling. Use `/grill-me` for everything else.
+**`/wayfinder` is where the planning weight has moved upstream.** Use it when the fog is thicker than one session: it names the destination, charts the open decisions as a `wayfinder:map` issue with one child ticket per decision, blocks them with GitHub's native dependencies, then works the frontier — one decision per session, each ticket typed `research`, `prototype`, `grilling` or `task`. It plans; it does not build. The map is done when nothing is left to decide. See [Wayfinding operations](../agents/issue-tracker.md#wayfinding-operations) for how this repo expresses maps, blocking, and the frontier query.
 
-The grilling session walks down every branch of the design tree until the idea is concrete: edge cases surfaced, ambiguities resolved, out-of-scope items named.
+Use `/grill-with-docs` when one session is enough and the topic involves domain concepts — it composes `/grilling` with `/domain-modeling`, so `CONTEXT.md` and the ADRs get updated as decisions land. Use `/grill-me` for everything else.
+
+Either way the session walks down every branch of the design tree until the idea is concrete: edge cases surfaced, ambiguities resolved, out-of-scope items named.
 
 ## Phase 3 — Research (optional)
 
 If the work involves an unfamiliar external API, a complex integration, or anything that would require repeated exploration in fresh context windows, cache the findings:
 
-Ask the agent to research the topic and save results to a `research.md` file in the relevant plugin directory (e.g. `apps/claude-code/pr-review/research.md`).
+```
+/research
+```
+
+It spins up a background agent that reads primary sources — official docs, source code, specs, first-party APIs — cites each claim, and writes one Markdown file. This repo keeps those notes in `docs/research/`, which is the convention the skill picks up. A `wayfinder` ticket labelled `wayfinder:research` is the same job scoped to one decision.
 
-Research assets are **temporary** — scoped to the current feature sprint. Delete them once the feature ships to prevent stale data from misleading future agents.
+A note written **beside the code it explains** (e.g. `apps/claude-code/pr-review/research.md`) is **temporary** — scoped to the current feature sprint. Delete it once the feature ships to prevent stale data from misleading future agents. Notes in `docs/research/` are the durable set and stay.
 
 ## Phase 4 — Prototype (optional)
 
-When design or UX decisions are uncertain, prototype first. Ask the agent to generate multiple variations on a throwaway route and iterate until you have a direction you're happy with.
+When design or state-model decisions are uncertain, prototype first:
+
+```
+/prototype
+```
+
+It branches on the question. "Does this logic feel right?" produces a single shareable HTML file that drives the state machine through the awkward cases, playable by a non-developer. "What should this look like?" produces several radically different UI variations on one route, switchable from a floating bar. Either way the code is throwaway. A `wayfinder` ticket labelled `wayfinder:prototype` is the same job scoped to one decision.
 
-Commit the winning design to the codebase before writing the PRD — concrete examples are more valuable than abstract descriptions.
+Commit the winning design before writing the spec — concrete examples are more valuable than abstract descriptions.
 
-## Phase 5 — Write the PRD
+## Phase 5 — Write the spec
 
-With grilling and prototyping complete, document the destination:
+With charting and prototyping complete, document the destination:
 
 ```
-/to-prd
+/to-spec
 ```
 
-This synthesizes the conversation into a PRD at `docs/issues/<slug>/PRD.md`, describing the end state, user stories, implementation decisions, and what's explicitly out of scope.
+This synthesizes the conversation into a spec and **publishes it as a GitHub issue**. Seven sections: Problem Statement, Solution, User Stories, Implementation Decisions, **Testing Decisions**, Out of Scope, Further Notes. It does not write a file.
+
+Testing Decisions carries the seams forward into `/tdd`, which is why the skill proposes those seams and checks them with you before it writes anything — prefer existing seams, and the highest one available.
 
-The PRD answers "what does done look like?" — not "how do we get there?"
+The spec answers "what does done look like?" — not "how do we get there?"
 
-## Phase 6 — Break it into issues
+It also applies `ready-for-agent` to the spec issue itself. That label there means "the spec is settled", **not** "an agent may implement this" — the spec has no `## What to build` or `## Blocked by` edges. Phase 6 produces the implementable tickets. A rollout must skip the spec issue.
 
-Turn the PRD into independently-executable tickets:
+## Phase 6 — Break it into tickets
+
+Turn the spec into independently-executable tickets:
 
 ```
-/to-issues
+/to-tickets
 ```
 
-This creates `docs/issues/<slug>/<NN>-<ticket>.md` files — vertical slices that cut through all integration layers. Each ticket should be small enough to fit in a single agent context window.
+This publishes **one GitHub issue per ticket**, in dependency order so each can reference real identifiers, linked with GitHub's native sub-issue and blocking relationships. Each ticket is a vertical slice that cuts through all integration layers, small enough to fit in a single agent context window.
+
+Two things to know about the output:
 
-Use the triage labels to track state — see `docs/agents/triage-labels.md` for the full 8-state vocabulary (`needs-triage` → `needs-info` → `needs-specs` → `ready-for-agent` / `ready-for-human` → `resolved` → `closed` / `rejected`).
+- **The human gate sits inside the skill, not after it.** `/to-tickets` iterates on the breakdown until you approve it, and only then publishes — so the `ready-for-agent` label it applies already carries your approval. Do not run `/triage` again over freshly published tickets. Approve properly inside the skill, because nothing downstream re-checks. `/triage` stays the on-ramp for raw work that arrives unspecified: bug reports, external PRs, ideas. See `docs/agents/triage-labels.md` for the full order (`needs-triage` → `needs-info` → `needs-specs` → `ready-for-agent` / `ready-for-human` → `resolved` → `closed`, or `rejected`).
+- **Two kinds of issue now carry `ready-for-agent`, and only one is implementable.** The spec issue from Phase 5 has it too, and a `wayfinder:map` and its decision tickets are labelled by a different scheme entirely. Before dispatching, check the Issue has the `## What to build` / `## Acceptance criteria` shape — a label match alone is not enough. `/archon-rollout` does not yet filter these out; treat its issue list as needing a glance.
+- **`docs/issues/<slug>/` is a repo convention, not skill output.** Nothing generates it since upstream v1.1 — `to-tickets`' local-file mode writes `.scratch/<slug>/issues/` and is only reached when no real tracker is configured. Existing `docs/issues/<slug>/` directories are the durable artefact set from earlier Features; create one by hand when a Feature wants file-based tickets.
 
 ## Phase 7 — Execute
 
@@ -72,9 +94,11 @@ Work through `ready-for-agent` issues one at a time with `/tdd`. For each issue,
 
 Respect the issue ordering signalled by `## Blocked by` (see [ADR-0007](../../apps/claude-code/unic-archon-dlc/docs/adr/0007-blocked-by-canonical-sequencing.md)) — a downstream issue inherits a broken foundation if a blocker has not landed.
 
-### Feature Runner — long-term AFK execution
+### AFK execution with `/archon-rollout`
+
+Dispatch a chain of `ready-for-agent` issues with `/archon-rollout`, which runs the native `archon-fix-github-issue` workflow per issue in its own worktree and respects the `## Blocked by` tree. Each run lands its own PR targeting `develop`.
 
-The Feature Runner (`unic-dlc-build`, shipped by `unic-archon-dlc`) is the AFK path going forward; see [ADR-0009](../../apps/claude-code/unic-archon-dlc/docs/adr/0009-retire-ralph-adopt-archon-runner.md) and [ADR-0010](../../apps/claude-code/unic-archon-dlc/docs/adr/0010-retire-implement-feature-skill.md). Until it is wired into this repo, AFK runs are not available — implement manually with `/tdd`.
+`unic-dlc-build` (shipped by `unic-archon-dlc`) is **not** the AFK path here. That plugin is a product this repo builds for Consumer repos; it is not installed against this one — see [ADR-0033](../adr/0033-de-dogfood-unic-archon-dlc.md).
 
 ### Human execution
 
@@ -90,16 +114,16 @@ Human QA often surfaces new issues or improvement ideas — add them back to the
 
 ## Quick reference
 
-| Phase        | When                                           | Tool                                                         |
-| ------------ | ---------------------------------------------- | ------------------------------------------------------------ |
-| 1. Capture   | Idea surfaces mid-task                         | GitHub Issue (or `/triage`)                                  |
-| 2. Grill     | Before any PRD or spec                         | `/grill-with-docs` or `/grill-me`                            |
-| 3. Research  | Unfamiliar external dependencies               | `research.md` (ad hoc)                                       |
-| 4. Prototype | Uncertain design or UX                         | Ad hoc throwaway route                                       |
-| 5. PRD       | After grilling                                 | `/to-prd` → `docs/issues/<slug>/PRD.md`                      |
-| 6. Issues    | After PRD                                      | `/to-issues` → `docs/issues/<slug>/<NN>-*.md`                |
-| 7. Execute   | Issues in `docs/issues/` are `ready-for-agent` | `/tdd` per issue (Feature Runner via `unic-dlc-build` later) |
-| 8. QA        | After execution                                | QA plan (agent-generated, human-verified)                    |
+| Phase        | When                             | Tool                                                                           |
+| ------------ | -------------------------------- | ------------------------------------------------------------------------------ |
+| 1. Capture   | Idea surfaces mid-task           | GitHub Issue (or `/triage`)                                                    |
+| 2. Chart     | Before any spec                  | `/wayfinder` if it exceeds one session, else `/grill-with-docs` or `/grill-me` |
+| 3. Research  | Unfamiliar external dependencies | `/research`                                                                    |
+| 4. Prototype | Uncertain design or state model  | `/prototype`                                                                   |
+| 5. Spec      | After charting                   | `/to-spec` → one GitHub issue                                                  |
+| 6. Tickets   | After the spec                   | `/to-tickets` → one GitHub issue per ticket, natively linked                   |
+| 7. Execute   | Tickets are `ready-for-agent`    | `/tdd` or `/implement` per issue, `/archon-rollout` for AFK                    |
+| 8. QA        | After execution                  | QA plan (agent-generated, human-verified)                                      |
 
 ## Related
 
diff --git a/skills-lock.json b/skills-lock.json
index 39650c38..48f3aed1 100644
--- a/skills-lock.json
+++ b/skills-lock.json
@@ -1,107 +1,161 @@
 {
   "version": 1,
   "skills": {
-    "caveman": {
+    "ask-matt": {
       "source": "mattpocock/skills",
       "sourceType": "github",
-      "skillPath": "skills/productivity/caveman/SKILL.md",
-      "computedHash": "934433479903febc585bf6deb5f0cebc63137e3f86b7babe0aab1ecb94d6d7a4"
+      "skillPath": "skills/engineering/ask-matt/SKILL.md",
+      "computedHash": "b2e8ef5ffc2f142022c1e1e1bba68073f0821356a8e1cf1b23670f61d13fe50b"
+    },
+    "code-review": {
+      "source": "mattpocock/skills",
+      "sourceType": "github",
+      "skillPath": "skills/engineering/code-review/SKILL.md",
+      "computedHash": "56a409d679605958439d1e9ca6c11c29835a4be95584825967ea4a491803ebd2"
     },
     "codebase-design": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/engineering/codebase-design/SKILL.md",
-      "computedHash": "2426dc4accf1a85dedfb560edb3a877ec8828b7375ea08c970df2b6c900a2a22"
+      "computedHash": "6d9d51d8caa01633fd00cf87089c5618c982321f942ac69f62565dc001c6b22f"
     },
-    "diagnose": {
+    "diagnosing-bugs": {
       "source": "mattpocock/skills",
       "sourceType": "github",
-      "skillPath": "skills/engineering/diagnose/SKILL.md",
-      "computedHash": "15939a26f86edec2d4862042b8564e5a062cb81d04e047a0cea6305c8830b5f5"
+      "skillPath": "skills/engineering/diagnosing-bugs/SKILL.md",
+      "computedHash": "fd6c99466b7ba43be624e6e66ed6d7af2796ded7218f24c83820823977819e22"
     },
     "domain-modeling": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/engineering/domain-modeling/SKILL.md",
-      "computedHash": "67343881f5def98487d56243155716110afbcbf22ec92421c882d532b941cb17"
+      "computedHash": "363cb0f53b0b431e7c00086ad1f823500b7e1b70b5616ee969c979f0934e9e6e"
+    },
+    "git-guardrails-claude-code": {
+      "source": "mattpocock/skills",
+      "sourceType": "github",
+      "skillPath": "skills/misc/git-guardrails-claude-code/SKILL.md",
+      "computedHash": "8c29552c621da0121427306afd92f8e02f47f446cdb0b55ceae01de6879fcb3a"
     },
     "grill-me": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/productivity/grill-me/SKILL.md",
-      "computedHash": "784f0dbb7403b0f00324bce9a112f715342777a0daee7bbb7385f9c6f0a170ea"
+      "computedHash": "f361db4e15e6bfd562a9282b1dccda513910a50061f9e838ce017be9c69dde3f"
     },
     "grill-with-docs": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/engineering/grill-with-docs/SKILL.md",
-      "computedHash": "1adf321072f53cce3dcaf5357d91b8230d4aa647bb8a51756745337a6ee567b8"
+      "computedHash": "9c460cbd94fd3c63cdef967dbdb6e66ca687103cdc380cd37834e4d10b738f78"
     },
     "grilling": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/productivity/grilling/SKILL.md",
-      "computedHash": "ef685a6fa0bbe73b05bbd8dc1ec97258191587f07c6aa7dbc9006675ceb8f90f"
+      "computedHash": "4ebdd12fe61ff3abf20cff6683740e2b9b3739454be0a3f4a928a1c4d07d6b34"
     },
     "handoff": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/productivity/handoff/SKILL.md",
-      "computedHash": "d543685cbfb0c64b7bc51a8dc3465975528da9b64f987f863765973b2f3867ab"
+      "computedHash": "ad03e8d4ea3cbbff66420eb7ba3cc375b5cbe1821a2449b53e863256cf5b5cde"
+    },
+    "implement": {
+      "source": "mattpocock/skills",
+      "sourceType": "github",
+      "skillPath": "skills/engineering/implement/SKILL.md",
+      "computedHash": "2139cfedf24791adbc839aaab6019cff158af1e28bfead020ec6e0ce01b3e74d"
     },
     "improve-codebase-architecture": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/engineering/improve-codebase-architecture/SKILL.md",
-      "computedHash": "c77b86b4332919499608f9af1880074e1fec65a59b95c70c27a9f39cd137865e"
+      "computedHash": "66e8a50c83c3c724fcfe0769701b665c56cec220cc4f49cc1aee8bdfc07de94a"
     },
     "prototype": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/engineering/prototype/SKILL.md",
-      "computedHash": "e4d0c8f8cb3fc096ee99405a15491da466545cf4a3694bee5a0c9db2fa621a43"
+      "computedHash": "73862de6cd32acf30799bfb2220357b96c1a58ab0e3d01126b769fd659d6555a"
+    },
+    "research": {
+      "source": "mattpocock/skills",
+      "sourceType": "github",
+      "skillPath": "skills/engineering/research/SKILL.md",
+      "computedHash": "bd3e2c6826671d82c86ed0da3dac3370ebcf63b0fe847f91bb444e1fb7dac21b"
+    },
+    "resolving-merge-conflicts": {
+      "source": "mattpocock/skills",
+      "sourceType": "github",
+      "skillPath": "skills/engineering/resolving-merge-conflicts/SKILL.md",
+      "computedHash": "28aad6f8b1b7025abc8892fa8890f68fe1533499b28a565f416b159131d22fad"
     },
     "setup-matt-pocock-skills": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/engineering/setup-matt-pocock-skills/SKILL.md",
-      "computedHash": "0164a8b1ef998abca426056c6ed8a7716a9d4692fc6daa5378f68381a6dafd24"
+      "computedHash": "f9c2b933dda18eea572e96f6ebbcd5b30e0d1bfdc074af53cc99728dc5f0bdac"
     },
     "tdd": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/engineering/tdd/SKILL.md",
-      "computedHash": "15a7b5e36383ebadb2dec5e586679e55e9663d292da418926b8da6fc0ef27d84"
+      "computedHash": "614ac2e45fb0ec02f6ce422d26bd9aa4e33aa4867323f5a3a5c0c20b96f78ff4"
+    },
+    "teach": {
+      "source": "mattpocock/skills",
+      "sourceType": "github",
+      "skillPath": "skills/productivity/teach/SKILL.md",
+      "computedHash": "68999bb1a241384b2f921f3321d779b7d05eb6089077b70d88cee2aee3d75ccc"
+    },
+    "to-questionnaire": {
+      "source": "mattpocock/skills",
+      "sourceType": "github",
+      "skillPath": "skills/productivity/to-questionnaire/SKILL.md",
+      "computedHash": "d8938509f3400d9977343e11e876fc6e1982b0b9c133a2f2e9d3d730a67a103e"
     },
-    "to-issues": {
+    "to-spec": {
       "source": "mattpocock/skills",
       "sourceType": "github",
-      "skillPath": "skills/engineering/to-issues/SKILL.md",
-      "computedHash": "47f648f3414848ccfc62cb41d2828b7e575fb5e7cbd6c4bdf630c063b5dc5e82"
+      "skillPath": "skills/engineering/to-spec/SKILL.md",
+      "computedHash": "7e07d4cfabd1a4f61627ebe2705601784fae7b9aca7e13af3e201ace75738200"
     },
-    "to-prd": {
+    "to-tickets": {
       "source": "mattpocock/skills",
       "sourceType": "github",
-      "skillPath": "skills/engineering/to-prd/SKILL.md",
-      "computedHash": "6d741474efd4bc3db55fabc2722ed78ca9c374cabcb6212936d79d4fd4a30fcb"
+      "skillPath": "skills/engineering/to-tickets/SKILL.md",
+      "computedHash": "0349eee265e7005e667b4543de849672106c46d545e998f37d3319300bb07751"
     },
     "triage": {
       "source": "mattpocock/skills",
       "sourceType": "github",
       "skillPath": "skills/engineering/triage/SKILL.md",
-      "computedHash": "2b6efb6da12d92551772fcc04acf331f4e0e6f7bd9d4cb23ce0b301e0b128feb"
+      "computedHash": "1bc5349f0b61e19a6df61496b5a03d88cd69595dd303353f87945997a9e4a884"
+    },
+    "wait-what": {
+      "source": "mattpocock/skills",
+      "sourceType": "github",
+      "skillPath": "skills/productivity/wait-what/SKILL.md",
+      "computedHash": "9638acdcd76457ca70a007b5a02c4bf44893fb3064692a9158d907e82f200eec"
+    },
+    "wayfinder": {
+      "source": "mattpocock/skills",
+      "sourceType": "github",
+      "skillPath": "skills/engineering/wayfinder/SKILL.md",
+      "computedHash": "f343ecf46157cb645a5494644418308ad95391e9fc696faa47ae5a412bf5f6e4"
     },
-    "write-a-skill": {
+    "wizard": {
       "source": "mattpocock/skills",
       "sourceType": "github",
-      "skillPath": "skills/productivity/write-a-skill/SKILL.md",
-      "computedHash": "b44d8aab2ead83c716e01af4c9a24ccc4575ce70ad58ec4f1749fb88c9cc82ba"
+      "skillPath": "skills/engineering/wizard/SKILL.md",
+      "computedHash": "3cfe7e22cba6a19a8b73e3bc231970202b26db82e1ac44aa16ad592e8a1897b3"
     },
-    "zoom-out": {
+    "writing-for-agents": {
       "source": "mattpocock/skills",
       "sourceType": "github",
-      "skillPath": "skills/engineering/zoom-out/SKILL.md",
-      "computedHash": "8357aeaece3b709c442eab67e64b86844e05e2f1ea95b109565eba50b6def36e"
+      "skillPath": "skills/productivity/writing-for-agents/SKILL.md",
+      "computedHash": "29b5360d2a4539cd565d0dd683c4971dedb3c405e40038462e582282976eceb1"
     }
   }
 }