arcane-cli 0.15.5 → 0.15.7

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

@@ -18,15 +18,15 @@ Analyze the provided PRD and produce a scoped execution plan.
 
 Use these files for context. Each is optional — if a file is missing, proceed with the stated fallback and note the gap in the output's Open Questions:
 
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology, story sizing rules, and the canonical **ADO Hierarchy Rules**. *Fallback: if missing, use the default sizing of 4–8 right-sized stories per cycle described below and skip external-tracker hierarchy mapping.*
-- [governance/testing-standards.md](../../governance/testing-standards.md) — Testing frameworks per stack. *Fallback: if missing, flag test strategy as an open question.*
-- [governance/cicd-standards.md](../../governance/cicd-standards.md) — Pipeline requirements. *Fallback: if missing, omit pipeline considerations.*
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology, story sizing rules, and the canonical **ADO Hierarchy Rules**. *Fallback: if missing, use the default sizing of 4–8 right-sized stories per cycle described below and skip external-tracker hierarchy mapping.*
+- [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Testing frameworks per stack. *Fallback: if missing, flag test strategy as an open question.*
+- [governance/cicd-standards.md](../../.arcane/governance/cicd-standards.md) — Pipeline requirements. *Fallback: if missing, omit pipeline considerations.*
 - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to check against. *Fallback: if missing, treat all architecture decisions as new candidates.*
 - [security/threat-model.md](../../security/threat-model.md) — Active threat model. *Fallback: if missing, apply OWASP Top 10 as the baseline.*
-- [agents/agent-policies.md](../../agents/agent-policies.md) — Agent roster, power levels, capabilities. *Fallback: if missing, assign work by role label (architecture, backend, frontend, mobile, QA, DevOps, research) instead of named personas.*
-- [naming-conventions.md](../../naming-conventions.md) — Agent roster and role-to-persona mapping. *Fallback: if missing, refer to roles by their generic label.*
+- [agents/agent-policies.md](../../.arcane/governance/agent-policies.md) — Agent roster, power levels, capabilities. *Fallback: if missing, assign work by role label (architecture, backend, frontend, mobile, QA, DevOps, research) instead of named personas.*
+- [naming-conventions.md](../../.arcane/governance/naming-conventions.md) — Agent roster and role-to-persona mapping. *Fallback: if missing, refer to roles by their generic label.*
 - [project.md](../../project.md) — Project goals and business context. *Fallback: if missing, derive context from the PRD itself.*
-- [governance/product-excellence-standards.md](../../governance/product-excellence-standards.md) — PRD Quality Scorecard and scoring rubric. *Fallback: if missing, skip the Quality Quick-Check (section 1.5) and note that it was skipped.*
+- [governance/product-excellence-standards.md](../../.arcane/governance/product-excellence-standards.md) — PRD Quality Scorecard and scoring rubric. *Fallback: if missing, skip the Quality Quick-Check (section 1.5) and note that it was skipped.*
 
 > **Roster by reference.** This spell maps work to **roles** (architecture, backend, frontend, mobile, QA, DevOps, research, marketing). Resolve each role to a concrete agent persona via `agents/agent-policies.md` / `naming-conventions.md` at run time — do not assume a fixed set of persona names.
 
@@ -118,7 +118,7 @@ For each epic, define:
 
 Only applies when `tracking_mode=external`. Skip entirely for internal mode.
 
-Do **not** inline the work-item-type fallback order or the parent/child linkage rules here — they are the single source of truth in [governance/development-methodology.md](../../governance/development-methodology.md) → **Process-Template-Aware ADO Hierarchy Rules**. Detect the provider from `external_provider`, then apply those rules. *Fallback: if that doc is missing, record the tracker mapping as an Open Question and proceed without item-type assignment.*
+Do **not** inline the work-item-type fallback order or the parent/child linkage rules here — they are the single source of truth in [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) → **Process-Template-Aware ADO Hierarchy Rules**. Detect the provider from `external_provider`, then apply those rules. *Fallback: if that doc is missing, record the tracker mapping as an Open Question and proceed without item-type assignment.*
 
 Scope-specific delta (the only thing this spell adds on top of those rules): each split **epic** maps to the **Epic-level** logical level — use the `Epic` work item type whenever the resolved provider/template offers it, and record the selected type per epic in `execution-plan.md`. All lower-level and linkage decisions defer to the governance rules above.
 

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

@@ -18,10 +18,10 @@ Run the ship workflow for the specified branch or PR.
 
 Use these files for context:
 
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop phases
-- [governance/cicd-standards.md](../../governance/cicd-standards.md) — CI/CD pipeline requirements and deployment gates
-- [governance/testing-standards.md](../../governance/testing-standards.md) — Coverage thresholds
-- [governance/git-conventions.md](../../governance/git-conventions.md) — Branch policies and merge strategy
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop phases
+- [governance/cicd-standards.md](../../.arcane/governance/cicd-standards.md) — CI/CD pipeline requirements and deployment gates
+- [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Coverage thresholds
+- [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) — Branch policies and merge strategy
 
 Workflow:
 
@@ -86,7 +86,7 @@ Workflow:
 7. **Request human approval** — present the ship report and wait for explicit approval.
 
 8. **Execute merge** (after approval):
-   - Merge using the project's merge strategy as defined in [governance/git-conventions.md](../../governance/git-conventions.md). **Do NOT squash** — squash merges are prohibited because they collapse per-commit attribution. Prefer rebase and fast-forward.
+   - Merge using the project's merge strategy as defined in [governance/git-conventions.md](../../.arcane/governance/git-conventions.md). **Do NOT squash** — squash merges are prohibited because they collapse per-commit attribution. Prefer rebase and fast-forward.
    - Verify CI passes on the target branch post-merge.
    - Tag release if applicable.
 

package/dist/assets/.github/prompts/spell-suggest-feature.prompt.md

@@ -10,7 +10,7 @@ agent: agent
 - This prompt captures feature suggestions discovered during smoke testing or regular use.
 - It creates a structured user story, assesses impact, and files a tracker item using whatever provider the repo is configured for (respects `tracking_mode`; ADO is one option, not an assumption).
 - Output is a tracked backlog item ready for future `spell-plan` invocation (or `spell-scope` for large, multi-feature suggestions).
-- See [[governance/development-methodology|Development Methodology]] for the full Spell Loop reference and tracker-provider specifics.
+- See [[.arcane/governance/development-methodology|Development Methodology]] for the full Spell Loop reference and tracker-provider specifics.
 
 ---
 
@@ -18,7 +18,7 @@ Capture and document the described feature suggestion.
 
 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 check for overlap
 - [TODO.md](../../TODO.md) — Current backlog items
@@ -72,7 +72,7 @@ Workflow:
      Extract the work item ID from the response.
    - If `tracking_mode=internal`, skip external item creation and track in `TODO.md` only.
    - If `external_provider=jira` or `other`, add a TODO note for provider-specific automation and continue with `TODO.md` tracking.
-   - The ADO command above is illustrative; for the authoritative per-provider creation steps and field mappings, see [[governance/development-methodology|Development Methodology]].
+   - The ADO command above is illustrative; for the authoritative per-provider creation steps and field mappings, see [[.arcane/governance/development-methodology|Development Methodology]].
 
 6. **Update backlog** — add a line to `TODO.md`:
    ```markdown
@@ -107,4 +107,4 @@ This spell sits at the front of the Spell Loop — it captures and tracks; it do
 - **Feeds into [[spell-scope|spell-scope]]** for large or multi-feature suggestions — if the impact assessment lands on **L** effort (or the idea spans several features), route it to `spell-scope` first to break it down before planning.
 - **Consumes from usage/testing** — there is no upstream spell; suggestions originate from smoke testing or regular use (e.g. while running `spell-test`).
 
-See [[governance/development-methodology|Development Methodology]] for the canonical Spell Loop hand-off flow.
+See [[.arcane/governance/development-methodology|Development Methodology]] for the canonical Spell Loop hand-off flow.

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

@@ -10,7 +10,7 @@ agent: agent
 - This prompt runs tests, validates coverage against thresholds, and generates evidence artifacts.
 - Used after `spell-implement` to verify quality before `spell-review`.
 - Enforces the testing standards from ADR-050 (80% line / 95% critical path coverage).
-- See [[governance/testing-standards|Testing Standards]] for framework details.
+- See [[.arcane/governance/testing-standards|Testing Standards]] for framework details.
 
 ---
 
@@ -18,8 +18,8 @@ Run test suites and validate quality for the specified scope.
 
 Use these files for context:
 
-- [governance/testing-standards.md](../../governance/testing-standards.md) — Frameworks, thresholds, evidence requirements
-- [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop context
+- [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Frameworks, thresholds, evidence requirements
+- [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop context
 - The feature's `stories.json` — for acceptance criteria to validate
 
 Workflow:

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/assets/README.md

@@ -0,0 +1,14 @@
+# Project
+
+> Draft orientation created by Arcane. Replace this text with the repository's actual purpose.
+
+## Overview
+
+Describe what this repository contains, who it serves, and how to get started.
+
+## Start Here
+
+- [Project context](project.md)
+- [Current work](TODO.md)
+- [Decisions](DECISIONS.md)
+- [Arcane governance](.arcane/governance/)

package/dist/assets/project.md

@@ -0,0 +1,26 @@
+---
+title: Project Overview
+status: draft
+---
+
+# Project Overview
+
+## Mission
+
+Describe the outcome this project exists to produce.
+
+## Users
+
+Describe the people or systems this project serves.
+
+## Scope
+
+List the capabilities included in this repository and the boundaries that remain outside it.
+
+## Current Goals
+
+- Define the first measurable project goal.
+
+## Constraints
+
+- Record technical, business, security, or timeline constraints.

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",
@@ -345,9 +352,11 @@ var COMPONENTS = [
   // Session continuity — files required for spell-close-session / spell-open-session
   {
     name: "session-continuity",
-    description: "Session lifecycle files (TODO.md, DECISIONS.md, ai-context/, journal/) for close/open session spells",
+    description: "Install-once project orientation and session lifecycle files",
     skipExisting: true,
     files: [
+      "README.md",
+      "project.md",
       "TODO.md",
       "DECISIONS.md",
       "ai-context/system-prompt-context.md",