arcane-cli 0.15.5 → 0.15.6

package/dist/assets/.arcane/governance/agent-work-queue-model.md

@@ -9,7 +9,7 @@ tags: [governance, queue, agents, work-management]
 
 # Agent Work Queue Model
 
-Defines a single markdown-first queue for assigning work across businesses, while keeping Azure DevOps at Story-level visibility per [[DECISIONS#ADR-015|ADR-015]].
+Defines a single markdown-first queue for assigning work across businesses, while keeping Azure DevOps at Story-level visibility for human milestone tracking.
 
 ## Executive Summary
 
@@ -31,19 +31,19 @@ Defines a single markdown-first queue for assigning work across businesses, whil
 
 ## Canonical Fields
 
-| Field | Description |
-|------|-------------|
-| Queue ID | Unique work identifier |
-| Business | `acme-store`, `example-app`, etc. |
-| Repo | Target repo name |
-| DevOps Item | Story/Task/Bug link or ID |
-| Priority | Critical / High / Medium / Low |
+| Field          | Description                                    |
+| -------------- | ---------------------------------------------- |
+| Queue ID       | Unique work identifier                         |
+| Business       | `acme-store`, `example-app`, etc.              |
+| Repo           | Target repo name                               |
+| DevOps Item    | Story/Task/Bug link or ID                      |
+| Priority       | Critical / High / Medium / Low                 |
 | Assigned Agent | {AGENT_NAME}, Lafayette, Mercurio, Lince, etc. |
-| Power Level | Apprentice/Wizard/Sorcerer/Magus/Archmage |
-| Execution Host | Atlas, Voyager, Nimbus |
-| Approval Gate | Required reviewer and checkpoint |
-| Exit Criteria | Objective definition of done |
-| Status | Backlog / Ready / In Progress / Blocked / Done |
+| Power Level    | Apprentice/Wizard/Sorcerer/Magus/Archmage      |
+| Execution Host | Atlas, Voyager, Nimbus                         |
+| Approval Gate  | Required reviewer and checkpoint               |
+| Exit Criteria  | Objective definition of done                   |
+| Status         | Backlog / Ready / In Progress / Blocked / Done |
 
 ---
 

package/dist/assets/.arcane/governance/decision-documentation-standard.md

@@ -26,10 +26,10 @@ This document defines how significant decisions are documented in this repositor
 
 Arcane separates framework-level decisions from org-specific ones using two prefixes:
 
-| Prefix    | File                  | Scope                                                                                |
-| --------- | --------------------- | ------------------------------------------------------------------------------------ |
-| `ADR-NNN` | `DECISIONS.md`        | Org-specific decisions (ventures, infrastructure, runtime config, org conventions)   |
-| `ARC-NNN` | `arcane/DECISIONS.md` | Arcane framework decisions (spell library, CLI, agent system, governance templates)  |
+| Prefix    | File                  | Scope                                                                               |
+| --------- | --------------------- | ----------------------------------------------------------------------------------- |
+| `ADR-NNN` | `DECISIONS.md`        | Org-specific decisions (ventures, infrastructure, runtime config, org conventions)  |
+| `ARC-NNN` | `arcane/DECISIONS.md` | Arcane framework decisions (spell library, CLI, agent system, governance templates) |
 
 **Rules:**
 
@@ -99,7 +99,7 @@ This check was added after [[governance/rcas/RCA-001-naming-collision|RCA-001]]
 **Create a companion doc if:**
 
 - Decision justification exceeds 5 bullets in "Reasoning" section
-- Multiple ADRs share a common theme (e.g., authentication strategy covers ADR-007, ADR-008, ADR-009, ADR-017)
+- Multiple ADRs share a common theme (e.g., several authentication decisions belong in one authentication strategy)
 - Implementation has significant gotchas or edge cases
 - Decision has ongoing review/maintenance requirements (quarterly audits, version compatibility)
 - You anticipate "why did we do this?" questions from future team members or external auditors
@@ -115,13 +115,13 @@ This check was added after [[governance/rcas/RCA-001-naming-collision|RCA-001]]
 
 Use existing folder structure; **do not create `deep-dives/` or `DECISIONS-details/` folders**.
 
-| Decision Theme                       | Location           | Example                                                                                 |
-| ------------------------------------ | ------------------ | --------------------------------------------------------------------------------------- |
-| Authentication, credentials, keys    | `security/`        | [security/authentication-strategy.md](../security/authentication-strategy.md)           |
-| Hardware, OS, dual-boot              | `infrastructure/`  | [infrastructure/compute-architecture.md](../infrastructure/compute-architecture.md)     |
-| Agent runtime config, agent policies | `agents/`          | [agents/architecture-decisions.md](../agents/architecture-decisions.md)                 |
-| Git, naming, documentation standards | `governance/`      | This file                                                                               |
-| Business-specific operations         | `ventures/{name}/` | `ventures/acme-store/DECISIONS.md`, `ventures/example-app/operations-model.md` |
+| Decision Theme                       | Location           | Example                                                                             |
+| ------------------------------------ | ------------------ | ----------------------------------------------------------------------------------- |
+| Authentication, credentials, keys    | `security/`        | [security/authentication-strategy.md](../security/authentication-strategy.md)       |
+| Hardware, OS, dual-boot              | `infrastructure/`  | [infrastructure/compute-architecture.md](../infrastructure/compute-architecture.md) |
+| Agent runtime config, agent policies | `agents/`          | [agents/architecture-decisions.md](../agents/architecture-decisions.md)             |
+| Git, naming, documentation standards | `governance/`      | This file                                                                           |
+| Business-specific operations         | `ventures/{name}/` | `ventures/acme-store/DECISIONS.md`, `ventures/example-app/operations-model.md`      |
 
 **Rationale:** Keeps security knowledge with security docs, infrastructure with infrastructure, etc. Easier to discover via folder browsing.
 
@@ -131,7 +131,7 @@ Use existing folder structure; **do not create `deep-dives/` or `DECISIONS-detai
 
 - ✅ `security/authentication-strategy.md` — covers SSH, PATs, API keys, tokens (multiple ADRs)
 - ✅ `infrastructure/compute-architecture.md` — covers dual-boot, Ubuntu choice, hardware sizing
-- ❌ `security/ADR-008-deep-dive.md` — Forces 1:1 mapping, harder to group related decisions
+- ❌ `security/ADR-NNN-deep-dive.md` — Forces 1:1 mapping, harder to group related decisions
 
 **Filename format:** `{topic-slug}.md` (lowercase, hyphen-separated)
 
@@ -214,7 +214,7 @@ Add this section **after Reasoning, before Rejected alternatives** in the ADR:
 **Deep dive:** [[security/authentication-strategy|Authentication Strategy]]
 ```
 
-**Example from ADR-017:**
+**Example from an authentication ADR:**
 
 ```markdown
 **Reasoning:**
@@ -238,12 +238,12 @@ Create "Related ADRs" section at the top of every companion doc:
 ```markdown
 ## Related ADRs
 
-- [[DECISIONS#ADR-007|ADR-007: Runtime Gateway Security]]
-- [[DECISIONS#ADR-008|ADR-008: Inter-Machine Communication]]
-- [[DECISIONS#ADR-017|ADR-017: Git SSH Authentication]]
+- [[DECISIONS#ADR-NNN|Runtime Gateway Security decision]]
+- [[DECISIONS#ADR-NNN|Inter-Machine Communication decision]]
+- [[DECISIONS#ADR-NNN|Git SSH Authentication decision]]
 ```
 
-**Rationale:** Creates bidirectional graph edges in Obsidian visualization. Clicking ADR-017 shows link to authentication-strategy.md; clicking authentication-strategy.md shows all related ADRs.
+**Rationale:** Creates bidirectional graph edges in Obsidian visualization. Clicking an ADR shows its authentication strategy companion; the companion links back to each related ADR.
 
 ---
 

package/dist/assets/.arcane/governance/framework-decisions.md

@@ -0,0 +1,71 @@
+---
+title: Legacy Framework Decision Reference
+audience: both
+status: active
+distributable: true
+tags: [decisions, adr, framework, references]
+---
+
+# Legacy Framework Decision Reference
+
+Arcane framework decisions now use the `ARC-NNN` sequence. The entries below preserve the legacy `ADR-NNN` identifiers still cited by distributed governance and spells so every installed citation resolves offline. Consumer repository decisions remain in the root `DECISIONS.md` and use their own local sequence.
+
+## ADR-002 — Documentation in Markdown and Git
+
+Keep operational documentation in reviewable, version-controlled Markdown alongside the work it governs.
+
+## ADR-011 — Troubleshooting Standard
+
+Troubleshooting guidance uses Symptom, Cause, Fix, Verify, and Prevention sections so remediation is reproducible.
+
+## ADR-019 — Spell Prompt Naming
+
+Arcane workflow prompts use the `spell-` prefix to make their purpose and invocation surface explicit.
+
+## ADR-028 — Agent Git Attribution Model
+
+The content producer is the commit author, the approving operator is the committer, and agent-authored commits carry attribution trailers.
+
+## ADR-029 — Canonical Commit Metadata Schema
+
+Agent commits use stable `Agent`, `Model`, and `Provider` trailers, with optional role, task, channel, and approval metadata.
+
+## ADR-031 — Agent Role Consolidation
+
+Agent identities represent durable roles rather than framework-specific technology stacks.
+
+## ADR-032 — Context-Dependent Agent Power Levels
+
+Agent autonomy is assigned per agent and repository through the Spectator-to-Archmage ladder.
+
+## ADR-034 — Actionable Recommendation Guardrails
+
+Recommendations involving cost, accounts, subscriptions, or irreversible action require disclosure, current verification, alternatives, and proportionate approval.
+
+## ADR-048 — Code Versus Docs Branch Policy
+
+Code repositories use protected integration branches and reviewed PRs. A genuinely local-only documentation repository may integrate a reviewed docs change with a local fast-forward when no remote PR path exists.
+
+## ADR-049 — Spell Loop
+
+Arcane's lifecycle is plan, architect, implement, test, review, and ship, with session and operational spells supporting the loop.
+
+## ADR-050 — Testing Standards
+
+Projects select stack-appropriate test tooling and enforce coverage and critical-path evidence before shipping.
+
+## ADR-051 — Infrastructure Agent Ownership
+
+The infrastructure role owns CI/CD, deployment automation, and platform operations while remaining subject to repository authority gates.
+
+## ADR-052 — Product Excellence Standards
+
+PRD enhancement uses explicit quality dimensions and profile-dependent Bronze, Silver, and Gold targets.
+
+## ADR-061 — Arcane Framework Identity
+
+Arcane is a four-layer methodology composed of Spells, Governance, Agents, and the CLI.
+
+## ADR-068 — Root Cause Analysis Standard
+
+Material incidents receive structured root cause analysis with evidence, corrective actions, prevention, and follow-up ownership.

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

@@ -167,7 +167,7 @@ Use `git add -p` or selective staging to separate unrelated changes that were ed
 ```bash
 # Stage only the files related to one logical change
 git add governance/new-standard.md DECISIONS.md CLAUDE.md
-git commit -m "docs(governance): add new-standard with ADR-053"
+git commit -m "docs(governance): add new-standard with ADR-NNN"
 
 # Then stage the unrelated fix
 git add README.md

package/dist/assets/.github/prompts/spell-todo.prompt.md

@@ -67,7 +67,7 @@ Expand the idea into one or more concrete TODO items. Each item must:
 
 If the idea naturally decomposes into multiple sub-items (e.g., "build dashboard" → design, implement, deploy, document), list them individually — do not bundle vague compound items.
 
-If the idea is an `adr-candidate`, also draft a one-sentence ADR title suggestion (e.g., `ADR-027: Use GitHub Actions for CI instead of Azure Pipelines`).
+If the idea is an `adr-candidate`, also draft a one-sentence ADR title suggestion (e.g., `ADR-NNN: Use GitHub Actions for CI instead of Azure Pipelines`).
 
 ## Step 3 — Route to the Right Document
 

package/dist/index.js

@@ -134,7 +134,7 @@ var PROFILE_CONFIGS = [
     id: "lite",
     displayName: "Essentials",
     description: "Spells + core governance \u2014 fast start",
-    components: ["spell-prompts", "claude-commands", "agent-output-instructions", "git-conventions", "testing-standards", "session-continuity"]
+    components: ["spell-prompts", "claude-commands", "agent-output-instructions", "git-conventions", "testing-standards", "framework-decisions", "session-continuity"]
   },
   {
     id: "methodology",
@@ -146,6 +146,7 @@ var PROFILE_CONFIGS = [
       "agent-output-instructions",
       "git-conventions",
       "testing-standards",
+      "framework-decisions",
       "session-continuity",
       "decision-documentation-standard",
       "agent-work-queue-model",
@@ -161,6 +162,7 @@ var PROFILE_CONFIGS = [
       "agent-output-instructions",
       "git-conventions",
       "testing-standards",
+      "framework-decisions",
       "decision-documentation-standard",
       "agent-work-queue-model",
       "naming-conventions",
@@ -203,6 +205,11 @@ var COMPONENTS = [
     description: "Testing framework selection, coverage thresholds, and CI gates",
     files: [".arcane/governance/testing-standards.md"]
   },
+  {
+    name: "framework-decisions",
+    description: "Offline reference for legacy framework ADR citations",
+    files: [".arcane/governance/framework-decisions.md"]
+  },
   {
     name: "decision-documentation-standard",
     description: "ADR format and decision-logging conventions",