@arbiterforge/ca-pi 0.14.17 → 0.15.1

package/plugins/ca-pi/includes/artifacts.md

@@ -72,6 +72,30 @@ ADR compatibility review, open-question handling, harvest and user/SMARTS gates.
 One criterion may need multiple tests. Never invent a condition, oracle, source,
 command, result, approval or reviewer to satisfy a required field.
 
+Before requesting review or approval of a plan, use the private
+`_approvallib._preflight_plan_verification(client, identity)` with its current engine identity.
+It checks all task verification definitions through complete bounded engine reads
+and collects the current source-input snapshot, reporting every unsupported
+command and any input-policy failure together. Both ordinary and initial paired
+approval arming enforce this check. No declared command, test discovery, or test
+module is executed or imported. Proposed test files and names may be absent;
+the installed collector still has to support the proposed runner's output format.
+Missing package-script definitions cannot establish a runner contract: declare a
+supported direct runner or supply the reviewed script definition first. Runtime
+executable/workspace binding and fresh named-result evidence remain required.
+
+`verification_inputs.roots` and `exclude_directories` use exact slash-separated
+repository-relative paths. Exclusions are directory paths, not globs or basename
+matches and not relative to an individual root. For root `site`, a generated
+dependency exclusion is `site/node_modules`, not `node_modules`. Review each
+excluded output directory explicitly; `.gitignore` does not define this policy.
+An exclusion outside all selected roots is rejected as ineffective. Overlapping
+roots cannot reinclude an excluded directory. Roots must exist before execution;
+use an existing containing directory for a planned new file so its creation
+changes the snapshot. An oversized included file is reported with its path and
+the 32 MiB per-file limit; revise the explicit policy rather than increasing the
+limit or excluding source/test/governance inputs needed for the task.
+
 The existing user, SMARTS, reviewer, or verification boundary must first persist
 its actual policy-owned workflow event as canonical JSON in the reserved
 content-addressed authority-source store. Interactive prompt approval currently
@@ -85,11 +109,19 @@ before asking the approval question:
 python "<plugin-root>/hooks/_approvallib.py" arm --root "<project-root>" --artifact-id <artifact-id>
 ```
 
-Present the returned `reply` value verbatim and require that exact reply. The
-`UserPromptSubmit` hook rechecks the armed identity, records the host-observed
-prompt as the policy-owned source, captures its receipt, and applies approval.
-An ordinary `yes`, a changed artifact, a wrong token, or a model-authored event
-does not confer authority. On the next turn, verify `validate` at the `approved`
+On Claude Code, when the result carries `ask_envelope`, pass it unchanged as the
+entire AskUserQuestion input (no `answers`, `annotations` or other field): the
+user approves by clicking its Approve option, and the host-observed selection is
+applied with origin `claude:AskUserQuestion:<session>`. Otherwise, or if the
+user prefers typing, present the returned `short_reply` (a four-character code
+such as `approve K7MQ`); the full `reply` is also accepted, and you
+require that exact reply: the hook tolerates surrounding whitespace, invisible characters, a code
+fence or quotes and a closing period, but nothing else in the message, and it
+reports a mismatch instead of staying silent. The `UserPromptSubmit` hook
+rechecks the armed identity, records the full armed reply as the host-observed
+policy-owned source, captures its receipt, and applies approval. An ordinary
+`yes`, a changed artifact, a wrong or expired code, a reply inside other text, or
+a model-authored event does not confer authority. On the next turn, verify `validate` at the `approved`
 gate before continuing. If the user declines or the artifact changes, cancel the
 exact pending request before arming another one:
 
@@ -149,7 +181,8 @@ python "<plugin-root>/hooks/_prerequisitelib.py" arm --root "<project-root>" --a
 ```
 
 Show the returned title, requirement, and review-packet digest, then require the
-returned `satisfy-prerequisite ...` reply verbatim. The `UserPromptSubmit` hook
+returned `short_reply` (`satisfy-prerequisite <code>`) or the full `reply`, with
+the same tolerance and mismatch reporting as approval. The `UserPromptSubmit` hook
 durably records that observed decision before publishing its authority source,
 captures a prerequisite receipt, and applies the existing prerequisite CAS
 operation. Its final nonce is non-secret freshness/correlation data, not a
@@ -221,6 +254,28 @@ workspace or executable drift. If an attempt is interrupted, use the adapter's
 `recover` operation to retain it as failed or abandoned; never rerun an uncertain
 attempt under the same request.
 
+Named Playwright commands require `test --reporter=json`; each required name must
+equal a unique native `spec.title`. Named Vitest commands require
+`run --reporter=verbose`; use the complete rendered `suite > case` identity after
+the filename, not a leaf-name alias. Named unittest commands require `-v` or
+`--verbose`. A passing row cannot conceal a duplicate, skip, failure or retry.
+Plain exit checks cannot attest named tests.
+
+Named npm commands support inspectable single-runner scripts, a contained
+repository-relative `--prefix`, and arguments forwarded after `--`. Compound
+scripts and pre/post lifecycle scripts require separately declared direct-runner
+commands; retain every check from the original suite when splitting commands.
+On Windows, only the qualified standard `npm.cmd` layout is adapted: the runner
+pins the wrapper, sibling `node.exe`, sibling `node_modules/npm/bin/npm-cli.js`,
+and script manifest. It deliberately selects that sibling CLI rather than the
+shim's optional global-prefix redirection. Unknown batch wrappers fail closed.
+Direct Node script entrypoints are also pinned. These launch-file bindings do
+not establish transitive dependency closure for deliberately excluded inputs.
+
+New observations use the closed `declared-command/0.2.0` producer profile to
+retain collector and launch-file identities. Historical `0.1.0` bindings remain
+separate and cannot be relabelled as qualified launch evidence.
+
 For `spec_review` or `quality_review`, arm the corresponding activity without
 workspace mappings and dispatch the returned `launch_envelope` unchanged to one
 fresh host subagent. The host hooks bind the exact launch call, child start and
@@ -234,7 +289,8 @@ individually.
 
 An interrupted or `BLOCKED` HTML task never resumes by editing its status. Arm
 the installed reconciliation adapter for the exact task or scope, present its
-returned reply verbatim, and let `UserPromptSubmit` capture and apply the observed
+returned `short_reply` (`reconcile <STATE> <code>` for a task, `reconcile <code>`
+for a scope; the full `reply` also works), and let `UserPromptSubmit` capture and apply the observed
 user decision across repositories:
 
 ```sh

package/plugins/ca-pi/includes/sprint-authority.md

@@ -17,8 +17,10 @@ python "<plugin-root>/hooks/_approvallib.py" arm-sprint --root "<project-root>"
 ```
 
 Omit `--delegate-methods` for approval without delegated plan-method changes. Show the returned
-`reply` verbatim. It explicitly names both IDs, `delegate-methods` or `approve-only`, and the nonce.
-An ordinary yes, wrong nonce/mode or changed member does not approve either. `sprint-approve`
+`short_reply`, which restates the mode: `approve-sprint delegate <code>` or
+`approve-sprint approve-only <code>`. The full `reply` naming both IDs, `delegate-methods` or
+`approve-only`, and the nonce is also accepted, with the same tolerance as single approval.
+An ordinary yes, wrong code/nonce/mode or changed member does not approve either. `sprint-approve`
 recomputes both model/revision identities and the projected binding, verifies both observations
 from the same actual reply, and commits the two approvals through the existing native journal.
 It produces separate bound receipts and an optional `grant_receipt`. No partial approval is visible

package/plugins/ca-pi/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arbiterforge/ca-pi",
-  "version": "0.14.17",
+  "version": "0.15.1",
   "private": true,
   "license": "AGPL-3.0-only",
   "type": "module",

package/plugins/ca-pi/routines/writing-plans/SKILL.md

@@ -118,7 +118,18 @@ returned same-slug `.codearbiter/plans/<slug>.html` target may be created. Creat
 that plan through the installed structured-artifact engine as `draft_preview`,
 using the source spec's exact artifact ID and normative digest. For ordinary sequential planning,
 this must be the approved spec's exact artifact ID and normative digest. Populate it only with typed operations
-and validate it at the ready gate. For initial combined review, retain `draft_preview` and return
+and validate it at the ready gate. Before presenting either ordinary or combined review, call
+the private `_approvallib._preflight_plan_verification(client, identity)` with the current engine identity.
+It reads every task through bounded engine pages, checks each declared runner's supported
+named-outcome format, snapshots current inputs, and rejects identity drift. Resolve the complete
+reported set of command/input diagnostics before asking for approval. It does not run commands,
+discover or import tests, or require proposed test files and test names to exist. Input roots must
+already exist: choose an existing containing directory for files the plan will create. Roots and
+excluded directories are exact repository-relative paths, not basenames, globs, or paths relative
+to each root; for root `site`, use `site/node_modules`, `site/dist`, and other reviewed output paths.
+The ordinary and paired approval adapters repeat this preflight before arming their user reply.
+This admission check is not verification evidence; execution still binds actual commands and
+requires current named outcomes. For initial combined review, retain `draft_preview` and return
 both ready identities to the caller: `sprint-approve` owns the binding and both approvals after one
 actual host-observed reply. Do not separately `plan-bind` or approve that pair. On ordinary approved-spec
 planning, use `plan-bind` to bind it to the approved spec before plan approval. This path must not create `.codearbiter/plans/<slug>.md`;