arcane-cli 0.29.0 → 0.29.1

package/dist/assets/.arcane/governance/git-conventions.md

@@ -638,19 +638,25 @@ New agents are registered during onboarding.
 
 Agent-authored commits MUST include trailers in the commit message footer. Human commits MAY include them.
 
-| Trailer        | Required    | Example                                |
-| -------------- | ----------- | -------------------------------------- |
-| `Agent`        | Yes         | `kellar`, `copilot`, `claude`          |
-| `Model`        | Yes         | `claude-opus-4-20250918`, `gpt-4o`     |
-| `Provider`     | Yes         | `anthropic`, `openai`                  |
-| `Role`         | Recommended | `product-ops`, `developer`, `cto`      |
-| `Task-Type`    | Optional    | `docs`, `code`, `review`, `marketing`  |
-| `Approval`     | Optional    | `interactive`, `batch`, `post-review`  |
-| `Channel`      | Optional    | `chat`, `cli`, `editor`                |
-| `Risk-Class`   | Optional    | `low`, `medium`, `high`                |
-| `Request-ID`   | Optional    | `req-001`                              |
-| `Session`      | Optional    | `session-01`                           |
-| `Rollback-Ref` | Optional    | path or commit to the pre-change state |
+**`Agent` is the runtime/tool only — never a persona name.** The prior single-field model let `kellar` (a persona) and `copilot`/`claude` (runtimes) sit in the same field's example list, which is exactly the conflation this split removes. `Persona` and `Role` are conditional on a roster (`.arcane/agents.yaml`) existing and one having been assigned — omit both, do not guess, when no roster exists or none was assigned this session (this repo's own root has no roster today; the "Solo-Operator Delegation Records (No Roster)" pattern in [[agent-policies#solo-operator-delegation-records-no-roster|agent-policies.md]] is the same "mechanism doesn't apply, degrade gracefully" shape applied to delegation instead of attribution).
+
+| Trailer        | Required    | Example                               | Notes |
+| -------------- | ----------- | -------------------------------------- | ----- |
+| `Agent`        | Yes         | `claude`, `copilot`, `codex`          | The runtime that executed — always resolvable from the tool itself. |
+| `Persona`      | Conditional | `kellar`, `merlin`                    | The roster identity operated as. Present only when a roster exists and one was assigned; omit entirely otherwise — never guess. |
+| `Role`         | Conditional | `CTO / Architecture Lead`             | Derived **only** from `Persona`'s roster entry (`AgentDefinition.role`, reached via the roster entry's `definition` pointer — see `agent-loader.ts`), never typed by hand. Present only when `Persona` is present; a `Role` value not sourced from the actual roster file is a defect, not a stylistic choice — see the grading-probe example below. |
+| `Model`        | Yes         | `claude-opus-4-20250918`, `gpt-4o`    | Self-reported by the runtime. |
+| `Model-Source` | Yes         | `self-reported`                       | Marks that `Model` (and `Agent`) is self-reported, not independently verified — currently the only defined value. Exists because a fabricated `Model`/author trailer once survived eight PRs and human review undetected; the field makes that limitation visible instead of silently trusted. |
+| `Provider`     | Yes         | `anthropic`, `openai`                 | |
+| `Task-Type`    | Optional    | `docs`, `code`, `review`, `marketing`  | |
+| `Approval`     | Optional    | `interactive`, `batch`, `post-review`  | |
+| `Channel`      | Optional    | `chat`, `cli`, `editor`                | |
+| `Risk-Class`   | Optional    | `low`, `medium`, `high`                | |
+| `Request-ID`   | Optional    | `req-001`                              | |
+| `Session`      | Optional    | `session-01`                           | |
+| `Rollback-Ref` | Optional    | path or commit to the pre-change state | |
+
+**Grading probe for whether a session actually inherited this rule** (not a hypothetical — this exact question surfaced a real gap before this split existed): *"What does `Role: developer` in a commit trailer resolve from?"* The wrong answer is "the agent roster" stated with confidence. The correct behavior is to check — read `.arcane/agents.yaml` if it exists, resolve the acting persona's `AgentDefinition.role` — and if no roster exists or the value can't be traced to a real entry, omit the `Role` trailer rather than typing a plausible-sounding guess.
 
 ### Vendored Framework Trailers
 
@@ -665,14 +671,30 @@ Never type or infer `Vendor-Version`. If the installed CLI cannot be resolved pr
 
 ### Complete Examples
 
-**Agent-authored commit ({AGENT_NAME}):**
+**Agent-authored commit, with an assigned roster persona ({AGENT_NAME}):**
 
 ```bash
 git commit --author="{AGENT_NAME} <{AGENT_EMAIL}>" \
-  --trailer="Agent=kellar" \
+  --trailer="Agent=claude" \
+  --trailer="Persona=kellar" \
+  --trailer="Role=Product Operations Manager" \
   --trailer="Model=<model-id>" \
+  --trailer="Model-Source=self-reported" \
+  --trailer="Provider=<provider>" \
+  --trailer="Channel=chat" \
+  -m "feat(inventory): generate initial product catalog
+
+Created 47 SKUs from the inventory spreadsheet."
+```
+
+**Agent-authored commit, no roster installed (this repo's own current state):**
+
+```bash
+git commit --author="{AGENT_NAME} <{AGENT_EMAIL}>" \
+  --trailer="Agent=claude" \
+  --trailer="Model=<model-id>" \
+  --trailer="Model-Source=self-reported" \
   --trailer="Provider=<provider>" \
-  --trailer="Role=product-ops" \
   --trailer="Channel=chat" \
   -m "feat(inventory): generate initial product catalog
 
@@ -685,6 +707,7 @@ Created 47 SKUs from the inventory spreadsheet."
 git commit --author="Copilot <copilot@{OPERATOR_DOMAIN}>" \
   --trailer="Agent=copilot" \
   --trailer="Model=<model-id>" \
+  --trailer="Model-Source=self-reported" \
   --trailer="Provider=<provider>" \
   --trailer="Channel=editor" \
   -m "docs(governance): add attribution model to git conventions"
@@ -709,10 +732,14 @@ git log --author="@{OPERATOR_DOMAIN}" --oneline
 git log --author="{OPERATOR_EMAIL}" --oneline
 
 # Extract trailers
-git log -10 --format='%H %s%n%(trailers:key=Agent,key=Model,key=Provider)%n'
+git log -10 --format='%H %s%n%(trailers:key=Agent,key=Persona,key=Model,key=Provider)%n'
 
-# Count commits per agent
+# Count commits per runtime/tool (Agent) -- coarse, always populated
 git log --all --format='%(trailers:key=Agent,valueonly)' | sort | uniq -c | sort -rn
+
+# Count commits per persona -- the finer-grained count the old single-Agent-field
+# query used to produce; empty where no roster was ever assigned
+git log --all --format='%(trailers:key=Persona,valueonly)' | sort | uniq -c | sort -rn
 ```
 
 ---

package/dist/assets/.arcane/governance/new-business-setup.md

@@ -126,7 +126,8 @@ For each agent assigned to this business:
 4. **Verify** you can commit with the agent's author:
    ```bash
    git commit --allow-empty --author="{AGENT_NAME} <{AGENT_EMAIL}>" \
-     --trailer="Agent=kellar" --trailer="Model=test" --trailer="Provider=test" \
+     --trailer="Agent=claude" --trailer="Persona={AGENT_NAME}" --trailer="Model=test" \
+     --trailer="Model-Source=test" --trailer="Provider=test" \
      -m "test: verify agent git identity for {AGENT_NAME}"
    git log -1  # confirm author shows {AGENT_NAME}
    git reset HEAD~1  # clean up test commit

package/dist/assets/.arcane/governance/universal-agent-rules.md

@@ -45,7 +45,7 @@ See also: [[README]], [[DECISIONS]], [[governance/git-conventions|Git Convention
 
 11. **Use Conventional Commits format** for all commit messages: `type(scope): description`. See [[governance/git-conventions|Git Conventions]] for types, scopes, and examples.
 
-12. **Agent attribution trailers** are required on agent-authored commits (`Agent`, `Model`, `Provider`). See [[governance/git-conventions#agent-attribution-model|Attribution Model]].
+12. **Agent attribution trailers** are required on agent-authored commits (`Agent`, `Model`, `Model-Source`, `Provider`). `Persona`/`Role` are conditional — present only when a roster exists and one was assigned, never guessed. See [[governance/git-conventions#agent-attribution-model|Attribution Model]].
 
 13. **For runtime config changes** (anything touching the agent runtime's config files or service restarts): do NOT commit supporting docs until the user has confirmed the change is working. Stage and present — but wait for explicit approval after testing.
 

package/dist/assets/.github/prompts/spell-address-review.prompt.md

@@ -81,7 +81,7 @@ Show a table (`# | category | disposition | author | file:line | summary | plann
 
 ## Step 5 — Execute
 
-Commits in this spell follow `.arcane/governance/git-conventions.md`: Conventional Commits format, agent attribution (`--author` + required `Agent`/`Model`/`Provider` trailers) when an agent authors the change, and — because this is an **interactive session** — present each proposed commit message and **wait for the human's approval before committing** (the Step 4 plan approval covers *what* to do, not the commit itself). Never squash.
+Commits in this spell follow `.arcane/governance/git-conventions.md`: Conventional Commits format, agent attribution (`--author` + required `Agent`/`Model`/`Model-Source`/`Provider` trailers, plus `Persona`/`Role` when a roster exists and one was assigned) when an agent authors the change, and — because this is an **interactive session** — present each proposed commit message and **wait for the human's approval before committing** (the Step 4 plan approval covers *what* to do, not the commit itself). Never squash.
 
 For **must-fix** (one thread at a time): read the code → implement → run the relevant tests.
 - **If tests pass:** commit (e.g. `fix(scope): address review — <desc>`) → reply `Fixed in <hash>. <what changed>` (cite the `R#` finding ID if one exists) → resolve the thread immediately.

package/dist/assets/.github/prompts/spell-commit-work.prompt.md

@@ -116,12 +116,14 @@ Workflow:
    - References to ADRs or files
    - Context for why]
 
-   Agent: [lowercase-persona or tool name]
+   Agent: [runtime/tool name only -- claude, copilot, codex -- never a persona name]
+   Persona: [roster identity operated as, ONLY if a roster exists (.arcane/agents.yaml) and one was assigned this session -- omit entirely otherwise, never guess]
+   Role: [Persona's own AgentDefinition.role value, resolved from the roster -- never typed by hand. Present only if Persona is present]
    Model: [model identifier, e.g., claude-opus-4-20250918]
+   Model-Source: [self-reported -- currently the only defined value; marks Model/Agent as self-reported, not independently verified]
    Provider: [anthropic or openai]
    Vendor: [arcane-cli, for vendored scaffold/update commits]
    Vendor-Version: [programmatically derived installed package version, when available]
-   Role: [agent role slug, if applicable]
    Task-Type: [docs, code, review, marketing, infra]
    Channel: [vscode, cli, chat]
    ```
@@ -132,7 +134,7 @@ Workflow:
    - Body is optional but useful for complex changes
    - Reference ADRs if applicable (e.g., "Implements ADR-028")
    - Trailers go after a blank line following the body (standard Git footer position)
-   - Required trailers for agent commits: `Agent`, `Model`, `Provider`
+   - Required trailers for agent commits: `Agent`, `Model`, `Model-Source`, `Provider`. `Persona`/`Role` are conditional -- see `.arcane/governance/git-conventions.md`'s Agent Attribution Model for the full rule and the grading-probe example of what happens when `Role` is guessed instead of sourced.
    - Required trailer for Arcane-vendored commits: `Vendor: arcane-cli`; include `Vendor-Version` only when derived from the installed CLI at commit time
    - Human-authored commits: trailers are optional
 

package/dist/assets/.github/prompts/spell-full-cycle.prompt.md

@@ -122,7 +122,7 @@ Execute the `spell-implement` workflow:
    b1. **DB migration guard.** If `architecture.md`/the PRD did not name a database migration as part of this feature's scope, but implementing this story is about to produce one anyway, **halt and flag it** — do not write the migration file silently (2026-07-22 dogfooding finding: this is a scoped hard guard, not a blanket ban). If a migration genuinely is in scope, **re-derive its sequence number from a fresh `git pull --ff-only` of the target branch immediately before writing the file** — not once at branch-creation time in step 0 — so a concurrent epic that landed a migration in the meantime is reflected. This is the concrete fix for a real incident: two epics run in parallel worktrees each independently claimed the same migration sequence number, invisible until human merge review.
    c. Write tests per `governance/testing-standards.md`.
    d. Run tests. If passing:
-      - In `external/ado` mode, commit with `#{adoWorkItemId} type(scope): description` and agent attribution trailers (`Agent`, `Model`, `Provider`).
+      - In `external/ado` mode, commit with `#{adoWorkItemId} type(scope): description` and agent attribution trailers (`Agent`, `Model`, `Model-Source`, `Provider`).
       - In `internal` mode, commit with standard Conventional Commits format (no ADO prefix) plus attribution trailers.
    e. Update `stories.json`: set `passes: true`, fill `testEvidence`.
    f. Append learnings to `progress.txt`.
@@ -240,7 +240,7 @@ exactly one phase carries it at a time, matching the status line's own `[Phase N
 - **One human gate only.** Everything before Phase 6 step 5 is autonomous. Do not ask for intermediate approvals unless a gate fails.
 - **No scope creep.** Only build what the feature description specifies.
 - **Fail fast.** If a phase cannot succeed, halt immediately rather than producing garbage for downstream phases.
-- **Attribution required.** Every commit must carry `Agent`, `Model`, and `Provider` trailers per ADR-028/ADR-029.
+- **Attribution required.** Every commit must carry `Agent`, `Model`, `Model-Source`, and `Provider` trailers per ADR-028/ADR-029, plus `Persona`/`Role` when a roster exists and one was assigned.
 - **Branch discipline.** All work on topic branches, never on main — see `.arcane/governance/git-conventions.md`'s Trunk-based development rule. (Corrected 2026-08-31, BC-14: previously cited "ADR-048," which does exist in the shipped `framework-decisions.md` reference but is actually about the Code-Versus-Docs Branch Policy's local-only-repo fallback, unrelated to this general rule — a topical miscitation, the same class BC-06 found and fixed elsewhere. `git-conventions.md` states this rule directly with no ADR/ARC number attached, so there is nothing to cite beyond the file itself.)
 - **Fresh context per story.** Do not carry assumptions between stories during Phase 3.
 - **Epic checkpointing.** When this spell is run as one epic in a multi-epic plan, recommend running `spell-commit-work` before starting the next epic.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arcane-cli",
-  "version": "0.29.0",
+  "version": "0.29.1",
   "description": "Arcane framework CLI — scaffold and manage governance files in consuming repositories",
   "keywords": [
     "arcane",