@arbiterforge/ca-pi 0.10.12 → 0.14.6

package/plugins/ca-pi/routines/finishing-a-development-branch/SKILL.md

@@ -13,8 +13,29 @@ after `commit-gate` clears — never before.
 Read these, or STOP and surface the gap — never guess the branch name or the default branch:
 
 - `<project-root>/.codearbiter/CONTEXT.md` — the default-branch name and project context.
-- `<project-root>/.codearbiter/plans/<slug>.md` — the plan this branch executed, when `/feature` or `/sprint` produced one. The yardstick for "is the work complete."
+- The discovered authoritative spec/plan pair for the pipeline, when `/feature`
+  or `/sprint` produced one. Use the exact selected `.md` or `.html` plan as the
+  yardstick for "is the work complete." Re-run the private bridge resolver
+  `_resolve_workflow_pair` with the trusted project root and pipeline slug rather
+  than reconstructing either path. Load `<plugin-root>/includes/artifacts.md`
+  for HTML and obtain HTML plan state only through the installed engine
+  `identity`, `index`, and symbol-scoped `read` operations. The finishing step
+  must not create, convert, or consult a counterpart.
 - `<project-root>/.codearbiter/last-checkpoint` — the most recent gate results; confirms `commit-gate` cleared on this branch.
+- `<plugin-root>/includes/verification-boundary.md` — the exact-head hosted-CI evidence required before merge.
+
+For an HTML pair, query the engine `identity` and `eligible` again after process
+recreation. Require `all_accepted_and_current: true` for the exact spec and plan
+identities, with their acceptance receipts still bound in engine state and the
+commit-gate proof. Finalization must not parse rendered HTML and must not consult
+a shadow Markdown ledger; displayed labels, status words, checkboxes, or digests
+cannot establish completion.
+
+Enforce that requirement by invoking the installed bridge's
+`_preflight_current_acceptance` with the exact `_resolve_workflow_pair` result,
+repository-bound client, and engine-returned spec/plan IDs. Carry its returned
+identity/receipt proof into state assembly. Any refusal blocks terminal options;
+do not recreate the proof from the PR description, checkpoint prose, or labels.
 
 `commit-gate` MUST have cleared on the current HEAD. If it has not, this skill does not run — return to it.
 
@@ -55,7 +76,7 @@ Gate: branch confirmed non-default, diff summary read, gate results and plan del
 Present exactly three terminal options with the Phase 1 state attached, then STOP for the choice:
 
 1. **Open a PR** — push the branch and open a pull request against the default branch, then stop. The PR stays open; the merge happens later, by the user or reviewers.
-2. **Merge via PR** — push the branch, open the PR, and once its checks are green, merge it **through the PR** so the work lands on the default branch now. Distinct from option 1: this one completes the merge. Still PR-only — no direct push to the default branch, no force-push.
+2. **Merge via PR** — push the branch, open the PR, and once its current exact-head merge-readiness aggregate is green, merge it **through the PR** so the work lands on the default branch now. Missing, stale, cancelled, mismatched, or red hosted evidence blocks this option. Distinct from option 1: this one completes the merge. Still PR-only — no direct push to the default branch, no force-push.
 3. **Discard** — abandon the branch.
 
 Under `/feature`: STOP and let the user pick.
@@ -70,7 +91,7 @@ Gate: a single terminal option is chosen — by the user under `/feature`, or au
 Carry out the chosen option, and only that one:
 
 - **Open a PR** — push the branch and open the PR against the default branch. The reviewer path-matrix, the anti-slop PR-body composition (description citing the plan items satisfied, the gate results, the §2 conflict level of any non-obvious tradeoff), and the babysitter attach are the steps documented in the `/ca-pr` command flow (`<plugin-root>/skills/ca-pr/SKILL.md`) — **execute those steps here; do not re-invoke `/ca-pr`** (under `/sprint` this skill is reached via `commit-gate`, without the `/pr` command ever running, so a route back would loop). Leave the PR open; the merge is not yours to take.
-- **Merge via PR** — open the PR as above, confirm its checks are green, revalidate Phase 1's ADR source ancestry and exact base/head, then merge it through the PR with the selected method and `--match-head-commit`. Never push to the default branch directly, never force-push.
+- **Merge via PR** — open the PR as above, bind its current head SHA, and require the repository merge-readiness aggregate for that exact head under `verification-boundary.md`. Missing, stale, cancelled, mismatched, pending, or red evidence blocks. Revalidate Phase 1's ADR source ancestry and exact base/head, then merge it through the PR with the selected method and `--match-head-commit`. Never push to the default branch directly, never force-push.
 - **Discard** — requires explicit user confirmation naming the branch. Before discarding, verify the branch is fully pushed; if any commit is un-pushed, STOP and report exactly what would be lost — never delete un-pushed work silently. Discard proceeds only after the user confirms with that loss in view.
 
 Gate: the chosen option completed — for open-PR a PR exists against the default branch; for merge the work landed through that PR; for discard the user confirmed against a stated loss summary.
@@ -107,6 +128,7 @@ warm sentence.
 - MUST NOT discard a branch without explicit user confirmation that names the branch.
 - MUST NOT delete un-pushed commits silently — STOP and report the loss before any discard.
 - MUST NOT run before `commit-gate` has cleared on the current HEAD.
+- MUST NOT merge without the repository merge-readiness aggregate passing for the PR's current exact head; missing, stale, cancelled, mismatched, pending, or red hosted evidence blocks.
 - MUST NOT guess the branch or default-branch name — read `CONTEXT.md` or STOP.
 - MUST draw the Receipt only from Phase 1 state + `last-checkpoint` — never a fresh audit-trail crawl — and never build a rolling cross-branch "saves" tally.
 - MUST keep the close to at most one warm sentence; never on a no-op close.

package/plugins/ca-pi/routines/refactor/SKILL.md

@@ -13,6 +13,7 @@ Read these, or STOP and surface the gap — never guess a command or a threshold
 
 - `<project-root>/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value) and project context.
 - `<project-root>/.codearbiter/tech-stack.md` — the test, coverage, lint, and type-check invocations; file layout.
+- `<plugin-root>/includes/verification-boundary.md` — the required split between focused local parity proof and exhaustive exact-head hosted CI.
 - `<project-root>/.codearbiter/coding-standards.md` — style, structure, naming. Required for Phase 4.
 
 The working tree MUST be clean over the named surface before Phase 1. A dirty surface conflates the refactor diff with unrelated edits and breaks parity verification — STOP and surface it.
@@ -67,9 +68,9 @@ Gate: the refactor confined to the surface table, with any Phase 3 seam tests no
 
 ## Phase 5 — Parity verification · gate: BLOCK
 
-Run the full project test suite from `tech-stack.md`. Every pre-existing test from Phase 2 MUST pass with NO modification to its source — inspect the diff and confirm zero edits to any pre-existing test file. A modified pre-existing test is, by definition, evidence the surface's observable behavior changed: revert it. If it cannot pass after revert, the refactor introduced a behavior change and is routed to `tdd` as a feature or fix. Phase 3 seam tests (if any) MUST pass. Record the pass/fail tally and any modified-test detection.
+Run every impact-bounded local parity test identified in Phase 2, following `verification-boundary.md`. Each MUST pass with NO modification to its source — inspect the diff and confirm zero edits to any pre-existing test file. A modified pre-existing test is, by definition, evidence the surface's observable behavior changed: revert it. If it cannot pass after revert, the refactor introduced a behavior change and is routed to `tdd` as a feature or fix. Phase 3 seam tests (if any) MUST pass. Record the pass/fail tally and any modified-test detection. The exhaustive pre-existing suite remains a required exact-head hosted-CI merge gate.
 
-Gate: full suite green with zero pre-existing tests modified. BLOCK if any pre-existing test was modified to pass, or if any test fails.
+Gate: scoped parity tests green with zero pre-existing tests modified. BLOCK if any pre-existing test was modified to pass, or if any applicable test fails; the branch still MUST NOT merge until exhaustive exact-head hosted CI passes.
 
 ## Phase 6 — Lint and coverage · gate: BLOCK