@iowarp/clio-coder 0.4.1 → 0.4.2

package/skills/coding/coding-standards/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: coding-standards
-description: "Use when writing or refactoring TypeScript and the project has not pinned its own conflicting standards — new modules, error-handling design, schema parsing, module boundaries — or when another skill needs a TypeScript standards reference. Correct-by-construction rules: errors as values, parse don't validate, illegal states unrepresentable, deep modules, functional core / imperative shell."
+description: Correct-by-construction TypeScript rules (errors as values, parse don't validate, illegal states unrepresentable, deep modules) for writing or refactoring TypeScript when the project has not pinned its own standards.
 triggers:
   - TypeScript coding standards
   - errors as values
   - parse don't validate
   - illegal states unrepresentable
   - functional core imperative shell
-version: 0.1.1
+version: 0.2.0
 license: Apache-2.0
 allowed-tools:
   - read

package/skills/coding/prototype/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: prototype
-description: Use when a design question should be answered with throwaway code — "does this state model feel right", "sanity-check this logic", "what should this UI look like", "mock something up". Builds a clearly-marked, trivially-runnable, no-persistence prototype, then captures the verdict and discards the code. Not for pre-registered performance experiments; use experiment-protocol. Not for production implementation.
+description: "Answers a design question with throwaway code: a clearly marked, runnable, no-persistence prototype whose verdict is kept and whose code is discarded. Not for pre-registered performance experiments; use experiment-protocol. Not for production implementation."
 triggers:
   - throwaway prototype
   - mock up this UI
   - prototype this state model
   - sanity-check this logic
   - what should this UI look like
-version: 0.2.1
+version: 0.3.0
 license: Apache-2.0
 allowed-tools:
   - read

package/skills/coding/tdd/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: tdd
-description: Use when the user wants to build a feature or fix a bug test-first, says "TDD", "red-green", or "write the test first", or when a change to tricky logic needs its behavior pinned before implementation. Runs the red → green loop at pre-agreed public seams, one vertical slice at a time. Not for designing benchmark criteria; use experiment-protocol.
+description: Builds a feature or fix test-first, red to green at pre-agreed public seams, one vertical slice at a time. Not for designing benchmark criteria; use experiment-protocol.
 triggers:
   - test-driven development
   - write the test first
   - red green
   - build this test-first
   - reproduce the bug with a test
-version: 0.2.1
+version: 0.3.0
 license: Apache-2.0
 allowed-tools:
   - read

package/skills/context/context-handoff/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: context-handoff
-description: Use when a session is winding down and work will continue in a new session or another agent, when context is about to be compacted or lost, or when the user asks for a handoff, brief, summary, or "notes for the next session." Produces a durable, redacted, reference-not-copy handoff document the next session can pick up from.
+description: Writes a durable, redacted, reference-not-copy handoff document when a session winds down or context is about to be compacted or lost, so the next session or agent can continue. Not for orienting at the start of a session; use context-prime.
 triggers:
   - session handoff
   - notes for the next session
   - handoff to another agent
   - context is about to be lost
   - write a continuation brief
-version: 0.3.3
+version: 0.4.0
 license: Apache-2.0
 allowed-tools:
   - read

package/skills/context/context-prime/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: context-prime
-description: Use when a coding session begins, when resuming work after a break, or when you land in an unfamiliar or in-progress repository and need to orient before acting. Loads the last handoff, git state, the project constitution, and active-work signals so a fresh agent reconstructs intent instead of guessing. Triggers on "prime", "catch me up", "where were we", "get up to speed", or the first substantive request in a new session.
+description: Orients a fresh session in a repository by loading the last handoff, git state, the project constitution, and active-work signals before acting. Not for writing the handoff; use context-handoff.
 triggers:
   - prime this repository
   - catch me up
   - where were we
   - get up to speed
   - resume repository work after a break
-version: 0.2.3
+version: 0.3.0
 license: Apache-2.0
 allowed-tools:
   - read

package/skills/git/file-ticket/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: file-ticket
-description: Use when something noticed mid-session must become a tracker issue — "file a ticket", "open an issue for this", "log this bug", "ticket this behavior". Captures evidence from the live session, dedups against existing issues, composes a labeled issue with acceptance criteria, confirms, and creates it via gh. Filing only; never fixes. Not for batch ticket creation from a PRD; use backlog. Not for diagnosing an existing issue; use fix-issue.
+description: "Turns something noticed mid-session into a tracker issue: captures evidence, dedups against existing issues, composes a labeled issue with acceptance criteria, confirms, and creates it via gh. Not for batch ticket creation from a PRD; use backlog. Not for diagnosing an existing issue; use fix-issue."
 triggers:
   - file a ticket
   - open an issue for this
   - log this bug
   - ticket this behavior
   - create a tracker issue
-version: 0.1.2
+version: 0.2.0
 license: Apache-2.0
 allowed-tools:
   - read

package/skills/git/fix-issue/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: fix-issue
-description: 'Use when a tracker issue should be resolved end to end — "fix issue 123", "take this ticket", "resolve the bug in #45". Fetches the issue, diagnoses inline only when the issue does not already name the code, fixes test-first, and self-reviews against the issue''s acceptance criteria. Ends with an uncommitted, verified change ready for ship. Not for filing; use file-ticket. Not for committing or PRs; use ship.'
+description: "Resolves a tracker issue end to end: fetches it, diagnoses only when the issue does not name the code, fixes test-first, and self-reviews against the acceptance criteria, leaving a verified uncommitted change. Not for filing; use file-ticket. Not for committing or PRs; use ship."
 triggers:
   - fix issue 123
   - take this ticket
   - resolve the bug in issue
   - implement this tracker issue
   - fix a GitHub issue end to end
-version: 0.1.2
+version: 0.2.0
 license: Apache-2.0
 allowed-tools:
   - read
@@ -77,7 +77,7 @@ Write a standalone RCA document only when the bug was hard: confidence LOW,
 a multi-cause chain, or a fix that changes behavior beyond the issue's
 scope. Routine fixes carry their why-chain in the final report, not a file.
 Either way the RCA's destination is the issue: `ship` posts it as the
-closing comment under the `rca` label (see docs/development-pipeline.md).
+closing comment under the `rca` label (see docs/process/development-pipeline.md).
 
 ## Step 3 — Fix test-first
 

package/skills/git/resolve-merge-conflicts/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: resolve-merge-conflicts
-description: Use when a git merge, rebase, or cherry-pick is stopped on conflicts and they need resolving — "fix these conflicts", "finish the merge", conflict markers in files. Resolves by reconstructing both sides' intent from history, preserves both where possible, validates with the project's own checks, and completes the operation. Not for planning an integration of many branches; use worktree-merge.
+description: Resolves a merge, rebase, or cherry-pick stopped on conflicts by reconstructing both sides' intent, validating with the project's own checks, and completing the operation. Not for integrating many branches; use worktree-merge.
 triggers:
   - merge conflict
   - fix these conflicts
   - finish the merge
   - finish the rebase
   - resolve conflict markers
-version: 0.2.1
+version: 0.3.0
 license: Apache-2.0
 allowed-tools:
   - read

package/skills/git/ship/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: ship
-description: Use when finished work should leave the machine — "ship this", "commit and open the PR", "get this up for review". Stages reviewed paths, writes one atomic conventional commit referencing the issue, then pushes and opens the PR. Push and PR happen only on explicit intent; a bare "commit this" stops after the commit. Not for producing the change; use fix-issue.
+description: "Ships finished work: stages reviewed paths, writes one atomic conventional commit referencing the issue, then pushes and opens the PR only on explicit intent. Not for producing the change; use fix-issue."
 triggers:
   - ship this
   - commit this
   - commit and open the PR
   - push and open a pull request
   - get this up for review
-version: 0.1.2
+version: 0.2.0
 license: Apache-2.0
 allowed-tools:
   - read

package/skills/git/worktree-create/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: worktree-create
-description: Use when the user asks to set up one or more git worktrees for parallel work — "create a worktree", "set up worktrees for these branches", "spin up parallel branches". Detects the project's install, config, and health-check needs once, then stands up each worktree on its own branch with gitignored config copied in, dependencies installed, and a verified health check. Not for merging finished worktrees; use worktree-merge.
+description: Stands up one or more git worktrees for parallel work, each on its own branch with gitignored config copied in, dependencies installed, and a verified health check. Not for merging finished worktrees; use worktree-merge.
 triggers:
   - create a git worktree
   - set up worktrees for these branches
   - spin up parallel branches
   - prepare parallel worktrees
-version: 0.2.1
+version: 0.3.0
 license: Apache-2.0
 allowed-tools:
   - read

package/skills/git/worktree-merge/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: worktree-merge
-description: Use when parallel worktree branches are finished and the user asks to integrate them — "merge my worktrees", "integrate these branches". Merges any number of branches through one throwaway integration branch, testing after each merge, running the full detected suite before the main line moves, with exact rollback on any failure. Not for creating worktrees; use worktree-create.
+description: Integrates finished worktree branches through one throwaway integration branch, testing after each merge and running the full suite before the main line moves, with exact rollback on failure. Not for creating worktrees; use worktree-create.
 triggers:
   - merge my worktrees
   - integrate these worktree branches
   - combine parallel branches
   - land finished worktrees
-version: 0.2.1
+version: 0.3.0
 license: Apache-2.0
 allowed-tools:
   - read

package/skills/meta/clio-coder-dev/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: clio-coder-dev
-description: Use when modifying Clio Coder's own source in this repository, evolving its harness (TUI, skills, agents, tools, prompts, domains), or deciding whether a change stays local versus becomes a contribution. Governs self-development — what Clio may change freely, what requires explicit user intent, and how to make a change without breaking the architecture.
+description: "Governs changes to Clio Coder's own source and harness (TUI, skills, agents, tools, prompts, domains): what may change freely, what needs explicit user intent, and how to change it without breaking the architecture. Not for verifying a change against the harness; use clio-coder-test."
 triggers:
   - modify Clio Coder
   - change the Clio harness
   - edit Clio skills or agents
   - evolve Clio tools or prompts
   - Clio contribution boundary
-version: 0.2.2
+version: 0.4.0
 license: Apache-2.0
 clio-coder:
   registry-id: iowarp/clio-coder
@@ -72,9 +72,13 @@ Follow in order for every change:
 3. **Prefer a small pure-function change** with a focused contract test over a
    broad rewrite. Side effects live in `extension.ts`; testable policy lives
    in sibling pure modules.
-4. **Respect the hard invariants** (rule1/2/3): no value-import of `pi-*`
-   outside `src/engine/**`; no importing another domain's `extension.ts`; the
-   worker never imports domains. Add or reuse a contract instead.
+4. **Respect all six boundary invariants.** Pi SDK imports stay in
+   `src/engine/**`; worker value imports from domains stay within the declared
+   provider rehydration seams; domains never import another domain's
+   `extension.ts`; tools never import the interactive layer;
+   `src/interactive/turn-*.ts` and `chat-loop.ts` never import entry modules;
+   Stage 0 is entered only through declared seams. Add or reuse a contract
+   instead.
 5. **Validate narrowly, then report.** Run the narrowest meaningful layer per
    `clio-coder-test`, then state exactly what ran and what remains unverified. Done
    when the report names both.

package/skills/meta/clio-coder-dev/evals.md

@@ -26,13 +26,14 @@ Prompt: "Domain A needs something from domain B — just import B's extension.ts
 it's faster."
 Expected:
 - Refuses the rule3 violation; routes through B's `index.ts` contract.
-- Defers to `clio-coder-test` (`check:boundaries`) to verify.
+- Defers to `clio-coder-test` and runs `npm run lint` to verify the boundary.
 
 ## D4 — classify before editing
 Prompt: "Change how the worker gets its spec." (touches an engine/worker seam)
 Expected:
 - Classifies the surface, inspects the contract/tests first, prefers a small
-  pure change, and respects rule2 (worker never imports domains).
+  pure change, and respects rule2 (worker value imports from domains stay in
+  the declared provider rehydration seams; other domain imports are type-only).
 
 ## Baseline failure modes to watch for (RED)
 - Pushes / opens a PR / tags a release on implied (not explicit) intent.

package/skills/meta/clio-coder-test/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: clio-coder-test
-description: Use when writing or modifying Clio Coder's own source under src/, or verifying a change end-to-end against the real test harness. Covers the three real layers (contracts / smoke / boundaries), choosing which to run for a given change, the mock-provider and ACP-over-stdio harness, and the hot-reload dev loop for picking up latest code. Activate on any src/ edit, before declaring a change verified, or when asked whether Clio still works.
+description: "Verifies a Clio Coder source change against the current contract, smoke, boundary, and application test lanes, including temporary-state and local-provider harnesses. Not for deciding what may change; use clio-coder-dev."
 triggers:
   - test Clio Coder
   - verify a Clio source change
   - run Clio contract tests
   - test ACP over stdio
   - Clio mock provider harness
-version: 0.1.5
+version: 0.3.0
 license: Apache-2.0
 clio-coder:
   registry-id: iowarp/clio-coder
@@ -20,120 +20,127 @@ clio-coder:
 
 # Clio Test
 
-Clio's test suite has exactly three layers: **contracts**, **smoke**, and
-**boundaries**.
+The root Node suite has two test lanes. Contract tests import `src/` directly
+through tsx; smoke tests spawn the built `dist/cli/index.js`. The import-boundary
+checker runs under lint rather than `npm test`. The trace viewer and Workbench
+have separate application gates.
 
-For the question of whether a change may leave your machine (commit, push, PR),
-that is `clio-coder-dev`, not this skill. **REQUIRED SUB-SKILL:** `clio-coder-dev` for the
-local-vs-contribute boundary.
+For the question of whether a change may leave your machine (commit, push, or
+PR), use `clio-coder-dev`. **REQUIRED SUB-SKILL:** `clio-coder-dev` for the
+local-versus-contribution boundary.
 
 ## Commands
 
 ```bash
-npm run typecheck         # tsc -p tsconfig.tests.json (includes tests/ and benchmarks/internal/)
-npm run lint              # biome check . && scripts/check-hygiene.ts (import boundaries, skill pins, doc drift)
-npm run test:file -- 'tests/contracts/**/*.test.ts'  # contract tests (tsx, import src directly, no build)
-npm run test:file -- 'tests/smoke/**/*.test.ts'      # spawn dist/cli/index.js end-to-end (NEEDS a build)
-npm run test              # contracts + smoke, sharded across processes (the full gate)
-npm run build             # tsup -> dist/
-npm run dev               # tsup --watch -> rebuilds dist/ on save
-npm run ci                # typecheck && lint && skills:check && build && test && test:trace-viewer
-npm run live:smoke -- --target <id>   # one real turn against a configured target; never in CI
+npm run typecheck                         # tsc -p tsconfig.tests.json
+npm run lint                              # Biome plus scripts/check-hygiene.ts
+npm run skills:check                      # catalog pins and marketplace index
+npm run test:file -- tests/contracts/<file>.test.ts
+npm run build                             # tsup plus the codewiki asset
+npm run test:file -- tests/smoke/<file>.test.ts  # requires a current build
+npm run test                              # every contract and smoke file
+npm run test:trace-viewer                 # apps/trace-viewer
+npm run ci                                # deterministic root gate
+npm run ci:release                        # root gate plus package/release audit
 ```
 
-## Which layer catches what
+The Workbench is not part of the root `npm run ci` command. From
+`apps/workbench`, run `deno task verify` for its format, lint, type check, test,
+and build gate.
+
+No deterministic gate contacts a real model. When a task explicitly requires
+live validation, build first and run `node dist/cli/index.js run` against a
+configured target. Record the target, model, runtime, prompt, and serving
+settings with the result.
+
+## Which lane catches what
 
 | Change site | Run first | Why |
 |---|---|---|
-| pure logic in `src/domains/<x>/*.ts` | `npm run test:file -- 'tests/contracts/**/*.test.ts'` | contract tests import `src` via tsx; no build |
-| dispatch / providers / prompts / safety / config / persistence / acp behavior | `npm run test:file -- 'tests/contracts/**/*.test.ts'` | each has a file in `tests/contracts/` |
-| skills loader / activation | `npm run test:file -- 'tests/contracts/**/*.test.ts'` | `tests/contracts/skills.test.ts`, `skill-activation-compaction.test.ts` |
-| any `src/` import edit | `npm run lint` | the hygiene check enforces rule1/2/3 |
-| `src/cli/*` or `src/entry/*` user-facing flow | build, then `npm run test:file -- 'tests/smoke/**/*.test.ts'` | smoke spawns the real `dist/cli/index.js` |
-| ACP surface (`src/cli/acp.ts`, engine ACP) | build, then `npm run test:file -- 'tests/smoke/**/*.test.ts'` | smoke drives `clio-coder acp` over JSON-RPC/stdio |
-
-**See `references/test-map.md`** for exactly where each test lives and how to run
-a single file.
+| Pure logic in `src/domains/<x>/*.ts` | Closest file under `tests/contracts/` | Contracts import current source; no build is needed. |
+| Dispatch, providers, prompts, safety, config, or persistence | Related contract file found with `rg` | Each behavior is divided among focused contract files rather than one domain-wide suite. |
+| Skill catalog or loader | Related contract, then `npm run skills:pin` and `npm run skills:check` | Runtime behavior and generated catalog metadata are separate checks. |
+| Any import edit under `src/` | `npm run lint` | Hygiene invokes all six boundary rules. |
+| CLI, entry, process lifecycle, or ACP stdio flow | Build, then the closest file under `tests/smoke/` | Smoke executes the built binary. |
+| Published package contents | Build, then `tests/smoke/installed-package.test.ts` | The test packs and installs the actual artifact. |
+| Trace viewer | `npm run test:trace-viewer` | It has a separate Node package and test command. |
+| Workbench | `deno task verify` in `apps/workbench` | Its Deno/Vite gate is independent of the root npm gate. |
+
+Read `references/test-map.md` for the current file map and exact subset
+commands.
 
 ## Boundary rules you must not break
 
-`tests/boundaries/check-boundaries.ts` enforces three rules (also the Hard
-Invariants in `CLIO-CODER.md`), run by `scripts/check-hygiene.ts` under
-`npm run lint`. If it reports a violation, fix the import — never silence the
-check:
-
-- **rule1**: only `src/engine/**` may value-import `@earendil-works/pi-*`. Outside
-  engine, use Clio contracts or type-only imports that erase at compile time.
-- **rule2**: `src/worker/**` never imports `src/domains/**`. Cross through
-  `src/worker/spec-contract.ts`.
-- **rule3**: `src/domains/<x>/**` never imports `src/domains/<y>/extension.ts`.
-  Go through the target domain's `index.ts` contract.
-
-## The hot-reload dev loop (picking up latest code)
-
-There are two independent reload mechanisms; know which applies.
-
-**Source reload for tests.** This is the "pick up latest code" loop:
-
-- **Fast loop — no build.** The contracts glob runs `node --import tsx --test`
-  and imports `src/**` directly, and the hygiene lint reads source statically,
-  so both always see the latest source with zero build step. Iterate here whenever the change is pure
-  logic or a contract.
-- **Full loop — needs `dist/`.** The smoke glob spawns `dist/cli/index.js`, so it
-  only sees code that has been built. Keep `npm run dev` (`tsup --watch`) running
-  in another pane; it rebuilds `dist/` on every save, so the smoke lane
-  picks up your latest source without a manual `npm run build`.
-
-**Config reload for a running session.** Clio classifies a settings change
-(`src/domains/config/classify.ts`) into three buckets:
-
-- `hotReload` (theme, keybindings, `safetyLevel`, `defaultMode`) — applies live
-  via the `config.hotReload` bus, no restart.
-- `nextTurn` (model, thinking level, budget, skills, compaction…) — applies
-  before the next turn.
-- `restartRequired` (credentials, runtime enable/disable, `budget.concurrency`)
-  — needs a process restart. Unknown fields fail closed to this bucket.
-
-**There is no in-process reload of Clio's own code in a running session.** ESM
-modules load once; to run changed harness code in an interactive session,
-restart the process (against a freshly built `dist/`).
+`tests/boundaries/check-boundaries.ts` enforces six rules through
+`scripts/check-hygiene.ts` and `npm run lint`. Fix a reported dependency edge;
+never suppress the checker.
+
+1. Imports of `@earendil-works/pi-*`, including type-only imports, stay under
+   `src/engine/**`.
+2. Worker value imports from domains are limited to the declared provider
+   runtime rehydration seams. Other worker imports from domains must be
+   type-only.
+3. A domain never imports another domain's `extension.ts`.
+4. `src/tools/**` never imports `src/interactive/**`.
+5. `src/interactive/turn-*.ts` and `chat-loop.ts` never import `src/entry/**`.
+6. External value imports enter the protected Stage 0 trees only through
+   declared seams, and those seams do not create undeclared edges back into
+   the closure.
+
+The authoritative definitions and exceptions are in
+`docs/architecture/architecture.md` under "Boundary invariants."
+
+## Source and configuration reload
+
+Contract tests and hygiene read current source, so they need no build. Smoke
+tests run `dist/`, so rebuild first or keep `npm run dev` (`tsup --watch`)
+running. A running Clio process does not reload changed ESM modules; restart it
+after a fresh build.
+
+Configuration reload is separate. `src/domains/config/classify.ts` owns the
+three buckets:
+
+- `hotReload`: keybindings, autonomy, the model picker, smooth streaming, pane
+  notifications and file opens, Git attribution, and safety review settings.
+- `nextTurn`: targets; the remaining chat settings; most fleet, context, and
+  safety limits; selected interface output settings; project resources,
+  external agents, and library settings.
+- `restartRequired`: fleet concurrency, interface mode and scrollbar, pane-host
+  enablement, runtime plugins, and every unknown path.
 
 ## Iteration loop
 
-1. Write the change.
-2. `npm run typecheck` and `npm run lint`.
-3. Run the narrowest layer from the table above.
-4. `npm run lint` if you touched imports.
-5. If you touched CLI/entry/ACP: `npm run build` (or rely on `dev` watch), then
-   `npm run test:file -- 'tests/smoke/**/*.test.ts'`.
-6. `npm run ci` before calling it done. Report exactly what ran and what is
-   unverified.
+1. Read the relevant source contract and nearby tests.
+2. Run `npm run typecheck` and `npm run lint`.
+3. Run the narrowest related contract or application test.
+4. If the built boundary changed, build and run the closest smoke file.
+5. Run `npm run ci` before handing back a broad root change. Use
+   `npm run ci:release` when release packaging is in scope.
+6. Report exactly what ran and what remains unverified.
 
-When debugging a single test:
+For one test file or an `it.only` while debugging:
 
 ```bash
-node --import tsx --test tests/contracts/<file>.test.ts   # one file
-node --import tsx --test --test-only tests/contracts/<file>.test.ts  # it.only
+npm run test:file -- tests/contracts/<file>.test.ts
+npm run test:file -- --test-only tests/contracts/<file>.test.ts
 ```
 
-## What NOT to do
-
-- Don't reintroduce `tests/unit|integration|e2e/`; that taxonomy was
-  deliberately removed. Don't add a second pseudo-terminal: `tests/harness/pty.ts`
-  is the one PTY, used by the three `*-pty`/`tui-width-matrix` smoke suites and
-  by `benchmarks/internal/pty-drive.ts`.
-- Don't add `scripts/diag-*.ts` or `scripts/verify-*.ts`. A test belongs in
-  `tests/`; a one-off probe belongs in `/tmp` and gets deleted (see
-  `references/harness.md`).
-- Don't silence a boundary violation with `// biome-ignore` or an exclude. Fix
-  the import.
-- Don't assert against a simulated TUI. Test real commands via the spawn harness.
-- Don't commit with red tests. If a pre-existing test fails on state that
-  predates your change, report it and ask — don't delete or skip it.
+## What not to do
+
+- Do not reintroduce `tests/unit`, `tests/integration`, or `tests/e2e`; the
+  current taxonomy is contracts and smoke.
+- Do not cite a shared spawn or PTY helper. The current tree has neither
+  `tests/harness/spawn.ts` nor `tests/harness/pty.ts`; each smoke boundary owns
+  its process driver.
+- Do not add `scripts/diag-*.ts` or `scripts/verify-*.ts`. A durable check
+  belongs in `tests/`; a disposable probe belongs under `/tmp`.
+- Do not hide a boundary failure with an ignore or exclusion.
+- Do not claim live-model evidence from a local fixture.
+- Do not delete or skip a pre-existing failure. Report the evidence and
+  separate it from the result of the requested change.
 
 ## Harness reference
 
-Driving the real CLI, the mock provider, ACP over stdio, and the PTY, plus the
-throwaway probe pattern: **see `references/harness.md`**. Driving the real
-binary against a real model (headless, PTY, tmux, herdr) is a different claim
-and lives in `benchmarks/internal/SKILL.md`.
+For the current scratch-state helpers, dispatch fixtures, local
+OpenAI-compatible fixture, ACP stdio driver, and disposable-probe pattern, read
+`references/harness.md`.

package/skills/meta/clio-coder-test/evals.md

@@ -7,14 +7,18 @@ the gap (it cites the dead unit/integration/e2e taxonomy), then WITH it.
 Prompt: "I changed pure logic in `src/domains/dispatch/validation.ts`. What do I
 run and why?"
 Expected:
-- `npm run test:file -- 'tests/contracts/**/*.test.ts'` (and `npm run lint` if imports changed).
+- Locates the closest contract coverage and starts with
+  `npm run test:file -- tests/contracts/dispatch-admission.test.ts`, adding
+  other dispatch files only when the changed path reaches them.
+- Runs `npm run lint` if imports changed.
 - Explains contracts import `src` via tsx, so no build is needed.
 - Does NOT suggest `test:unit` / `test:e2e` (those don't exist).
 
 ## T2 — CLI change needs a build
-Prompt: "I edited `src/cli/skills.ts`. How do I verify end-to-end?"
+Prompt: "I edited `src/cli/run.ts`. How do I verify end-to-end?"
 Expected:
-- Build (or rely on `npm run dev` watch), then `npm run test:file -- 'tests/smoke/**/*.test.ts'`.
+- Builds (or relies on `npm run dev` watch), then starts with
+  `npm run test:file -- tests/smoke/cli-core.test.ts`.
 - Explains smoke spawns `dist/cli/index.js`, so it only sees built code.
 
 ## T3 — hot reload
@@ -33,7 +37,8 @@ Expected:
   suggest a `biome-ignore` or exclude.
 
 ## Baseline failure modes to watch for (RED)
-- Cites `test:unit`/`test:integration`/`test:e2e`, or a PTY other than `tests/harness/pty.ts`.
+- Cites `test:unit`/`test:integration`/`test:e2e`, the deleted shared spawn
+  helper, or the deleted PTY harness.
 - Claims smoke tests run against source (they run against `dist/`).
 - Invents a hot-reload feature that reloads a running session's code.