arcane-cli 0.33.9 → 0.34.1

package/dist/assets/.arcane/governance/decision-documentation-standard.md

@@ -72,7 +72,7 @@ Arcane separates framework-level decisions from org-specific ones using two pref
 2. Confirms no collision with other entities
 3. Identifies any docs, scripts, or prompts that reference the old name
 
-This check was added after [[governance/rcas/RCA-001-naming-collision|RCA-001]] discovered that ADR-061 named a product without checking whether the ops repo already used that name. **Enforcement: explicitly advisory prose (ARC-023) — no script or spell gate verifies that an ADR introducing a new name actually contains a "Naming impact" section or performed its three checks; `spell-scry` can run the grep-and-collision check manually, but nothing requires it before such an ADR is written.**
+This check was added after [[docs/rcas/RCA-001-naming-collision|RCA-001]] discovered that ADR-061 named a product without checking whether the ops repo already used that name. **Enforcement: explicitly advisory prose (ARC-023) — no script or spell gate verifies that an ADR introducing a new name actually contains a "Naming impact" section or performed its three checks; `spell-scry` can run the grep-and-collision check manually, but nothing requires it before such an ADR is written.**
 
 ### Tier 2: Companion Detail Docs
 

package/dist/assets/.arcane/governance/rca-process-standard.md

@@ -38,7 +38,7 @@ An RCA is **recommended** (but optional) for:
 
 ## RCA Template
 
-**Every RCA follows this structure. Artifacts are stored in `governance/rcas/` with the filename `RCA-NNN-short-slug.md` (sequential numbering, matching the related ADR when applicable). Enforcement: explicitly advisory prose (ARC-023) — no script validates RCA filenames, sequential numbering, or template structure.**
+**Every RCA follows this structure. Artifacts are stored in `docs/rcas/` with the filename `RCA-NNN-short-slug.md` (sequential numbering, matching the related ADR when applicable). Enforcement: explicitly advisory prose (ARC-023) — no script validates RCA filenames, sequential numbering, or template structure.**
 
 ```markdown
 ---
@@ -104,7 +104,7 @@ Bullet points — what the team now knows that it didn't before.
 ### 1. Initiate
 
 When a trigger condition is met:
-- Create the RCA artifact file in `governance/rcas/`
+- Create the RCA artifact file in `docs/rcas/`
 - Fill in the Incident Summary and Timeline sections
 - Record the ADR that establishes the RCA (if applicable)
 
@@ -147,13 +147,13 @@ RCAs do not have formal severity levels. The trigger conditions above determine
 ## Artifact Location
 
 ```
-governance/
+docs/
   rcas/
     RCA-001-naming-collision.md
     RCA-002-...
 ```
 
-**Why `governance/rcas/`?** RCAs are governance artifacts (process improvement), not journals (session logs) or decisions (ADRs). They complement ADRs by explaining *how a decision failed* rather than *what was decided*.
+**Why `docs/rcas/`, not `governance/rcas/`?** RCAs are project/domain documents (a record of what happened in *this* repository), not a framework-managed standard — [[portable-bootstrap#where-documents-live|portable-bootstrap.md's "Where Documents Live"]] reserves `.arcane/governance/` for framework-managed standards and explicitly forbids a duplicate root `governance/` tree; `docs/` is the same explicit-descriptive-path convention it names for project/domain documents. RCAs remain governance artifacts in *purpose* (process improvement, not a journal or a decision) — they complement ADRs by explaining *how a decision failed* rather than *what was decided* — just not in *filesystem location*. Enforcement: explicitly advisory prose (ARC-023) — no script checks that an RCA file actually lives under `docs/rcas/` rather than elsewhere.
 
 ## Maintenance
 

package/dist/index.js

@@ -4817,6 +4817,9 @@ async function runDoctor(targetDir, options = {}, assetsDir) {
   }
 }
 
+// src/commands/ward.ts
+import { readFile as readFile11 } from "fs/promises";
+
 // src/modules/ward.ts
 import { readdir as readdir6, readFile as readFile10 } from "fs/promises";
 import { join as join13, relative as relative2 } from "path";
@@ -4942,8 +4945,24 @@ function parseTerms(raw) {
   if (!raw) return [];
   return raw.split(",").map((t) => t.trim()).filter(Boolean);
 }
+function parseTermsFileContent(raw) {
+  return raw.split(/[,\r\n]+/).map((t) => t.trim()).filter(Boolean);
+}
+async function readTermsFile(filePath) {
+  try {
+    return parseTermsFileContent(await readFile11(filePath, "utf8"));
+  } catch (error) {
+    console.warn(
+      `\u26A0 arcane: could not read --terms-file "${filePath}": ${error.message}`
+    );
+    return [];
+  }
+}
 async function runWardCli(targetDir, options = {}, exclusions = []) {
-  const terms = parseTerms(options.terms);
+  const terms = [
+    ...parseTerms(options.terms),
+    ...options.termsFile ? await readTermsFile(options.termsFile) : []
+  ];
   const report = await runWard(targetDir, { terms, exclusions });
   console.log("\nspell ward \u2014 scanning for leaked identifiers\n");
   const leaks = report.findings.filter((f) => f.category === "leak");
@@ -5154,6 +5173,9 @@ program.command("doctor").description("Check your environment for Arcane prerequ
 program.command("ward").description("Scan the repo for leaked identifiers -- third-party trademarks and the operator's own personal identifiers alike (T18)").option(
   "--terms <terms>",
   "Comma-separated denylist terms, in addition to the built-in vendor-identifier list. Seed this from your OWN identity too, not just org/venture names -- usernames, machine names, and personal handles leak the same way a private venture name does (I1)"
+).option(
+  "--terms-file <path>",
+  "Read denylist terms from a file instead of --terms, to avoid shell-history exposure (ARC-041). Same comma/newline-separated format as ARCANE_ORG_TOKENS."
 ).option("--gate", "Exit non-zero if any leak is found (for CI)").action(async (opts) => {
   await runWardCli(process.cwd(), opts);
 });