@arbiterforge/ca-pi 0.14.12 → 0.14.16

package/README.md

@@ -10,10 +10,10 @@ 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.21.12" src="https://img.shields.io/badge/version-2.21.12-2b7489">
+<img alt="version 2.21.16" src="https://img.shields.io/badge/version-2.21.16-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">
+<img alt="agents" src="https://img.shields.io/badge/agents-20-555">
 <img alt="license AGPL v3" src="https://img.shields.io/badge/license-AGPL_v3-3da639">
 
 [Start learning](https://arbiterforge.github.io/codeArbiter/learn/)
@@ -128,10 +128,24 @@ codex plugin marketplace add arbiterForge/codeArbiter --ref ca-codex-marketplace
 codex plugin add ca-codex@codearbiter
 ```
 
-The `ca-codex-marketplace` branch is the promoted catalog. Each entry pins the
-exact immutable Git commit assembled from the same qualified member set as the
-release archive; `main` remains the development source tree and is not a
-substitute for the promoted binary-bearing distribution.
+The `ca-codex-marketplace` branch is the promoted catalog. Its entry pins an
+immutable `ca-codex-dist-v<version>` Git tag holding the exact qualified release
+archive, including the native artifact engine; `main` remains the development
+source tree and is not a substitute for the promoted binary-bearing
+distribution. (An `@arbiterforge/ca-codex` npm channel is planned but deferred,
+ADR-0040.)
+
+If `codearbiter` was previously registered without
+`--ref ca-codex-marketplace`, `marketplace upgrade` keeps that default-branch
+registration and does not migrate it to the promoted binary-bearing channel. Remove and
+re-add the marketplace once, then reinstall the plugin:
+
+```text
+codex plugin remove ca-codex@codearbiter
+codex plugin marketplace remove codearbiter
+codex plugin marketplace add arbiterForge/codeArbiter --ref ca-codex-marketplace
+codex plugin add ca-codex@codearbiter
+```
 
 Open `/hooks`, review and trust the `ca-codex` handlers, then start a fresh task. Run `$ca-init` and
 `$ca-doctor`.
@@ -165,7 +179,9 @@ pi config
 ```
 
 Replace `<version>` with the numeric suffix from the chosen tag while retaining the full
-`ca-pi-v...` tag in the install source.
+`ca-pi-v...` tag in the install source. The Git-tag install carries no native artifact engine, so
+it is a partial install that cannot author typed HTML specs and plans; use the npm channel for
+that.
 
 Pi 0.84.1 is the supported host for this release line. Generated aliases use `/ca-*`;
 `/skill:ca-*` is the host-native fallback. Every `ca-pi-v*` tag is also published to npm as
@@ -390,8 +406,10 @@ Run `/ca:statusline` to install the optional token-aware statusline.
 </div>
 
 Folder, Git state, rate limits, token use, cost, context headroom, model, effort, and session age
-render globally. The governance row activates only in an enabled repository. Running
-`/ca:statusline` again restores the previous statusline.
+render globally. The governance row activates only in an enabled repository.
+Run `/ca:statusline uninstall` to restore the previous statusline, or remove the
+codeArbiter setting when no previous line existed. Running `/ca:statusline install`
+again refreshes the installed path and preserves the backup; it does not uninstall.
 
 </details>
 
@@ -500,9 +518,10 @@ shipped with.
 under separate proprietary terms. Commercial licenses are not being offered at this time. Inquiries
 may be made through GitHub if AGPLv3 does not fit a use case.
 
-**Contributions.** Future community contributions require a Contributor License Agreement that
-permits relicensing under AGPLv3 and proprietary terms. See [`CLA.md`](./CLA.md). The CLA is a
-template pending legal review and is not yet in force.
+**Contributions.** No Contributor License Agreement is currently in force. See
+[`CLA.md`](./CLA.md) for its status and maintainer handling. A future agreement
+requires legal review and separate explicit assent; maintainers must not infer
+additional proprietary relicensing rights from the retired template.
 
 <div align="center">
 <sub>Built for Claude Code, Codex CLI, and Pi.</sub>

package/package.json

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

package/plugins/ca-pi/CHANGELOG.md

@@ -4,6 +4,45 @@ All notable changes to `ca-pi` are documented in this file.
 
 ## [Unreleased]
 
+## [0.14.16] - 2026-09-25
+
+### Changed
+
+- Publish ca-pi to npm independently of the other plugins on merge (ADR-0040).
+- Name the concrete per-host repair in the `CAPABILITY_MISSING` diagnostic.
+
+## [0.14.15] - 2026-09-24
+
+### Fixed
+
+- Check the installed host's required HTML workflow resources and hook
+  registrations before new full-lane authoring. Unsupported or incomplete
+  hosts stop early without creating fallback artifacts; legacy Markdown and
+  the inline small feature lane retain their existing behavior.
+- Include complete LICENSE and Go runtime notices in every installable
+  governance-plugin subtree and verify their exact-source package bytes.
+
+## [0.14.14] - 2026-09-24
+
+### Changed
+
+- Vendor the shared authority adapter with Claude Code verification and review
+  seams and the `claude-review/0.1.0` engine profile. This package's own
+  authority behavior is unchanged; Pi still stops at the verification and review boundary and `arm` now refuses Pi explicitly.
+
+## [0.14.13] - 2026-09-24
+
+### Fixed
+
+- Correct first-release re-entry after a declaration lands through a normal
+  merge, squash, or fast-forward. An empty adoption-bounded payload window
+  now requires an explicit confirm-or-replace decision, never silent widening.
+- Require successful release-tree inspection and empty porcelain output at
+  every direct clean-tree gate. Failed or timed-out probes stop before the
+  next operation instead of being mistaken for a clean tree.
+- Exercise the installed release guards and declaration/ledger re-entry with
+  real consumer histories, and distinguish partial fixtures from full journeys.
+
 ## [0.14.12] - 2026-09-23
 
 ### Fixed