arcane-cli 1.3.0 → 1.3.1

package/README.md

@@ -247,7 +247,7 @@ Unlike spells, agent files are never delivered by `spell init` or `spell update`
 
 ```jsonc
 // .arcane.json
-{ "spell_scope": "user" }   // absent, or "repo", means this repository carries its own spells
+{ "spell_scope": "user" }   // absent, or "repo", means this repository carries its own spells and agents
 ```
 
 ```bash

package/dist/assets/.arcane/governance/spell-authoring-standards.md

@@ -125,7 +125,12 @@ Arcane spells ship to other repositories and, eventually, open source. Keep them
   hand. Relative links inside a spell resolve from `.arcane/spells/`, two levels below the repo
   root (`../../.arcane/governance/…`, `../../README.md`); refer to a sibling spell as
   `spell-x.md`. Enforcement: executable check (ARC-023) — `npm run check:self-host-parity`
-  re-renders every shim from its canonical file and fails CI on any byte of difference.
+  re-renders every shim from its canonical file and fails CI on any byte of difference. **A spell
+  may also be installed once per machine** at `~/.arcane/spells/<id>.md` (ARC-045 decision 3), where
+  a `../../` link has no repository to resolve against: write a spell so that a broken context link
+  degrades to a named, skippable step rather than a dead end, which D2 Gold already asks for in its
+  "works in a vanilla consuming repo with no Arcane context files present" bar. Enforcement:
+  explicitly advisory prose (ARC-023) — nothing resolves a spell's links from the user tier.
 - **Never hard-code** an org name, person, venture, product, or machine name. Use a documented
   `{UPPER_SNAKE}` placeholder: `{ADO_ORG}`, `{ADO_PROJECT}`, `{BUSINESS_NAME}`, `{OPERATOR_NAME}`.
   Enforcement: executable check (ARC-023) — same mechanism as D2 Bronze above: the `org-token-lint`

package/dist/assets/.arcane/governance/universal-agent-rules.md

@@ -160,4 +160,8 @@ client through a separate mechanism: one canonical source per spell at `.arcane/
 (ARC-045), from which three thin shims are generated — `.github/prompts/*.prompt.md` for Copilot,
 `.claude/commands/*.md` for Claude Code, and `.agents/skills/*/SKILL.md` for Codex (CS-01) — never
 hand-authored per client. A shim carries no workflow of its own: when a spell must be read in full,
-read the canonical file.
+read the canonical file. Both spells and the agent roster can instead be installed once per machine,
+at `~/.arcane` (ARC-045 decision 3, ARC-047); a repository with `spell_scope: "user"` in `.arcane.json`
+carries neither its own spell files nor its own `.github/agents/*.agent.md`, and every client reads
+the machine-wide copies instead. This table is unaffected either way — standing instructions never
+move tier.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arcane-cli",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "Arcane framework CLI — scaffold and manage governance files in consuming repositories",
   "keywords": [
     "arcane",