arcane-cli 0.15.3 → 0.15.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/dist/assets/.arcane/governance/git-conventions.md +80 -68
  2. package/dist/assets/.github/prompts/spell-close-session.prompt.md +13 -10
  3. package/dist/assets/.github/prompts/spell-commit-work.prompt.md +7 -0
  4. package/package.json +1 -1
package/dist/assets/.arcane/governance/git-conventions.md CHANGED
@@ -36,18 +36,18 @@ type(scope): short description
36
36
 
37
37
  ### Commit Types
38
38
 
39
- | Type | When to Use | Example |
40
- | ---------- | ----------------------------------------------- | -------------------------------------------------------------- |
41
- | `feat` | New feature or capability | `feat(prompts): add spell-commit-work for checkpointing` |
42
- | `fix` | Bug fix | `fix(auth): restore token validation after refactor` |
43
- | `docs` | Documentation only | `docs(decisions): add table of contents to DECISIONS.md` |
44
- | `refactor` | Code/structure change, no behavior change | `refactor(playbooks): reorganize setup steps` |
45
- | `chore` | Maintenance, deps, tooling, cleanup | `chore(deps): bump <dependency> to <version>` |
46
- | `test` | Adding or fixing tests | `test(security): add token-expiry test` |
47
- | `perf` | Performance improvements | `perf(api): reduce cold-start latency` |
48
- | `ci` | CI/CD pipeline changes | `ci(azure): add DevOps pipeline for repo sync` |
49
- | `style` | Code formatting, whitespace (rare in this repo) | `style(markdown): fix inconsistent heading levels` |
50
- | `revert` | Revert a previous commit | `revert: undo feat(prompts): add spell-commit-work` |
39
+ | Type | When to Use | Example |
40
+ | ---------- | ----------------------------------------------- | -------------------------------------------------------- |
41
+ | `feat` | New feature or capability | `feat(prompts): add spell-commit-work for checkpointing` |
42
+ | `fix` | Bug fix | `fix(auth): restore token validation after refactor` |
43
+ | `docs` | Documentation only | `docs(decisions): add table of contents to DECISIONS.md` |
44
+ | `refactor` | Code/structure change, no behavior change | `refactor(playbooks): reorganize setup steps` |
45
+ | `chore` | Maintenance, deps, tooling, cleanup | `chore(deps): bump <dependency> to <version>` |
46
+ | `test` | Adding or fixing tests | `test(security): add token-expiry test` |
47
+ | `perf` | Performance improvements | `perf(api): reduce cold-start latency` |
48
+ | `ci` | CI/CD pipeline changes | `ci(azure): add DevOps pipeline for repo sync` |
49
+ | `style` | Code formatting, whitespace (rare in this repo) | `style(markdown): fix inconsistent heading levels` |
50
+ | `revert` | Revert a previous commit | `revert: undo feat(prompts): add spell-commit-work` |
51
51
 
52
52
  ### Scopes
53
53
 
@@ -303,10 +303,10 @@ When working across machines, topic branches are the coordination mechanism:
303
303
 
304
304
  ### Merge Strategy by Repo Risk
305
305
 
306
- | Repo Type | Examples | Merge Method | PR Required? |
307
- | -------------- | ------------------------------------------- | ------------ | ------------ |
308
- | **Docs repos** | docs hub, prototypes | PR | Yes |
309
- | **Code repos** | application, API, storefront repos | PR | Yes |
306
+ | Repo Type | Examples | Merge Method | PR Required? |
307
+ | -------------- | ---------------------------------- | ------------ | ------------ |
308
+ | **Docs repos** | docs hub, prototypes | PR | Yes |
309
+ | **Code repos** | application, API, storefront repos | PR | Yes |
310
310
 
311
311
  - **All repos have main branch protection.** Direct pushes to main are rejected. All changes must go through a PR.
312
312
 
@@ -319,22 +319,22 @@ When completing a PR in Azure DevOps, allow only these merge strategies by defau
319
319
 
320
320
  Do **not** use Squash commit.
321
321
 
322
- | Merge Type | Use? | Why |
323
- | --------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
324
- | **Rebase and fast-forward** | **Yes** | Preserves linear history while keeping individual commits and attribution trailers intact. |
325
- | **Merge (no fast forward)** | **Yes** | Preserves full branch context and review traceability where explicit merge commits are preferred. |
326
- | Squash commit | **No** | Collapses commit history and breaks per-commit attribution/analytics and granular rollback. |
327
- | Semi-linear merge | No | Adds unnecessary merge commits on top of rebased commits; avoid by default. |
322
+ | Merge Type | Use? | Why |
323
+ | --------------------------- | ------- | ------------------------------------------------------------------------------------------------- |
324
+ | **Rebase and fast-forward** | **Yes** | Preserves linear history while keeping individual commits and attribution trailers intact. |
325
+ | **Merge (no fast forward)** | **Yes** | Preserves full branch context and review traceability where explicit merge commits are preferred. |
326
+ | Squash commit | **No** | Collapses commit history and breaks per-commit attribution/analytics and granular rollback. |
327
+ | Semi-linear merge | No | Adds unnecessary merge commits on top of rebased commits; avoid by default. |
328
328
 
329
329
  ### Commit Governance
330
330
 
331
331
  Commit execution rights depend on the interaction context:
332
332
 
333
- | Context | Commit Behavior | Rationale |
334
- | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
335
- | **Interactive session** (Copilot, Claude in VS Code, Claude Code) | **Must ask human** before committing. Stage changes, present proposed message, wait for approval. | Human is actively collaborating; commits are a shared decision. |
336
- | **Autonomous agent** at Magus+ power level | May self-commit and self-merge within approved scope (per your power-level policy). Must use proper author/trailers. | Agent is operating independently with delegated authority. |
337
- | **Autonomous agent** below Magus | Must commit to topic branch and queue merge for human review. | Insufficient autonomy level for unsupervised merges to main. |
333
+ | Context | Commit Behavior | Rationale |
334
+ | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
335
+ | **Interactive session** (Copilot, Claude in VS Code, Claude Code) | **Must ask human** before committing. Stage changes, present proposed message, wait for approval. | Human is actively collaborating; commits are a shared decision. |
336
+ | **Autonomous agent** at Magus+ power level | May self-commit and self-merge within approved scope (per your power-level policy). Must use proper author/trailers. | Agent is operating independently with delegated authority. |
337
+ | **Autonomous agent** below Magus | Must commit to topic branch and queue merge for human review. | Insufficient autonomy level for unsupervised merges to main. |
338
338
 
339
339
  **Interactive session rule applies to ALL interactive tools, regardless of agent identity.** Even a high-power-level agent cannot auto-commit when operating through an interactive editor session — the human is present and must approve.
340
340
 
@@ -403,19 +403,19 @@ git push origin --delete <branch> # delete remote branch (safety net —
403
403
 
404
404
  **Known issues:**
405
405
 
406
- | Issue | Symptom | Fix |
407
- | --------------------------------------------------------------- | ----------------------------------- | ------------------------------------------ |
408
- | Reviewer already assigned | `reviewer add` returns already exists | Treat as idempotent success and continue |
409
- | `az repos pr set-vote` succeeds but approval still blocked | Policy requires additional approver | Confirm vote state, then request second human approval |
410
- | MCP `vote_pull_request` returns "Success" but vote stays 0 | `reviewer list` shows `vote: 0` | Use `Invoke-RestMethod` step 5 above |
411
- | `az rest --body '{"vote":10}'` fails | Shell parsing error on Windows | Use `Invoke-RestMethod` |
412
- | `az repos pr update --status completed` fails with policy error | "Needs 1 approval" | Verify `vote: 10` first, then retry |
413
- | MCP `create_pull_request` returns no data | No PR ID/URL in response | Fall back to `az repos pr create` |
414
- | `gh pr create` not found | `gh` CLI not installed | Use `az repos pr create` |
415
- | `creatorVoteCounts` is false on branch policy | Vote registers but PR still blocked | A second human must approve via ADO web UI |
416
- | `az repos pr update --status completed` returns `status: active` without error | PR silently not merged | Add `--squash false` to the command; the flag triggers the merge path correctly |
417
- | `git branch -d <branch>` fails after merge | Branch is attached to a worktree | Skip local delete; run remote delete + prune |
418
- | `git push origin --delete <branch>` fails with missing ref | Branch already deleted remotely | Treat as non-fatal and continue |
406
+ | Issue | Symptom | Fix |
407
+ | ------------------------------------------------------------------------------ | ------------------------------------- | ------------------------------------------------------------------------------- |
408
+ | Reviewer already assigned | `reviewer add` returns already exists | Treat as idempotent success and continue |
409
+ | `az repos pr set-vote` succeeds but approval still blocked | Policy requires additional approver | Confirm vote state, then request second human approval |
410
+ | MCP `vote_pull_request` returns "Success" but vote stays 0 | `reviewer list` shows `vote: 0` | Use `Invoke-RestMethod` step 5 above |
411
+ | `az rest --body '{"vote":10}'` fails | Shell parsing error on Windows | Use `Invoke-RestMethod` |
412
+ | `az repos pr update --status completed` fails with policy error | "Needs 1 approval" | Verify `vote: 10` first, then retry |
413
+ | MCP `create_pull_request` returns no data | No PR ID/URL in response | Fall back to `az repos pr create` |
414
+ | `gh pr create` not found | `gh` CLI not installed | Use `az repos pr create` |
415
+ | `creatorVoteCounts` is false on branch policy | Vote registers but PR still blocked | A second human must approve via ADO web UI |
416
+ | `az repos pr update --status completed` returns `status: active` without error | PR silently not merged | Add `--squash false` to the command; the flag triggers the merge path correctly |
417
+ | `git branch -d <branch>` fails after merge | Branch is attached to a worktree | Skip local delete; run remote delete + prune |
418
+ | `git push origin --delete <branch>` fails with missing ref | Branch already deleted remotely | Treat as non-fatal and continue |
419
419
 
420
420
  ### Branch Lifecycle
421
421
 
@@ -482,14 +482,14 @@ See also: [Agent Workflow — Sync with main before opening a PR](#agent-workflo
482
482
 
483
483
  ### PR Requirements
484
484
 
485
- | Requirement | Details |
486
- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
487
- | **Work item link** | Optional. Linking is encouraged for traceability but enforce it only if your branch policy requires it. |
488
- | **Title format** | Conventional Commits format: `type(scope): description` |
489
- | **Description** | Must include: summary of changes, rationale, verification steps, and a linked work item ID if applicable |
485
+ | Requirement | Details |
486
+ | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
487
+ | **Work item link** | Optional. Linking is encouraged for traceability but enforce it only if your branch policy requires it. |
488
+ | **Title format** | Conventional Commits format: `type(scope): description` |
489
+ | **Description** | Must include: summary of changes, rationale, verification steps, and a linked work item ID if applicable |
490
490
  | **Pre-PR sync** | **Mandatory rebase on latest `origin/<target>` before pushing.** See [🛑 Agent-mandatory pre-PR guard](#-agent-mandatory-pre-pr-guard) above — this applies even when opening PRs via raw `az repos pr create` / `gh pr create` / MCP tools. |
491
- | **Branch cleanup** | After merge, delete the source branch (local and remote). |
492
- | **PR link format** | All PR references in agent output should be clickable markdown links to the PR, not a bare `PR #NNN`. |
491
+ | **Branch cleanup** | After merge, delete the source branch (local and remote). |
492
+ | **PR link format** | All PR references in agent output should be clickable markdown links to the PR, not a bare `PR #NNN`. |
493
493
 
494
494
  ### Agent PR Workflow
495
495
 
@@ -522,6 +522,7 @@ Every commit must clearly identify **who produced the content** and **who approv
522
522
  - If **you** wrote the content: don't override author. Your global Git config is used.
523
523
  - If an **agent** produced the content: use `--author` to set the agent's identity.
524
524
  - If an **interactive AI tool** (Copilot, Claude in VS Code) produced the content: use the tool-level identity.
525
+ - If the content is an **Arcane vendored scaffold or managed update**: do not invent a vendor email identity and do not use an agent author. Keep the operator's Git identity and record package provenance with `Vendor: arcane-cli` plus a programmatically derived `Vendor-Version` when available. Split mixed vendor/operator changes first.
525
526
 
526
527
  ### Agent Email Convention
527
528
 
@@ -531,14 +532,14 @@ Give every agent/tool a stable email under a domain you control. Most hosts trea
531
532
 
532
533
  Maintain a registry of the identities you use, for example:
533
534
 
534
- | Identity | Email | Type | Role |
535
- | --------------- | --------------------------- | ------------------------------- | -------------------------- |
536
- | {OPERATOR_NAME} | `{OPERATOR_EMAIL}` | Human (owner) | — |
537
- | {AGENT_NAME} | `{AGENT_EMAIL}` | Autonomous agent | Product Operations Manager |
538
- | Merlin | `merlin@{OPERATOR_DOMAIN}` | Autonomous agent | CTO / Architecture Lead |
539
- | Lafayette | `lafayette@{OPERATOR_DOMAIN}` | Autonomous agent | Full-Stack Developer |
540
- | Copilot | `copilot@{OPERATOR_DOMAIN}` | GitHub Copilot | Tool |
541
- | Claude | `claude@{OPERATOR_DOMAIN}` | Claude Code | Tool |
535
+ | Identity | Email | Type | Role |
536
+ | --------------- | ----------------------------- | ---------------- | -------------------------- |
537
+ | {OPERATOR_NAME} | `{OPERATOR_EMAIL}` | Human (owner) | — |
538
+ | {AGENT_NAME} | `{AGENT_EMAIL}` | Autonomous agent | Product Operations Manager |
539
+ | Merlin | `merlin@{OPERATOR_DOMAIN}` | Autonomous agent | CTO / Architecture Lead |
540
+ | Lafayette | `lafayette@{OPERATOR_DOMAIN}` | Autonomous agent | Full-Stack Developer |
541
+ | Copilot | `copilot@{OPERATOR_DOMAIN}` | GitHub Copilot | Tool |
542
+ | Claude | `claude@{OPERATOR_DOMAIN}` | Claude Code | Tool |
542
543
 
543
544
  New agents are registered during onboarding.
544
545
 
@@ -546,19 +547,30 @@ New agents are registered during onboarding.
546
547
 
547
548
  Agent-authored commits MUST include trailers in the commit message footer. Human commits MAY include them.
548
549
 
549
- | Trailer | Required | Example |
550
- | -------------- | ----------- | --------------------------------------------- |
551
- | `Agent` | Yes | `kellar`, `copilot`, `claude` |
552
- | `Model` | Yes | `claude-opus-4-20250918`, `gpt-4o` |
553
- | `Provider` | Yes | `anthropic`, `openai` |
554
- | `Role` | Recommended | `product-ops`, `developer`, `cto` |
555
- | `Task-Type` | Optional | `docs`, `code`, `review`, `marketing` |
556
- | `Approval` | Optional | `interactive`, `batch`, `post-review` |
557
- | `Channel` | Optional | `chat`, `cli`, `editor` |
558
- | `Risk-Class` | Optional | `low`, `medium`, `high` |
559
- | `Request-ID` | Optional | `req-001` |
560
- | `Session` | Optional | `session-01` |
561
- | `Rollback-Ref` | Optional | path or commit to the pre-change state |
550
+ | Trailer | Required | Example |
551
+ | -------------- | ----------- | -------------------------------------- |
552
+ | `Agent` | Yes | `kellar`, `copilot`, `claude` |
553
+ | `Model` | Yes | `claude-opus-4-20250918`, `gpt-4o` |
554
+ | `Provider` | Yes | `anthropic`, `openai` |
555
+ | `Role` | Recommended | `product-ops`, `developer`, `cto` |
556
+ | `Task-Type` | Optional | `docs`, `code`, `review`, `marketing` |
557
+ | `Approval` | Optional | `interactive`, `batch`, `post-review` |
558
+ | `Channel` | Optional | `chat`, `cli`, `editor` |
559
+ | `Risk-Class` | Optional | `low`, `medium`, `high` |
560
+ | `Request-ID` | Optional | `req-001` |
561
+ | `Session` | Optional | `session-01` |
562
+ | `Rollback-Ref` | Optional | path or commit to the pre-change state |
563
+
564
+ ### Vendored Framework Trailers
565
+
566
+ Vendored scaffold/update commits use these provenance trailers instead of an invented Arcane author identity:
567
+
568
+ | Trailer | Requirement | Value |
569
+ | ---------------- | ----------- | ------------------------------------------------------------------------------------------------------------- |
570
+ | `Vendor` | Required | `arcane-cli` |
571
+ | `Vendor-Version` | Conditional | Output of `arcane --version` / `spell --version`, whose value is read from the installed CLI's `package.json` |
572
+
573
+ Never type or infer `Vendor-Version`. If the installed CLI cannot be resolved programmatically, omit the version trailer and disclose incomplete provenance rather than guessing.
562
574
 
563
575
  ### Complete Examples
564
576
 
package/dist/assets/.github/prompts/spell-close-session.prompt.md CHANGED
@@ -102,19 +102,19 @@ Rules:
102
102
  9. **Stage and commit session-close docs.**
103
103
 
104
104
  **Remote-capability check:** classify the state created by `spell-open-session` before branching, staging, push, or PR operations.
105
- - **Usable supported remote/merge path:** keep the current compliant session/PR/worktree branch and use the remote PR path below.
105
+ - **Usable supported remote/merge path:** requires an authenticated supported provider (`github.com`, `dev.azure.com`, or `visualstudio.com`). Keep the current compliant session/PR/worktree branch, resolve the actual remote name and integration branch, and use the provider-neutral PR path below.
106
106
  - **No usable remote/merge path:** remain on the current trunk. Do not create a dead session branch, push, pull, or open a PR. Apply the EF-28 interactive commit approval gate, commit locally on trunk after approval, report `Local-only close: committed on <trunk>; no remote PR/pull performed`, and skip steps 9a, 9c, and 10's remote operations.
107
107
  - **Read-only session:** if no repository mutation occurred, do not create a branch or commit.
108
108
 
109
109
  a. **Branch check — create a topic branch before any staging:**
110
110
  This remote branch path applies only when the remote-capability check found a usable merge path.
111
- Run `git branch --show-current`. If you are on `main`, create a topic branch **now** before any `git add`:
111
+ Run `git branch --show-current`. If you are on the resolved integration branch `<trunk>`, create a topic branch **now** before any `git add`:
112
112
 
113
113
  ```powershell
114
114
  git checkout -b docs/session-close-YYYY-MM-DD
115
115
  ```
116
116
 
117
- Never commit directly to `main` — the branch policy rejects direct pushes. If a session branch already exists (created by `spell-open-session`), stay on it.
117
+ Never commit directly to a remotely protected integration branch — the branch policy rejects direct pushes. If a session branch already exists (created by `spell-open-session`), stay on it.
118
118
 
119
119
  b. **Stage and apply the interactive commit gate from `spell-commit-work`:**
120
120
  - Run `git add -A && git diff --stat --cached` to show what changed.
@@ -129,10 +129,13 @@ Rules:
129
129
  - Missing/invalid authority visibly downgrades to PR creation only and requires human completion.
130
130
  - Interactive Magus+ completion still requires separate authenticated approval tied to the exact PR ID and head SHA.
131
131
 
132
- 10. **Return to main after the PR merges:**
133
- - Run `git checkout main && git pull origin main`. Do not end the session on a topic branch.
132
+ 10. **Synchronize the configured integration branch after the PR merges (remote path only):**
133
+ - Skip this entire step for local-only and read-only sessions.
134
+ - Resolve `<remote>` and `<trunk>` from observed Git/provider state: use the usable authenticated remote selected in step 9 and the merged PR's target branch (falling back to that remote's default branch). Never assume `origin` or `main`.
135
+ - Verify through the detected provider that the PR is merged before changing branches.
136
+ - Run `git switch <trunk>` followed by `git pull --ff-only <remote> <trunk>`. Do not end a remote-backed session on a topic branch.
134
137
  - Delete the local topic branch: `git branch -d <branch>`.
135
- - Verify `git log --oneline -3` shows the merge commit at HEAD.
138
+ - Verify `git log --oneline -3` shows the merged change at HEAD.
136
139
  - If stale local branches exist (merged or older than 7 days), list them and suggest cleanup.
137
140
  - See [governance/git-conventions.md](../../governance/git-conventions.md) Post-Merge Cleanup section.
138
141
 
@@ -166,7 +169,7 @@ Output format:
166
169
 
167
170
  ## PR Readiness
168
171
 
169
- Enumerate the current end state and the prescribed next action. Use this table to classify where the session landed (added clarity on top of the ADO PR lifecycle steps above — not a replacement for them):
172
+ Enumerate the current end state and the prescribed next action. Use this table to classify where the session landed within the provider-neutral lifecycle above:
170
173
 
171
174
  | End state | Next action |
172
175
  | --- | --- |
@@ -175,8 +178,8 @@ Enumerate the current end state and the prescribed next action. Use this table t
175
178
  | Open PR exists | Docs/changes reach `main` when it merges — show the PR URL. |
176
179
  | No PR + docs-only on a branch | Run `spell-create-pull-request --docs-only`. |
177
180
  | No PR + mixed code+docs on a branch | Run `spell-create-pull-request` once the feature is complete. |
178
- | Docs-only commit on `main` | Create a `chore/docs` branch, then run `spell-create-pull-request --docs-only`. |
179
- | Nothing ahead of `origin/main` | Branch is fully merged — clean up local/remote branches. |
181
+ | Docs-only commit on remote-backed `<trunk>` | Create a `chore/docs` branch, then run `spell-create-pull-request --docs-only`. |
182
+ | Nothing ahead of `<remote>/<trunk>` | Branch is fully merged — clean up local/remote branches. |
180
183
 
181
184
  ## Carry Forward
182
185
 
@@ -186,7 +189,7 @@ Enumerate the current end state and the prescribed next action. Use this table t
186
189
 
187
190
  Route the user to the right next spell based on the end state:
188
191
 
189
- - **Docs-only commit on `main`** — create a docs branch, then run `spell-create-pull-request --docs-only`.
192
+ - **Docs-only commit on remote-backed `<trunk>`** — create a docs branch, then run `spell-create-pull-request --docs-only`.
190
193
  - **On a feature branch, ready for review** — run `spell-create-pull-request`.
191
194
  - **On a feature branch, still in progress** — next session, run `spell-open-session` to resume.
192
195
  - **PR already open** — run `spell-address-review` after reviewers comment.
package/dist/assets/.github/prompts/spell-commit-work.prompt.md CHANGED
@@ -54,6 +54,10 @@ Workflow:
54
54
  - **Invariant: one commit has exactly one author.** Changes spanning authors must be split into separate commits.
55
55
  - Partition changed files by author first. Step 4 then groups by concern within each author partition; concern grouping must never recombine authors.
56
56
  - **Human wrote it:** no `--author` override needed (uses global Git config)
57
+ - **Arcane vendored scaffold/update:** no `--author` override; the operator's Git identity records the repository action. Add `Vendor: arcane-cli` and, when derivable, `Vendor-Version: <version>` trailers.
58
+ - Derive the version at commit time by running `arcane --version` (or the resolved `spell --version` alias). The CLI reads its installed package's `package.json`; never type the version, copy it from memory, or infer it from the repository manifest.
59
+ - If the installed CLI version cannot be read programmatically, omit `Vendor-Version` and report that provenance is incomplete. Never guess.
60
+ - A batch mixing vendored files with human- or agent-authored changes spans provenance authors and must be split before concern grouping.
57
61
  - **AI agent/tool produced it:** use `--author` with the agent's registered identity:
58
62
  - Roster agent: `--author="{AGENT_NAME} <{AGENT_EMAIL}>"` — resolve `{AGENT_NAME}` / `{AGENT_EMAIL}` from the active agent config (see [[agent-policies]] / [[naming-conventions]]); ask if unset.
59
63
  - Generic CLI/IDE tool: `--author="{TOOL_NAME} <{TOOL_NAME_LOWER}@{OPERATOR_DOMAIN}>"` — resolve `{TOOL_NAME}` from the channel in use and `{OPERATOR_DOMAIN}` from `.arcane.json`; ask if unset.
@@ -114,6 +118,8 @@ Workflow:
114
118
  Agent: [lowercase-persona or tool name]
115
119
  Model: [model identifier, e.g., claude-opus-4-20250918]
116
120
  Provider: [anthropic or openai]
121
+ Vendor: [arcane-cli, for vendored scaffold/update commits]
122
+ Vendor-Version: [programmatically derived installed package version, when available]
117
123
  Role: [agent role slug, if applicable]
118
124
  Task-Type: [docs, code, review, marketing, infra]
119
125
  Channel: [vscode, cli, chat]
@@ -126,6 +132,7 @@ Workflow:
126
132
  - Reference ADRs if applicable (e.g., "Implements ADR-028")
127
133
  - Trailers go after a blank line following the body (standard Git footer position)
128
134
  - Required trailers for agent commits: `Agent`, `Model`, `Provider`
135
+ - Required trailer for Arcane-vendored commits: `Vendor: arcane-cli`; include `Vendor-Version` only when derived from the installed CLI at commit time
129
136
  - Human-authored commits: trailers are optional
130
137
 
131
138
  8. **Gate and execute the commit:**
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "arcane-cli",
3
- "version": "0.15.3",
3
+ "version": "0.15.5",
4
4
  "description": "Arcane framework CLI — scaffold and manage governance files in consuming repositories",
5
5
  "keywords": [
6
6
  "arcane",