@arbiterforge/ca-pi 0.10.12 → 0.14.6

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

@@ -1,6 +1,6 @@
 ---
 name: ca-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.
 argument-hint: "[target] | --dry-run"
 ---
 
@@ -10,14 +10,14 @@ The only permitted path to a version tag. A release is a deployment-readiness as
 
 ## Flow
 
-Routes to the `release` skill, which resolves everything about the release from the project's **declared target file**, `<project-root>/.codearbiter/release-targets.md` — the tag prefix, the manifests, the changelog, the payload scope, and the optional checks. Nothing about any target is written here.
+Routes to the `release` skill, which resolves everything about the release from the project's **declared target file**, `<project-root>/.codearbiter/release-targets.md` — the tag prefix, declared version policy, manifests, changelog, payload scope, optional checks, and optional exact release-asset inventory. Nothing about any target is written here.
 
 `/ca-release` takes the target's name as its only argument. When the declared file names exactly one target, a bare `/ca-release` uses it; when it names more, the argument is required and the skill STOPs rather than guessing. A project with no declared file at all enters the skill's own back-fill lane, which proposes a row and writes nothing without explicit confirmation.
 
 1. **Pre-flight** — declared row resolved, working tree clean, not on the default branch, suite green, no blocking `[CONFIRM-NN]` open. Resolve `LAST_TAG` within that target's own tag series and scope the commit window to the row's declared payload, so a sibling target's commit never bumps this one or lands in its changelog.
-2. **Version** — classify the window by Conventional Commits type and apply the highest-precedence bump, against a base that accounts for both the last tag and every declared manifest. Every bumping commit must carry a `CHANGELOG:` footer; a missing one BLOCKs and is never auto-filled.
-3. **Surfaces** — roll the section into the declared changelog, update every declared manifest, and run the row's declared `pre-tag` checks. Those checks are check-only: one that mutates the tree BLOCKs.
-4. **Tag** — commit the release edits, then compose the annotated tag. Never push it or publish a Release without explicit user authorization — publication is a separate decision.
+2. **Version** — classify the window by Conventional Commits type and derive the next identity through the row's declared `version-policy` (`semver` by default). The base accounts for both the last compatible tag and every declared manifest. Every bumping commit must carry a `CHANGELOG:` footer; a missing one BLOCKs and is never auto-filled.
+3. **Surfaces** — roll the section into the declared changelog, update every declared manifest, and run the row's declared `pre-tag` checks. After those edits are committed, declared assets are qualified in the protected publisher before any tag push: either `release-build` produces an exact inventory in an empty hosted directory, or a reviewed retained exact-head CI cohort supplies provenance-bound packages with the same declared filenames. Tracked-tree mutation, arbitrary build failure, provenance mismatch, or inventory drift BLOCKs.
+4. **Tag** — compose the annotated tag and report any verified asset inventory. Never push it or publish a Release without explicit user authorization. On authorization, upload only the verified inventory and require the published names to match exactly.
 
 ## Dry run
 
@@ -31,7 +31,8 @@ prints the resolved row's fields verbatim, which doubles as a way to validate a
 `<project-root>/.codearbiter/release-targets.md` without tagging anything. Declared `pre-tag` checks
 are listed, not run — they assert against the manifests AFTER the bump this mode never performs, so
 running them early would report false failures against files `--dry-run` deliberately leaves
-untouched, not a preview of anything real. `release`'s own SKILL.md is authoritative for the exact
+untouched, not a preview of anything real. A declared `release-build` and its asset templates are also
+listed but never executed or rendered into files. `release`'s own SKILL.md is authoritative for the exact
 stopping point.
 
 ## Arguments

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

@@ -68,14 +68,7 @@ that names every member, never an implied yes.
    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>`.
-
-   One confirmation per item, one helper call per item — the two map 1:1 on
-   purpose. A batched "archive all 12?" turns twelve decisions into one, and the
-   helper's own per-item ordering (append to `done-tasks.md` first, then remove
-   from `open-tasks.md`) is what makes an interrupted sweep recoverable; a batch
-   loop that answered once would throw that away.
+   separately**, noting which ones the user says yes to.
 
    An item marked `[x]` with **no `(done YYYY-MM-DD)` stamp** cannot be aged, so
    it is never in the proposed set. Offer it only if the user asks, and only with
@@ -86,6 +79,41 @@ that names every member, never an implied yes.
    Declining is always available and costs nothing: an unarchived task stays
    exactly where it is. Never archive without a yes.
 
+   **If at least one item was confirmed:** an archive is calendar-driven hygiene,
+   not a consequence of any in-flight work, so it never rides another commit.
+   Before creating the archive branch, require a **clean working tree and index**
+   (`git status --porcelain` emits nothing); otherwise STOP before mutating the
+   board. Then switch to the configured default branch, fetch it and fast-forward
+   it with step 1's `--ff-only` pull, and STOP on checkout, fetch, divergence, or
+   pull failure. Verify that HEAD is the fetched default tip. Only then create and
+   switch to a fresh dedicated branch with non-overwriting `git switch -c`, e.g.
+   `chore/board-archive-<YYYY-MM-DD>-<HHMMSSZ>`. Branch creation MUST fail closed
+   if the branch name already exists; never reuse or reset an earlier sweep's
+   branch. Verify the new branch is current and still points at the fetched
+   default tip before the first archive helper call.
+
+   This ordered isolation is what makes the sweep committable at all: writing
+   straight to disk on whatever branch happens to be current would either land
+   on `main` (refused outright) or mix into an unrelated feature branch's staged
+   work (a type split under commit-gate Phase 3) — see #573. One fresh branch per
+   sweep, never reused across sessions.
+
+   On that branch, archive each confirmed item, still one at a time:
+   `"$PY" "<plugin-root>/hooks/taskwrite.py" archive <id>`.
+
+   One confirmation per item, one helper call per item — the two map 1:1 on
+   purpose. A batched "archive all 12?" turns twelve decisions into one, and the
+   helper's own per-item ordering (append to `done-tasks.md` first, then remove
+   from `open-tasks.md`) is what makes an interrupted sweep recoverable; a batch
+   loop that answered once would throw that away.
+
+   Once every confirmed item is archived, stage `.codearbiter/open-tasks.md` and
+   `.codearbiter/done-tasks.md` — the very first archive ever run creates
+   `done-tasks.md`; that new file is expected here, not scope creep — and hand
+   off to `/ca-chore docs`, which exits through `commit-gate` (classification
+   `docs`) and `finishing-a-development-branch` as usual. `.codearbiter/` prose
+   is already a listed `docs` chore type.
+
 Present a one-line summary of what was done and what was declined.
 
 ## When NOT to use