arcane-cli 0.15.5 → 0.15.7

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/.arcane/governance/portable-bootstrap.md

@@ -38,14 +38,21 @@ Paste this entire file into any AI client (Claude web, ChatGPT, etc.) to give it
 
 ## Key Files
 
-| Need               | File                                  |
-| ------------------ | ------------------------------------- |
-| Full rules         | `governance/universal-agent-rules.md` |
-| Project overview   | `project.md`                          |
-| Decisions log      | `DECISIONS.md`                        |
-| Agent policies     | `agents/agent-policies.md`            |
-| Git conventions    | `governance/git-conventions.md`       |
-| AI context summary | `ai-context/system-prompt-context.md` |
+| Need               | File                                          |
+| ------------------ | --------------------------------------------- |
+| Full rules         | `.arcane/governance/universal-agent-rules.md` |
+| Project overview   | `project.md`                                  |
+| Decisions log      | `DECISIONS.md`                                |
+| Agent policies     | `.arcane/governance/agent-policies.md`        |
+| Git conventions    | `.arcane/governance/git-conventions.md`       |
+| AI context summary | `ai-context/system-prompt-context.md`         |
+
+## Where Documents Live
+
+- **Framework-managed standards:** `.arcane/governance/`. Spells reference this single installed layer; do not create a duplicate root `governance/` tree.
+- **Project-owned orientation and continuity:** `README.md`, `project.md`, `TODO.md`, `DECISIONS.md`, `ai-context/`, and `journal/`. Arcane creates missing files once and preserves existing content.
+- **Project/domain documents:** use explicit descriptive paths such as `docs/`, `security/`, `infrastructure/`, or a configured business root. These add project context alongside framework standards.
+- **Overrides are not yet supported:** editing a managed `.arcane/governance/` standard can be replaced by `arcane update`. Additive project documents are safe; overriding a shipped standard requires the open customization/override model.
 
 ## Documentation Format
 
@@ -53,11 +60,11 @@ Every doc uses YAML frontmatter: `title`, `audience` (human/ai/both), `last_upda
 
 ## Naming Tiers
 
-| Tier      | Style           | Examples                                  |
-| --------- | --------------- | ----------------------------------------- |
-| Machines  | Iconic names    | Atlas, Voyager                       |
+| Tier      | Style           | Examples                                 |
+| --------- | --------------- | ---------------------------------------- |
+| Machines  | Iconic names    | Atlas, Voyager                           |
 | AI Agents | Persona + role  | Merlin — CTO, {AGENT_NAME} — Product Ops |
-| Systems   | Functional slug | `inventory-api`, `orders-worker`          |
+| Systems   | Functional slug | `inventory-api`, `orders-worker`         |
 
 ## Version Control Host
 
@@ -98,4 +105,4 @@ Development follows the **Spell Loop** — structured planning phases feeding an
 - `spell-explain-concept` — Break down complex architecture concepts
 - `spell-generate-bot-icons` — Create agent personas and icons
 
-Full reference: See `governance/development-methodology.md` in the repo.
+Full reference: See `.arcane/governance/development-methodology.md` in the repo.

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

@@ -10,7 +10,7 @@ agent: agent
 - This prompt takes a PRD and produces architecture decisions plus an implementable story breakdown.
 - It follows a structured solutioning pattern — progressive context chain from requirements to implementation plan.
 - Outputs `architecture.md` and `stories.json` that feed into `spell-implement`.
-- See [[governance/development-methodology|Development Methodology]] for full Spell Loop reference.
+- See [[.arcane/governance/development-methodology|Development Methodology]] for full Spell Loop reference.
 
 ---
 
@@ -18,8 +18,8 @@ Generate architecture decisions and story breakdown from the provided PRD.
 
 Use these files for context:
 
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology and stories.json format
-- [governance/testing-standards.md](../../governance/testing-standards.md) — Testing frameworks and coverage requirements
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology and stories.json format
+- [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Testing frameworks and coverage requirements
 - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to respect and extend
 
 Workflow:

package/dist/assets/.github/prompts/spell-bootstrap-business.prompt.md

@@ -24,7 +24,7 @@ If any required value is missing, ask only for missing fields.
 Use these files first (each is optional — if missing, proceed as noted):
 
 - [playbooks/new-business-setup.md](../../playbooks/new-business-setup.md) — setup playbook. If `playbooks/` doesn't exist, skip and derive steps from the business-type checklist below.
-- [naming-conventions.md](../../naming-conventions.md) — slug/file naming rules. If missing, default to lowercase-with-dashes slugs.
+- [naming-conventions.md](../../.arcane/governance/naming-conventions.md) — slug/file naming rules. If missing, default to lowercase-with-dashes slugs.
 - [ventures/\_template/overview.md](../../ventures/_template/overview.md) — overview template. If missing, generate a minimal overview from the fields below.
 - [README.md](../../README.md) — repo navigation. If missing, skip cross-linking.
 - [project.md](../../project.md) — project context. If missing, skip.

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

@@ -18,10 +18,10 @@ Explore the given problem space and generate solution options.
 
 Use these files for context. Each is **optional** — if a file is missing, proceed without it and note the gap in your output so the user knows what wasn't consulted:
 
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology. _If missing:_ proceed with general SDLC reasoning.
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology. _If missing:_ proceed with general SDLC reasoning.
 - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs (to avoid contradicting decided patterns). _If missing:_ assume no decided patterns and state that ADR conflicts could not be checked.
 - [project.md](../../project.md) — Project goals and business context. _If missing:_ infer context from the problem statement and ask a clarifying question if goals are unclear.
-- [naming-conventions.md](../../naming-conventions.md) — Agent roster and roles. _If missing:_ proceed without role references.
+- [naming-conventions.md](../../.arcane/governance/naming-conventions.md) — Agent roster and roles. _If missing:_ proceed without role references.
 - [TODO.md](../../../TODO.md) — In-progress work (referenced in step 4). _If missing:_ skip the in-progress-work cross-check and note it.
 
 ---

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

@@ -11,7 +11,7 @@ agent: agent
 - It records the bug in your configured tracker (external provider) or `TODO.md` (internal mode) and links the fix commit to it.
 - Output is a working fix with tests, committed using Conventional Commits format.
 - **When to use:** you have a concrete defect — wrong/broken behavior versus expected. If the report is actually a request for *new* behavior, route to `spell-suggest-feature` instead. For small non-blocking cleanups discovered along the way, capture them with `spell-todo`.
-- See [[governance/development-methodology|Development Methodology]] for full Spell Loop reference.
+- See [[.arcane/governance/development-methodology|Development Methodology]] for full Spell Loop reference.
 
 ---
 
@@ -19,9 +19,9 @@ Document, diagnose, and fix the described bug.
 
 Use these files for context (each is optional — if a file is missing, proceed and note the assumption you fell back on):
 
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology **and tracker-provider specifics** (which tracker, work-item types, commit-link syntax). If missing, default to `tracking_mode: internal` and track in `TODO.md`.
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology **and tracker-provider specifics** (which tracker, work-item types, commit-link syntax). If missing, default to `tracking_mode: internal` and track in `TODO.md`.
 - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to respect. If missing, proceed without ADR constraints.
-- [governance/testing-standards.md](../../governance/testing-standards.md) — Coverage thresholds. If missing, match the test conventions already present in the repo.
+- [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Coverage thresholds. If missing, match the test conventions already present in the repo.
 
 Workflow:
 
@@ -40,7 +40,7 @@ Workflow:
 2. **Record the bug** — file it in whatever tracker this repo uses. Resolve `tracking_mode` from `.arcane.json` (or the repo's feature/PRD frontmatter); if unset, **ask** rather than assuming.
 
    - **`tracking_mode: internal`** (or no tracker configured) — append the bug to `TODO.md` (create it if absent) using the captured fields from Step 1. Use the `TODO.md` entry's identifier as `{WORK_ITEM_ID}`. No external tooling required.
-   - **`tracking_mode: external`** — file a work item in the configured provider. Read [governance/development-methodology.md](../../governance/development-methodology.md) for the provider, work-item type, and required fields; do **not** assume Azure DevOps. Extract the returned id as `{WORK_ITEM_ID}`.
+   - **`tracking_mode: external`** — file a work item in the configured provider. Read [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) for the provider, work-item type, and required fields; do **not** assume Azure DevOps. Extract the returned id as `{WORK_ITEM_ID}`.
 
      *Azure DevOps is one such provider — if and only if `.arcane.json` / methodology names it (and the `az` CLI is available), file it like so. Resolve `{ADO_ORG}` and `{ADO_PROJECT}` from `.arcane.json`; ask if unset:*
      ```bash
@@ -86,7 +86,7 @@ Workflow:
 
    {WORK_ITEM_LINK}
    ```
-   Follow Conventional Commits format. For `{WORK_ITEM_LINK}`, use the commit-link convention your tracker expects (per [governance/development-methodology.md](../../governance/development-methodology.md)) — e.g. `Fixes AB#{WORK_ITEM_ID}` for Azure DevOps, `Fixes #{WORK_ITEM_ID}` for GitHub Issues, or a plain `Refs TODO.md` for internal mode. Wait for user approval before executing `git commit`.
+   Follow Conventional Commits format. For `{WORK_ITEM_LINK}`, use the commit-link convention your tracker expects (per [governance/development-methodology.md](../../.arcane/governance/development-methodology.md)) — e.g. `Fixes AB#{WORK_ITEM_ID}` for Azure DevOps, `Fixes #{WORK_ITEM_ID}` for GitHub Issues, or a plain `Refs TODO.md` for internal mode. Wait for user approval before executing `git commit`.
 
 8. **Close out the tracker** — update the work item's state to reflect the fix:
    - **`internal`** — mark the `TODO.md` entry as resolved (check it off / move to a Done section).
@@ -98,7 +98,7 @@ Workflow:
        --org https://dev.azure.com/{ADO_ORG} \
        --output json
      ```
-     For other providers, follow [governance/development-methodology.md](../../governance/development-methodology.md).
+     For other providers, follow [governance/development-methodology.md](../../.arcane/governance/development-methodology.md).
 
 Rules:
 - Fix only the reported bug. Do not bundle unrelated improvements.

package/dist/assets/.github/prompts/spell-check-drift.prompt.md

@@ -25,7 +25,7 @@ Use these files first:
 - [TODO.md](../../TODO.md)
 - [DECISIONS.md](../../DECISIONS.md)
 - [ai-context/system-prompt-context.md](../../ai-context/system-prompt-context.md)
-- [agents/agent-policies.md](../../agents/agent-policies.md)
+- [agents/agent-policies.md](../../.arcane/governance/agent-policies.md)
 - Most recent journal file(s) in [journal/](../../journal/)
 - Relevant business overviews under [ventures/](../../ventures/)
 

package/dist/assets/.github/prompts/spell-close-session.prompt.md

@@ -137,7 +137,7 @@ Rules:
     - Delete the local topic branch: `git branch -d <branch>`.
    - Verify `git log --oneline -3` shows the merged change at HEAD.
     - If stale local branches exist (merged or older than 7 days), list them and suggest cleanup.
-    - See [governance/git-conventions.md](../../governance/git-conventions.md) Post-Merge Cleanup section.
+    - See [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) Post-Merge Cleanup section.
 
 11. **Return a concise closure report.**
 

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

@@ -19,7 +19,7 @@ Commit the current work in progress using Conventional Commits format.
 
 Use these files first:
 
-- [governance/git-conventions.md](../../governance/git-conventions.md) — Conventional Commits reference and agent attribution model
+- [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) — Conventional Commits reference and agent attribution model
 - [DECISIONS.md](../../DECISIONS.md) — for ADR context if relevant
 
 Workflow:
@@ -50,7 +50,7 @@ Workflow:
      - Run the detected formatter, then `git add` the resulting changes so they are part of this commit.
      - **If no formatter is configured, skip this step gracefully** — do not install one and do not block the commit.
 
-3. **Determine authorship and partition the batch** — who produced each changed file or inseparable change set? See [governance/git-conventions.md](../../governance/git-conventions.md) Agent Attribution Model section and ADR-028.
+3. **Determine authorship and partition the batch** — who produced each changed file or inseparable change set? See [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) Agent Attribution Model section and ADR-028.
    - **Invariant: one commit has exactly one author.** Changes spanning authors must be split into separate commits.
    - Partition changed files by author first. Step 4 then groups by concern within each author partition; concern grouping must never recombine authors.
    - **Human wrote it:** no `--author` override needed (uses global Git config)
@@ -208,7 +208,7 @@ Workflow:
 - If branch is not attached to any active worktree, run `git branch -d <branch>`.
 - Return to `main` only when appropriate for the active session/worktree context.
 - If other stale local branches exist (merged or older than 7 days), list them and suggest cleanup.
-- See [governance/git-conventions.md](../../governance/git-conventions.md) Post-Merge Cleanup section.
+- See [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) Post-Merge Cleanup section.
 
 ## Troubleshooting
 

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

@@ -9,7 +9,7 @@ agent: agent
 
 - This spell takes an existing PRD and enchants it to production-grade quality.
 - It proactively identifies missing features, UX gaps, accessibility issues, performance targets, and security requirements that the original PRD didn't specify.
-- Applies two analytical lenses: a **research lens** (competitive analysis, industry standards) and a **marketing/brand lens** (brand, UX, first-impression review). In the default Arcane roster these map to the Alexander and Circe personas; other orgs map their own — see [agent-policies](../../agents/agent-policies.md) / [naming-conventions](../../governance/naming-conventions.md).
+- Applies two analytical lenses: a **research lens** (competitive analysis, industry standards) and a **marketing/brand lens** (brand, UX, first-impression review). In the default Arcane roster these map to the Alexander and Circe personas; other orgs map their own — see [agent-policies](../../.arcane/governance/agent-policies.md) / [naming-conventions](../../.arcane/governance/naming-conventions.md).
 - Output: Enhanced PRD with `[ENCHANTED]`-tagged additions, before/after quality scorecard, and research summaries.
 - Use this between `spell-plan` and `spell-architect` (or `spell-scope` for large PRDs). It **consumes** a drafted PRD and **feeds** an architecture/scoping spell; it does not author a PRD from scratch (that is `spell-plan`) nor implement one (`spell-implement`).
 
@@ -19,11 +19,11 @@ Enchant the provided PRD to exceptional quality.
 
 Use these files for context. All are optional — if a file is absent, fall back as noted and continue rather than aborting:
 
-- [governance/product-excellence-standards.md](../../governance/product-excellence-standards.md) — Quality dimensions, PRD Quality Scorecard, scoring rubric (Bronze / Silver / Gold). **If missing:** warn the user that the canonical scorecard was not found, then proceed with the embedded dimension list (Requirements Completeness, UX, Accessibility, Performance, Security, Responsive Design, Competitive Differentiation) and default to the **Public MVP** profile.
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology, story sizing rules. **If missing:** treat story sizing as advisory and proceed.
-- [governance/testing-standards.md](../../governance/testing-standards.md) — Testing frameworks and coverage thresholds. **If missing:** omit framework-specific coverage targets from acceptance criteria.
+- [governance/product-excellence-standards.md](../../.arcane/governance/product-excellence-standards.md) — Quality dimensions, PRD Quality Scorecard, scoring rubric (Bronze / Silver / Gold). **If missing:** warn the user that the canonical scorecard was not found, then proceed with the embedded dimension list (Requirements Completeness, UX, Accessibility, Performance, Security, Responsive Design, Competitive Differentiation) and default to the **Public MVP** profile.
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology, story sizing rules. **If missing:** treat story sizing as advisory and proceed.
+- [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Testing frameworks and coverage thresholds. **If missing:** omit framework-specific coverage targets from acceptance criteria.
 - [security/threat-model.md](../../security/threat-model.md) — Active threat model. **If missing:** apply generic OWASP-style security baselines for the Security dimension.
-- [agents/agent-policies.md](../../agents/agent-policies.md) / [governance/naming-conventions.md](../../governance/naming-conventions.md) — Agent roster and persona naming. **If missing:** apply the two lenses (research, marketing/brand) without naming personas.
+- [agents/agent-policies.md](../../.arcane/governance/agent-policies.md) / [governance/naming-conventions.md](../../.arcane/governance/naming-conventions.md) — Agent roster and persona naming. **If missing:** apply the two lenses (research, marketing/brand) without naming personas.
 - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to respect. **If missing:** assume no binding ADR constraints.
 - [project.md](../../project.md) — Project goals and business context. **If missing:** infer business context from the PRD itself and flag any assumptions.
 
@@ -42,7 +42,7 @@ Accept the PRD from one of these input sources:
 | **Tracker work item ID** | `#508` or `508` with a tracker reference | Respect `tracking_mode` and detect the provider (see below), then fetch the work item and extract its title, description, and acceptance criteria |
 
 If the input is a tracker work item ID:
-1. **Determine tracking mode and provider.** Read `tracking_mode` (internal/external) from `.arcane.json` or PRD frontmatter, and detect the configured tracker provider rather than assuming one. The shared tracker-resolution rules live in [governance/development-methodology.md](../../governance/development-methodology.md) — follow them rather than hard-coding a single provider.
+1. **Determine tracking mode and provider.** Read `tracking_mode` (internal/external) from `.arcane.json` or PRD frontmatter, and detect the configured tracker provider rather than assuming one. The shared tracker-resolution rules live in [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — follow them rather than hard-coding a single provider.
    - For an **Azure DevOps** provider, fetch via `az boards work-item show --id {id} --org https://dev.azure.com/{ADO_ORG} --output json` and extract `System.Description`, `Microsoft.VSTS.Common.AcceptanceCriteria`, and `System.Title`. Resolve `{ADO_ORG}` (and `{ADO_PROJECT}` if needed) from `.arcane.json` or the PRD frontmatter; **if unset, ask the user** rather than assuming a default.
    - For other providers (e.g. a GitHub issue), use the provider's equivalent fetch and map title / body / acceptance-criteria fields accordingly.
 2. If the work item has child items, fetch those too — they may contain additional requirements.
@@ -93,7 +93,7 @@ For each dimension where the current score is **below the profile's target**, id
 
 ### 3. Research Phase (Research Lens)
 
-Apply the **research lens** (in the default Arcane roster this is the Alexander / Research & Backlog Analyst persona — see [agent-policies](../../agents/agent-policies.md) / [naming-conventions](../../governance/naming-conventions.md); other orgs map their own analyst). Conduct a thorough analysis:
+Apply the **research lens** (in the default Arcane roster this is the Alexander / Research & Backlog Analyst persona — see [agent-policies](../../.arcane/governance/agent-policies.md) / [naming-conventions](../../.arcane/governance/naming-conventions.md); other orgs map their own analyst). Conduct a thorough analysis:
 
 #### 3a. Competitive Analysis
 - Identify the top 3 alternatives/competitors for this type of app
@@ -143,7 +143,7 @@ Document findings as (the persona name below reflects the default roster; substi
 
 ### 4. Marketing & Brand Review (Marketing/Brand Lens)
 
-Apply the **marketing/brand lens** (in the default Arcane roster this is the Circe / Marketing Strategist persona — see [agent-policies](../../agents/agent-policies.md) / [naming-conventions](../../governance/naming-conventions.md); other orgs map their own strategist). Evaluate the PRD from a brand and user-perception perspective:
+Apply the **marketing/brand lens** (in the default Arcane roster this is the Circe / Marketing Strategist persona — see [agent-policies](../../.arcane/governance/agent-policies.md) / [naming-conventions](../../.arcane/governance/naming-conventions.md); other orgs map their own strategist). Evaluate the PRD from a brand and user-perception perspective:
 
 #### 4a. First Impressions
 - If a user saw this app for the first time with zero context, what would they think?

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

@@ -10,7 +10,7 @@ agent: agent
 - This prompt chains all Spell Loop phases into a single autonomous pipeline.
 - Includes optional PRD enchantment (spell-enchant) between Plan and Architect for quality enhancement.
 - Only one human touchpoint: approving the PR at ship time.
-- Delegates each phase to the appropriate specialized agent role (research, architecture, build, QA, marketing review). Resolve concrete personas from [agent-policies](../../governance/agent-policies.md) / [naming-conventions](../../governance/naming-conventions.md); if neither is present, proceed with role names directly.
+- Delegates each phase to the appropriate specialized agent role (research, architecture, build, QA, marketing review). Resolve concrete personas from [agent-policies](../../.arcane/governance/agent-policies.md) / [naming-conventions](../../.arcane/governance/naming-conventions.md); if neither is present, proceed with role names directly.
 - If any phase fails, the pipeline halts and reports the blocker — no silent failures.
 
 ---
@@ -19,13 +19,13 @@ Run the complete Spell Loop end-to-end for the described feature.
 
 Use these files for context:
 
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology and stories.json format
-- [governance/testing-standards.md](../../governance/testing-standards.md) — Testing frameworks and coverage requirements
-- [governance/cicd-standards.md](../../governance/cicd-standards.md) — CI/CD pipeline and deployment gates
-- [governance/git-conventions.md](../../governance/git-conventions.md) — Branch discipline and commit format
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology and stories.json format
+- [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Testing frameworks and coverage requirements
+- [governance/cicd-standards.md](../../.arcane/governance/cicd-standards.md) — CI/CD pipeline and deployment gates
+- [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) — Branch discipline and commit format
 - [project.md](../../project.md) — Project goals and priorities
 - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to respect
-- [governance/product-excellence-standards.md](../../governance/product-excellence-standards.md) — PRD Quality Scorecard for enchantment
+- [governance/product-excellence-standards.md](../../.arcane/governance/product-excellence-standards.md) — PRD Quality Scorecard for enchantment
 
 ---
 

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

@@ -10,7 +10,7 @@ agent: agent
 - This is the core autonomous loop of the Spell Loop methodology.
 - Each iteration: pick a story → implement → run tests → commit if passing → update stories.json → loop.
 - Uses fresh context per iteration — only stories.json, progress.txt, and git history carry forward.
-- See [[governance/development-methodology|Development Methodology]] for full Spell Loop reference.
+- See [[.arcane/governance/development-methodology|Development Methodology]] for full Spell Loop reference.
 
 ---
 
@@ -18,8 +18,8 @@ Run the autonomous implementation loop for the current feature.
 
 Use these files for context:
 
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology
-- [governance/testing-standards.md](../../governance/testing-standards.md) — Testing frameworks and coverage requirements
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology
+- [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Testing frameworks and coverage requirements
 - The feature's `architecture.md` — for tech decisions and patterns
 - The feature's `stories.json` — for the work breakdown
 - The feature's `progress.txt` (in `features/{slug}/`, if present) — accumulated learnings from prior iterations; read it before each iteration and append new learnings as the loop proceeds

package/dist/assets/.github/prompts/spell-open-session.prompt.md

@@ -24,9 +24,9 @@ Use these files first:
 - [project.md](../../project.md)
 - [TODO.md](../../TODO.md)
 - [DECISIONS.md](../../DECISIONS.md)
-- [naming-conventions.md](../../naming-conventions.md)
+- [naming-conventions.md](../../.arcane/governance/naming-conventions.md)
 - [ai-context/system-prompt-context.md](../../ai-context/system-prompt-context.md)
-- [agents/agent-policies.md](../../agents/agent-policies.md)
+- [agents/agent-policies.md](../../.arcane/governance/agent-policies.md)
 - Most recent journal file(s) in [journal/](../../journal/)
 - Relevant business overview(s) under [ventures/](../../ventures/)
 

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

@@ -10,7 +10,7 @@ agent: agent
 - This prompt generates a PRD.md from a feature description or TODO item.
 - It follows a structured analysis pattern — requirements, acceptance criteria, and constraints.
 - Output feeds directly into `spell-architect` as the next phase of the Spell Loop.
-- See [[governance/development-methodology|Development Methodology]] for full Spell Loop reference.
+- See [[.arcane/governance/development-methodology|Development Methodology]] for full Spell Loop reference.
 
 ---
 
@@ -18,7 +18,7 @@ Generate a Product Requirements Document for the described feature or initiative
 
 Use these files for context:
 
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology
 - [project.md](../../project.md) — Project goals and priorities
 - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to respect
 

package/dist/assets/.github/prompts/spell-present-arcane.prompt.md

@@ -5,7 +5,7 @@ argument-hint: '[summary|deck] + optional audience/size — e.g., "for investors
 agent: agent
 ---
 
-See [[governance/development-methodology|Development Methodology]] for full Spell Loop reference. Project context: [[project|Project Overview]].
+See [[.arcane/governance/development-methodology|Development Methodology]] for full Spell Loop reference. Project context: [[project|Project Overview]].
 
 ## Mode Selection
 
@@ -39,10 +39,10 @@ Read these files before generating the presentation. They are the ground truth *
 | [project.md](../../project.md) | Mission, vision, core principles, entities, goals | `README.md`, then ask the operator for the mission |
 | [ai-context/system-prompt-context.md](../../ai-context/system-prompt-context.md) | Environment, agent stack, current state | Infer environment from repo; omit slide detail if unknown |
 | [DECISIONS.md](../../DECISIONS.md) | Key ADRs — decisions that shaped the architecture | Skip ADR callouts; note that decision records are absent |
-| [agents/agent-capability-matrix.md](../../agents/agent-capability-matrix.md) | Agent lineup and capability tiers | `.github/agents/*.agent.md`; else present the system generically |
-| [agents/agent-policies.md](../../agents/agent-policies.md) | Power levels, autonomy model | [[governance/naming-conventions]]; else describe roles generically |
+| `.github/agents/*.agent.md` | Agent lineup and capability tiers | Present the system generically if no generated agent files exist |
+| [agents/agent-policies.md](../../.arcane/governance/agent-policies.md) | Power levels, autonomy model | [[.arcane/governance/naming-conventions]]; else describe roles generically |
 | `{BUSINESS_ROOT}/<business>/overview.md` | Per-business status (repeat for each business found) | Enumerate `{BUSINESS_ROOT}/*`; if none, present Arcane without a ventures act |
-| [governance/development-methodology.md](../../governance/development-methodology.md) | The Spell Loop — development workflow | Describe the Spell Loop from the spell library filenames |
+| [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) | The Spell Loop — development workflow | Describe the Spell Loop from the spell library filenames |
 | `{INFRA_DOC}` — hardware/infra inventory (e.g. `infrastructure/hardware-inventory.md`) | Hardware context for demo credibility | Detect any infra/hardware doc; else omit the infrastructure slide |
 | [README.md](../../README.md) | Repo structure overview | List top-level directories directly |
 
@@ -87,7 +87,7 @@ Read these files before generating the presentation. They are the ground truth *
 
 5. **Arcane — the operating system for AI-run businesses** — What the repo is, what it contains, how it's structured
 6. **Security model** — full-disk encryption, least privilege, no root, SecretRef, private network mesh — why security is non-negotiable for a production system
-7. **The AI agent stack** — the gateway plus the agent lineup, power levels, and tool profiles. Populate the roster from the agent-capability-matrix / `.github/agents/*.agent.md` (see [[governance/agent-policies]] / [[governance/naming-conventions]]); name each `{AGENT_NAME}` with its role rather than assuming a fixed cast. If no roster files exist, describe agent *roles* (e.g. research, marketing, ops, dev) generically.
+7. **The AI agent stack** — the gateway plus the agent lineup, power levels, and tool profiles. Populate the roster from the agent-capability-matrix / `.github/agents/*.agent.md` (see [[.arcane/governance/agent-policies]] / [[.arcane/governance/naming-conventions]]); name each `{AGENT_NAME}` with its role rather than assuming a fixed cast. If no roster files exist, describe agent *roles* (e.g. research, marketing, ops, dev) generically.
 8. **The Spell Loop** — Arcane's development methodology: spell-plan → spell-architect → spell-implement → spell-ship
 9. **Multi-client AI governance** — Same rules enforced across every AI client the operator uses. Cite the relevant governance ADR if a decision record exists (resolve the ADR id from `DECISIONS.md`); otherwise state the principle without an id.
 10. **Ventures overview** — one line per business found under `{BUSINESS_ROOT}` (e.g. `{BUSINESS_NAME}` — launch-ready, `{BUSINESS_NAME}` — active dev), plus the idea pipeline. If none exist, replace with a roadmap slide.

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

@@ -25,7 +25,7 @@ Use these files for context:
 
 - [project.md](../../project.md) — Business goals and priorities
 - The relevant business docs under `{BUSINESS_ROOT}/` — KPIs, metrics, and product strategy. **If `{BUSINESS_ROOT}` or these docs are missing, proceed with what `project.md` provides and flag the gap; if even `project.md` is absent, report "insufficient context to review" and list what is missing rather than inventing goals.**
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop context
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop context
 
 Workflow:
 

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

@@ -10,7 +10,7 @@ agent: agent
 - This prompt performs an adversarial code review — "looks good" is not acceptable.
 - The reviewer must explicitly cover every lens — correctness, security, performance, tests, naming/clarity, architecture — and state "no issues" for any lens that is clean. There is no finding quota: zero findings is a valid outcome on a clean or small diff.
 - Checks architecture compliance, test coverage, security, and coding standards.
-- See [[governance/development-methodology|Development Methodology]] for the adversarial review pattern.
+- See [[.arcane/governance/development-methodology|Development Methodology]] for the adversarial review pattern.
 
 ---
 
@@ -18,8 +18,8 @@ Perform an adversarial review of the specified code changes.
 
 Use these files for context:
 
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Adversarial review requirements
-- [governance/testing-standards.md](../../governance/testing-standards.md) — Coverage thresholds to validate
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Adversarial review requirements
+- [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Coverage thresholds to validate
 - [DECISIONS.md](../../DECISIONS.md) — ADRs to check compliance against
 - [security/threat-model.md](../../security/threat-model.md) — Security controls to validate
 - The feature's `architecture.md` — tech decisions that code must follow