From fb6efbf5d68ace40701e1e8c921637b331c24dc0 Mon Sep 17 00:00:00 2001 From: Jake Ruesink Date: Sun, 9 Aug 2026 11:09:48 -0500 Subject: [PATCH 1/2] fix(audit): reference catalogs and pointers are not governance documents MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Validation Date Coverage asked every canonical governance file for a `Last validated:` line. Two document kinds were never governance documents: - `docs/patterns/**` — a reference catalog read on demand. lc-classic-starter sat CRITICAL at 22% coverage, and 7 of its 9 governance files were catalog entries. Stamping ~20 of them changes no agent behaviour. - pointer documents — already named by isPointerDocument, which this check did not consult. Both leave the denominator rather than being counted and forgiven, and the exemption is stated in the check detail so a coverage figure that rose stays auditable: "100% ... (excludes 7 reference/pointer docs)". Scoped to this one coverage figure — both kinds remain on the scoring surface for every other check, exactly as the shim exclusion in #41 was scoped to Low-Yield. Two mistakes of mine are worth recording, because both were caught by the harness rather than by me: I also exempted `docs/bootstrap-templates/**`, which the brief never asked for. Anvil's own governance surface is 18 bootstrap templates, all dated, so the exemption emptied its denominator and an empty denominator read as 0% — turning Anvil's own verdict from PASS to CRITICAL. verify:self-audit-proof caught it, one turn after I loosened that proof's PR-churn normalization, which is decent evidence the loosening did not blind it. Templates are now treated as the governance documents they are. The empty-denominator case is guarded separately: when every governance file is exempt there is nothing left to measure, so the check falls back to the full set rather than inventing a 0%. Fleet sweep across 17 repos, before -> after: exactly one verdict moves, lc-classic-starter CRITICAL -> NEEDS WORK. Nothing else shifts. forge stays CRITICAL correctly — after exempting its 3 catalog entries, its two remaining `.devagent` files are ordinary instruction docs that genuinely carry no date. Co-Authored-By: Claude Opus 5 (1M context) --- scripts/audit.ts | 34 +++- scripts/governance-metadata-scoping.test.ts | 170 ++++++++++++++++++++ 2 files changed, 200 insertions(+), 4 deletions(-) create mode 100644 scripts/governance-metadata-scoping.test.ts diff --git a/scripts/audit.ts b/scripts/audit.ts index 6a479c0..dfc016b 100644 --- a/scripts/audit.ts +++ b/scripts/audit.ts @@ -1601,11 +1601,31 @@ export function assessStageA( const oversizedCount = inventory.canonicalFiles.filter( (f) => f.linesOverBudget, ).length; + // Governance metadata is asked of documents that govern. A reference catalog + // read on demand and a pointer to the canonical document are neither, so they + // leave the denominator rather than being counted and forgiven. Scoped to this + // coverage figure deliberately — both still belong to the scoring surface for + // every other check. + const exemptFromGovernanceMetadata = + inventory.canonicalGovernanceFiles.filter( + (file) => isPatternDocPath(file.relativePath) || file.importsRootMirror, + ); + // If every governance file is exempt there is nothing left to measure, and an + // empty denominator must not read as 0% — that would fail a repo for having + // only the document kinds we just decided not to ask. Fall back to the full + // set, which is exactly the pre-exemption behaviour. + const datedCandidates = + exemptFromGovernanceMetadata.length === governanceCount + ? inventory.canonicalGovernanceFiles + : inventory.canonicalGovernanceFiles.filter( + (file) => !exemptFromGovernanceMetadata.includes(file), + ); + const datedExempt = governanceCount - datedCandidates.length; const datedCoverage = - governanceCount === 0 + datedCandidates.length === 0 ? 0 - : inventory.canonicalGovernanceFiles.filter((f) => f.hasLastValidated) - .length / governanceCount; + : datedCandidates.filter((f) => f.hasLastValidated).length / + datedCandidates.length; const checks: StageCheck[] = []; @@ -1655,7 +1675,13 @@ export function assessStageA( label: "Validation Date Coverage", status: datedCoverage < 0.3 ? "fail" : datedCoverage < 0.7 ? "warn" : "pass", - detail: `${Math.round(datedCoverage * 100)}% of governance files include Last validated`, + // Name the exemptions, so a coverage figure that rose is auditable rather + // than mysterious. + detail: + `${Math.round(datedCoverage * 100)}% of governance files include Last validated` + + (datedExempt > 0 + ? ` (excludes ${datedExempt} reference/pointer doc${datedExempt === 1 ? "" : "s"})` + : ""), }); checks.push({ diff --git a/scripts/governance-metadata-scoping.test.ts b/scripts/governance-metadata-scoping.test.ts new file mode 100644 index 0000000..7e23451 --- /dev/null +++ b/scripts/governance-metadata-scoping.test.ts @@ -0,0 +1,170 @@ +import { expect, test } from "bun:test"; + +import { + assessStageA, + type DriftSummary, + type RuleFile, + type RuleInventory, +} from "./audit.ts"; + +function makeRuleFile(overrides: Partial): RuleFile { + return { + path: `/repo/${overrides.relativePath ?? "AGENTS.md"}`, + relativePath: "AGENTS.md", + tool: "agents", + format: "markdown", + sizeLines: 120, + hasAlwaysApply: false, + hasGlob: false, + hasDescription: true, + hasLastValidated: false, + hasWhySection: true, + hasExamplesSection: true, + linesOverBudget: false, + authorship: "governance", + fingerprint: overrides.relativePath ?? "AGENTS.md", + loadTier: "always-on", + importsRootMirror: false, + ...overrides, + }; +} + +function inventoryOf(files: RuleFile[]): RuleInventory { + return { + allFiles: files, + canonicalFiles: files, + canonicalGovernanceFiles: files, + canonicalGeneratedFiles: [], + mirrorConfig: { hasConfig: false, agents: [] }, + mirrorGroups: [], + mirrorHealthyCount: 0, + mirrorDriftedCount: 0, + mirrorOrphanProjectionCount: 0, + mirrorSourceOnlyCount: 0, + duplicateGroups: [], + expectedDuplicateGroups: [], + accidentalDuplicateGroups: [], + duplicateMirrorCount: 0, + expectedDuplicateMirrorCount: 0, + accidentalDuplicateMirrorCount: 0, + duplicationRate: 0, + accidentalDuplicationRate: 0, + }; +} + +const NO_DRIFT: DriftSummary = { + pathIssues: 0, + dateIssues: 0, + notes: 0, +} as DriftSummary; + +function dateCheck(files: RuleFile[]) { + const stage = assessStageA(inventoryOf(files), NO_DRIFT); + return stage.checks.find((check) => check.id === "date-hygiene"); +} + +test("a reference catalog does not need governance metadata", () => { + // lc-classic-starter's shape: two governance docs, both dated, plus seven + // docs/patterns entries read on demand. It reported 22% and sat CRITICAL. + const files = [ + makeRuleFile({ relativePath: "AGENTS.md", hasLastValidated: true }), + makeRuleFile({ relativePath: "TOOLS.md", hasLastValidated: true }), + ...["a", "b", "c", "d", "e", "f", "README"].map((name) => + makeRuleFile({ + relativePath: `docs/patterns/${name}.md`, + hasLastValidated: false, + }), + ), + ]; + + const check = dateCheck(files); + + expect(check?.status).toBe("pass"); + expect(check?.detail).toContain("100%"); + // The exemption is stated, so a coverage figure that rose is auditable. + expect(check?.detail).toContain("excludes 7 reference/pointer docs"); +}); + +test("a pointer document does not need governance metadata", () => { + const files = [ + makeRuleFile({ relativePath: "AGENTS.md", hasLastValidated: true }), + makeRuleFile({ + relativePath: "CLAUDE.md", + hasLastValidated: false, + importsRootMirror: true, + sizeLines: 11, + }), + ]; + + const check = dateCheck(files); + + expect(check?.status).toBe("pass"); + expect(check?.detail).toContain("excludes 1 reference/pointer doc"); +}); + +test("real governance docs still have to carry a date", () => { + // The guard against exempting our way to green. forge's remaining two files + // are ordinary instruction docs, and it must stay failing. + const files = [ + makeRuleFile({ relativePath: "AGENTS.md", hasLastValidated: false }), + makeRuleFile({ + relativePath: ".devagent/plugins/ralph/AGENTS.md", + hasLastValidated: false, + }), + makeRuleFile({ + relativePath: "docs/patterns/auditable-autonomy.md", + hasLastValidated: false, + }), + ]; + + const check = dateCheck(files); + + expect(check?.status).toBe("fail"); + expect(check?.detail).toContain("0%"); +}); + +test("a repo with no exemptions reads exactly as before", () => { + const files = [ + makeRuleFile({ relativePath: "AGENTS.md", hasLastValidated: true }), + makeRuleFile({ relativePath: "CLAUDE.md", hasLastValidated: false }), + ]; + + const check = dateCheck(files); + + expect(check?.detail).toBe("50% of governance files include Last validated"); +}); + +test("a repo whose governance surface is entirely exempt is not failed at 0%", () => { + // The regression this nearly shipped with: exempting every file emptied the + // denominator, and an empty denominator read as 0% — failing Anvil itself, + // whose whole governance surface is bootstrap templates. With nothing left to + // measure, fall back to the full set rather than inventing a failure. + const files = ["a", "b", "c"].map((name) => + makeRuleFile({ + relativePath: `docs/patterns/${name}.md`, + hasLastValidated: true, + }), + ); + + const check = dateCheck(files); + + expect(check?.status).toBe("pass"); + expect(check?.detail).toBe("100% of governance files include Last validated"); +}); + +test("bootstrap templates are governance documents, not reference catalogs", () => { + // Deliberately NOT exempt: Anvil's own 18 templates are its governance + // surface and are all dated. Exempting them was scope creep that inverted + // Anvil's own verdict to CRITICAL. + const files = [ + makeRuleFile({ + relativePath: "docs/bootstrap-templates/ts-no-any.md", + hasLastValidated: false, + }), + makeRuleFile({ relativePath: "AGENTS.md", hasLastValidated: true }), + ]; + + const check = dateCheck(files); + + expect(check?.detail).toBe("50% of governance files include Last validated"); +}); From 740abe095c2fe9e4b81406254d9a3fa9136a20ef Mon Sep 17 00:00:00 2001 From: Jake Ruesink Date: Sun, 9 Aug 2026 11:10:46 -0500 Subject: [PATCH 2/2] chore: bump 0.1.0-alpha.13 Co-Authored-By: Claude Opus 5 (1M context) --- README.md | 8 ++++---- docs-site/public/llms-full.txt | 2 +- docs-site/src/content/docs/reference/cli.md | 2 +- docs/byok-trust-model.md | 2 +- docs/first-user-proof-packet.md | 6 +++--- docs/first-user-proof.md | 4 ++-- docs/getting-started.md | 6 +++--- docs/proofs/current-outside-tester-send-packet.md | 14 +++++++------- package.json | 2 +- 9 files changed, 23 insertions(+), 23 deletions(-) diff --git a/README.md b/README.md index c6e2602..b6f3100 100644 --- a/README.md +++ b/README.md @@ -106,7 +106,7 @@ Relative `--target` paths resolve from your current shell cwd. If you are alread Choose the lane that matches your setup before your first run. -If you are collecting the outside-user proof, stay on the exact pinned version and launcher from [First User Proof](docs/first-user-proof.md) instead of switching to the unpinned examples in this README. The current pinned `0.1.0-alpha.12` proof packet uses one repo-root `bunx` command with `--ci --output ./anvil-audit.md` so the saved report comes back from the first run. +If you are collecting the outside-user proof, stay on the exact pinned version and launcher from [First User Proof](docs/first-user-proof.md) instead of switching to the unpinned examples in this README. The current pinned `0.1.0-alpha.13` proof packet uses one repo-root `bunx` command with `--ci --output ./anvil-audit.md` so the saved report comes back from the first run. ### Local-only first pass (no provider required) @@ -151,7 +151,7 @@ bun run ./bin/anvil.ts --version Verified on the current alpha packet: - `--help` prints the four shipped entry commands: `audit`, `drift`, `bootstrap`, `mine-pr` -- `--version` prints `0.1.0-alpha.12` +- `--version` prints `0.1.0-alpha.13` Why you might choose this lane: @@ -173,10 +173,10 @@ For first-run setup and CI/lint guidance, see: Lambda Curry maintains this project with internal automation behind it, but that machinery is secondary to the public product path above. -- **Status:** Report as Decision Tool shipped; current charter follow-through is to collect outside-Lambda-Curry first-run proof on pinned `0.1.0-alpha.12` +- **Status:** Report as Decision Tool shipped; current charter follow-through is to collect outside-Lambda-Curry first-run proof on pinned `0.1.0-alpha.13` - **Verification posture:** CI artifact (audit report) + downstream observed impact in rule quality - **Current checked-in self-audit:** `docs/audits/anvil-audit-2026-08-08.md` reports `98/100` Structural Lint, `35/35` Guardrail Readiness, `0` issues, and `0` remediation tasks on current `main` -- **Current proof packet:** `docs/proofs/current-outside-tester-send-packet.md` keeps the external proof lane on one canonical repo-root command that saves `./anvil-audit.md`; the pinned packet stays on `@lambdacurry/anvil@0.1.0-alpha.12` +- **Current proof packet:** `docs/proofs/current-outside-tester-send-packet.md` keeps the external proof lane on one canonical repo-root command that saves `./anvil-audit.md`; the pinned packet stays on `@lambdacurry/anvil@0.1.0-alpha.13` Anvil is not primarily a UI project. Its real proof surface is whether downstream outputs and consumers reflect the intended rule behavior correctly. diff --git a/docs-site/public/llms-full.txt b/docs-site/public/llms-full.txt index 002f336..71d2fb4 100644 --- a/docs-site/public/llms-full.txt +++ b/docs-site/public/llms-full.txt @@ -745,7 +745,7 @@ anvil audit --target ./my-repo [options] Relative `--target` paths resolve from your current shell cwd. -If you arrived here from the external first-user proof docs, use the exact pinned command from that packet. The current `0.1.0-alpha.12` packet uses the public `--ci` spelling; `--no-ai` remains only as a deprecated compatibility alias. +If you arrived here from the external first-user proof docs, use the exact pinned command from that packet. The current `0.1.0-alpha.13` packet uses the public `--ci` spelling; `--no-ai` remains only as a deprecated compatibility alias. ## `anvil drift` diff --git a/docs-site/src/content/docs/reference/cli.md b/docs-site/src/content/docs/reference/cli.md index 7a2f4be..e9a333e 100644 --- a/docs-site/src/content/docs/reference/cli.md +++ b/docs-site/src/content/docs/reference/cli.md @@ -32,7 +32,7 @@ anvil audit --target ./my-repo [options] Relative `--target` paths resolve from your current shell cwd. -If you arrived here from the external first-user proof docs, use the exact pinned command from that packet. The current `0.1.0-alpha.12` packet uses the public `--ci` spelling; `--no-ai` remains only as a deprecated compatibility alias. +If you arrived here from the external first-user proof docs, use the exact pinned command from that packet. The current `0.1.0-alpha.13` packet uses the public `--ci` spelling; `--no-ai` remains only as a deprecated compatibility alias. ## `anvil drift` diff --git a/docs/byok-trust-model.md b/docs/byok-trust-model.md index 0f04e37..86b6a22 100644 --- a/docs/byok-trust-model.md +++ b/docs/byok-trust-model.md @@ -18,7 +18,7 @@ By default, Anvil scans your repo locally, then expects a working AI provider fo If you want the privacy-first path, run: -> **Current alpha note:** The published `0.1.0-alpha.12` proof packet uses one canonical repo-root `bunx` command with `--ci --output ./anvil-audit.md`. Packaged relative `--target` and `--output` paths still resolve from your shell cwd, so normal repo-relative first-run commands are honest when you use the unpinned command (it tracks the latest published build). +> **Current alpha note:** The published `0.1.0-alpha.13` proof packet uses one canonical repo-root `bunx` command with `--ci --output ./anvil-audit.md`. Packaged relative `--target` and `--output` paths still resolve from your shell cwd, so normal repo-relative first-run commands are honest when you use the unpinned command (it tracks the latest published build). ```bash # zero-install diff --git a/docs/first-user-proof-packet.md b/docs/first-user-proof-packet.md index 18f876f..6d6a4ef 100644 --- a/docs/first-user-proof-packet.md +++ b/docs/first-user-proof-packet.md @@ -20,7 +20,7 @@ Send back whether it worked first try, the first useful fix the report pointed t bunx @lambdacurry/anvil@ audit --target . --ci --output ./anvil-audit.md ``` -Replace `` with the specific published build you want validated. The current `0.1.0-alpha.12` proof packet sends only the repo-root saved-report command above so the artifact comes back from the same first run without asking the tester to choose between layouts. +Replace `` with the specific published build you want validated. The current `0.1.0-alpha.13` proof packet sends only the repo-root saved-report command above so the artifact comes back from the same first run without asking the tester to choose between layouts. Helpful docs: - Getting started: https://lambda-curry.github.io/anvil/getting-started/first-audit @@ -54,7 +54,7 @@ Before sending the note above, make sure: ## 3. Exact command blocks to send -Pick one install path and one shell layout, then send only that exact command so the tester is not choosing between multiple moving parts. For the current `0.1.0-alpha.12` packet, the canonical layout is Bun zero-install from the target repo root. +Pick one install path and one shell layout, then send only that exact command so the tester is not choosing between multiple moving parts. For the current `0.1.0-alpha.13` packet, the canonical layout is Bun zero-install from the target repo root. Replace `` before you send anything. Do not use the floating `@alpha` tag in the external proof packet. @@ -128,7 +128,7 @@ bun run verify:first-user-proof -- docs/proofs/YYYY-MM-DD--first-user-pr ``` The validator returns a deterministic `counts` / `does-not-count` result and names the missing proof fields or contract mismatches directly. -For the current pinned `0.1.0-alpha.12` proof lane, that includes checking that the retained audit command keeps the packet's `--ci` spelling. +For the current pinned `0.1.0-alpha.13` proof lane, that includes checking that the retained audit command keeps the packet's `--ci` spelling. When the packet keeps a local report artifact, it also requires `Saved report path or screenshot link` to match the retained audit command's `--output` path. Save one small packet with these fields: diff --git a/docs/first-user-proof.md b/docs/first-user-proof.md index 4ad362a..a786fd7 100644 --- a/docs/first-user-proof.md +++ b/docs/first-user-proof.md @@ -15,7 +15,7 @@ Capture one real outside-Lambda-Curry run that proves: Do this only after the exact published version you want to validate is live, and before Milestone 3 is called complete. -Do not send this packet with the floating `@alpha` tag. Replace `` in the command below with the specific published build you are validating, for example `0.1.0-alpha.12`. +Do not send this packet with the floating `@alpha` tag. Replace `` in the command below with the specific published build you are validating, for example `0.1.0-alpha.13`. ## Suggested tester profile @@ -115,7 +115,7 @@ bun run verify:first-user-proof -- docs/proofs/YYYY-MM-DD--first-user-pr ``` That validator checks the outside-tester status, pinned CLI version, first-try success, returned artifact, and other minimum packet fields, then returns `counts` or `does-not-count` with explicit reasons. -For the current pinned `0.1.0-alpha.12` proof lane, it requires the retained audit command to keep the exact `--ci` spelling from the packet. +For the current pinned `0.1.0-alpha.13` proof lane, it requires the retained audit command to keep the exact `--ci` spelling from the packet. ## Done signal for Milestone 3 gate diff --git a/docs/getting-started.md b/docs/getting-started.md index c838a9a..16be489 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -64,7 +64,7 @@ anvil --version What you should see in the current alpha: - `--help` lists the four shipped commands: `audit`, `drift`, `bootstrap`, `mine-pr` -- `--version` prints `0.1.0-alpha.12` +- `--version` prints `0.1.0-alpha.13` If you are validating Anvil from a cloned checkout instead of a global install, run: @@ -125,7 +125,7 @@ Top 5 improvements: ## Save the report to a file -> **Current alpha note:** The published `0.1.0-alpha.12` proof packet uses one canonical repo-root `bunx` command with `--ci --output ./anvil-audit.md`, while the packaged CLI still resolves relative `--target` and `--output` paths from your shell cwd on `bunx`, `npx`, and Bun global install. Normal relative-path examples are honest when you use the unpinned command (it tracks the latest published build). +> **Current alpha note:** The published `0.1.0-alpha.13` proof packet uses one canonical repo-root `bunx` command with `--ci --output ./anvil-audit.md`, while the packaged CLI still resolves relative `--target` and `--output` paths from your shell cwd on `bunx`, `npx`, and Bun global install. Normal relative-path examples are honest when you use the unpinned command (it tracks the latest published build). ```bash # zero-install with bunx @@ -235,7 +235,7 @@ anvil audit \ `--ci` keeps discovery, drift detection, coverage scoring, and markdown output local. The report headline becomes `Structural Lint Score`, and the improvement section is generated from repo-local heuristics instead of a provider. -`--no-ai` still works as a deprecated compatibility alias for the same mode. The current external first-user proof packet stays pinned to `0.1.0-alpha.12` and uses `--ci` for the local-only lane. +`--no-ai` still works as a deprecated compatibility alias for the same mode. The current external first-user proof packet stays pinned to `0.1.0-alpha.13` and uses `--ci` for the local-only lane. Privacy-first example artifact from the same example target: diff --git a/docs/proofs/current-outside-tester-send-packet.md b/docs/proofs/current-outside-tester-send-packet.md index 2b2b71c..c52a024 100644 --- a/docs/proofs/current-outside-tester-send-packet.md +++ b/docs/proofs/current-outside-tester-send-packet.md @@ -2,7 +2,7 @@ Use this packet to route one outside-Lambda-Curry tester through Anvil's remaining Milestone 3 proof lane. -This packet stays pinned to `@lambdacurry/anvil@0.1.0-alpha.12`. Do not swap the tester onto the floating `@alpha` tag. +This packet stays pinned to `@lambdacurry/anvil@0.1.0-alpha.13`. Do not swap the tester onto the floating `@alpha` tag. ## Three-line opener @@ -15,7 +15,7 @@ Send back whether it worked first try, the first useful fix the report pointed t ## Exact command to send ```bash -bunx @lambdacurry/anvil@0.1.0-alpha.12 audit --target . --ci --output ./anvil-audit.md +bunx @lambdacurry/anvil@0.1.0-alpha.13 audit --target . --ci --output ./anvil-audit.md ``` Send this as the only command. It assumes the tester is already in the target repo root, guarantees the saved report path, and keeps the local-only flag aligned with current public docs. @@ -27,7 +27,7 @@ Could you try one first-run Anvil audit on a real repo of yours? Paste the single command below from that repo's root; it saves `./anvil-audit.md`, stays local, and does not require an AI provider. ```bash -bunx @lambdacurry/anvil@0.1.0-alpha.12 audit --target . --ci --output ./anvil-audit.md +bunx @lambdacurry/anvil@0.1.0-alpha.13 audit --target . --ci --output ./anvil-audit.md ``` Helpful docs: @@ -39,7 +39,7 @@ What I'd love back: 1. Whether the exact command worked on the first try 2. If it did not, what failed first 3. If you changed the launcher or command, what you used instead - - If you switched to global `anvil`, keep both the pinned `bun add -g @lambdacurry/anvil@0.1.0-alpha.12` line and the `anvil audit ...` line together in `Exact command`. + - If you switched to global `anvil`, keep both the pinned `bun add -g @lambdacurry/anvil@0.1.0-alpha.13` line and the `anvil audit ...` line together in `Exact command`. 4. Whether you ran it from the repo root or somewhere else 5. The first useful fix the report pointed to, if any 6. Anything that felt confusing, too internal, or too hand-wavy @@ -47,7 +47,7 @@ What I'd love back: - If you send back the saved report path itself, keep `./anvil-audit.md`, the exact path the retained command wrote with `--output`. If you want one extra cross-check, this should print the same pinned version: -`bunx @lambdacurry/anvil@0.1.0-alpha.12 --version` +`bunx @lambdacurry/anvil@0.1.0-alpha.13 --version` If you changed launchers before the successful run, use the matching `--version` command from that same install path instead of mixing launchers in the saved packet. Do not append `anvil --version` to a `bunx` or `npx` proof packet. @@ -57,7 +57,7 @@ Count this as Milestone 3 proof only if all of these are true: - the tester is outside Lambda Curry - the tester completes a successful first run on a real repo -- the retained audit command keeps the pinned `0.1.0-alpha.12` local-only `--ci` spelling +- the retained audit command keeps the pinned `0.1.0-alpha.13` local-only `--ci` spelling - the exact command and returned artifact are retained in a saved proof packet - any rough edge found is captured as follow-up work @@ -79,7 +79,7 @@ bun run verify:first-user-proof -- docs/proofs/YYYY-MM-DD--first-user-pr ``` Run that verifier from an Anvil repo checkout or an unpacked published Anvil package root; the verifier now ships with the same proof-doc bundle. -It keys validation off the saved packet's `Pinned CLI version`, so this retained `0.1.0-alpha.12` packet can still be checked after current `main` advances to a later package version. +It keys validation off the saved packet's `Pinned CLI version`, so this retained `0.1.0-alpha.13` packet can still be checked after current `main` advances to a later package version. Historical note: the original dated retained packet for this same pinned proof lane remains at `docs/proofs/2026-05-23-alpha4-outside-tester-send-packet.md`. diff --git a/package.json b/package.json index 1cc6cc4..c322302 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@lambdacurry/anvil", - "version": "0.1.0-alpha.12", + "version": "0.1.0-alpha.13", "description": "AI rules + engineering guardrails audit engine for AI-assisted codebases", "keywords": [ "agents",