arcane-cli 0.15.9 → 0.16.2

package/README.md

@@ -30,7 +30,7 @@ npm install -g arcane-cli   #  then:  spell init
 
 <div align="center">
 
-**🔁 opinionated lifecycle** &nbsp;·&nbsp; **📜 33 spells** &nbsp;·&nbsp; **🤖 12 agents** &nbsp;·&nbsp; **⚖️ 19 governance standards** &nbsp;·&nbsp; **📝 markdown-native** &nbsp;·&nbsp; **🔌 any AI client / tracker**
+**🔁 opinionated lifecycle** &nbsp;·&nbsp; **📜 34 spells** &nbsp;·&nbsp; **🤖 12 agents** &nbsp;·&nbsp; **⚖️ 19 governance standards** &nbsp;·&nbsp; **📝 markdown-native** &nbsp;·&nbsp; **🔌 any AI client / tracker**
 
 </div>
 
@@ -113,20 +113,20 @@ Arcane isn't a prompt snippet — it's a full framework. Everything installs int
 
 | Layer | What you get |
 | --- | --- |
-| 📜 **Spells** | **33** prompt-driven workflows spanning the entire lifecycle — planning, architecture, implementation, testing, review, shipping, session management, and ops. |
+| 📜 **Spells** | **34** prompt-driven workflows spanning the entire lifecycle — planning, architecture, implementation, testing, review, shipping, session management, and ops. |
 | ⚖️ **Governance** | **19** battle-tested standards as drop-in templates: git conventions, testing standards, CI/CD, threat model, ADR format, naming, security hardening, and more. |
 | 🤖 **Agents** | **12** ready-made agent personas with roles, clusters, and a gamified autonomy model — assign work and power levels per repo. |
 | 🛠️ **CLI** | `spell init / add / update / status / uninstall` — install by profile or à la carte, and keep everything in sync as new versions ship. |
 
 <details>
-<summary><b>📜 The full spell catalogue (33)</b></summary>
+<summary><b>📜 The full spell catalogue (34)</b></summary>
 
 **Core Spell Loop** — `plan` · `enchant` · `scope` · `architect` · `implement` · `test` · `review` · `ship`
 **Session** — `open-session` · `close-session` · `status`
 **Operational & Git** — `commit-work` · `todo` · `check-drift` · `bug` · `create-pull-request` · `address-review` · `bump`
 **Specialized** — `full-cycle` · `review-batch` · `security-review` · `dotnet-expert` · `product-review` · `suggest-feature`
-**Knowledge & Docs** — `document` · `explain-concept` · `feedback` · `save-idea`
-**Business & Admin** — `bootstrap-business` · `brainstorm` · `generate-bot-icons` · `present-arcane` · `arcane-version`
+**Knowledge & Docs** — `document` · `explain-concept` · `feedback` · `save-idea` · `manifest`
+**Business & Admin** — `summon-venture` · `brainstorm` · `generate-bot-icons` · `present-arcane` · `arcane-version`
 
 </details>
 

package/dist/assets/.arcane/governance/development-methodology.md

@@ -364,12 +364,15 @@ A tool that both writes and validates its own work cannot be trusted to catch it
 | `spell-close-session`      | Journal, summarize, update TODO              |
 | `spell-commit-work`        | Conventional Commits with trailers           |
 | `spell-check-drift`        | Documentation audit for staleness            |
-| `spell-bootstrap-business` | Scaffold new business docs                   |
+| `spell-summon-venture`     | Create a new venture: folder, books, registry entry (hub-gated) |
 | `spell-explain-concept`    | Bridge concepts to project context           |
 | `spell-todo`               | Manage TODO.md lifecycle                     |
 | `spell-generate-bot-icons` | Generate agent avatar assets                 |
 | `spell-bug`                | Bug lifecycle: document → tracker/TODO → fix → verify |
 | `spell-suggest-feature`    | Feature capture: user story → tracker/TODO → backlog  |
+| `spell-save-idea`          | Fast-capture an idea into `IDEAS.md` (hub: optionally into a venture's book) |
+| `spell-manifest`           | Hub-gated: promote idea/todo-book entries downstream — consumer repo, PRD, tracker, or public disclosure |
+| `spell-feedback`           | Session-quality feedback; framework-shaped items route upstream to arcane's GitHub (genericized, disclosure-gated) |
 
 ---
 

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

@@ -220,6 +220,13 @@ Create the session branch as the **first action** of any session, before any fil
   1. `git branch -m <old> <new>`
   2. `git push -u origin <new>`
   3. `git push origin --delete <old>` (skip this if an active PR still depends on `<old>`).
+- **EF-20 hazard:** on some Windows/Git-for-Windows filesystems, a rename or delete can trigger
+  an interactive retry prompt (e.g. a file lock from an editor or antivirus scan) that blocks
+  indefinitely on a terminal with no non-interactive fallback. When running these commands
+  directly through a tool that supports a per-call timeout (an agent's shell tool, a CI step),
+  set one rather than assuming the command will return. Arcane's own TypeScript Git helper
+  (`src/modules/git.ts`) applies this as a standing contract — closed stdin plus a
+  command-class timeout — for every `git` invocation the CLI itself makes.
 
 **Agents:**
 

package/dist/assets/.arcane/governance/portable-bootstrap.md

@@ -95,7 +95,7 @@ Development follows the **Spell Loop** — structured planning phases feeding an
 - `spell-commit-work` — Standard Git workflow: stage → message → approve → execute
 - `spell-todo` — Review TODO.md, prioritize, move resolved items to canonical docs
 - `spell-check-drift` — Find stale assumptions in docs vs. reality
-- `spell-bootstrap-business` — Initialize a new business: folder, template docs, project setup
+- `spell-summon-venture` — Create a new venture (hub-gated): folder, template docs, idea/todo books, registry entry
 
 ### Specialized
 

package/dist/assets/.arcane/templates/venture-template/IDEAS.md

@@ -0,0 +1,11 @@
+# Idea Inbox — {Venture Name}
+
+Per-venture idea book (hub-side). Add with `spell-save-idea --venture {slug}` (or natural
+phrasing, e.g. "save this idea for {slug}"); triage with `spell-todo --sweep`; promote downstream
+with `spell-manifest`. Entries are append-only; mark status in the trailing comment rather than
+deleting.
+
+Private by default, including for ventures whose own repo is public — promotion to a public
+destination is a deliberate disclosure event, not a side effect of saving an idea here.
+
+---

package/dist/assets/.arcane/templates/venture-template/TODO.md

@@ -0,0 +1,8 @@
+# Open Items — {Venture Name}
+
+Per-venture todo book (hub-side). Add with `spell-todo` targeting this venture (or natural
+phrasing, e.g. "add a todo for {slug}"); triage alongside the hub root list with `spell-todo
+--sweep`. This is a scratchpad for unresolved items, not a system of record — when an item is
+resolved, move the outcome to the venture's `overview.md` or `DECISIONS.md`, then delete it here.
+
+---

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

@@ -0,0 +1,9 @@
+# Manifest
+
+Invoke the Arcane `spell-manifest` spell workflow.
+
+See the full prompt at `.github/prompts/spell-manifest.prompt.md` for the complete workflow definition.
+
+---
+
+@.github/prompts/spell-manifest.prompt.md

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

@@ -0,0 +1,9 @@
+# Summon Venture
+
+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.
+
+---
+
+@.github/prompts/spell-summon-venture.prompt.md

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

@@ -28,6 +28,7 @@ Use these files first:
 - [agents/agent-policies.md](../../.arcane/governance/agent-policies.md)
 - Most recent journal file(s) in [journal/](../../journal/)
 - Relevant business overviews under [ventures/](../../ventures/)
+- `ventures/registry.json`, if present (hub-role and registry-consistency detectors)
 
 Scope selection (`--scope <value>`, default `all`):
 
@@ -48,6 +49,12 @@ Concrete detectors to run (in addition to general contradiction/stale-date check
   - If normalized content differs, report **real content drift** with normal severity grading.
   - If normalized content matches, report **line-ending-only drift** separately. Do not count these paths as real content findings and do not include them in severity totals or the Go / No-Go decision.
   - Report exact path counts for both classes. Never summarize all byte-different files as content drift.
+- **Hub-artifact leak (non-hub repos)** — if `.arcane.json` does not have `role: "hub"`, the existence of any `ventures/*/IDEAS.md`, `ventures/*/TODO.md`, or `ventures/registry.json` is **Critical**: hub-only artifacts (potentially including sibling-venture and portfolio data) do not belong in a repo that isn't a declared hub. This check is deliberately structural (file existence only) — a non-hub repo cannot safely hold the sibling-name list a content-level check would need, so that asymmetry is by design, not a gap.
+- **Hub role/registry consistency (hub repos only)** — when `.arcane.json` has `role: "hub"`:
+  - `role: "hub"` with no `{business_root}` directory (default `ventures/`) present — **High**: the manifest claims a role the repo can't actually fulfill.
+  - `ventures/registry.json` slugs that don't match an existing `ventures/<slug>/` folder, or venture folders with no registry entry — **Medium**, both directions.
+  - Malformed `status: promoted → …` / `status: dropped …` markers in any book (unparseable destination, missing date) — **Low**.
+  - A `ventures/<slug>/` folder with a `role`-shaped `.arcane.json`-like marker of its own (i.e., it looks like it's trying to be a hub itself) — **Medium**: flag for operator review; nested hubs are unsupported.
 
 For each drift finding include:
 

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

@@ -1,7 +1,7 @@
 ---
 name: Spell — Feedback
-description: Collect structured feedback on AI-assistance quality and workflow friction, and append it to FEEDBACK.md for continuous improvement.
-argument-hint: Optional focus area — e.g., "spell-implement loop", "review quality", "session handoff"
+description: Collect structured feedback on AI-assistance quality and workflow friction, and append it to FEEDBACK.md for continuous improvement. Framework-shaped items can route upstream to arcane's public GitHub issues.
+argument-hint: Optional focus area — e.g., "spell-implement loop", "review quality", "session handoff". Use `--flush` instead to re-offer any previously queued upstream items.
 agent: agent
 ---
 
@@ -10,11 +10,16 @@ agent: agent
 - This spell captures post-session feedback on how well the spells and AI assistance worked.
 - It structures the feedback into actionable improvement items and appends them to `FEEDBACK.md` at the repo root.
 - Use it after any session where assistance felt notably effective or notably off — the record feeds `spell-enchant`.
+- **Framework-shaped items** (about a spell, template, governance doc, playbook, or CLI behavior — not this repo's own content) can additionally route upstream as a GitHub issue on `{ARCANE_UPSTREAM_REPO}` — the same public intake path any arcane user would use, genericized first and gated by an explicit disclosure confirm. This is the whole consumer→arcane feedback loop: arcane is the one thing every consumer repo may reference without violating sibling isolation, because it's the installed, publicly-homed dependency, not a sibling venture.
 
 ---
 
 Collect and record feedback to improve the Arcane workflow.
 
+## Flush Mode (`--flush`)
+
+If the argument is `--flush`, skip Steps 1–5 entirely. Scan `FEEDBACK.md` for improvement items marked `<!-- upstream: queued -->`, and for each one run Step 6's filing flow (genericize, confirm, file or re-queue) without re-collecting feedback. Report how many were filed, re-queued, and how many remain.
+
 The user's input describes what to give feedback on. If no argument is provided, ask one question: _"What part of the workflow or AI assistance do you want to give feedback on?"_ and wait.
 
 ## Step 1 — Identify Scope
@@ -56,6 +61,8 @@ Extract:
 
 Mark an item **substantial** (TODO-worthy) if any apply: it requires editing a spell/governance/agent file, it blocked task completion, or it recurs across sessions. Trivial one-off nits stay in `FEEDBACK.md` only.
 
+For each substantial item, additionally classify **framework-shaped** vs **repo-local**: framework-shaped means the fix belongs in arcane itself (a spell prompt, template, governance doc, playbook, or CLI behavior this repo installed rather than authored); repo-local means it's specific to this repo's own content or configuration. Only framework-shaped items are offered upstream routing in Step 6.
+
 ## Step 4 — Show Proposal
 
 ```
@@ -66,7 +73,7 @@ Mark an item **substantial** (TODO-worthy) if any apply: it requires editing a s
 **Friction:** [...]
 **Worked well:** [...]
 **Improvement items:**
-- [ ] [item] [SUBSTANTIAL if TODO-worthy]
+- [ ] [item] [SUBSTANTIAL if TODO-worthy] [FRAMEWORK-SHAPED if upstream-eligible]
 
 Append to FEEDBACK.md? (yes / edit / skip)
 ```
@@ -101,8 +108,23 @@ If the rating is ≤ 2, prepend a `⚠️ LOW RATING` line to this proposal so i
 ```
 
 3. For each item marked **substantial** in Step 3, offer to add it to `TODO.md` as a `[feedback]`-tagged item. If the user accepts, hand off to [`spell-todo`](spell-todo.prompt.md) rather than editing `TODO.md` directly — it picks the right section and avoids duplicates.
-4. Do NOT commit — leave that to `spell-commit-work`.
-5. Confirm what was appended and where, then point the user to [`spell-enchant`](spell-enchant.prompt.md) if the feedback suggests a spell or PRD is ready to be lifted to the next quality tier.
+4. For each item additionally marked **framework-shaped**, run Step 6.
+5. Do NOT commit — leave that to `spell-commit-work`.
+6. Confirm what was appended and where, then point the user to [`spell-enchant`](spell-enchant.prompt.md) if the feedback suggests a spell or PRD is ready to be lifted to the next quality tier.
+
+## Step 6 — Upstream Routing (Framework-Shaped Items)
+
+`{ARCANE_UPSTREAM_REPO}` is this install's own arcane framework repository (`owner/repo`) — resolve it from the installed `arcane-cli` package's `repository` field (e.g. `node_modules/arcane-cli/package.json`, or `npm view arcane-cli repository.url` if not vendored locally); ask the user if it cannot be determined. Never hardcode a specific org/repo here — a fork or downstream rename changes this value.
+
+For each framework-shaped item:
+
+1. **Genericize.** Strip anything identifying this specific consumer: venture/business names, org tokens, machine names, hub or local paths. Write "a consumer repo session" instead of naming the actual venture, generalize file paths to their relative form. The finding must read the same whether it came from this repo or any other arcane user's.
+2. **Check `gh`.** If unauthenticated or offline, skip straight to the fallback below.
+3. **Disclosure confirm.** Print the exact issue title and body that will be filed publicly on `{ARCANE_UPSTREAM_REPO}`, and ask for the literal word `disclose` — same discipline as `spell-manifest`'s disclosure gate; this is the same kind of act (private observation → public issue). Anything else is a decline, not an error.
+4. **File.** On `disclose`: `gh issue create --repo {ARCANE_UPSTREAM_REPO} --title "<title>" --body "<genericized body>"`. Report the issue URL.
+5. **Fallback.** If `gh` is unavailable, offline, or the operator declines: append `<!-- upstream: queued -->` to that item's line in `FEEDBACK.md`. Never block the rest of the session on this — queuing is a complete, valid outcome. The next `spell-feedback` run (or `spell-feedback --flush`) re-offers every queued item.
+
+Maintainer side is unchanged: GitHub issues are arcane's normal public intake; triage into arcane's own `IDEAS.md`/`DECISIONS.md` happens in arcane sessions like any other issue. This spell never writes to a hub's venture books and never reads `ventures/registry.json` — framework feedback and venture ideas are different channels on purpose (venture ideas → hub books → `spell-manifest`; framework lessons → here → arcane's GitHub).
 
 ## Rules
 
@@ -111,3 +133,5 @@ If the rating is ≤ 2, prepend a `⚠️ LOW RATING` line to this proposal so i
 - If overall quality is ≤ 2, flag it with `⚠️ LOW RATING` in the Step 4 proposal (before the append decision) and offer `spell-todo` to capture a concrete fix.
 - After approval, write immediately — no further questions.
 - Never include secrets or tokens.
+- Never file an upstream issue without the literal `disclose` confirmation on that exact entry — batch approval of the local `FEEDBACK.md` append does not extend to Step 6.
+- Never write a venture name, hub path, or machine name into an upstream issue — genericize before showing the disclosure confirm, not after.

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

@@ -0,0 +1,132 @@
+---
+name: Spell — Manifest
+description: Hub-gated interactive triage that promotes idea-book and todo-book entries downstream — to a consumer repo, a PRD scaffold, a tracker item, public disclosure, or another venture's book.
+argument-hint: Optional --venture <slug> to restrict triage to one venture's books
+agent: agent
+---
+
+## Executive Summary
+
+- This prompt is the promotion step of the idea lifecycle: it takes `status: new` entries out of hub-side `IDEAS.md`/`TODO.md` books and lands them where they actually get built — a consumer repo, a tracker, a PRD, or (deliberately, never by accident) a public disclosure.
+- **Hub-gated:** requires `role: "hub"` in `.arcane.json`. Refuses cleanly in a consumer repo.
+- Batch-capable: list entries once, select by number/range, route each (or all identically), execute with one final confirmation — except disclosure, which is never covered by a batch confirmation and always requires its own literal answer.
+- Every downstream write is leak-scanned first: no sibling venture names, no hub paths, no machine names ever land in a consumer artifact.
+- Idempotent: promoted entries are marked in place, so re-running never double-lands the same idea.
+
+---
+
+## Step 0 — Hub Gate
+
+Read `.arcane.json`. If `role` is not `"hub"`, stop and report:
+
+> `spell-manifest` runs only in a hub repo (`role: "hub"` in `.arcane.json`). This repo is a consumer — triage its own `IDEAS.md`/`TODO.md` with `spell-todo` (task), `spell-suggest-feature` (tracked story), or `spell-plan` (PRD) instead.
+
+Do not read or list anything further. If `role` is `"hub"`, resolve `{BUSINESS_ROOT}` from `.arcane.json` (default `ventures/`) and load `{BUSINESS_ROOT}/registry.json`. If the registry is missing or fails to parse, stop and report the exact error — never triage blind without knowing the venture list (sibling names come from here, and the leak scan in Step 5 depends on it).
+
+## Step 1 — Collect
+
+Parse `status: new` entries from the hub root `IDEAS.md` and every `{BUSINESS_ROOT}/<slug>/IDEAS.md` / `TODO.md` that exists. If `--venture <slug>` was given, resolve it through the registry's aliases first (exact slug → alias → closest match offered — never guessed; unknown slug lists the closest matches and stops) and restrict collection to that venture's two books plus the hub root.
+
+Tolerate operator YAML frontmatter above a book's header — entries always live below the `---` divider. Malformed entries (missing timestamp, unparseable status comment) are listed under a `Skipped` heading with `file:line`, never silently dropped.
+
+## Step 2 — List
+
+Print one numbered list, grouped by book, oldest entry first within each group. Numbering is session-scoped — it does not persist across runs.
+
+```
+Idea triage — hub books (N books, M new entries)
+
+hub IDEAS.md
+  1. [2026-08-02] [#dx] Portfolio-wide spell usage stats dashboard
+ventures/ordovica/IDEAS.md
+  2. [2026-07-30] [#ui] Dark-mode toggle for event pages
+ventures/ordovica/TODO.md
+  3. [ ] Confirm cart snapshot order (open item, no status comment — todo-book entries are listed as-is)
+```
+
+## Step 3 — Select
+
+Ask: `Promote which? (numbers/ranges, e.g. 1,3,5-8, or "all")`. Accept a single answer covering the whole batch. `all` selects every listed entry, including ones in books outside `--venture` if no filter was given.
+
+## Step 4 — Route (per entry)
+
+For each selected entry, in list order, resolve the venture it belongs to (`hub` for root-book entries) and offer destinations. The menu depends on that venture's registry entry:
+
+| # | Destination | Requires | What lands |
+| --- | --- | --- | --- |
+| a | Consumer repo-root `IDEAS.md` | a registered clone on this machine | New entry, `status: new`, fresh timestamp |
+| b | PRD scaffold in consumer `features/<slug>/PRD.md` | a registered clone | spell-plan-style stub: Problem Statement = idea text; tracking frontmatter from that repo's own `.arcane.json`; open question noting no work-item ID exists yet |
+| c | Tracker item | venture `tracking != "none"` | ADO: resolve process template + work item type, `az boards work-item create`. GitHub: `gh issue create --repo <owner>/<repo>`. Works without a local clone. |
+| d | Public disclosure to that repo's `IDEAS.md` | a registered clone, destination `visibility: "public"` | Same as (a) — but gated by Step 5's disclosure confirm, always |
+| e | Demote to a TODO book | — | Venture's own `TODO.md` (or hub root `TODO.md` for hub-book entries), as a `- [ ]` line |
+| f | Drop | — | Nothing lands |
+| g | Cross-copy to another venture's book | target venture exists in registry | Fresh `status: new` entry appended to that venture's book |
+
+If the venture has no registered repo (`repos: []`, e.g. an idea-stage venture), only (e), (f), (g) are offered. Typing `same` for any entry after the first repeats the previous entry's destination.
+
+Once every selected entry has a destination, print one consolidated plan and ask `Proceed? (go / edit / cancel)`. This confirmation covers ordinary destinations only — it never authorizes a disclosure; see Step 5.
+
+## Step 5 — Disclosure Gate
+
+Any destination whose repo has `visibility: "public"` — (a) or (d) landing in a public repo, or (c) filing a tracker item in a public tracker (a GitHub issue on a public repo is exactly as much a disclosure as its `IDEAS.md`) — is a disclosure, never covered by `all`, `go`, or any other batch confirmation. Per entry, print the **exact text** that will become public and ask for the literal word `disclose`. Anything else skips that one entry (it stays `status: new`) without aborting the rest of the batch.
+
+On a repo's first-ever disclosure (its `IDEAS.md` has no existing entries with a `promoted → public:` marker), offer to add this boundary statement to that file's header in the same staged change:
+
+> Build-in-public covers source, decisions, and the accepted roadmap; idea incubation is curated and lands here when committed.
+
+## Step 6 — Execute
+
+Per entry, in list order: **land downstream first, mark the hub entry after.** Before writing anything to a consumer repo, run the leak scan (Step 7) on the outbound text; a hit blocks that entry and asks for an operator rewrite rather than writing leaked content. After a successful downstream write, mark the hub entry:
+
+```
+<!-- status: promoted → <dest> YYYY-MM-DD -->
+```
+
+where `<dest>` is one of:
+
+```
+repo:<slug>/IDEAS.md
+prd:<slug>/features/<feature-slug>
+ado:<slug>#<id>
+github:<slug>#<id>                    (append " (disclosed)" if the repo is public)
+public:<slug>/IDEAS.md (disclosed)
+hub:TODO.md
+book:<other-slug>/IDEAS.md
+```
+
+Dropped entries get `<!-- status: dropped YYYY-MM-DD -->`, optionally with a trailing `(reason)`.
+
+Before any downstream write, grep the target file for the entry's normalized first ~40 characters — if already present, treat this entry as already-landed, mark the hub entry promoted, and skip the write. This is what makes an interrupted or re-run batch safe.
+
+## Step 7 — Leak Scan
+
+Before writing outbound text to any consumer or public destination, scan it for:
+
+- Every other venture's slug and aliases from the registry (never the destination's own)
+- Hub path fragments (`{BUSINESS_ROOT}` paths, this repo's own root-relative paths)
+- Machine names (the `clones` keys across the registry)
+- This repo's org-token denylist, if `.arcane.json`/config defines one
+
+A hit blocks the write and reports exactly what matched; offer the operator a rewrite or `keep in book` (leave the entry `status: new`, untouched). This scan is only possible hub-side, because only the hub holds the full sibling list — that asymmetry is deliberate, not a gap: a consumer repo could never run this check on itself without first being handed the very list it must never see.
+
+## Step 8 — Report
+
+Stage (never commit) the touched files in each repo that received a write, including this hub repo. Print one proposed commit message per repo:
+
+```
+Staged (not committed):
+  hub:            ventures/ordovica/IDEAS.md
+                  proposed: docs(ideas): promote 1 entry to ordovica
+  ordovica:       IDEAS.md
+                  proposed: docs(ideas): capture dark-mode toggle candidate
+Run spell-commit-work in each repo. N entries remain new.
+```
+
+## Rules
+
+- Never run outside a hub repo. Never infer hub status.
+- Never let `all` or the plan-confirm authorize a disclosure — that confirmation is always separate, always per-entry, always the literal word `disclose`.
+- Never write a sibling venture's slug, a hub path, or a machine name into a consumer or public artifact — the leak scan is mandatory, not advisory.
+- Never commit. Stage and report; hand off to `spell-commit-work`.
+- Never guess a venture from partial input — resolve through the registry's aliases or ask.
+- Land downstream before marking the hub entry promoted, so an interrupted batch never loses track of what actually shipped.

package/dist/assets/.github/prompts/spell-save-idea.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: Spell — Save Idea
-description: Quickly capture a fleeting idea into the repo's idea inbox so it is not lost. Low ceremony, no approval gate, optimized for voice and speed.
-argument-hint: The idea itself — a sentence to a couple of paragraphs (e.g., "add a dark-mode toggle to the settings page")
+description: Quickly capture a fleeting idea into the repo's idea inbox so it is not lost. Low ceremony, no approval gate, optimized for voice and speed. In a hub repo, optionally target a venture's own idea book.
+argument-hint: The idea itself — a sentence to a couple of paragraphs (e.g., "add a dark-mode toggle to the settings page"), optionally "for <venture>" (hub only, e.g. "save this idea for ordo — …")
 agent: agent
 ---
 
@@ -9,8 +9,9 @@ agent: agent
 
 - This spell saves a short idea into `IDEAS.md` at the repo root with a timestamp, so a good thought is not lost between sessions.
 - It is deliberately fast and low-friction: no approval gate, no multi-step proposal — capture and confirm.
-- Use it the moment an idea occurs to you. Triage later with `spell-todo` or `spell-suggest-feature`.
+- Use it the moment an idea occurs to you. Triage later with `spell-todo` or `spell-suggest-feature`; in a hub, promote with `spell-manifest`.
 - This is the lightweight counterpart to `spell-document` (which formalizes a whole conversation into polished docs).
+- **In a hub repo:** "save this idea for &lt;venture&gt;" targets that venture's own `IDEAS.md` book instead of the hub root — private by default, including for ventures whose own repo is public.
 
 ---
 
@@ -18,6 +19,36 @@ Capture the user's idea into the idea inbox with minimal ceremony.
 
 The user's input IS the idea. If no idea text was provided, ask one short question: _"What's the idea?"_ and stop until they answer.
 
+## Step 0 — Venture Targeting (Hub Only)
+
+If the input names a venture ("save this idea for ordo", `--venture <slug>`), resolve it through `ventures/registry.json`'s aliases first (exact slug → alias → closest match offered — never guessed). Unknown slug:
+
+```
+No venture "<slug>" under ventures/ (closest: ordovica, tidewright).
+1) use <closest>  2) save to hub root IDEAS.md  3) cancel (create the venture first: spell-summon-venture)
+```
+
+Never silently create a venture folder.
+
+If `role` in `.arcane.json` is not `"hub"`, venture-targeting phrasing is refused:
+
+```
+Venture targeting works only in the hub repo (role: "hub" in .arcane.json). This repo has no venture books.
+1) save to this repo's IDEAS.md (venture reference removed)
+2) skip — capture it in the hub: spell-save-idea --venture <slug> "<idea>"
+Which? (1/2)
+```
+
+If option 1 is chosen and the named venture is a *different* venture than this repo's own, strip that name from the idea text before writing it — a sibling venture's name must never land in a consumer repo's `IDEAS.md`. If it's this repo's own venture, keep the text as given.
+
+An idea that only *mentions* a venture, without targeting phrasing, is not redirected — proceed with the hub root and append a non-blocking hint to the Step 3 confirmation instead (speed rule: don't block on a maybe):
+
+```
+(mentions ordovica — re-save with --venture ordovica, or route it later with spell-manifest)
+```
+
+When targeting a venture book that doesn't exist yet as a file, create it from the venture-template `IDEAS.md` stub (same header convention as the hub root, below) with the venture's name filled in. Tolerate operator YAML frontmatter above either book's header — always append after the final `---` divider, never before it.
+
 ## Step 1 — Normalize the Idea
 
 - Take the user's input verbatim as the core idea.
@@ -29,7 +60,7 @@ The user's input IS the idea. If no idea text was provided, ask one short questi
 
 ## Step 2 — Append to IDEAS.md
 
-Append (never overwrite) an entry to `IDEAS.md` at the repo root.
+Append (never overwrite) an entry to `IDEAS.md` — the repo root, or the resolved venture's own book from Step 0.
 
 Entry format:
 
@@ -69,7 +100,7 @@ Print a single concise confirmation, nothing more:
 After confirming, add at most one short line offering a next step **only if the idea is obviously
 actionable or product-shaped**:
 
-> Want to turn this into a tracked item? Run `spell-todo` (task) or `spell-suggest-feature` (product idea).
+> Want to turn this into a tracked item? Run `spell-todo` (task) or `spell-suggest-feature` (product idea). In a hub, `spell-manifest` promotes it downstream once ready.
 
 Do not ask follow-up questions. Do not commit — leave that to `spell-commit-work`.
 

package/dist/assets/.github/prompts/spell-summon-venture.prompt.md

@@ -0,0 +1,109 @@
+---
+name: Spell — Summon Venture
+description: Create a new venture in a hub repo — folder, overview/config/legal docs, idea and todo books, and a registry entry — in one hub-gated move.
+argument-hint: Venture Name | Venture Type | One-line description
+agent: agent
+---
+
+## Executive Summary
+
+- This prompt creates a new venture in a **hub** repo: the venture folder, its starter docs, its two idea/todo books, and its `ventures/registry.json` entry — one operation instead of several manual steps.
+- **Hub-gated:** requires `role: "hub"` in `.arcane.json`. Refuses cleanly in a consumer repo, pointing at the right place to capture the idea instead.
+- Use this when starting a new venture (business, product, or personal project) that the hub should track.
+- Input format is: `Venture Name | Venture Type | Description` — prompt will ask for missing fields.
+- Renamed from `spell-bootstrap-business` — venture books and the registry didn't exist when that spell was named. Clean rename, no compatibility alias, per [[DECISIONS#ARC-008|ARC-008]]'s precedent.
+
+---
+
+## Step 0 — Hub Gate
+
+Read `.arcane.json`. If `role` is not `"hub"`, stop and report:
+
+> `spell-summon-venture` runs only in a hub repo (`role: "hub"` in `.arcane.json`). This repo is a consumer. If you're capturing an idea for a venture that should exist, save it in the hub instead — ask there for `spell-save-idea --venture <new-slug> "<idea>"`, which offers to scaffold the venture book if the slug doesn't exist yet.
+
+Do not create anything. Do not infer hub status from a `ventures/` directory existing — that directory can legitimately exist in a consumer repo too (this exact spell creates it there in non-hub contexts under the old model; the gate is what changed).
+
+If `role` is `"hub"`, resolve `{BUSINESS_ROOT}` from `.arcane.json`'s `business_root` field (default `ventures/`) and continue.
+
+## Step 1 — Gather Venture Details
+
+Parse the prompt argument as:
+`<Venture Name> | <Venture Type> | <One-line Description>`
+
+If any required value is missing, ask only for missing fields. Additionally ask for **ownership** if not stated or inferable from context: `llc` (company-owned), `co-venture` (shared with an external partner), or `personal` (non-commercial, no co-owner) — never guess this; it's load-bearing for the registry and for later idea-lifecycle disclosure decisions.
+
+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 venture-type checklist below.
+- [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.
+- [.arcane/templates/venture-template/IDEAS.md](../../.arcane/templates/venture-template/IDEAS.md) and [.arcane/templates/venture-template/TODO.md](../../.arcane/templates/venture-template/TODO.md) — book stubs. If missing, use the header format from [[spell-save-idea|spell-save-idea]] / [[spell-todo|spell-todo]].
+- [README.md](../../README.md) — repo navigation. If missing, skip cross-linking.
+- [project.md](../../project.md) — project context. If missing, skip.
+
+## Step 2 — Create the Venture
+
+1. Create `{BUSINESS_ROOT}/<slug>/` using existing repo style (lowercase with dashes). If `{BUSINESS_ROOT}` doesn't exist yet, create it.
+2. Create these files:
+   - `overview.md` from template, filled with provided venture details and current date.
+   - `config.md` with placeholders for `{PLATFORM_NAME}` configuration, data paths, and platform integrations. (`{PLATFORM_NAME}` is the org's operating platform — resolve from `.arcane.json`/frontmatter; ask if unset.)
+   - `legal.md` with baseline legal checklist and links to relevant repo docs.
+   - `IDEAS.md` from the venture-template stub, with the venture name filled in.
+   - `TODO.md` from the venture-template stub, with the venture name filled in.
+3. Add a startup checklist tailored to the venture type (`e-commerce`, `app`, `protocol`, `service`, or `personal`).
+
+## Step 3 — Register the Venture
+
+Open (or create, with the standard header — see `ventures/registry.json`'s own `_comment` field for the expected shape) `ventures/registry.json` and append an entry keyed by the slug:
+
+```json
+"<slug>": {
+  "name": "<Venture Name>",
+  "aliases": [],
+  "status": "idea",
+  "visibility": "private",
+  "ownership": "<llc|co-venture|personal>",
+  "tracking": "none",
+  "repos": []
+}
+```
+
+`status` starts `"idea"` and `tracking` starts `"none"` — this spell only creates the hub-side folder, it does not provision a code repo or tracker project. Update the `repos[]` array separately once a real repo exists. `visibility` defaults to `"private"`; only change it if the operator states the venture is public-facing at creation time.
+
+## Step 4 — Cross-Links and Summary
+
+Add cross-links only when appropriate:
+
+- Update [README.md](../../README.md) only if there is a clear place for venture navigation.
+- Update [TODO.md](../../TODO.md) (hub root) only with concrete, actionable next tasks — venture-specific tasks belong in the new venture's own `TODO.md`, not here.
+
+Return a ready-to-start summary.
+
+Output format:
+
+## Created
+
+- File and folder paths created, including the `ventures/registry.json` entry.
+
+## Defaults Applied
+
+- Slug, ownership, naming decisions, and template assumptions used.
+
+## Immediate Next Actions
+
+1. Action one.
+2. Action two.
+3. Action three.
+4. Action four.
+5. Action five.
+
+## Questions To Finalize
+
+- Up to 3 targeted questions, or `None`.
+
+Rules:
+
+- Follow repository frontmatter conventions.
+- Do not create Azure resources directly; document steps only.
+- Keep generated docs editable and operational, not verbose.
+- Never run outside a hub repo. Never infer hub status — only `role: "hub"` counts.

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

@@ -1,7 +1,7 @@
 ---
 name: Spell — Todo
-description: Elaborate a raw idea into one or more well-scoped TODO items and place them in the right document(s).
-argument-hint: The raw idea to elaborate (e.g., "add spending limits doc", "automate ADR numbering", "build a dashboard for {AGENT_NAME}"). `{AGENT_NAME}` resolves from `.arcane.json` / frontmatter; ask if unset.
+description: Elaborate a raw idea into one or more well-scoped TODO items and place them in the right document(s). In a hub repo, optionally target a venture's own TODO book, or sweep every book's open-item counts.
+argument-hint: The raw idea to elaborate (e.g., "add spending limits doc", "automate ADR numbering", "build a dashboard for {AGENT_NAME}"), optionally "for <venture>" (hub only). `{AGENT_NAME}` resolves from `.arcane.json` / frontmatter; ask if unset. Use `--sweep` instead to report open-item counts across every book.
 agent: agent
 ---
 
@@ -11,16 +11,52 @@ agent: agent
 - It reads the current TODO landscape and repo structure to avoid duplicates and pick the right home.
 - Use this any time you have an idea mid-session and don't want to lose it or park it in the wrong place.
 - If the idea is ADR-worthy or journal-worthy, it flags that and routes accordingly.
+- **In a hub repo:** "add a todo for &lt;venture&gt;" targets that venture's own `TODO.md` book instead of the hub root. `--sweep` skips elaboration entirely and reports new/open counts across every book (hub root + every venture).
 
 ---
 
-Elaborate the idea given by the user and add it to the right document(s).
+## Sweep Mode (`--sweep`)
+
+If the argument is (or starts with) `--sweep`, skip every other step in this spell entirely and run this instead:
+
+- **In a hub repo:** report `status: new` counts and oldest-entry age for the hub root `TODO.md` plus every `ventures/<slug>/TODO.md` that exists. Group by book, point at `spell-manifest` for entries ready to promote. Report-only — no edits.
+- **In a consumer repo:** report the same, for the repo-root `TODO.md` only (no venture books exist there).
+
+Output format:
+
+```
+Todo sweep — N books, M open items
+
+hub TODO.md               12 open, oldest 2026-07-14
+ventures/ordovica/TODO.md  3 open, oldest 2026-08-10
+```
+
+## Step 0 — Venture Targeting (Hub Only)
+
+If the input names a venture ("add a todo for ordo", `--venture <slug>`), resolve it through `ventures/registry.json`'s aliases first (exact slug → alias → closest match offered — never guessed). Unknown slug:
+
+```
+No venture "<slug>" under ventures/ (closest: ordovica, tidewright).
+1) use <closest>  2) add to hub root TODO.md  3) cancel (create the venture first: spell-summon-venture)
+```
+
+If `role` in `.arcane.json` is not `"hub"`, venture-targeting phrasing is refused:
+
+> Venture targeting works only in the hub repo (`role: "hub"` in `.arcane.json`). This repo has no venture books.
+> 1) add to this repo's TODO.md (venture reference removed)
+> 2) skip — capture it in the hub: `spell-todo --venture <slug> "<idea>"`
+
+If option 1 is chosen and the named venture is a *different* venture than this repo's own, strip that name from the item text before writing it — a sibling venture's name must never land in a consumer repo's `TODO.md`. If it's this repo's own venture, keep the text as given.
+
+An idea that only *mentions* a venture, without targeting phrasing, is not redirected — proceed with the hub root as normal (speed rule: don't block on a maybe).
+
+Elaborate the idea given by the user and add it to the right document(s) — the hub root `TODO.md` by default, or the resolved venture's own `TODO.md` when targeted.
 
 The raw idea from the user is in the prompt argument. If no argument was provided, ask the user to describe the idea before proceeding.
 
 Use these files first:
 
-- [TODO.md](../../TODO.md) — section structure and existing items (avoid duplicates)
+- [TODO.md](../../TODO.md) — section structure and existing items (avoid duplicates); or the targeted venture's own `TODO.md`
 - [DECISIONS.md](../../DECISIONS.md) — ADR registry (check if the idea is decision-worthy)
 - [README.md](../../README.md) — repo structure (find the right canonical doc to reference)
 - [project.md](../../project.md) — active priorities (calibrate urgency)