@arbiterforge/ca-pi 0.10.5 → 0.10.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.4" src="https://img.shields.io/badge/version-2.17.4-2b7489">
+<img alt="version 2.17.5" src="https://img.shields.io/badge/version-2.17.5-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,7 +117,7 @@ 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.4`;
+The public GitHub-slug flow is **available now**. The repository currently ships `ca-codex 0.9.5`;
 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:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arbiterforge/ca-pi",
-  "version": "0.10.5",
+  "version": "0.10.6",
   "license": "AGPL-3.0-only",
   "repository": {
     "type": "git",

package/plugins/ca-pi/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to `ca-pi` are documented in this file.
 
 ## [Unreleased]
 
+## [0.10.6] - 2026-09-06
+
+### Changed
+
+- Correct privacy disclosures and align task archival documentation with the established standup-owned policy.
+
 ## [0.10.5] - 2026-09-05
 
 ### Fixed

package/plugins/ca-pi/hooks/_host.py

@@ -11,7 +11,7 @@ import hostapi  # noqa: E402
 class PiHost(hostapi.Host):
     name = "pi"
     adapter_name = "@arbiterforge/ca-pi"
-    adapter_version = "0.10.5"
+    adapter_version = "0.10.6"
     update_target = "ca-pi"
     update_tag_prefix = "ca-pi-v"
     update_command = "pi update npm:@arbiterforge/ca-pi"

package/plugins/ca-pi/hooks/hostapi.py

@@ -313,7 +313,7 @@ class Host:
 
     name = "claude"
     adapter_name = "ca"
-    adapter_version = "2.17.4"
+    adapter_version = "2.17.5"
 
     # Update-notifier descriptor. Each independently versioned host overrides
     # these three values in its per-plugin _host.py. Keeping the target,

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

@@ -65,8 +65,9 @@ that names every member, never an implied yes.
    user; do not auto-flip.
 
 6. **Archival sweep — proposed per item, never batched** (B-24). Long-done tasks
-   accumulate on the board and inflate the in-flight count until it stops meaning
-   anything. List the done items older than the cutoff, then ask about **each one
+   accumulate on the board; they are already excluded from the in-flight count.
+   List dated done items strictly more than 14 calendar days old
+   (`ARCHIVE_CUTOFF_DAYS`), then ask about **each one
    separately** and archive only the ones the user says yes to:
    `"$PY" "<plugin-root>/hooks/taskwrite.py" archive <id>`.
 

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

@@ -46,7 +46,13 @@ an ID (`/ca-task start --as <group>.<type> -- "<title>"`) to disambiguate.
 - Promoting workflow follow-ups in bulk → that is the harvest
   (`<plugin-root>/includes/harvest.md`), which calls this writer for you.
 - Reading the board / counts → `/ca-status` (read-only).
-- Archiving long-settled done items → deferred (D-2); done items stay in-place for now.
+- Archiving long-settled done items → `/ca-standup` owns the sweep (D-2,
+  resolved 2026-07-31). It proposes dated done items strictly more than 14 calendar
+  days old and requires a separate yes for each item before invoking
+  `<plugin-root>/hooks/taskwrite.py` with `archive <id>`. This is the helper's
+  archive verb, not a new public `/ca-task archive` mode. Undated done items are never
+  proposed automatically; standup's explicit-request and `--allow-undated` rules
+  apply. Declined items stay on the board.
 - Filing a separate `chore(board)` PR just to flip a task state → task-board transitions
   (`[x]` done-flip, `[~]` start-flip, new `[ ]` add) ride the **work commit** via
   commit-gate, co-located atomically with the code that completes, starts, or spawns the