@arbiterforge/ca-pi 0.10.12 → 0.14.6

package/README.md

@@ -10,7 +10,7 @@ project context. You decide. codeArbiter enforces.
 <img alt="Claude Code plugin" src="https://img.shields.io/badge/Claude_Code-plugin-d97757">
 <img alt="Codex plugin" src="https://img.shields.io/badge/OpenAI_Codex-plugin-10a37f">
 <img alt="Pi Feature Forge preview" src="https://img.shields.io/badge/ca--pi-Feature_Forge_preview-d97757">
-<img alt="version 2.17.10" src="https://img.shields.io/badge/version-2.17.10-2b7489">
+<img alt="version 2.21.6" src="https://img.shields.io/badge/version-2.21.6-2b7489">
 <img alt="core lanes" src="https://img.shields.io/badge/core_lanes-18-555">
 <img alt="skills" src="https://img.shields.io/badge/skills-23-555">
 <img alt="agents" src="https://img.shields.io/badge/agents-19-555">
@@ -117,10 +117,11 @@ Approve the normal plugin trust prompt, open the target repository, and continue
 
 ### Codex CLI
 
-The public GitHub-slug flow is **available now**. The repository currently ships `ca-codex 0.9.10`;
-the dated end-to-end public-install record discovered `ca-codex 0.2.4` from release `v2.8.13`.
-Current packaging and shared-core parity are continuously verified, while that dated live-install
-record stays labeled rather than being silently promoted to evidence for a newer adapter:
+The public GitHub-slug flow is **available now**.
+The current adapter version is read from `plugins/ca-codex/.codex-plugin/plugin.json`.
+The dated end-to-end public-install record discovered `ca-codex 0.2.4` from release `v2.8.13`.
+Current packaging and shared-core parity are continuously verified, while that historical record
+stays labeled rather than being promoted to evidence for a newer adapter:
 
 ```text
 codex plugin marketplace add arbiterForge/codeArbiter

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arbiterforge/ca-pi",
-  "version": "0.10.12",
+  "version": "0.14.6",
   "license": "AGPL-3.0-only",
   "repository": {
     "type": "git",
@@ -15,6 +15,7 @@
   },
   "files": [
     "plugins/ca-pi/*.md",
+    "plugins/ca-pi/package.json",
     "plugins/ca-pi/agents/",
     "plugins/ca-pi/extensions/",
     "plugins/ca-pi/generated/",

package/plugins/ca-pi/CHANGELOG.md

@@ -4,6 +4,171 @@ All notable changes to `ca-pi` are documented in this file.
 
 ## [Unreleased]
 
+## [0.14.6] - 2026-09-20
+
+### Fixed
+
+- Reject projected merges that would strand an eligible ca-pi version, and
+  preserve the exact main CI run that supplies its release trigger and package.
+
+## [0.14.5] - 2026-09-19
+
+### Fixed
+
+- Preserve structured-artifact approval evidence in packaged receipts and fail
+  closed for prompt-backed approvals because Pi has no supported prompt adapter.
+
+## [0.14.4] - 2026-09-19
+
+### Fixed
+
+- `/ca:standup`'s archival sweep now creates its own dedicated chore branch
+  before archiving anything and hands off to `/ca:chore docs`, instead of
+  writing directly to `open-tasks.md`/`done-tasks.md` on whatever branch was
+  current with no commit path at all (#573).
+- `commit-gate`'s Phase 6 board-edit exemption no longer over-attributes an
+  unconditional "any deleted entry is scope creep" rule to ADR-0008; a docs
+  chore whose own Phase 3 classification is the board change is in-scope by
+  that classification directly.
+
+## [0.14.3] - 2026-09-18
+
+### Fixed
+
+- Default new full-lane feature and sprint work to qualified typed HTML
+  specifications and plans while preserving exact-format legacy pairs and
+  keeping HTML farm dispatch disabled.
+
+## [0.14.2] - 2026-09-18
+
+### Fixed
+
+- Preserve payload pathspec argument boundaries, validate Cargo manifests,
+  establish first-release and zero-tag behavior before classification, and
+  derive provenance identities from one remote ref snapshot. Run package
+  generation through the portable Python command on Windows and CI hosts,
+  preserve helper records as LF, reject ambiguous committed release notes
+  before tag mutation, and bind hosted assets and automatic publication to the
+  exact qualified changelog commit and manifest blobs.
+
+## [0.14.1] - 2026-09-18
+
+### Fixed
+
+- Require a merged default-branch commit and green hosted exact-head evidence
+  before release tag composition, and establish one POSIX shell before the
+  portable workflow runs on Windows.
+
+## [0.14.0] - 2026-09-17
+
+### Added
+
+- Publish the exact preassembled structured-artifact npm tarball only from the
+  native-qualified release cohort with cold-install and read-back receipts. New
+  full-lane work remains Markdown by default; typed HTML is available only as an
+  explicitly requested, fail-closed pilot, and partial Git-tag installs remain
+  usable.
+
+## [0.13.2] - 2026-09-17
+
+### Fixed
+
+- `_hooklib.py`: `gate-events.log` no longer accumulates REMIND/WARN noise
+  (shared core/pysrc change, synced via `tools/sync-core.py`). See the root
+  `CHANGELOG.md` for full detail.
+
+## [0.13.1] - 2026-09-17
+
+### Fixed
+
+- `_cleanuplib.py`: follow-on fixes to 0.13.0's T-03 remediation, found by a further independent review after that fix had merged (shared core/pysrc change). See the root `CHANGELOG.md` for full detail.
+
+## [0.13.0] - 2026-09-17
+
+### Added
+
+- `_cleanuplib.py`: adds T-03, the authoritative branch/worktree inventory (shared core/pysrc change, synced via `tools/sync-core.py`). See the root `CHANGELOG.md` for full detail.
+
+### Fixed
+
+- `_cleanuplib.py`: closes 3 blocking and 5 high-severity gaps an independent review found in T-03 as first merged (shared core/pysrc change). See the root `CHANGELOG.md` for full detail.
+
+## [0.12.0] - 2026-09-16
+
+### Added
+
+- Add the disabled structured-artifact foundation, Linux and Windows recovery support, verified native bridges, descriptor-relative Unix installation, and generated Pi workflow guidance while preserving the existing public surface. The Windows developer installer and HTML farm dispatch remain fail-closed pending their respective release/integration qualification.
+
+## [0.11.9] - 2026-09-17
+
+### Fixed
+
+- `core/pysrc/_cleanuplib.py`: closes 6 blocking and several high-severity gaps an independent review found in the T-03/T-04/T-05 cleanup-framework backend against ADR-0036's supersession gate (verdict: NO-GO on the backend as it stood). `execute_branch_deletion` now requires a `ProofResult` and refuses an unproven target outright; the force/atomic-delete path is unlocked only by `proof.method == "pr_delivery"`, never a caller-supplied flag; `evaluate_merge_proof`'s ancestry path is now repository-qualified; worktree occupancy is revalidated fresh at every mutation attempt; a claimed-successful delete is reverified before being recorded "applied"; a read failure is never folded into "branch confirmed absent"; the journal's retention bound now exceeds the proposal's own named 40-branch batch example. The journal file is renamed `.cleanup-journal.json` (was `.resources.json`). Still not wired into any live cleanup route -- that remains T-06's job.
+
+## [0.11.8] - 2026-09-17
+
+### Added
+
+- `core/pysrc/_cleanuplib.py`: the cleanup-framework's shared decision and interaction vocabulary (T-02) -- typed `Scope`, `Target`, and `Decision` objects with explicit `unknown`/`error` outcome states, plus two pure classifiers: `scope_covers` (a scope never authorizes a resource kind or member it didn't explicitly name) and `required_confirmation_count` (how many new confirmations an operation needs, based only on its authorization source -- zero for an already-bound direct instruction, snapshot reply, or accepted work lifecycle; exactly one for an unauthorized proposal; always one more for an unresolved unique-content loss, regardless of how many). Not yet wired into any live cleanup route.
+
+## [0.11.7] - 2026-09-17
+
+### Added
+
+- `core/pysrc/_cleanuplib.py`: a repository-bound operation journal and a guarded, revalidating branch-deletion executor for the cleanup-framework mutation backend (T-05, branch-deletion slice). The executor journals intent before mutating, revalidates a branch's tip immediately before every delete attempt (including the forced retry), refuses current/default/explicitly-protected/worktree-occupied branches, and reconciles any still-pending record from actual repository state rather than retrying blindly. Not yet wired into any live cleanup route. Worktree-removal guarding and filesystem-operation constraints are separate, not-yet-built increments sharing this same pattern.
+
+### Fixed
+
+- CI now runs the T-04 integration-proof evaluator's and T-05's own unit test suites (`test_cleanuplib.py`, `test_cleanuplib_mutation.py`) — both had been merged without a CI step invoking them, so they ran locally but were invisible to the pipeline.
+
+## [0.11.6] - 2026-09-17
+
+### Added
+
+- `core/pysrc/_cleanuplib.py`: a repository-qualified integration-proof evaluator (`evaluate_merge_proof`) for routine branch cleanup. Proves a candidate branch tip's content landed on an authorized integration target via ancestry (no `gh` required) or an exact, repository-qualified PR-delivery record; tree-equality is accepted only as corroboration and never grants eligibility by itself. Not yet wired into any live cleanup route.
+
+## [0.11.5] - 2026-09-16
+
+### Fixed
+
+- `core/pysrc/_standuplib.py`'s worktree inventory now captures lock state, detached-HEAD status, and the exact OID from `git worktree list --porcelain` output instead of silently dropping them; a locked worktree is now excluded outright from standup's hygiene-candidate list.
+
+## [0.11.4] - 2026-09-16
+
+### Fixed
+
+- `includes/routing-table.md`'s Hard gate column had drifted behind already-shipped skill behavior: the standup row required per-item confirmation for every worktree removal even though `commands/standup.md` already permits one named enumerated group, and the post-merge-cleanup row named ancestry + `branch -d` only even though `skills/post-merge-cleanup/SKILL.md` already documents the PR-record squash-proof path and its restricted `-D` exception.
+
+## [0.11.3] - 2026-09-16
+
+### Fixed
+
+- `marker_name_for()` now case-folds every path segment before encoding, matching `_canon`/`lookup_policy`'s existing case-insensitive registry comparison, so a differently-cased Write/Edit target no longer computes a marker name that was never minted (#624).
+
+## [0.11.2] - 2026-09-15
+
+### Fixed
+
+- Keep exhaustive repository and cross-platform verification on exact-head hosted CI instead of requiring contributors to replay the full matrix locally before committing or opening a pull request.
+
+## [0.11.1] - 2026-09-14
+
+### Fixed
+
+- Permit explicit changelog reconciliation only for exact published commits through a reviewed, default-branch-bound ledger while retaining strict failure for ordinary missing footers.
+
+## [0.11.0] - 2026-09-13
+
+### Added
+
+- Support declared numeric release policies and exact verified asset inventories while preserving SemVer defaults and explicit publication authorization.
+
+## [0.10.13] - 2026-09-13
+
+### Fixed
+
+- Continue active authorized work across startup, resume, and compact hook boundaries while retaining the idle-session command prompt.
+
 ## [0.10.12] - 2026-09-09
 
 ### Fixed

package/plugins/ca-pi/SKILLS.md

@@ -60,7 +60,7 @@ skill is invoked — never bulk-read this directory.
 |---|---|
 | `/ca-commit` | Run the full commit gate — the only sanctioned path to a git commit. |
 | `/ca-pr` | 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. |
-| `/ca-release` | Cut a release the only sanctioned way — SemVer bump from the commit log, a CHANGELOG section, an annotated tag. Takes the declared target's name as its only argument, or --dry-run to preview one with no write. The only path to a version tag. |
+| `/ca-release` | Cut a release the only sanctioned way — derive the target's declared version policy from the commit log, roll its changelog, compose an annotated tag, and optionally publish its exact declared assets. Takes the declared target's name as its only argument, or --dry-run to preview one with no write. The only path to a version tag. |
 
 ### Operate
 

package/plugins/ca-pi/SPRINT.md

@@ -7,11 +7,30 @@ file is the thin entry point, this file is the procedure. -->
 Brainstorm a sprint with the user, then execute it end-to-end — deciding "as the user" on everything
 that is not a true hard gate. Every auto-decision is logged. Hard gates are real stops, rare by design.
 
+## Structured-artifact boundary
+
+For new sprint work or an existing `.html` spec/plan match, load
+`<plugin-root>/includes/artifacts.md` before resume classification or artifact
+I/O. Call `_select_authoring_route` with the trusted project root, slug,
+`workflow: sprint`, and `lane: full`; use only its returned format and paths. For a selected HTML
+route it checks the installed capability before writing; a missing or invalid
+helper is a STOP and the workflow must not fall back to Markdown.
+Its validated identity, authority, binding and task-state operations replace the
+`.md` and status-column assumptions below for that pipeline. An existing `.md`
+pair remains on the legacy path. Discovery requires a
+complete same-extension spec/plan pair: select that exact pair as authoritative. A
+mixed-extension or duplicate match is a STOP. A lone spec resumes in its exact format, and the
+next plan must use the same extension. The workflow must not create, rename, or
+convert its counterpart to repair ambiguity. New full-lane sprint specs use the
+installed structured-artifact engine and default to canonical `.html`. The HTML
+path must block `--farm` before canary
+or dispatch; do not project it into legacy farm JSON.
+
 ## Execution backend: premium (default) vs. `--farm`
 
-> **`--farm` is a Feature Forge `preview`** — shipped off by default and not yet validated on real
-> runs. The premium subagent path is the blessed default. The promotion bar lives in
-> `<project-root>/.codearbiter/open-questions.md` (CONFIRM-05).
+> **`--farm` is a Feature Forge `preview`** — shipped off by default. Historical runs informed its
+> design but count as zero current qualification evidence. The premium subagent path is the blessed
+> default. The fresh-evidence promotion bar lives in `<plugin-root>/includes/farm.md`.
 
 `/sprint` runs the normal premium-subagent path unless invoked as `/sprint --farm`. The `--farm` flag
 selects the pluggable execution backend: Claude still authors the spec, the failing tests, and the plan,
@@ -25,16 +44,27 @@ backends. The worker-seam design (the cheap/premium/agentic policies the seam ad
 
 ## Phase 1 — Sprint spec · gate: STOP
 
-**Resume first:** if `<project-root>/.codearbiter/specs/<sprint-slug>.md` and
-`plans/<sprint-slug>.md` already exist for this sprint, do not re-brainstorm — confirm the resume
+**Resume first:** discover this sprint's existing artifacts. Call the private
+bridge resolver `_resolve_workflow_pair` with the trusted project root and sprint
+slug; its returned paths and format own this resume. Select a complete
+same-extension spec/plan pair as authoritative. A lone spec resumes in its exact
+format, and the next plan must use the same extension. A mixed-extension or
+duplicate match is a STOP. For an HTML pair, obtain state only through the
+installed engine `identity`, `index`, and symbol-scoped `read` operations. For a
+Markdown pair, use the existing Markdown status ledger. Resume either exact format
+without creating or consulting a shadow artifact; the workflow must not create,
+rename, or convert its counterpart. Do not re-brainstorm — confirm the resume
 with the user and re-enter per `/feature`'s Resume ladder (approved spec + plan with non-`ACCEPTED`
-tasks → straight to Phase 2, executing only the remaining tasks; the plan's `status` column is the
-ledger). An interrupted sprint is re-entered, never restarted.
+tasks → straight to Phase 2, executing only the remaining tasks; the legacy plan's
+`status` column or the typed engine's execution ledger is authoritative for its
+own format). An interrupted sprint is re-entered, never restarted.
 
 Route to `brainstorming` (`<plugin-root>/routines/brainstorming/SKILL.md`), scoped to a **sprint** — a coherent chunk of work (several features or one
-goal), not a single feature. Drive it to a concrete sprint spec at
-`<project-root>/.codearbiter/specs/<sprint-slug>.md`, then to `writing-plans` (`<plugin-root>/routines/writing-plans/SKILL.md`) for the task
-breakdown at `<project-root>/.codearbiter/plans/<sprint-slug>.md`.
+goal), not a single feature. Drive it to a concrete sprint spec at the
+route-selected spec path, then to `writing-plans`
+(`<plugin-root>/routines/writing-plans/SKILL.md`) for the task breakdown at the
+matching route-selected plan path. New sprint work uses `.html` through the
+installed engine.
 
 This is the ONE interactive gate, and it is load-bearing: the thoroughness of the spec is what makes
 hard-gate stops rare later. Capture the user's intent, priorities, risk tolerance, and any

package/plugins/ca-pi/agents/backend-author.md

@@ -23,7 +23,7 @@ Read in full before writing any code:
 
 ## TDD Workflow (Non-Negotiable)
 
-Follow the six-step fixed order in `<plugin-root>/includes/author-tdd-workflow.md` for every task — failing tests first, minimum implementation, full suite, lint/type-check, only then stage.
+Follow the six-step fixed order in `<plugin-root>/includes/author-tdd-workflow.md` for every task — failing tests first, minimum implementation, impact-bounded local verification, lint/type-check, only then stage. The shared `verification-boundary` reserves exhaustive cross-platform proof for exact-head hosted CI.
 
 ## Required Test Coverage per Feature
 

package/plugins/ca-pi/agents/frontend-author.md

@@ -23,7 +23,7 @@ Read in full before writing any code:
 
 ## TDD Workflow (Non-Negotiable)
 
-Follow the six-step fixed order in `<plugin-root>/includes/author-tdd-workflow.md` for every task — failing tests first, minimum implementation, full suite, lint/type-check, only then stage.
+Follow the six-step fixed order in `<plugin-root>/includes/author-tdd-workflow.md` for every task — failing tests first, minimum implementation, impact-bounded local verification, lint/type-check, only then stage. The shared `verification-boundary` reserves exhaustive cross-platform proof for exact-head hosted CI.
 
 ## Required Test Coverage per Feature
 

package/plugins/ca-pi/generated/command-catalog.json

@@ -293,7 +293,7 @@
     },
     "release": {
       "name": "release",
-      "description": "Cut a release the only sanctioned way — SemVer bump from the commit log, a CHANGELOG section, an annotated tag. Takes the declared target's name as its only argument, or --dry-run to preview one with no write. The only path to a version tag.",
+      "description": "Cut a release the only sanctioned way — derive the target's declared version policy from the commit log, roll its changelog, compose an annotated tag, and optionally publish its exact declared assets. Takes the declared target's name as its only argument, or --dry-run to preview one with no write. The only path to a version tag.",
       "skillPath": "skills/ca-release/SKILL.md",
       "visibility": "core",
       "workflow": "ship",

package/plugins/ca-pi/helpers/artifacts/release.json

@@ -0,0 +1,38 @@
+{
+  "format": "codearbiter.artifact-release/0.1.0",
+  "version": "0.1.0",
+  "protocol": "codearbiter.artifact-api/0.1.0",
+  "schema_version": "0.3.1",
+  "binaries": {
+    "darwin/amd64": {
+      "file": "ca-artifact-darwin-amd64",
+      "sha256": "fab98b0fd68bafe5f2f52941f704dc32bf623eaa68be18e9e68cc9bc07f05cac",
+      "native_tested": true
+    },
+    "darwin/arm64": {
+      "file": "ca-artifact-darwin-arm64",
+      "sha256": "44211f23050e42ac155432e6d3e3edc58fd7180171a982c6c4a39378ec15218d",
+      "native_tested": true
+    },
+    "linux/amd64": {
+      "file": "ca-artifact-linux-amd64",
+      "sha256": "100e36cf452a79fb678ee2f99956953ae97da5b49bc673e77cef094a87bd1cab",
+      "native_tested": true
+    },
+    "linux/arm64": {
+      "file": "ca-artifact-linux-arm64",
+      "sha256": "6c1aa70e582e5054c8125cb89585bfd0f0eda6a2b32f3c67c9cdbff76ca78e0f",
+      "native_tested": true
+    },
+    "windows/amd64": {
+      "file": "ca-artifact-windows-amd64.exe",
+      "sha256": "6a17e6188fede9f8b8271d0f9eeab41512b58118e5b12781e62b4ce8dc0c5519",
+      "native_tested": true
+    },
+    "windows/arm64": {
+      "file": "ca-artifact-windows-arm64.exe",
+      "sha256": "746bfd19ed124b14376326b05a435aad381d7a72093f0e8002fa66e186e64194",
+      "native_tested": true
+    }
+  }
+}