arcane-cli 0.33.3 → 0.33.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -30,7 +30,7 @@ npm install -g arcane-cli # then: spell init
|
|
|
30
30
|
|
|
31
31
|
<div align="center">
|
|
32
32
|
|
|
33
|
-
**🔁 opinionated lifecycle** · **📜 41 spells** · **🤖 12 agents** · **⚖️ 25 governance standards** · **📝 markdown-native** · **🔌 any AI client / tracker**
|
|
33
|
+
**🔁 opinionated lifecycle** · **📜 <!--count:spells-->41<!--/count:spells--> spells** · **🤖 <!--count:agents-->12<!--/count:agents--> agents** · **⚖️ <!--count:governance-->25<!--/count:governance--> governance standards** · **📝 markdown-native** · **🔌 any AI client / tracker**
|
|
34
34
|
|
|
35
35
|
</div>
|
|
36
36
|
|
|
@@ -113,9 +113,9 @@ Arcane isn't a prompt snippet — it's a full framework. Everything installs int
|
|
|
113
113
|
|
|
114
114
|
| Layer | What you get |
|
|
115
115
|
| --- | --- |
|
|
116
|
-
| 📜 **Spells** |
|
|
117
|
-
| ⚖️ **Governance** |
|
|
118
|
-
| 🤖 **Agents** |
|
|
116
|
+
| 📜 **Spells** | **<!--count:spells-->41<!--/count:spells-->** prompt-driven workflows spanning the entire lifecycle — planning, architecture, implementation, testing, review, shipping, session management, and ops. |
|
|
117
|
+
| ⚖️ **Governance** | **<!--count:governance-->25<!--/count:governance-->** battle-tested standards as drop-in templates: git conventions, testing standards, CI/CD, threat model, ADR format, naming, security hardening, and more. |
|
|
118
|
+
| 🤖 **Agents** | **<!--count:agents-->12<!--/count:agents-->** ready-made agent personas with roles, clusters, and a gamified autonomy model — assign work and power levels per repo. |
|
|
119
119
|
| 🛠️ **CLI** | `spell init / add / update / status / uninstall` — install by profile or à la carte, and keep everything in sync as new versions ship. |
|
|
120
120
|
|
|
121
121
|
<!-- arcane:start -->
|
|
@@ -135,12 +135,14 @@ Arcane isn't a prompt snippet — it's a full framework. Everything installs int
|
|
|
135
135
|
</details>
|
|
136
136
|
<!-- arcane:end -->
|
|
137
137
|
|
|
138
|
+
<!-- arcane:governance:start -->
|
|
138
139
|
<details>
|
|
139
140
|
<summary><b>⚖️ The governance standards (25)</b></summary>
|
|
140
141
|
|
|
141
|
-
`
|
|
142
|
+
`git-conventions` · `testing-standards` · `framework-decisions` · `decision-documentation-standard` · `agent-work-queue-model` · `naming-conventions` · `agent-policies` · `threat-model` · `hardening-checklist` · `authentication-strategy` · `new-business-setup` · `agent-approved-paths` · `portable-bootstrap` · `development-methodology` · `cicd-standards` · `poc-management-pattern` · `product-excellence-standards` · `spell-authoring-standards` · `rca-process-standard` · `universal-agent-rules` · `records-conventions` · `external-verification-standards` · `web-discoverability-standards` · `mobile-release-standards` · `compliance-standards`
|
|
142
143
|
|
|
143
144
|
</details>
|
|
145
|
+
<!-- arcane:governance:end -->
|
|
144
146
|
|
|
145
147
|
---
|
|
146
148
|
|
|
@@ -21,14 +21,19 @@ Determine the correct semver bump and apply it.
|
|
|
21
21
|
|
|
22
22
|
## Step 1 — Check whether a bump is needed
|
|
23
23
|
|
|
24
|
-
Run the version check gate
|
|
24
|
+
Run the version check gate in **staged mode** (LH-06a) — this spell runs before the commit that
|
|
25
|
+
will actually contain the change, so the default `merge-base..HEAD` diff can't see it yet; staged
|
|
26
|
+
mode unions that diff with `git diff --cached --name-only` so today's not-yet-committed work is
|
|
27
|
+
checked too, not just history:
|
|
25
28
|
|
|
26
29
|
```
|
|
27
|
-
npm run check:version-bump
|
|
30
|
+
npm run check:version-bump -- --staged
|
|
28
31
|
```
|
|
29
32
|
|
|
30
33
|
- If it **passes** → no bump needed. Stop here and report "No version bump required."
|
|
31
34
|
- If it **fails** → proceed to Step 2.
|
|
35
|
+
- If the changed content isn't staged yet (working-tree edits only), use `-- --working-tree`
|
|
36
|
+
instead, which additionally unions plain `git diff --name-only`.
|
|
32
37
|
|
|
33
38
|
## Step 2 — Determine semver type
|
|
34
39
|
|
|
@@ -42,6 +42,10 @@ Workflow:
|
|
|
42
42
|
- If coverage passes, record the coverage summary for use in the commit body or PR description.
|
|
43
43
|
- **Never commit code that fails CI locally.** The pipeline is not the first gate — this step is.
|
|
44
44
|
|
|
45
|
+
- **Distributable-change halt** (LH-06a; only when this repo has its own `scripts/check-version-bump.ts` — Arcane's own repo, or one that adopted the same convention; skip gracefully otherwise, this is not a general-purpose check every consumer repo can run):
|
|
46
|
+
- Run `npm run check:version-bump -- --staged` before committing. This is the staged-diff mode, not the default CI mode — it can see today's not-yet-committed change, which the default `merge-base..HEAD` diff cannot.
|
|
47
|
+
- **HALT if it fails.** Distributable content (`src/assets/`, `registry.ts`, `profiles.ts`) changed without a version bump. Run `spell-bump` first, then return here.
|
|
48
|
+
|
|
45
49
|
- **Format before committing** _(stack-aware; runs alongside the test gate above)_:
|
|
46
50
|
- Detect the configured formatter from the project's own config — do not assume one. Look for the toolchain's standard markers, for example:
|
|
47
51
|
- JS/TS: `.prettierrc*` / `prettier` in `package.json` → `npx prettier --write .`
|