arcane-cli 0.39.0 → 1.1.0

package/dist/assets/.claude/commands/spell-create-pull-request.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY whenever opening a pull request for the current bra
 
 Invoke the Arcane `spell-create-pull-request` spell workflow.
 
-See the full prompt at `.github/prompts/spell-create-pull-request.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-create-pull-request.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-create-pull-request.prompt.md
+@.arcane/spells/spell-create-pull-request.md

package/dist/assets/.claude/commands/spell-document.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when conversation content (an analysis, a decision,
 
 Invoke the Arcane `spell-document` spell workflow.
 
-See the full prompt at `.github/prompts/spell-document.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-document.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-document.prompt.md
+@.arcane/spells/spell-document.md

package/dist/assets/.claude/commands/spell-dotnet-expert.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when working on a .NET project and best-practice gu
 
 Invoke the Arcane `spell-dotnet-expert` spell workflow.
 
-See the full prompt at `.github/prompts/spell-dotnet-expert.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-dotnet-expert.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-dotnet-expert.prompt.md
+@.arcane/spells/spell-dotnet-expert.md

package/dist/assets/.claude/commands/spell-eas-store-deploy.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when deploying an Expo app to the App Store or Goog
 
 Invoke the Arcane `spell-eas-store-deploy` spell workflow.
 
-See the full prompt at `.github/prompts/spell-eas-store-deploy.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-eas-store-deploy.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-eas-store-deploy.prompt.md
+@.arcane/spells/spell-eas-store-deploy.md

package/dist/assets/.claude/commands/spell-enchant.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when a PRD should be enhanced — UX, accessibility
 
 Invoke the Arcane `spell-enchant` spell workflow.
 
-See the full prompt at `.github/prompts/spell-enchant.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-enchant.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-enchant.prompt.md
+@.arcane/spells/spell-enchant.md

package/dist/assets/.claude/commands/spell-explain-concept.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when the user needs a concept, architecture, or sys
 
 Invoke the Arcane `spell-explain-concept` spell workflow.
 
-See the full prompt at `.github/prompts/spell-explain-concept.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-explain-concept.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-explain-concept.prompt.md
+@.arcane/spells/spell-explain-concept.md

package/dist/assets/.claude/commands/spell-feedback.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when the user reports friction with AI assistance o
 
 Invoke the Arcane `spell-feedback` spell workflow.
 
-See the full prompt at `.github/prompts/spell-feedback.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-feedback.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-feedback.prompt.md
+@.arcane/spells/spell-feedback.md

package/dist/assets/.claude/commands/spell-full-cycle.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY for an end-to-end feature request that should chain
 
 Invoke the Arcane `spell-full-cycle` spell workflow.
 
-See the full prompt at `.github/prompts/spell-full-cycle.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-full-cycle.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-full-cycle.prompt.md
+@.arcane/spells/spell-full-cycle.md

package/dist/assets/.claude/commands/spell-generate-bot-icons.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when a bot/agent needs a Teams-ready avatar and ico
 
 Invoke the Arcane `spell-generate-bot-icons` spell workflow.
 
-See the full prompt at `.github/prompts/spell-generate-bot-icons.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-generate-bot-icons.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-generate-bot-icons.prompt.md
+@.arcane/spells/spell-generate-bot-icons.md

package/dist/assets/.claude/commands/spell-implement.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY to work through stories.json autonomously once arch
 
 Invoke the Arcane `spell-implement` spell workflow.
 
-See the full prompt at `.github/prompts/spell-implement.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-implement.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-implement.prompt.md
+@.arcane/spells/spell-implement.md

package/dist/assets/.claude/commands/spell-make-discoverable.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when auditing a web property's search/AI-assistant
 
 Invoke the Arcane `spell-make-discoverable` spell workflow.
 
-See the full prompt at `.github/prompts/spell-make-discoverable.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-make-discoverable.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-make-discoverable.prompt.md
+@.arcane/spells/spell-make-discoverable.md

package/dist/assets/.claude/commands/spell-manifest.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY in a hub repo to triage idea-book/todo-book entries
 
 Invoke the Arcane `spell-manifest` spell workflow.
 
-See the full prompt at `.github/prompts/spell-manifest.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-manifest.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-manifest.prompt.md
+@.arcane/spells/spell-manifest.md

package/dist/assets/.claude/commands/spell-open-session.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY at the start of any new session, even if the user j
 
 Invoke the Arcane `spell-open-session` spell workflow.
 
-See the full prompt at `.github/prompts/spell-open-session.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-open-session.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-open-session.prompt.md
+@.arcane/spells/spell-open-session.md

package/dist/assets/.claude/commands/spell-plan.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when a feature description needs to become a PRD be
 
 Invoke the Arcane `spell-plan` spell workflow.
 
-See the full prompt at `.github/prompts/spell-plan.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-plan.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-plan.prompt.md
+@.arcane/spells/spell-plan.md

package/dist/assets/.claude/commands/spell-present-arcane.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when asked to present, demo, or explain Arcane itse
 
 Invoke the Arcane `spell-present-arcane` spell workflow.
 
-See the full prompt at `.github/prompts/spell-present-arcane.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-present-arcane.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-present-arcane.prompt.md
+@.arcane/spells/spell-present-arcane.md

package/dist/assets/.claude/commands/spell-product-review.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when evaluating a shipped feature's real-world perf
 
 Invoke the Arcane `spell-product-review` spell workflow.
 
-See the full prompt at `.github/prompts/spell-product-review.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-product-review.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-product-review.prompt.md
+@.arcane/spells/spell-product-review.md

package/dist/assets/.claude/commands/spell-review-batch.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when multiple open PRs need an adversarial review p
 
 Invoke the Arcane `spell-review-batch` spell workflow.
 
-See the full prompt at `.github/prompts/spell-review-batch.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-review-batch.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-review-batch.prompt.md
+@.arcane/spells/spell-review-batch.md

package/dist/assets/.claude/commands/spell-review.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY before merging any nontrivial change, even if the u
 
 Invoke the Arcane `spell-review` spell workflow.
 
-See the full prompt at `.github/prompts/spell-review.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-review.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-review.prompt.md
+@.arcane/spells/spell-review.md

package/dist/assets/.claude/commands/spell-save-idea.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY to capture a fleeting idea immediately, even if the
 
 Invoke the Arcane `spell-save-idea` spell workflow.
 
-See the full prompt at `.github/prompts/spell-save-idea.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-save-idea.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-save-idea.prompt.md
+@.arcane/spells/spell-save-idea.md

package/dist/assets/.claude/commands/spell-scope.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when a PRD is too large for one Spell Loop cycle an
 
 Invoke the Arcane `spell-scope` spell workflow.
 
-See the full prompt at `.github/prompts/spell-scope.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-scope.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-scope.prompt.md
+@.arcane/spells/spell-scope.md

package/dist/assets/.claude/commands/spell-scry.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when naming anything new (a spell, a field, a produ
 
 Invoke the Arcane `spell-scry` spell workflow.
 
-See the full prompt at `.github/prompts/spell-scry.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-scry.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-scry.prompt.md
+@.arcane/spells/spell-scry.md

package/dist/assets/.claude/commands/spell-security-review.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY before shipping any change that introduces new atta
 
 Invoke the Arcane `spell-security-review` spell workflow.
 
-See the full prompt at `.github/prompts/spell-security-review.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-security-review.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-security-review.prompt.md
+@.arcane/spells/spell-security-review.md

package/dist/assets/.claude/commands/spell-ship.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY before any deploy, even if the user just says 'ship
 
 Invoke the Arcane `spell-ship` spell workflow.
 
-See the full prompt at `.github/prompts/spell-ship.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-ship.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-ship.prompt.md
+@.arcane/spells/spell-ship.md

package/dist/assets/.claude/commands/spell-status.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when asked for a quick snapshot of session/repo sta
 
 Invoke the Arcane `spell-status` spell workflow.
 
-See the full prompt at `.github/prompts/spell-status.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-status.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-status.prompt.md
+@.arcane/spells/spell-status.md

package/dist/assets/.claude/commands/spell-suggest-feature.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when smoke testing or usage surfaces a feature gap
 
 Invoke the Arcane `spell-suggest-feature` spell workflow.
 
-See the full prompt at `.github/prompts/spell-suggest-feature.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-suggest-feature.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-suggest-feature.prompt.md
+@.arcane/spells/spell-suggest-feature.md

package/dist/assets/.claude/commands/spell-summon-venture.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY in a hub repo when creating a new venture from scra
 
 Invoke the Arcane `spell-summon-venture` spell workflow.
 
-See the full prompt at `.github/prompts/spell-summon-venture.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-summon-venture.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-summon-venture.prompt.md
+@.arcane/spells/spell-summon-venture.md

package/dist/assets/.claude/commands/spell-sync-pull-request.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY whenever an open PR has fallen behind its target br
 
 Invoke the Arcane `spell-sync-pull-request` spell workflow.
 
-See the full prompt at `.github/prompts/spell-sync-pull-request.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-sync-pull-request.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-sync-pull-request.prompt.md
+@.arcane/spells/spell-sync-pull-request.md

package/dist/assets/.claude/commands/spell-test.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY to validate a completed story or feature against co
 
 Invoke the Arcane `spell-test` spell workflow.
 
-See the full prompt at `.github/prompts/spell-test.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-test.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-test.prompt.md
+@.arcane/spells/spell-test.md

package/dist/assets/.claude/commands/spell-todo.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY whenever a raw idea needs to become one or more wel
 
 Invoke the Arcane `spell-todo` spell workflow.
 
-See the full prompt at `.github/prompts/spell-todo.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-todo.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-todo.prompt.md
+@.arcane/spells/spell-todo.md

package/dist/assets/.claude/commands/spell-verification-ledger.md

@@ -6,8 +6,8 @@ description: Use PROACTIVELY when a session had real verification events worth a
 
 Invoke the Arcane `spell-verification-ledger` spell workflow.
 
-See the full prompt at `.github/prompts/spell-verification-ledger.prompt.md` for the complete workflow definition.
+See the full prompt at `.arcane/spells/spell-verification-ledger.md` for the complete workflow definition.
 
 ---
 
-@.github/prompts/spell-verification-ledger.prompt.md
+@.arcane/spells/spell-verification-ledger.md

package/dist/assets/.github/instructions/agent-output.instructions.md

@@ -58,19 +58,20 @@ stale number is invisible until someone tries.
   `DECISIONS.md` either fails to resolve, or worse, silently resolves to the
   *consumer's own* `DECISIONS.md` (an empty per-consumer starter template, not
   Arcane's real decision record) — wrong content, not just a dead link.
-- **Spell prompts and instructions this framework ships**
-  (`.github/prompts/*.prompt.md`, `.github/instructions/*.md`): **plain text only —
-  cite the bare ID, no link at all** (`ARC-035`, not `[ARC-035](...)`). A full
-  canonical URL is *also* unsafe here, not just a same-repo link: it bakes a literal
-  `github.com/{GITHUB_ORG}/{REPO_NAME}` — this project's own org and repo name — into
-  content the org-token portability gate (`scripts/org-token-lint.ts`, D2 in
-  `spell-authoring-standards.md`) exists specifically to keep out of distributed
-  spells. **Confirmed live 2026-08-31 (BC-06):** the build's `Org-token lint` failed
-  on exactly this pattern in three prompt files, including two this same correction
-  pass had introduced minutes earlier while fixing the *other* link defect. Known
-  gap: the portability scan today only walks `.github/prompts/`, so a full URL in a
-  `.github/instructions/*.md` file — like this one's own Merge Strategy section, two
-  paragraphs down — ships uncaught; tracked in `TODO.md`.
+- **Spells and instructions this framework ships**
+  (`.arcane/spells/*.md`, the generated `.github/prompts/*.prompt.md` shims,
+  `.github/instructions/*.md`): **plain text only — cite the bare ID, no link at all**
+  (`ARC-035`, not `[ARC-035](...)`). A full canonical URL is *also* unsafe here, not
+  just a same-repo link: it bakes a literal `github.com/{GITHUB_ORG}/{REPO_NAME}` —
+  this project's own org and repo name — into content the org-token portability gate
+  (`scripts/org-token-lint.ts`, D2 in `spell-authoring-standards.md`) exists
+  specifically to keep out of distributed spells. **Confirmed live 2026-08-31
+  (BC-06):** the build's `Org-token lint` failed on exactly this pattern in three
+  prompt files, including two this same correction pass had introduced minutes
+  earlier while fixing the *other* link defect. The portability scan walks
+  `.arcane/spells/`, `.github/prompts/`, `.github/instructions/` and
+  `.agents/skills/` (the instructions gap first noted here closed 2026-09-01; the
+  canonical folder joined in CS-03).
 - **Cross-repo references from anywhere else** (chat, PR output, another repo
   entirely): the full canonical-repo URL.
 

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

@@ -6,110 +6,4 @@ argument-hint: --pr <number> (required) [--fix-all] — the PR to address; --fix
 agent: agent
 ---
 
-## Executive Summary
-
-- This spell handles inbound code-review feedback: read comments, act on them, and resolve the threads.
-- Each comment is triaged — must-fix / suggestion / question / nitpick — and given a disposition.
-- Must-fix items are implemented, committed, and pushed; others are implemented or answered with rationale.
-- Every thread is resolved at the end (many providers require all threads resolved before merge).
-- This is the author-side counterpart to `spell-review` (the reviewer side). Provider-agnostic.
-
----
-
-Respond to review feedback for the specified pull request.
-
-Context to consult:
-
-- `.arcane/governance/git-conventions.md` — commit format, agent attribution trailers, PR policy, and the interactive-session commit gate.
-- `.arcane/governance/development-methodology.md` — workflow phases.
-
-Related spells:
-
-- `spell-review` — the reviewer side. If review was run here, its findings carry stable IDs (`R1`, `R2`, …); reference those IDs when replying so each thread maps to the original finding.
-- `spell-create-pull-request` — opens the PR this spell responds to. Run it first if no PR exists yet.
-
-## Arguments
-
-- `--pr <number>` — **required.** The PR to address. If omitted, check the current branch for an associated PR or ask the user.
-- `--fix-all` — optional. Treat all suggestions and nitpicks as fix-now (no deferrals).
-
-## Step 0 — Setup
-
-1. **Resolve the PR.** If `--pr` is given, use it. If omitted, look up the PR for the current branch (`gh pr view --json number` / `az repos pr list --source-branch <branch>`). If still none, **stop** and ask the user for the PR number — do not guess.
-2. **Working tree must be clean.** Run `git status`. If dirty, **stop** and ask the user to commit or stash first — never stash silently, since uncommitted work can get tangled into the review-fix commits below.
-3. **Detect the provider** from the git remote:
-
-   | Remote URL contains | Provider |
-   | --- | --- |
-   | `github.com` | GitHub (`gh`) |
-   | `dev.azure.com` / `visualstudio.com` | Azure DevOps (`az repos`) |
-   | anything else | unknown — **stop** and ask the user |
-
-4. **Fetch the PR plus all comment threads:**
-   - **GitHub:** `gh pr view <PR> --comments`
-   - **Azure DevOps:** `az repos pr thread list --id <PR>`
-
-## Step 1 — Parse threads
-
-For each thread extract: thread ID, author, file + line (if inline), comment text, status, existing replies. Keep only **active** threads; ignore already-resolved ones. If a comment references a `spell-review` finding ID (`R1`, …), carry it through so the reply can cite it.
-
-**If zero active threads remain:** report "No active review threads to address — nothing to do" and stop. Do not create commits or push.
-
-## Step 2 — Categorize each comment
-
-| Category | Criteria | Action |
-| --- | --- | --- |
-| must-fix | bug, security issue, logic error, broken behavior, standards violation | implement, commit, push |
-| suggestion | better approach, refactor, optional improvement | implement OR reply with rationale |
-| question | clarification / "why did you…?" | answer in the thread |
-| nitpick | minor style / naming preference | implement OR reply with rationale |
-
-Heuristics: "must"/"should"/"required"/"blocking" → must-fix; ends with "?" or starts "why/how/what" → question; "nit"/"minor"/"optional"/"consider" → nitpick; alternative offered without requiring → suggestion. When unsure, escalate to suggestion (not nitpick).
-
-## Step 3 — Disposition
-
-| Disposition | When |
-| --- | --- |
-| Fix Now | all must-fix; suggestions/nitpicks < ~30 min effort AND within files the PR already touches |
-| Defer | scope-expanding items: new features, infra/tooling, cross-file refactors, > ~1 hr effort |
-| Decline | the current approach is intentional — reply with rationale |
-
-`--fix-all` forces all suggestions/nitpicks to Fix Now. Deferred items get a `TODO.md` entry with a `(PR #<n> feedback)` note **and** a reply on the thread pointing to that TODO before the thread is resolved — never resolve a deferred thread silently, or the reviewer cannot tell it was tracked vs. ignored.
-
-## Step 4 — Present the plan, then wait
-
-Show a table (`# | category | disposition | author | file:line | summary | planned action`) plus counts. Wait for confirmation; let the user reclassify any item before proceeding.
-
-## Step 5 — Execute
-
-Commits in this spell follow `.arcane/governance/git-conventions.md`: Conventional Commits format, agent attribution (`--author` + required `Agent`/`Model`/`Model-Source`/`Provider` trailers, plus `Persona`/`Role` when a roster exists and one was assigned) when an agent authors the change, and — because this is an **interactive session** — present each proposed commit message and **wait for the human's approval before committing** (the Step 4 plan approval covers *what* to do, not the commit itself). Never squash.
-
-For **must-fix** (one thread at a time): read the code → implement → run the relevant tests.
-- **If tests pass:** commit (e.g. `fix(scope): address review — <desc>`) → reply `Fixed in <hash>. <what changed>` (cite the `R#` finding ID if one exists) → resolve the thread immediately.
-- **If tests fail:** do **not** commit. Either fix the regression and re-run, or — if the fix is wrong or larger than expected — revert the change, reply on the thread explaining what blocked it, and reclassify to Defer (TODO + thread note). A broken must-fix must never land.
-
-For **suggestions/nitpicks**: if implementing, make the change, run tests, and batch into one commit; reply and resolve. If declining, reply with specific, respectful rationale (reference an ADR or convention if relevant) and resolve as won't-fix.
-
-For **questions**: answer clearly in the thread; if the question reveals a real issue, reclassify and handle it; resolve after answering.
-
-Resolve threads via the provider:
-- **GitHub:** resolve the review thread (`gh` / GitHub MCP resolve-thread).
-- **Azure DevOps:** update the thread status (`Fixed` or `WontFix`).
-- **If a thread cannot be auto-resolved** (provider API error, insufficient permissions, or the reviewer must resolve it themselves): leave the reply in place, list the thread in the Step 6 report under "needs manual resolution," and do not treat the sweep as complete.
-
-## Step 6 — Sweep, push, report
-
-1. Re-fetch threads; resolve any still-active ones (this is the merge gate on many providers). Any thread that genuinely cannot be auto-resolved (see Step 5) is reported as "needs manual resolution," not silently left open.
-2. `git push` all commits.
-3. Print a summary table of actions taken (category, file, action, commit), thread status (resolved / deferred-with-TODO / needs manual resolution), commits pushed, and next steps (CI, notify reviewer, ready for re-review).
-4. Optionally post the summary back to the PR as a top-level comment for a durable record.
-
-## Rules
-
-- Always present the plan and wait for confirmation before changing code.
-- This is an interactive session: get human approval for each commit message before committing (per git-conventions Commit Governance).
-- Never commit a change whose tests fail — fix, revert, or defer instead.
-- Resolve each thread immediately after addressing it — do not batch resolution to the very end (except the final sweep).
-- Never dismiss feedback without reasoning, and never resolve a deferred thread without leaving a TODO pointer on it.
-- Follow `.arcane/governance/git-conventions.md` for commit format and attribution; do not squash.
-- Never include secrets or tokens in replies or commits.
+This prompt is the Arcane `spell-address-review` spell. Read [`.arcane/spells/spell-address-review.md`](../../.arcane/spells/spell-address-review.md) and follow it as the complete workflow.