arcane-cli 0.28.1 → 0.29.0

package/README.md

@@ -120,10 +120,10 @@ Arcane isn't a prompt snippet — it's a full framework. Everything installs int
 
 <!-- arcane:start -->
 <details>
-<summary><b>📜 The full spell catalogue (40)</b></summary>
+<summary><b>📜 The full spell catalogue (41)</b></summary>
 
 **Session** — `open-session` · `close-session` · `commit-work` · `status` · `arcane-version`
-**Capture** — `save-idea` · `todo` · `feedback` · `suggest-feature` · `document` · `brainstorm` · `explain-concept`
+**Capture** — `save-idea` · `todo` · `feedback` · `suggest-feature` · `document` · `verification-ledger` · `brainstorm` · `explain-concept`
 **Delivery** — `create-pull-request` · `sync-pull-request` · `address-review`
 **Review** — `review` · `review-batch`
 **Planning** — `plan` · `architect` · `scope` · `product-review`

package/dist/assets/.claude/commands/spell-verification-ledger.md

@@ -0,0 +1,13 @@
+---
+description: Use PROACTIVELY when a session had real verification events worth a structured record — especially a claim that didn't survive a check.
+---
+
+# Verification Ledger
+
+Invoke the Arcane `spell-verification-ledger` spell workflow.
+
+See the full prompt at `.github/prompts/spell-verification-ledger.prompt.md` for the complete workflow definition.
+
+---
+
+@.github/prompts/spell-verification-ledger.prompt.md

package/dist/assets/.github/prompts/spell-close-session.prompt.md

@@ -31,7 +31,7 @@ Workflow:
    - Decisions made (even implicit ones like naming choices, tool preferences, or workflow patterns).
    - Problems encountered and how they were resolved (troubleshooting).
    - Lessons learned (anything that cost time, surprised the user, or should prevent future mistakes).
-   - **Capture tie-in tip:** If this session produced durable analysis worth formalizing (a design, an investigation, a research finding, a reusable explanation), suggest running `spell-document` before closing so it lands in the right doc — a research finding defaults to `docs/research/<topic-slug>.md` per `portable-bootstrap.md`'s Research Reports convention. For quick ideas worth keeping but not yet actionable, suggest `spell-save-idea`.
+   - **Capture tie-in tip:** If this session produced durable analysis worth formalizing (a design, an investigation, a research finding, a reusable explanation), suggest running `spell-document` before closing so it lands in the right doc — a research finding defaults to `docs/research/<topic-slug>.md` per `portable-bootstrap.md`'s Research Reports convention. For quick ideas worth keeping but not yet actionable, suggest `spell-save-idea`. If this session had a real verification event worth a structured record — especially a confidently stated claim that a check later contradicted — suggest `spell-verification-ledger` separately; it is not part of this close-session flow itself.
 
 1b. **Verify in-flight async work before writing any output artifact (EF-21). Enforcement: structured spell gate (ARC-023) — this workflow requires the observable state of every dispatched item before proceeding to step 2.** "I started it" is not "it worked." Before the journal, TODO.md, or the handoff are written, enumerate every piece of asynchronous work dispatched during this session that could still be running or could have failed after being kicked off — CI/CD runs, deployments, package publishes, long-running background tasks, PR checks. For each, **actively check** its current status through whatever means is available (CI provider API/CLI, deployment dashboard, `gh run view`, `az pipelines runs show`, etc.) — attempt the check before reaching for `unverifiable`; that state exists for genuine access limits (no CLI/API access, no credentials, provider outage), not for skipping a check that was merely inconvenient to run. Then classify into exactly one state:
 

package/dist/assets/.github/prompts/spell-verification-ledger.prompt.md

@@ -0,0 +1,101 @@
+---
+name: Spell — Verification Ledger
+description: Extract a structured record of claims that were checked this session and what the check showed — especially the ones that didn't survive. Separate from spell-close-session; run on demand, not every session.
+argument-hint: Optional focus (e.g., "just the corrections", "since the last commit")
+agent: agent
+---
+
+## Executive Summary
+
+- The highest-value output of a working session is often the corrections — claims that were checked and
+  did not survive. `spell-close-session` captures what happened and sanitized lessons learned; it does
+  not capture what was asserted, what was checked, what the check showed, or what changed as a result.
+  This spell extracts exactly that, separately.
+- **Run on demand, not every session.** Most sessions have nothing worth a ledger entry; this spell says
+  so plainly and stops rather than manufacturing content to fill one (same discipline as
+  `spell-document`).
+- **A `corrected` result is the point, not a failure to hide.** A ledger showing three confirmed claims
+  and one correction is more valuable than one showing four confirmed claims and nothing else — the
+  correction is evidence the verification step actually did something, not theater.
+- Appends to a single running file, [`docs/verification-ledger.md`](../../docs/verification-ledger.md),
+  so a calibration rate (how often a checked claim survives) is computable across sessions without
+  reading scattered journal entries.
+
+---
+
+## What counts as a ledger-worthy event
+
+Only an assertion that was actually **checked against an independent source** counts — not every
+statement made during the session. The check has to have been capable of coming back either way:
+
+- A confident claim, followed by a real verification step (a tool call, a live read, re-running
+  something, checking a second source), whose result **confirmed** the claim.
+- A confident claim, followed by the same kind of check, whose result **contradicted** it —
+  a **correction**.
+- A check that was attempted but couldn't produce a definitive answer (no access, an ambiguous result)
+  — **unverifiable**. Distinct from never having been checked at all, which isn't ledger-worthy at all.
+
+Not ledger-worthy: a claim nobody checked, a preference or judgment call with no verifiable fact behind
+it, or a check whose outcome was never in doubt (confirming something already directly observed moments
+earlier is not a verification event).
+
+## Workflow
+
+1. **Scan the session for ledger-worthy events**, per the definition above. Look specifically for
+   moments where a check contradicted an initial assertion — a count that was off, a file path that
+   didn't exist, a "should be done" that direct inspection showed wasn't, a citation that pointed at the
+   wrong content. These are usually more memorable than confirmations; do not let them get lost among
+   routine, expected-to-pass checks.
+
+2. **Stop here if nothing qualifies.** If the session had no real verification events — no claim was
+   both asserted with confidence and independently checked — say so plainly and do not proceed. A quiet,
+   uneventful session with nothing to report is a valid outcome, not a gap to paper over.
+
+3. **Classify each event:**
+
+   | Field | What it captures |
+   | --- | --- |
+   | Claim | The assertion as originally stated, in the speaker's own words at the time — not softened in hindsight. |
+   | Verification method | What was actually done to check it (a specific command, a specific file read, a specific re-fetch) — not "verified," which asserts nothing checkable itself. |
+   | Result | `confirmed` / `corrected` / `unverifiable`. |
+   | Correction | For `corrected` only: what the check actually showed, and what changed as a result (a claim retracted, a decision reversed, a fix applied). |
+
+4. **Present the extracted ledger for approval** before writing — the same approval gate
+   `spell-document` uses, since this is also durable content leaving the conversation:
+
+   ```text
+   ## Verification Ledger Proposal — [session topic]
+
+   | Claim | Verification method | Result | Correction |
+   | --- | --- | --- | --- |
+   | ... | ... | confirmed | — |
+   | ... | ... | corrected | ... |
+
+   Approve? (yes / edit / skip)
+   ```
+
+5. **Append, don't rewrite.** After approval, append a new `## YYYY-MM-DD — <session topic>` section
+   with the approved table to `docs/verification-ledger.md`. Get the real date from the system rather
+   than guessing. If the file doesn't exist yet, create it with a short header explaining its purpose
+   and schema, then the first section — never insert a section anywhere but the end.
+
+## Rules
+
+- Never fabricate a ledger-worthy event to fill a report — an empty result from step 2 is a complete,
+  valid run of this spell.
+- Quote the claim as it was actually stated, not a cleaned-up paraphrase that makes the miss look
+  smaller (or larger) than it was.
+- Do not editorialize about fault or blame in the ledger itself — the value is the calibration signal
+  (how often checks confirm vs. correct), not a record of who was wrong.
+- Do not commit the changes — that is `spell-commit-work`'s job.
+
+## Related
+
+- **Complements, does not replace:** `spell-close-session`'s narrative record and sanitized lessons
+  learned. Run this spell separately when a session had real verification events worth a structured
+  record, not as a mandatory step of every close.
+- `spell-document` — the general-purpose formalization spell this one borrows its
+  extract-then-approve-then-write shape from, narrowed to one specific, structured record type.
+
+> **Tip:** Run `spell-close-session` afterward to log the session, or `spell-commit-work` to commit the
+> ledger update.

package/dist/index.js

@@ -505,6 +505,8 @@ var COMPONENTS = [
       ".claude/commands/spell-suggest-feature.md",
       ".github/prompts/spell-document.prompt.md",
       ".claude/commands/spell-document.md",
+      ".github/prompts/spell-verification-ledger.prompt.md",
+      ".claude/commands/spell-verification-ledger.md",
       ".github/prompts/spell-brainstorm.prompt.md",
       ".claude/commands/spell-brainstorm.md",
       ".github/prompts/spell-explain-concept.prompt.md",
@@ -4640,7 +4642,10 @@ program.command("unblock-push").description("Lift this repository's push block (
 program.command("doctor").description("Check your environment for Arcane prerequisites").option("--fix", "Automatically create missing session continuity files").action(async (opts) => {
   await runDoctor(process.cwd(), { fix: opts.fix }, ASSETS_DIR);
 });
-program.command("ward").description("Scan the repo for leaked third-party identifiers and trademarks (T18)").option("--terms <terms>", "Comma-separated denylist terms, in addition to the built-in vendor-identifier list").option("--gate", "Exit non-zero if any leak is found (for CI)").action(async (opts) => {
+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("--gate", "Exit non-zero if any leak is found (for CI)").action(async (opts) => {
   await runWardCli(process.cwd(), opts);
 });
 var agentsCommand = program.command("agents").description("Manage the portable agent system (init, sync, list)");