@arbiterforge/ca-pi 0.6.0

package/plugins/ca-pi/skills/ca-audit/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: ca-audit
+description: Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.
+argument-hint: "[<from-ref> <to-ref> | --since-checkpoint | --since <date>]"
+---
+
+# /ca-audit — promotion packet
+
+Everything codeArbiter logs, it logs append-only and scattered: `overrides.log`, `triage.log`,
+`decisions/`, `sprint-log.md`, `checkpoints/`. This command assembles them into the one document a
+team lead, compliance reviewer, or auditor actually asks for: *what happened in this window, who
+authorized it, and what is still open.* Read-only over every source; its only write is the packet.
+
+## Window
+
+- `<from-ref> <to-ref>` — two tags/SHAs (e.g. `v1.2.0 v1.3.0`).
+- `--since-checkpoint` — from the `last-checkpoint` record to HEAD.
+- `--since <date>` — ISO date to HEAD.
+- No argument → from the most recent tag to HEAD (no tags → last checkpoint; neither → BLOCK and
+  ask for an explicit window).
+
+## Flow
+
+1. Resolve the window to a commit range and a time range; both appear in the packet header.
+2. Gather, citing each source file:
+   - **Commits** — `git log` over the range, grouped by Conventional-Commit type; merge commits
+     listed with their PR reference.
+   - **Overrides** — every `overrides.log` line in the time range, verbatim (including
+     `SECURITY-OVERRIDE` and `DEV:` entries), each with its `BY:` identity.
+   - **Triage** — every small-lane classification in `triage.log` in range.
+   - **Decisions** — ADRs created or superseded in range (from `decisions/` file dates and the
+     supersede chains), each with its Decided-by attribution.
+   - **Sprint auto-decisions** — entries from `sprint-log.md` in range; list every `low`-confidence
+     entry verbatim, count the `high` ones.
+   - **Open questions** — all currently-unresolved `[CONFIRM-NN]` items.
+   - **Checkpoint findings** — from the most recent `checkpoints/*.md`: findings still open.
+3. Write the packet to `<project-root>/.codearbiter/audits/<YYYY-MM-DD>.md` (second run the
+   same day appends `-2`, `-3`, … — an existing packet is never overwritten). Surface the path and
+   a three-line summary: commits, overrides, open items.
+
+## Hard gate
+
+Read-only over every source — MUST NOT modify any log, decision, or checkpoint while assembling.
+MUST NOT overwrite an existing packet. MUST quote override and low-confidence sprint entries
+verbatim — never paraphrase an audit line. An empty section is stated as empty, never omitted —
+"no overrides in window" is itself the finding.
+
+## When NOT to use
+
+- Live project state right now → `/ca-status`.
+- Triggering reviews → `/ca-checkpoint` (this command only reports what reviews already found).

package/plugins/ca-pi/skills/ca-btw/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: ca-btw
+description: Lightweight Q&A about the project — answer from context and return, no routing, no state change.
+argument-hint: "<question>"
+---
+
+# /ca-btw — quick Q&A
+
+The one exception to the slash-command pipeline. Answer the question and return. No skill is routed
+to, no agent dispatched, no file written. Always safe to invoke.
+
+## Flow
+
+1. Read `<project-root>/.codearbiter/` docs as needed to answer accurately — `CONTEXT.md`,
+   `tech-stack.md`, `coding-standards.md`, `security-controls.md`, `decisions/`, `specs/`, `plans/`.
+2. Answer directly and conversationally — not a formatted report.
+3. If the answer is not in context, say so plainly. Never guess.
+
+## Hard gate
+
+Read-only. MUST NOT write or modify any file, route to a skill, dispatch an agent, run tests, or
+resolve a `[CONFIRM-NN]`. If the question is really a request to build or fix something, say so and
+point to `/ca-feature` or `/ca-fix` — do not start implementation from `/ca-btw`.

package/plugins/ca-pi/skills/ca-checkpoint/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: ca-checkpoint
+description: Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report.
+argument-hint: (none)
+---
+
+# /ca-checkpoint — codebase sweep
+
+Periodic sweep of the entire codebase with the reviewer fleet, funneled to a single dated report. Surfaces findings — not a promotion gate, enforces no sign-off.
+
+## Flow
+
+1. Build the unit list — the same fleet as `/ca-review`, scoped to the whole codebase against the
+   `<project-root>/.codearbiter/` docs:
+
+   | Reviewer | Reads |
+   |---|---|
+   | `security-reviewer` | `security-controls.md`; reviews security posture |
+   | `auth-crypto-reviewer` | `security-controls.md`; authn/crypto/key/secret paths |
+   | `dependency-reviewer` | dependency manifests; license + supply-chain posture |
+   | `migration-reviewer` | migration history; safety + classification |
+   | `coverage-auditor` | test coverage vs. obligations across the tree |
+   | `architecture-drift-reviewer` | `decisions/`; drift between code and accepted ADRs |
+
+2. Route to `dispatching-parallel-agents` (`<plugin-root>/routines/dispatching-parallel-agents/SKILL.md`) with that unit list (read-only batch). It dedupes, then
+   funnels through `finding-triage` → `checkpoint-aggregator`.
+3. `checkpoint-aggregator` writes the dated report to
+   `<project-root>/.codearbiter/checkpoints/YYYY-MM-DD.md`: findings by severity with
+   file:line, and out-of-scope items marked inline `[NEEDS-TRIAGE]`.
+4. Write the current override **count** to `<project-root>/.codearbiter/last-checkpoint` — the
+   integer baseline the startup briefing subtracts for its overrides-since-checkpoint counter. The value is
+   the number of non-comment, non-blank lines in `overrides.log` at this moment (`0` if the log is
+   absent). This re-zeros the `over:N` segment until the next `/ca-override`. Write a bare integer,
+   not a timestamp — the briefing treats any value above the current total as stale and falls back
+   to showing every override.
+5. Report the checkpoint path.
+
+## Hard gate
+
+Read-only except writing the checkpoint doc and `last-checkpoint` — MUST NOT modify code. MUST NOT
+consume raw reviewer output — only the `finding-triage` → `checkpoint-aggregator` verdict. MUST NOT
+resolve a `[CONFIRM-NN]` surfaced during the sweep by guessing. The report surfaces findings; it does
+not block or sign off anything.
+
+## When NOT to use
+
+- Reviewing just the current diff → `/ca-review`.
+- A pre-implementation threat model → `/ca-threat-model`.
+- ADR health only → `/ca-adr-status`.
+- A whole-codebase deep audit → `/ca-tribunal` (checkpoint is the lean periodic sweep; tribunal its rare deep counterpart).

package/plugins/ca-pi/skills/ca-chore/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: ca-chore
+description: Sanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose.
+argument-hint: "<docs|deps|revert> <description or SHA>"
+---
+
+# /ca-chore — non-behavioral change lane
+
+The sanctioned path for work that has no behavioral surface to test-drive. Three types, each with
+the gates that fit it — and nothing it doesn't need. Everything still exits through `commit-gate`
+(classification `docs` / `chore` / `revert`) and lands via branch/PR.
+
+## Types
+
+**docs** — README, comments, CHANGELOG, `.codearbiter/` prose, typo fixes.
+- Gates: secrets scan over the diff; diff review (no behavioral code change smuggled in);
+  anti-slop copy pass on any user-facing doc in the change; `commit-gate`.
+- **Anti-slop copy pass** — for any user-facing doc the change touches (repo-root community docs
+  and `docs/**`; not codeArbiter's own framework bodies), load
+  `<plugin-root>/includes/anti-slop-design/INDEX.md`, then `core.md` and the
+  `medium-documents` leaf (§7.A.1), and run the §3.A em-dash ban and the §3.B copy self-audit over
+  the authored prose before `commit-gate`. The `H-13` PostToolUse reminder surfaces §3.A separator
+  dashes as you write, so the pass is a confirmation, not a discovery.
+- No `tdd` — prose has no failing test to write.
+
+**deps** — bump an existing dependency's version (manifest + lockfile together, never one without
+the other).
+- Gates: dispatch `dependency-reviewer` (same vetting as `/ca-add-dep` — license, provenance,
+  supply chain, changelog of the bump); full test suite green after the bump; `commit-gate`.
+- A bump that requires code changes to adopt is not a chore — route the code change through
+  `/ca-feature` or `/ca-fix`.
+
+**revert** — back out a named commit.
+- Gates: `git revert <SHA>` (never hand-edited backout); full suite green after the revert; the
+  commit message references the reverted SHA and the reason; `commit-gate`.
+- No new regression test demanded — the revert restores already-tested behavior. If the revert is
+  fixing a defect the suite missed, open `/ca-fix` afterward to pin it.
+
+## Flow
+
+1. Classify `$ARGUMENTS` into one of the three types. Anything with a behavioral code change beyond
+   a mechanical revert is NOT a chore — redirect to `/ca-feature` or `/ca-fix` and stop.
+2. Run the type's gates above.
+3. Exit through `commit-gate` with the matching classification, then
+   `finishing-a-development-branch` as usual.
+
+## Hard gate
+
+MUST reject a change containing behavioral code (beyond the revert itself) — that is `/ca-feature`
+or `/ca-fix` territory. MUST keep manifest and lockfile changes in the same commit for `deps`.
+MUST run the full suite for `deps` and `revert`. MUST run the anti-slop copy pass on any user-facing
+doc a `docs` change authors or edits. Never skips `commit-gate`.
+
+## When NOT to use
+
+- Any new or changed behavior → `/ca-feature` / `/ca-fix`.
+- Adding a NEW dependency → `/ca-add-dep`.
+- Restructuring code → `/ca-refactor`.

package/plugins/ca-pi/skills/ca-cleanup/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: ca-cleanup
+description: Finish an already-merged branch — classify the leftover artifacts, return to a fast-forwarded default checkout, and delete the merged local branch. Every discard confirmed per item; containment proven, never assumed.
+argument-hint: (none)
+---
+
+# /ca-cleanup — post-merge branch transition
+
+Your PR merged. You are still standing on the branch, with build output, worktree
+residue, and scratch files around you. This command owns the ordinary walk back:
+prove the branch actually landed, decide what the leftovers are, get to a clean
+fast-forwarded default checkout, and drop the merged local branch.
+
+It exists because nothing else owned it. `/ca-standup` is daily hygiene and
+deliberately never touches the current branch or the default one;
+`/ca-chore` takes docs, dependency bumps, and reverts. Issue #308 recorded
+what the gap produced: a routine cleanup routed to `/ca-chore`, which
+refused it, and then to `/ca-override` — a bypass invented to cover missing
+coverage. This is that coverage.
+
+## Routes to
+
+The `post-merge-cleanup` skill (`<plugin-root>/routines/post-merge-cleanup/SKILL.md`),
+which owns the containment proof, the artifact classification, and the per-item
+confirmations.
+
+## When NOT to use
+
+- The branch has NOT merged yet → `/ca-pr` (`finishing-a-development-branch`)
+  owns the terminal decision; come back here after it lands.
+- Daily start-of-day hygiene across *other* branches and worktrees →
+  `/ca-standup`.
+- A read-only look at what is dirty → `/ca-status`.
+- Uncommitted work you want to keep → `/ca-commit`. This command never
+  commits for you.
+
+## Hard gate
+
+- MUST prove the current branch is contained in the **fetched** default branch —
+  SHA-ancestry, or a squash-merge proven by the merged PR record (`headRefOid`
+  == HEAD) — before anything is deleted. An unproven or unfetched comparison
+  STOPs — a branch that only *looks* merged is not merged.
+- MUST classify every dirty or untracked artifact as **unique**, **redundant**,
+  or **superseded**, and MUST NOT discard a unique or unclassifiable one without
+  explicit per-item confirmation naming it.
+- MUST confirm each removal individually — no batched yes, no implied yes.
+- MUST reach the default branch with a clean working tree, and MUST fast-forward
+  with `--ff-only` only — never a merge commit, never a rebase, never a reset
+  that discards work.
+- MUST use `git branch -d`, and MAY use `-D` only when the squash-merge PR-record
+  proof held this run and `-d` refused, with that proof restated and the branch
+  named in the confirmation. MUST NOT otherwise force-delete a branch, force-push,
+  delete a remote branch, or write to the default branch.
+- MUST NOT require `/ca-override`. This is ordinary lifecycle work; if it
+  cannot proceed, the reason is a stated gate, not a bypass.

package/plugins/ca-pi/skills/ca-commands/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: ca-commands
+description: Show the codeArbiter command catalog — the public command list and what each routes to.
+argument-hint: (none)
+---
+
+# /ca-commands — command catalog
+
+Present the public command list. Read-only, no state change.
+
+## Flow
+
+1. Read the quick-reference table from `<plugin-root>/COMMANDS.md` — the single source of truth
+   for the catalog.
+2. Output that table only — command, one-line description, route. No prose walkthrough, and no
+   second copy maintained here (a hard-coded table drifts against `COMMANDS.md`).
+
+## Hard gate
+
+Read-only. MUST NOT modify a file or route to a skill. MUST render from `COMMANDS.md`, never from a
+catalog copied into this file. Output the catalog only.

package/plugins/ca-pi/skills/ca-commit/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: ca-commit
+description: Run the full commit gate — the only sanctioned path to a git commit.
+argument-hint: (none)
+---
+
+# /ca-commit — commit gate
+
+The only path to a commit. The orchestrator issues no `git commit` without the `commit-gate` skill
+clearing first. "It looks good" is not authorization. No arguments — the skill reads current git
+state (staged files, diff, test results) and decides whether every gate is green.
+
+## Routes to
+
+The `commit-gate` skill (`<plugin-root>/routines/commit-gate/SKILL.md`) — all phases. The skill
+is canonical for its phases, gates, and output format.
+
+## When NOT to use
+
+- Before writing code → `/ca-feature` or `/ca-fix` first.
+- To check PR readiness → `/ca-pr` (dispatches additional BLOCK-level reviewers).
+- To run tests without committing → run the test command from `tech-stack.md` directly.
+
+## Hard gate
+
+MUST NOT commit without `commit-gate` clearing. MUST NOT commit if the project test suite is not
+green.

package/plugins/ca-pi/skills/ca-conflict/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: ca-conflict
+description: Stop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation.
+argument-hint: (none)
+---
+
+# /ca-conflict — conflict protocol
+
+Orchestrator protocol, not a skill route. When a rule conflict surfaces — the persona, a `.codearbiter/` document, and code contradict each other, or two docs contradict each other — all other work STOPs and the conflict is presented for the user to resolve. The orchestrator never picks a side.
+
+## Flow
+
+1. **Halt** — suspend the in-progress task. No partial progress.
+2. **Identify** the conflicting sources (A and B): which document, file, or rule each is.
+3. **Quote** the exact passages side by side.
+4. **Classify** the conflict against the §2 conflict-resolution hierarchy and name the level the
+   tension sits at. Note which source was more recently updated — informational, not determinative.
+5. **Present** and wait. Work resumes only after the user explicitly resolves.
+
+## Output
+
+```
+## Conflict detected — work halted
+
+### Source A
+File: <path> · Last updated: <date>
+> <exact quoted text>
+
+### Source B
+File: <path> · Last updated: <date>
+> <exact quoted text>
+
+### Nature of conflict
+<what the two sources disagree about>
+
+### Conflict-hierarchy level
+Level N — <why the tension sits here>
+
+### To resolve
+<options — update A, update B, or supersede one via an ADR>
+
+---
+Work is halted. Resolve before the orchestrator proceeds.
+```
+
+## When routed automatically
+
+The orchestrator surfaces a conflict on its own when the persona and a `.codearbiter/` doc contradict
+each other, two docs contradict, code contradicts an accepted ADR, a new ADR contradicts an accepted
+one, or a task instruction contradicts a hard gate.
+
+## After resolution
+
+The orchestrator records the resolution; if the user authorized a doc update, it makes that update
+(the one sanctioned side effect) and resumes from the suspension point.
+
+## Hard gate
+
+MUST stop ALL other work. MUST NOT pick a side without explicit user instruction. MUST NOT decide by
+recency alone. MUST NOT silently continue past a detected conflict. If the conflict involves a guessed
+or auto-resolved `[CONFIRM-NN]`, flag that as a separate critical finding.

package/plugins/ca-pi/skills/ca-context-check/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: ca-context-check
+description: Optional manual drift audit — report stale provenance-tracked docs, then per stale doc offer re-scout, re-baseline, or defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
+argument-hint: (none)
+---
+
+# /ca-context-check — manual drift audit
+
+An optional, on-demand audit for bypass cases: a merge or external edit
+changed a tracked source file you are not about to commit, so commit-gate's
+auto-heal did not fire. Routes to the `context-check` skill.
+
+## When to use
+
+Use this only when you believe drift was introduced outside a commit (e.g. a
+direct push, a merge you did not author, a manual file edit while outside a
+normal commit workflow). The SessionStart drift line (backed by
+`startup_drift_line`) is the usual signal that this check is warranted.
+
+## When NOT to use
+
+- **Routine maintenance** — commit-gate auto-heal runs automatically on every
+  commit that touches a `drift_trigger` source. No manual intervention needed
+  for the common case.
+- Full brownfield re-scan from scratch → `/ca-create-context`.
+- Project state snapshot → `/ca-status`.
+
+## Hard gate
+
+Read-only unless the user explicitly chooses re-scout (partial scout run) or
+re-baseline (hash update in `.codearbiter/.provenance/`). MUST NOT commit on
+its own. MUST NOT modify any derived doc without an explicit user selection.

package/plugins/ca-pi/skills/ca-create-context/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: ca-create-context
+description: Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.
+argument-hint: (none)
+---
+
+# /ca-create-context — brownfield populate
+
+Wraps an existing codebase in project state without guessing. Dispatches parallel scouts to read the repository, synthesizes their findings into the surviving `.codearbiter/` doc set, resolves gaps via a targeted interview, and locks the project initialized. No arguments — the skill reads the repo and asks only what it cannot determine.
+
+The only permitted path to populate `.codearbiter/` when meaningful source code already exists. For a greenfield project with no source, use `/ca-decompose`.
+
+## Routes to
+
+The `context-creation` skill (`<plugin-root>/routines/context-creation/SKILL.md`) — six gated
+phases: pre-flight, scout dispatch, synthesis, gap interview, write, lock. Scouts return paths, line
+numbers, and named values only — never raw source or secret values. The skill is canonical for the
+phases and their gates.
+
+## When NOT to use
+
+- Project already initialized (`<!--INITIALIZED-->` in `CONTEXT.md`) → `/ca-status`.
+- Greenfield project, no source → `/ca-decompose`.
+- `.codearbiter/` not yet scaffolded → `/ca-init` first.
+- Update one doc → edit `<project-root>/.codearbiter/` directly or use `/ca-feature`.
+
+## Hard gate
+
+BLOCK if `<!--INITIALIZED-->` is already present in `CONTEXT.md`. BLOCK if no meaningful source exists
+(route to `/ca-decompose`). BLOCK if any scout fails to return before synthesis. BLOCK if any
+`[CONFIRM-NN]` exits the gap interview unresolved and undeferred. MUST NOT write `<!--INITIALIZED-->`
+until every gap is resolved or deferred to `open-questions.md`.

package/plugins/ca-pi/skills/ca-debug/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: ca-debug
+description: Investigate-then-decide root-cause analysis for a defect whose cause is unknown. No code changes — exits to /ca-fix, /ca-adr, or a no-action close.
+argument-hint: "<observed symptom>"
+---
+
+# /ca-debug — root-cause investigation
+
+Investigates a defect, anomaly, or unexpected behavior whose cause is not yet known. Separates investigation from implementation: no code is modified while debugging. Describe the symptom with enough fidelity that another operator could reproduce it — observed behavior, reproduction steps (or intermittent-trigger profile), and environment. Vague descriptions ("it's flaky") are rejected; the orchestrator asks for clarification before routing.
+
+If the cause is already known and a regression test is already named, invoke `/ca-fix` directly.
+
+## Routes to
+
+The `debug` skill (`<plugin-root>/routines/debug/SKILL.md`) — five gated phases: symptom
+capture, hypothesis generation, evidence gathering, root-cause decision, handoff. Phase 4 forces one
+named exit:
+
+- **(a) Confirmed bug → `/ca-fix`**, carrying the confirmed bug statement, cited evidence, and a named
+  regression test obligation tied to the minimal repro.
+- **(b) Behavior/design ambiguity → `/ca-adr`**, with the ambiguity statement and evidence ledger,
+  authored only with explicit user attribution.
+- **(c) No-action close** — symptom and rationale appended to
+  `<project-root>/.codearbiter/open-tasks.md`.
+
+A real finding that is out of scope for those exits is marked inline `[NEEDS-TRIAGE]` and the
+investigation continues.
+
+## When NOT to use
+
+- Known bug with a named regression test → `/ca-fix` directly.
+- Design discussion with no failing behavior → `/ca-adr`.
+- New feature → `/ca-feature`.
+- A general "why does it behave this way" question with no defect → `/ca-btw`.
+- Re-entry from inside `/ca-fix` or `/ca-adr` → exit that command first (routing-cycle prevention).
+
+## Hard gate
+
+MUST NOT modify any code during Phases 1–5 — code changes belong to `/ca-fix`. MUST exit Phase 4 with
+exactly one of (a)/(b)/(c). Exit (a) MUST carry a regression test obligation. Exit (b) MUST obtain
+user attribution before any `/ca-adr`. MUST NOT promote INCONCLUSIVE evidence to CONFIRMED without a
+cited source.

package/plugins/ca-pi/skills/ca-decompose/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: ca-decompose
+description: Greenfield decomposition interview — a layered interview that populates .codearbiter/ and locks it initialized.
+argument-hint: (none)
+---
+
+# /ca-decompose — greenfield populate
+
+Stands up project state for a greenfield project — one with no meaningful source code yet. A senior-architect persona drives a six-layer interview eliciting purpose, scope, primary users, domain vocabulary, and architectural constraints, persisting each layer to disk so a context reset loses nothing, then writes the surviving `.codearbiter/` doc set and locks the project initialized. No arguments — the skill interviews the user (a handoff summary may be supplied freely during the interview).
+
+The only permitted path to populate `.codearbiter/` when no meaningful source exists. For an existing codebase, use `/ca-create-context`.
+
+## Routes to
+
+The `decompose` skill (`<plugin-root>/routines/decompose/SKILL.md`) — six gated phases:
+pre-flight, persona adoption, layered interview, synthesis, population, lock. The skill is canonical
+for the layers and their gates.
+
+## When NOT to use
+
+- Project already initialized (`<!--INITIALIZED-->` in `CONTEXT.md`) → `/ca-status`.
+- Existing codebase with source present → `/ca-create-context`.
+- `.codearbiter/` not yet scaffolded → `/ca-init` first.
+- Update one doc → edit `<project-root>/.codearbiter/` directly or use `/ca-feature`.
+
+## Hard gate
+
+BLOCK if `<!--INITIALIZED-->` is already present in `CONTEXT.md`. BLOCK if meaningful source is
+detected (route to `/ca-create-context`). BLOCK if any `[CONFIRM-NN]` exits synthesis unresolved and
+undeferred. MUST NOT write `<!--INITIALIZED-->` until every required doc is present and non-empty.

package/plugins/ca-pi/skills/ca-dev/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: ca-dev
+description: Maintainer override — suspend orchestration to edit codeArbiter itself. Env-gated (CODEARBITER_DEV=1), entry/exit logged to overrides.log.
+argument-hint: "[note]"
+---
+
+# /ca-dev — maintainer override
+
+Suspends orchestration for working ON codeArbiter — skill, agent, command, and hook bodies,
+`ORCHESTRATOR.md`, settings. Not for project work; for that, use the normal commands or
+`/ca-override`.
+
+## Flow
+
+1. **Env gate** — check the `CODEARBITER_DEV` environment variable. Not set to `1` → refuse in one
+   line ("dev mode requires CODEARBITER_DEV=1") and remain in orchestration. This keeps the mode a
+   deliberate maintainer posture, not a casual bypass.
+2. **Log entry** — detect identity from `git config user.email`; append to
+   `<project-root>/.codearbiter/overrides.log` (append-only, `>>`):
+
+   ```
+   [ISO-8601 timestamp] | BY: <email> | DEV: enter | NOTE: <note or —>
+   ```
+
+3. **Marker** — drop `<project-root>/.codearbiter/.markers/dev-active` (gitignored UI flag).
+4. **Mode** — plain, direct coding assistant: no routing, no skills, no gates, no `[CONFIRM-NN]`
+   surfacing, no redirect. Persists until `/ca-arbiter` or a new session.
+
+Note (#271): if another session starts in this repo while this marker is live, SessionStart no longer
+unconditionally clears it out from under you — it is session-scoped now, so a concurrently-running dev
+session's marker survives a different session's startup. See `/ca-arbiter` for the exit-path detail.
+
+## Hard gate
+
+MUST refuse without `CODEARBITER_DEV=1`. MUST write the `DEV: enter` log line before suspending
+orchestration. Even in dev mode, `overrides.log` is never rewritten — the append-only rule has no
+dev exception.
+
+## When NOT to use
+
+- Bypassing a single gate on project work → `/ca-override "reason"`.
+- Asking a question → `/ca-btw`.

package/plugins/ca-pi/skills/ca-doctor/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: ca-doctor
+description: Verify the active host install, package, command ownership, enforcement, wrapper self-test, and active-dispatch coverage gap. Read-only.
+argument-hint: (none)
+---
+
+# /ca-doctor — install health
+
+Silent dormancy is the worst failure shape this plugin has: the gates look installed but never fire.
+This command proves the active host is healthy and reports every non-OK finding with an exact
+remediation.
+
+## Flow
+
+1. The `/ca-doctor` alias has already run the extension's structured Pi doctor report before sending
+   this generated skill. Present the `<codearbiter-doctor-report>` block below verbatim.
+2. The report inspects, without granting trust: active Git package origin/version, exact Pi CLI and
+   module package identity, stable Pi/Node/Python support, shared-core and bridge paths, command and
+   native-equivalent skill-expansion ownership, child/ambient-marker state, and final wrapper sources.
+3. Its `wrapper-self-test` row submits only `git add --all --dry-run` directly to the stored governed
+   Pi bash wrapper. The exact shared-core `[H-03]` block is healthy and cannot stage files; execution
+   or a different block is unhealthy. This self-test does not traverse Pi's active dispatcher. Do not
+   rerun or respell it.
+4. Its `active-dispatch` row remains degraded because supported Pi 0.80.5/0.80.10 public extension
+   APIs cannot submit that deterministic call through the active dispatcher. PI-AC-28 remains blocked
+   until supported-version real-host promotion/CI evidence closes the gap.
+
+## Remediation ladder
+
+1. Restart Pi so package resources and final wrappers register in one fresh process.
+2. Reinstall `ca-pi` from the approved pinned Git tag. For project-local packages, inspect `/trust`
+   and grant trust only if you accept that source; codeArbiter never grants it.
+3. If dormancy was intended, `/ca-init` opts the repository in.
+
+## When NOT to use
+
+- Scaffold state only → `/ca-init --check`.
+- Project progress, not install health → `/ca-status`.
+
+## Hard gate
+
+Read-only. MUST NOT create markers, stage files, grant trust, weaken a block, or retry the
+wrapper self-test with different spelling. MUST preserve the degraded active-dispatch diagnosis until
+supported-version real-host promotion/CI evidence closes PI-AC-28.