arcane-cli 0.33.1 → 0.33.3
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** · **📜
|
|
33
|
+
**🔁 opinionated lifecycle** · **📜 41 spells** · **🤖 12 agents** · **⚖️ 25 governance standards** · **📝 markdown-native** · **🔌 any AI client / tracker**
|
|
34
34
|
|
|
35
35
|
</div>
|
|
36
36
|
|
|
@@ -136,9 +136,9 @@ Arcane isn't a prompt snippet — it's a full framework. Everything installs int
|
|
|
136
136
|
<!-- arcane:end -->
|
|
137
137
|
|
|
138
138
|
<details>
|
|
139
|
-
<summary><b>⚖️ The governance standards (
|
|
139
|
+
<summary><b>⚖️ The governance standards (25)</b></summary>
|
|
140
140
|
|
|
141
|
-
`universal-agent-rules` · `development-methodology` · `git-conventions` · `testing-standards` · `cicd-standards` · `decision-documentation-standard` · `naming-conventions` · `agent-policies` · `agent-approved-paths` · `agent-work-queue-model` · `threat-model` · `hardening-checklist` · `authentication-strategy` · `product-excellence-standards` · `rca-process-standard` · `poc-management-pattern` · `spell-authoring-standards` · `new-business-setup` · `portable-bootstrap` · `framework-decisions` · `records-conventions` · `external-verification-standards` · `web-discoverability-standards`
|
|
141
|
+
`universal-agent-rules` · `development-methodology` · `git-conventions` · `testing-standards` · `cicd-standards` · `decision-documentation-standard` · `naming-conventions` · `agent-policies` · `agent-approved-paths` · `agent-work-queue-model` · `threat-model` · `hardening-checklist` · `authentication-strategy` · `compliance-standards` · `product-excellence-standards` · `rca-process-standard` · `poc-management-pattern` · `spell-authoring-standards` · `new-business-setup` · `portable-bootstrap` · `framework-decisions` · `records-conventions` · `external-verification-standards` · `web-discoverability-standards` · `mobile-release-standards`
|
|
142
142
|
|
|
143
143
|
</details>
|
|
144
144
|
|
|
@@ -54,7 +54,7 @@ Paste this entire file into any AI client (Claude web, ChatGPT, etc.) to give it
|
|
|
54
54
|
- **Framework-managed standards:** `.arcane/governance/`. Spells reference this single installed layer; **do not create a duplicate root `governance/` tree. Enforcement: explicitly advisory prose (ARC-023) — no check scans a repo for a duplicate root-level `governance/` directory.**
|
|
55
55
|
- **Project-owned orientation and continuity:** `README.md`, `project.md`, `TODO.md`, `DECISIONS.md`, `ai-context/`, and `journal/`. Arcane creates missing files once and preserves existing content.
|
|
56
56
|
- **Project/domain documents:** use explicit descriptive paths such as `docs/`, `security/`, `infrastructure/`, or a configured business root. These add project context alongside framework standards.
|
|
57
|
-
- **Overrides
|
|
57
|
+
- **Overrides survive `arcane update`:** editing a managed `.arcane/governance/` standard no longer risks silent loss. Additive project documents were always safe; a hand-edit to a shipped standard now is too. **Enforcement: executable check (ARC-038, shipped BC-31)** — `spell update` compares each file's on-disk content against its recorded hash at install time: unchanged, it refreshes normally; edited, it fetches the exact previously-installed published version as a three-way merge base against your edit and the new vendor content, auto-merging non-overlapping changes and leaving standard conflict markers only on genuine collisions. If the prior published version can't be fetched, your edit is left untouched with a warning rather than replaced.
|
|
58
58
|
|
|
59
59
|
## Research Reports
|
|
60
60
|
|
|
@@ -46,8 +46,8 @@ Framework selection, coverage thresholds, and test evidence requirements across
|
|
|
46
46
|
|
|
47
47
|
| Category | Minimum Coverage | Examples |
|
|
48
48
|
|----------|-----------------|----------|
|
|
49
|
-
| **Standard code** | 80% | Business logic, data access, UI components, API handlers. Enforcement: executable check (ARC-023) — vitest.config.ts configures a global 80% lines/branches/functions/statements threshold under `coverage.thresholds`,
|
|
50
|
-
| **Critical paths** | 95% | Authentication, payment processing, IoT firmware commands, calibration protocols, encryption/signing. Enforcement: executable check (ARC-023) — vitest.config.ts overrides this to 95% for src/modules/copier.ts, manifest.ts, merger.ts, registry.ts, and src/config/profiles.ts (manifest.ts's branches override is 90%, not 95%)
|
|
49
|
+
| **Standard code** | 80% | Business logic, data access, UI components, API handlers. Enforcement: executable check (ARC-023) — vitest.config.ts configures a global 80% lines/branches/functions/statements threshold under `coverage.thresholds`, evaluated in CI: ci.yml's build-test Test step runs `npm run test:coverage` (LH-04), which fails the build if any threshold is missed. |
|
|
50
|
+
| **Critical paths** | 95% | Authentication, payment processing, IoT firmware commands, calibration protocols, encryption/signing. Enforcement: executable check (ARC-023) — vitest.config.ts overrides this to 95% for src/modules/copier.ts, manifest.ts, merger.ts, registry.ts, and src/config/profiles.ts (manifest.ts's branches override is 90%, not 95%); the same CI step evaluates these overrides too. |
|
|
51
51
|
|
|
52
52
|
### What Counts as "Critical"
|
|
53
53
|
|