@arbiterforge/ca-pi 0.8.1 → 0.10.0

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

@@ -6,6 +6,12 @@ argument-hint: (none)
 
 # /ca-cleanup — post-merge branch transition
 
+<!-- catalog-compatibility-notice:start -->
+> Compatibility route. Prefer `/ca-pr --cleanup` for new usage. This installed route remains
+> functional under the command-route compatibility policy at <plugin-root>/includes/command-compatibility.md;
+> continue with the unchanged cleanup workflow below.
+<!-- catalog-compatibility-notice:end -->
+
 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

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

@@ -6,6 +6,12 @@ argument-hint: (none)
 
 # /ca-context-check — manual drift audit
 
+<!-- catalog-compatibility-notice:start -->
+> Compatibility route. Prefer `/ca-status drift` for new usage. This installed route remains
+> functional under the command-route compatibility policy at <plugin-root>/includes/command-compatibility.md;
+> continue with the unchanged drift workflow below.
+<!-- catalog-compatibility-notice:end -->
+
 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.

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

@@ -6,6 +6,12 @@ argument-hint: (none)
 
 # /ca-create-context — brownfield populate
 
+<!-- catalog-compatibility-notice:start -->
+> Compatibility route. Prefer `/ca-init --brownfield` for new usage. This installed route remains
+> functional under the command-route compatibility policy at <plugin-root>/includes/command-compatibility.md;
+> continue with the unchanged brownfield workflow below.
+<!-- catalog-compatibility-notice:end -->
+
 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`.

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

@@ -6,6 +6,12 @@ argument-hint: (none)
 
 # /ca-decompose — greenfield populate
 
+<!-- catalog-compatibility-notice:start -->
+> Compatibility route. Prefer `/ca-init --greenfield` for new usage. This installed route remains
+> functional under the command-route compatibility policy at <plugin-root>/includes/command-compatibility.md;
+> continue with the unchanged greenfield workflow below.
+<!-- catalog-compatibility-notice:end -->
+
 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`.

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

@@ -42,3 +42,7 @@ remediation.
 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.
+
+For an arbiter-enabled repository, the mechanical report treats the Git backstop as healthy only
+after exact managed-shim and live-enforcer validation, plus a harmless selected-Git
+`git hook run pre-push` probe with empty input. It never executes a foreign hook.

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

@@ -1,7 +1,7 @@
 ---
 name: ca-init
 description: Opt this repo into codeArbiter — scaffold the root-level .codearbiter/ state store.
-argument-hint: "(none) | --stage N | --check"
+argument-hint: "[--stage N] [--greenfield|--brownfield] | --check"
 ---
 
 # /ca-init — first-run scaffold
@@ -15,6 +15,23 @@ the SessionStart persona injection. The scaffolded
 `CONTEXT.md` is a **stub** (no initialization sentinel), so after scaffolding the project still needs
 populating before normal operation.
 
+<!-- catalog-command-modes:start -->
+## Explicit population strategies
+
+<!-- command-mode:--greenfield legacy-route:decompose -->
+`--greenfield` selects the exact `<plugin-root>/skills/ca-decompose/SKILL.md` workflow.
+
+<!-- command-mode:--brownfield legacy-route:create-context -->
+`--brownfield` selects the exact `<plugin-root>/skills/ca-create-context/SKILL.md` workflow.
+
+The two flags are mutually exclusive and neither may combine with `--check`. `--stage N` may
+accompany one only while `.codearbiter/CONTEXT.md` is absent: scaffold at that stage, then enter the
+selected workflow. When an uninitialized stub already exists, skip the refusing scaffolder and enter
+the selected workflow directly. An initialized marker or source-shape mismatch retains the selected
+legacy workflow's BLOCK. Without an explicit strategy, continue with the unchanged auto-detection
+procedure below.
+<!-- catalog-command-modes:end -->
+
 ## Procedure
 
 1. Run the scaffolder against the repo's git toplevel (resolved by the script):

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

@@ -1,13 +1,29 @@
 ---
 name: ca-pr
 description: Open a pull request the only sanctioned way — clear every BLOCK-level review finding, then stage the PR. Never a direct write to the default branch.
-argument-hint: (none)
+argument-hint: "[\"title\"] | --watch [PR] | --cleanup"
 ---
 
 # /ca-pr — open a pull request
 
 The only permitted path to a pull request. Every change lands through a PR — never a direct write or force-push to the default branch. No PR is drafted while any BLOCK-level review finding stands.
 
+<!-- catalog-command-modes:start -->
+## Compatibility modes
+
+<!-- command-mode:--watch legacy-route:watch -->
+`--watch [PR number | URL | branch]` loads and follows
+`<plugin-root>/skills/ca-watch/SKILL.md` with the remaining arguments. This is an internal resource
+handoff to the exact watcher contract, not a second host-command invocation.
+
+<!-- command-mode:--cleanup legacy-route:cleanup -->
+`--cleanup` loads and follows `<plugin-root>/skills/ca-cleanup/SKILL.md` with no remaining argument. It
+retains the cleanup route's containment proof and per-item confirmations.
+
+The flags are mutually exclusive. A bare or quoted title named `watch` or `cleanup` is not a mode;
+without either flag, continue with the unchanged PR flow below.
+<!-- catalog-command-modes:end -->
+
 ## Flow
 
 Routes to the `finishing-a-development-branch` skill, open-PR path. The orchestrator reads the current

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

@@ -6,7 +6,7 @@ argument-hint: "[path | #<pr> | <pr-url>] (defaults to the current diff)"
 
 # /ca-review — diff review
 
-Read-only review of a change. Routes to `dispatching-parallel-agents` (`<plugin-root>/routines/dispatching-parallel-agents/SKILL.md`): dispatches the reviewer fleet by path matrix, dedupes, then funnels through `finding-triage` → `checkpoint-aggregator` to a single verdict. No code is modified.
+Read-only review of a change. Routes to `dispatching-parallel-agents` (`<plugin-root>/routines/dispatching-parallel-agents/SKILL.md`): dispatches the reviewer fleet by path matrix, dedupes, then funnels through `finding-triage` → `verdict-aggregator` to a single in-memory verdict. No code is modified.
 
 **The change under review does not have to be yours.** `/ca-review #123` reviews an inbound pull request through the same fleet, the same matrix, and the same triage. That is the point of issue #80: a tool that only reviews the diff you just wrote is a linter for authors, not a gate for a team, and reviewing code you did NOT write is where a governance gate earns its keep.
 
@@ -38,7 +38,7 @@ It is an ARGUMENT, not a second command. The scope resolver already took one, th
 
 3. Route to `dispatching-parallel-agents` with that unit list (read-only batch — no collision check).
    It dedupes overlapping findings, then funnels through `finding-triage` (severity + inline
-   `[NEEDS-TRIAGE]` on out-of-scope items) → `checkpoint-aggregator` (single verdict).
+   `[NEEDS-TRIAGE]` on out-of-scope items) → `verdict-aggregator` (single read-only verdict).
 4. Surface the aggregated verdict: findings by severity, file:line, remediation, and the applicable
    control from `<project-root>/.codearbiter/security-controls.md` for security findings.
 5. **For a PR target, posting the verdict is a separate, confirmed step.** Report locally first; post only on explicit instruction, with `gh pr review <number> --comment --body-file <file>`. A review comment on someone else's PR is outward-facing and effectively public the moment it lands — it notifies subscribers and cannot be un-sent. Never `--request-changes` or `--approve` from here: those carry merge authority, and this command produces a finding list, not a maintainer's decision.
@@ -52,8 +52,7 @@ It is an ARGUMENT, not a second command. The scope resolver already took one, th
 
 ## Hard gate
 
-Read-only — MUST NOT modify a file, and MUST NOT check out, merge, or otherwise move the repository to the PR's branch: reviewing an inbound PR means reading its DIFF, not adopting its code, and a checkout would run its content through hooks that trust the working tree. BLOCK on any CRITICAL or HIGH finding on your OWN change: it must be resolved before `/ca-pr`. On an inbound PR there is nothing local to block — the verdict is the deliverable. MUST NOT consume raw reviewer output — only the `finding-triage` → `checkpoint-aggregator`
-verdict. MUST NOT resolve a `[CONFIRM-NN]` surfaced during review by guessing.
+Read-only — MUST NOT modify a file, and MUST NOT check out, merge, or otherwise move the repository to the PR's branch: reviewing an inbound PR means reading its DIFF, not adopting its code, and a checkout would run its content through hooks that trust the working tree. BLOCK on any CRITICAL or HIGH finding on your OWN change: it must be resolved before `/ca-pr`. On an inbound PR there is nothing local to block — the verdict is the deliverable. MUST NOT consume raw reviewer output — only the `finding-triage` → `verdict-aggregator` verdict. MUST NOT resolve a `[CONFIRM-NN]` surfaced during review by guessing.
 
 ## When NOT to use
 

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

@@ -1,13 +1,25 @@
 ---
 name: ca-status
 description: Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.
-argument-hint: (none)
+argument-hint: "(none) | drift"
 ---
 
 # /ca-status — state snapshot
 
 A read-only summary of `.codearbiter/` state. No skill is routed to; no file is modified.
 
+<!-- catalog-command-modes:start -->
+## Drift mode
+
+<!-- command-mode:drift legacy-route:context-check -->
+With the exact argument `drift`, load and follow
+`<plugin-root>/skills/ca-context-check/SKILL.md`. The audit begins read-only; re-scout or re-baseline may
+write only after the user's explicit selection. In drift mode the `context-check` contract governs;
+the opening summary and Hard gate below apply only to the no-argument snapshot. With no argument,
+continue with the unchanged read-only snapshot below. Reject other arguments rather than treating
+them as drift mode.
+<!-- catalog-command-modes:end -->
+
 ## Flow
 
 The orchestrator reads and presents:

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

@@ -6,6 +6,12 @@ argument-hint: "<PR number | url | branch>"
 
 # /ca-watch — PR CI babysitter
 
+<!-- catalog-compatibility-notice:start -->
+> Compatibility route. Prefer `/ca-pr --watch` for new usage. This installed route remains
+> functional under the command-route compatibility policy at <plugin-root>/includes/command-compatibility.md;
+> continue with the unchanged watcher workflow below.
+<!-- catalog-compatibility-notice:end -->
+
 Watch a pull request's checks to completion without babysitting them by hand. The
 wait happens server-side, so it costs nothing while CI runs; arbiter wakes once, on
 the verdict — diagnoses a red, or offers you the merge on a green. Arbiter never