@warpgogol/forge 5.3.4 → 6.2.0

package/src/tests/implement-stamp.test.ts

@@ -429,6 +429,44 @@ describe("rfc.implement.stamp", () => {
     expect(result.data?.violations).toEqual([]);
   });
 
+  it("auto-selects the sole implement/feat-prefixed commit among multiple candidates", async () => {
+    const rfcFile = join(workspaceRoot, "docs", "rfcs", "rfc-0001-test-rfc.md");
+    await writeFile(rfcFile, RFC_BODY("RFC-0001", "accepted", true));
+    await commitAll(workspaceRoot, "docs: audit RFC-0001");
+    await writeFile(join(workspaceRoot, "src.txt"), "impl");
+    const implCommit = await commitAll(workspaceRoot, "implement: RFC-0001 — the change");
+    await writeFile(join(workspaceRoot, "src.txt"), "evidence");
+    await commitAll(workspaceRoot, "docs: RFC-0001 evidence sweep");
+
+    const result = await runRfcImplementStamp(
+      makeInputAutoDetect("RFC-0001"),
+      makeContext(workspaceRoot),
+    );
+
+    expect(result.exitCode).toBe(0);
+    expect(result.data?.status).toBe("pass");
+    expect(implCommit.startsWith(result.data?.data?.implementationCommit ?? "")).toBe(true);
+  });
+
+  it("still blocks with annotated candidates when several implement-prefixed commits exist", async () => {
+    const rfcFile = join(workspaceRoot, "docs", "rfcs", "rfc-0001-test-rfc.md");
+    await writeFile(rfcFile, RFC_BODY("RFC-0001", "accepted", true));
+    await commitAll(workspaceRoot, "implement: RFC-0001 step 1");
+    await writeFile(join(workspaceRoot, "src.txt"), "step 2");
+    await commitAll(workspaceRoot, "implement: RFC-0001 step 2");
+
+    const result = await runRfcImplementStamp(
+      makeInputAutoDetect("RFC-0001"),
+      makeContext(workspaceRoot),
+    );
+
+    expect(result.exitCode).toBe(1);
+    const imp03 = result.data?.violations.find((v) => v.rule === "RFC-IMP-03");
+    expect(imp03?.message).toContain("Multiple commits reference RFC-0001");
+    expect(imp03?.message).toContain("[implementation-shaped]");
+    expect(imp03?.message).toContain("Likely:");
+  });
+
   // ── RFC-0795: RFC-IMP-07 dependsOn dependency gate tests ──────────────────
 
   it("blocks stamping when a dependsOn RFC is not implemented (RFC-IMP-07)", async () => {

package/src/tests/session-handlers.test.ts

@@ -99,6 +99,39 @@ describe("session.save", () => {
     expect(data2.skipped[0]).toHaveProperty("reason", "already converted");
   });
 
+  test("ignores non-.atif files — claim intermediates and writer temp files are skipped", async () => {
+    const rawDir = join(dir, "docs/sessions/.raw");
+    await writeFile(join(rawDir, "orphan.atif.claim-999"), SAMPLE_ATIF, "utf-8");
+    await writeFile(join(rawDir, "half-written.atif.tmp"), SAMPLE_ATIF, "utf-8");
+
+    const result = await runSessionSave(makeInput(), makeContext(dir));
+    const data = result.data as SessionSaveResult & { skipped: Array<{ rawFile: string }> };
+
+    // Neither junk file was converted, claimed, or deleted.
+    const touched = data.skipped.map((s) => s.rawFile);
+    expect(touched).not.toContain("orphan.atif.claim-999");
+    expect(touched).not.toContain("half-written.atif.tmp");
+    const remaining = await readdir(rawDir);
+    expect(remaining).toContain("orphan.atif.claim-999");
+    expect(remaining).toContain("half-written.atif.tmp");
+  });
+
+  test("--keep-raw restores the original filename after the atomic claim", async () => {
+    const rawDir = join(dir, "docs/sessions/.raw");
+    const uniqueAtif = `2026-07-28T10:00:00+02:00
+User: keep-raw claim restore test.
+Assistant: Done.
+Commands: session.save`;
+    await writeFile(join(rawDir, "keepraw-claim.atif"), uniqueAtif, "utf-8");
+
+    const result = await runSessionSave(makeInput({ "keep-raw": true }), makeContext(dir));
+    expect(result.data.id).not.toBe("");
+
+    const remaining = await readdir(rawDir);
+    expect(remaining).toContain("keepraw-claim.atif");
+    expect(remaining.filter((n) => n.startsWith("keepraw-claim.atif.claim-"))).toHaveLength(0);
+  });
+
   test("deletes raw file on skip when --keep-raw is not set (idempotency cleanup)", async () => {
     const uniqueAtif = `2026-07-27T09:15:00+02:00
 User: Fix the session.save idempotency bug in save.ts.

package/src/types.ts

@@ -17,6 +17,12 @@ Mechanical v1 to v2 header migration across the workspace: 942 files rewritten
 
 Sweep batch 4: 73 Compass headers on headerless engine files (certification, component-runtime, isolation, evolution, testing), real KEY_DECISIONS on 75 files (kernel, cache, dht, swim, gitmesh, runtime), ~80 purpose expansions (CONTRACT-02/PURPOSE-02), non-goals on 13 CONTRACT-03 files, CS-07 history literal fix repo-wide (253 files). Policy: .template.ts/.template.astro excludedPaths. werkstatt-engine now 0 diagnostics.</item>
   <item>RFC-1147: ForgeRegisteredCommandInfo.provider narrowed to "workspace" and siteName field removed — forge never enumerated sites; mirrors the KernelRegisteredCommandInfo cleanup.</item>
+  <item>RFC-1231: step 1 — rename supportsAllSites to acceptsAllFlag
+
+Mechanical sweep: the field only ever gated --all argv acceptance; fan-out
+follows the parsed selector. Guard renamed assertAllSitesAllowed ->
+assertAllFlagAccepted, message updated. 417 declaration sites + type
+surfaces (KernelCommandMetadata, ForgeCommandMetadata) in one atomic pass.</item>
 </CHANGE_SUMMARY>
 */
 
@@ -185,7 +191,7 @@ export interface ForgeCommandMetadata {
    */
   modulePath?: string;
   requiresNetwork?: boolean;
-  supportsAllSites?: boolean;
+  acceptsAllFlag?: boolean;
   /** RFC-0963: validation contract this command belongs to (e.g. "content", "seo"). */
   contract?: string;
   /** RFC-0963: rule IDs this validator can emit. Empty for non-emitting validators. */
@@ -200,6 +206,12 @@ export interface ForgeCommandMetadata {
    * with GateMetadata from @warpgogol/site-kernel. Does NOT affect execution.
    */
   gate?: GateMetadata;
+  /**
+   * RFC-1243: coverage declaration for commands with no mechanical invocation
+   * record. Structurally mirrors KernelCommandMetadata.
+   */
+  coverage?: "operator" | "ci" | "delegated";
+  coverageNote?: string;
 }
 
 // ---------------------------------------------------------------------------

package/src/utils/generated-marker.ts

@@ -7,10 +7,14 @@ source (dependency inversion).</purpose>
   <item>Do not perform file I/O — operates on in-memory content strings only.</item>
 </non-goals>
 </MODULE_CONTRACT>
+<KEY_DECISIONS>
+  <item>RFC-1237: generatedHeaderFields emits marker data as leading YAML keys (not comment lines) so the emit-canonical envelope header survives yamlParse round-trips — comment headers could not express ownerCommand/regenerateCommand in parsed form.</item>
+</KEY_DECISIONS>
 <CHANGE_SUMMARY>
   <item>Moved from @warpgogol/site-kernel/generated-marker to forge as canonical source.</item>
   <item>Added optional commandPrefix to GeneratedHeaderInput — defaults to "forge" for autonomous mode; site-kernel passes "pnpm exec werkstatt run".</item>
   <item>Added editable flag to GeneratedHeaderInput — when true, emits a permissive marker and advisory that encourages agents to edit the file. AGENTS.md files use editable: true; other generated files keep the restrictive marker.</item>
+  <item>RFC-1237: added generatedHeaderFields — structured marker keys for generated YAML files (generatedMarker/doNotEdit/ownerCommand/editInstead/regenerateCommand), the emit-canonical envelope header format.</item>
 </CHANGE_SUMMARY>
 */
 
@@ -166,6 +170,30 @@ export function commentStyleForPath(filePath: string): GeneratedHeaderCommentSty
   return "line-slash";
 }
 
+/**
+ * RFC-1237: structured marker fields for generated YAML files — the key-format
+ * counterpart of buildGeneratedHeader's comment rendering. Generators whose
+ * output is YAML prepend these as leading top-level keys; consumers strip them
+ * (e.g. loadInternalManifest drops generatedMarker/doNotEdit/ownerCommand/
+ * editInstead/regenerateCommand before parsing the payload).
+ */
+export function generatedHeaderFields(
+  input: Pick<GeneratedHeaderInput, "ownerCommand" | "commandPrefix" | "site" | "editable">,
+): Record<string, string> {
+  const prefix = input.commandPrefix ?? "forge";
+  const editable = input.editable ?? false;
+  const regenerateCommand = input.site
+    ? `${prefix} ${input.ownerCommand} --site ${input.site}`
+    : `${prefix} ${input.ownerCommand}`;
+  return {
+    generatedMarker: editable ? EDITABLE_GENERATED_MARKER : GENERATED_MARKER,
+    doNotEdit: editable ? SAFE_TO_EDIT_LINE : DO_NOT_EDIT_LINE,
+    ownerCommand: input.ownerCommand,
+    editInstead: `the ${input.ownerCommand} generator source (not this file).`,
+    regenerateCommand,
+  };
+}
+
 export function buildGeneratedHeader(input: GeneratedHeaderInput): string {
   const style = commentStyleForPath(input.filePath);
   const prefix = input.commandPrefix ?? "forge";

package/src/validators/skill-validate.ts

@@ -6,9 +6,6 @@
 </non-goals>
 </MODULE_CONTRACT>
 <CHANGE_SUMMARY>
-  <item>RFC-1225: forgeRoot resolves via resolveForgeRoot (monorepo or npm-installed package); unresolvable root returns a single SKILL-00; pack discovery loads forge.yaml from workspaceRoot.</item>
-  <item>RFC-1227: SKILL-17 exempts HTML comment regions (file metadata written by the platform's own changelog tooling); pack-skill loop drops SKILL-17 (RFC-0553 scoped it to shipped canonical skills only).</item>
-  <item>RFC-0642: added SKILL-18 — forge skill instruction lines must not reference software-specific binding keys (typecheck, scopedBuild, test); use semantic keys (validate, produce, verify) instead.</item>
   <item>RFC-0660: added SKILL-19 (knowledge entry schema validity) and SKILL-20 (entry identifier uniqueness) for structured knowledge files.</item>
   <item>RFC-0661: added SKILL-21 (knowledge layer token budget warnings), refactored warning handling — warnings go to separate `warnings` array, not `violations`.</item>
   <item>RFC-1097: step 6 — compass.migrate codemod run
@@ -17,7 +14,8 @@ Mechanical v1 to v2 header migration across the workspace: 942 files rewritten
   <item>RFC-1097: sweep — packages/forge + services clean
 
 Sweep batch 2: real KEY_DECISIONS on 10 files, expanded purposes (CONTRACT-02/PURPOSE-02), headers on mission/index + gen-upstreams, sanitizeItemText in summary.record (literal Compass tags corrupted history), excludedPaths for wrangler types, test-fixtures testPattern. forge+services now 0 diagnostics under --mode error.</item>
-  <history>RFC-0374, RFC-0393, RFC-0523, RFC-0524, RFC-0539, RFC-0548, RFC-0553</history>
+  <item>RFC-1249: wire werkstatt.commands.validate into packages.check + retire CMD-OUTPUT debt</item>
+  <history>RFC-0374, RFC-0393, RFC-0523, RFC-0524, RFC-0539, RFC-0548, RFC-0553, RFC-0642, RFC-1225, RFC-1227, SKILL-00, SKILL-17</history>
 </CHANGE_SUMMARY>
 */
 

package/skills/fo/fo-idea-implement/ADR-FLOW.md

@@ -1,179 +0,0 @@
-# ADR Implementation Flow
-
-Execute this flow when the document is an ADR (prefix `ADR-`, or file in `docs/adrs/`).
-
-## 4.1. Read the ADR
-
-Read the ADR file. Extract:
-
-- **Status** — must be `accepted`, `reviewing`, or `proposed`. If `superseded` or `rejected` (terminal), stop with message: `ADR-XXXX is <status> (terminal). Terminal ADRs cannot be implemented. To change this decision, create a new ADR or RFC that supersedes ADR-XXXX.` If `implemented`, stop with message: `ADR-XXXX is already implemented. Nothing to do.`
-- **Decision** — the core decision from the `## Decision` section.
-- **Context** — the local situation and constraints from `## Context`.
-- **Consequences** — what the decision implies for the codebase.
-- **Related** — any RFCs, ADRs, or DNA invariants referenced.
-
-## 4.2. Transition to accepted (if needed)
-
-If the ADR is `proposed` or `reviewing`, transition it to `accepted`:
-
-1. Set `status: accepted` in the frontmatter.
-2. Set `updatedAt: <today's date>`.
-3. If `reviewers` is empty, read the default reviewer(s) from the `reviewers` field comment in `docs/adrs/adr-0000-template.md`. Set all listed default reviewers.
-4. Commit:
-
-   ```txt
-   adr: accept ADR-XXXX <short title>
-
-   Transition ADR-XXXX to accepted status for implementation.
-   ```
-
-   Stage only the ADR file.
-
-If the ADR is already `accepted`, proceed directly.
-
-## 4.3. Implement the decision
-
-Read the `## Decision` section and implement it in code. Follow the same principles as RFC implementation:
-
-- Make autonomous, ecosystem-aligned decisions.
-- Use `edit`/`multi_edit` for changes to existing files, `write_to_file` for new files.
-- Commit each logical phase of work:
-
-  ```txt
-  implement: ADR-XXXX — <phase description>
-
-  <one-line description of what was done in this phase>.
-  ```
-
-  Stage only the files touched by this phase — see `_shared/fo-pipeline-conventions.md` §Commit discipline.
-
-- Recoverable errors: see `_shared/fo-pipeline-conventions.md` §Recoverable errors.
-
-## 4.4. Run scoped build checks
-
-After implementation is complete, run heavy checks for the impacted workspaces only:
-
-1. ADR validation:
-
-   ```sh
-   ref(forge.yaml bindings.commands.validateAdr)
-   ```
-
-2. Determine impacted packages/apps from the ADR's `scope` and the files touched during implementation. Build only those workspaces:
-
-   ```sh
-   pnpm --filter @gogol/<package> run build:check
-   ```
-
-   Or for apps:
-
-   ```sh
-   pnpm --filter <app-name> run build:check
-   ```
-
-   See `_shared/fo-pipeline-conventions.md` §Build verification discipline.
-
-## 4.5. Fix errors
-
-If any check fails, fix every error:
-
-1. Read the error output.
-2. Identify the root cause.
-3. Fix it.
-4. Re-run the failing check to confirm the fix.
-5. Commit each fix:
-
-   ```txt
-   fix: ADR-XXXX — <error description>
-
-   <one-line description of the root cause and fix>.
-   ```
-
-Continue until all impacted checks pass.
-
-## 4.6. Documentation audit (fo-doc-audit)
-
-After implementation is complete and all checks pass, invoke `fo-doc-audit` via the `skill` tool. It analyzes the session's changes, checks all documentation surfaces, applies needed updates, and commits them separately. Wait for it to complete.
-
-If `fo-doc-audit` reports that no updates are needed, proceed to the next step.
-
-## 4.7. ADR code-trace
-
-Before stamping `implemented`, verify that the ADR is mentioned in the codebase — this leaves a trace linking code back to the decision record, just as RFCs leave traces.
-
-1. **Search for the ADR id** — use `grep_search` to scan `apps/`, `packages/`, and `services/` for the ADR id string (e.g. `ADR-0003`). Check:
-   - **COMPASS block comments** — `MODULE_CONTRACT`, `CHANGE_SUMMARY`, or other Compass scaffolding comments that reference the ADR id.
-   - **Inline code mentions** — comments, docstrings, or annotations in source files that reference the ADR id.
-
-2. **If mentions are found** — the trace exists. Proceed to step 4.8.
-
-3. **If no mentions are found** — attempt to find the most relevant file(s) where the decision was implemented. If the file(s) can be identified:
-   - Add a Compass block comment referencing the ADR id to the file's `MODULE_CONTRACT` or `CHANGE_SUMMARY` section. For example: `<item>ADR-0003: <brief note on what this ADR decided for this module.</item>`
-   - If the file has no Compass scaffolding, add a brief inline comment at the top of the file: `// Implements ADR-XXXX: <one-line decision summary>`
-   - Commit the trace:
-
-     ```txt
-     trace: ADR-XXXX — add code mention
-
-     Add ADR-XXXX reference to <file> to link the decision to the code.
-     ```
-
-   - Proceed to step 4.8.
-
-4. **If the relevant file(s) cannot be identified** — ask the operator: `ADR-XXXX was implemented but no code mention was found. Please point to the file(s) where this ADR's decision was applied so I can add a trace reference.` After the operator provides the file(s), add the trace as described in step 3, commit, and proceed.
-
-**For already-implemented ADRs** (if this step is reached for an ADR that was already `implemented`): this check is informational — attempt to find the trace and add it if missing, but do not block on it.
-
-## 4.8. Stamp implemented
-
-After all checks pass and documentation is updated, transition the ADR to `implemented`:
-
-1. Set `status: implemented` in the frontmatter.
-2. Set `implementedAt: <today's date>`.
-3. Set `updatedAt: <today's date>`.
-4. Commit:
-
-   ```txt
-   adr: implement ADR-XXXX <short title>
-
-   Transition ADR-XXXX to implemented status. Decision is live in code,
-   scoped build passes.
-   ```
-
-   Stage only the ADR file.
-
-## 4.9. Review (fo-review) — MANDATORY GATE
-
-**This step is unconditional.** It MUST be executed after every implementation run — regardless of whether build checks passed, failed, or were fixed. No exceptions. The ADR report (step 4.11) MUST NOT be emitted until this step is complete.
-
-1. **Determine the diff scope** — identify the git fixed point at the start of this implementation session (the commit before the first `implement:` or `adr:` commit). Capture the diff via `git diff <fixed-point>...HEAD`.
-2. **Invoke `fo-review`** — run the review skill inline via the `skill` tool, passing the diff scope. Wait for it to complete (mechanical floor, seven axes, spec compliance, persist report + commit). If the `skill` tool call fails, retry once. If it fails again, proceed to step 4.11 and note the failure in the report.
-3. **Read the review report** — extract the verdict and all findings.
-
-If the review verdict is **Approved** with zero findings, skip step 4.10 and proceed directly to step 4.11 (Report).
-
-## 4.10. Fix findings (fo-fix) — MANDATORY if findings exist
-
-If the review has ANY findings — this step MUST be executed — it is not optional. "Findings" means any issue noted under any review axis (A–G), regardless of severity label ("minor", "cosmetic", "advisory") or the review's overall verdict. An **approved** verdict with minor findings **still requires** `fo-fix` — do not skip because the verdict is "approved" or findings are "minor". The only case where this step is skipped is a review with **zero findings** (every axis says "No issues."):
-
-1. **Re-verify findings** — before fixing, quickly check whether each finding is still relevant: the flagged code may have been changed by a subsequent step. Discard stale findings.
-2. **Invoke `fo-fix`** — run the fix skill inline via the `skill` tool. It reads the persisted review report, applies fixes in priority order, runs scoped typecheck verification, commits, and delegates doc updates to `fo-doc-audit`. Wait for it to complete. If the `skill` tool call fails, retry once. If it fails again, proceed to step 4.11 and note the failure in the report.
-3. **Re-run scoped build checks** if `fo-fix` made code changes — repeat step 4.4 for any workspaces touched by the fixes.
-
-If the review verdict is **Approved** with zero findings, skip this step — no fix is needed.
-
-## 4.11. Report
-
-After implementation, review, and fix are complete, report:
-
-```
-## ADR-XXXX Implementation Summary
-
-### Decision: <one-line summary>
-### Phases implemented: <count>
-### Commits: <count>
-### Scoped build: <Pass | Fail — fixed>
-### Review: <verdict> — <N> findings
-### Fix: <done, <N> findings fixed | skipped, no findings>
-### Status: implemented (<date>)
-```

package/skills/fo/fo-review/AXES.md

@@ -1,70 +0,0 @@
-# Review Axes
-
-Load this file when running step 4 of `fo-review`. For each axis, check every item. An item either **passes**, **fails** (specific finding with evidence), or is **not applicable** (state why). Skip N/A items silently — do not pad the report.
-
-## Axis A — Structural correctness
-
-Beyond what the mechanical floor catches:
-
-- **Strict typing** — flag `any`, implicit casts, missing interfaces, untyped parameters, non-exhaustive switch/if chains.
-- **No magic numbers or untyped data** — flag literal constants that should be named, enums, or config; flag strings standing in for domain concepts.
-- **Minimalism** — flag over-engineered abstractions, speculative generality, duplicated logic, or middle-man modules that can be simplified.
-- **Dead code** — flag unreachable branches, unused exports, commented-out code blocks.
-- **Error handling** — flag swallowed errors, bare `catch` blocks without context, missing error types.
-
-## Axis B — DNA alignment
-
-Check the diff against every DNA invariant it touches. The list below is the minimum scan set — if the diff touches a DNA invariant not listed here, check it too.
-
-- **DNA-1** (monorepo boundary) — no `apps/* → apps/*` or `apps/* → services/*` imports.
-- **DNA-4** (canonical content) — no hardcoded copy strings or configuration in routes/components that belongs in `src/content/`.
-- **DNA-5 / DNA-17** (mirror quintet) — every new `.astro` component/section has colocated `manifest.yaml`, content schema, `.css`, and content `.md`.
-- **DNA-6** (kebab-case) — all new filenames use kebab-case.
-- **DNA-7** (thin routes) — route files are orchestrators only; no inline `<style>`, hardcoded body copy, or layout logic.
-- **DNA-8** (page → section → component → content) — visitor-facing page bodies are composed as ordered section components.
-- **DNA-10** (no hardcoded tokens) — CSS uses `--ds-*` custom properties only; no raw `rgba()` or `#hex`.
-- **DNA-23** (cosmic naming) — new manifests carry `cosmicName` from the correct closed catalog; three-way alignment (manifest ↔ `PLANET_IMPORT_PATHS` / `MOON_IMPORT_PATHS` ↔ `system.md`).
-- **DNA-24** (block-declarative pages) — page entries are frontmatter-only; no markdown bodies.
-- **DNA-25** (single buildPage) — routes call `buildPage`; no hand-assembled block composition.
-- **DNA-40** (env-example) — new env vars are documented in `.env.example`.
-- **DNA-42** (Compass markup) — new authored source files carry `MODULE_CONTRACT` and `CHANGE_SUMMARY`.
-- **DNA-51** (Werkstatt primitives) — mutating Werkstatt commands use shared lock/idempotency/atomic-write helpers.
-
-## Axis C — Ecosystem fit
-
-- **Package boundaries**: imports flow `apps/* → packages/*` and `services/* → packages/*`, never `apps/* → apps/*` or `apps/* → services/*`.
-- **Pipeline placement**: new checks are placed in the correct pipeline (`build.prepare`, `build.check`, `sites-check`, `sites-check-postbuild`) with justified blocking vs. advisory choice.
-- **Compass sync**: if the diff changes repository-wide requirements, shared package contracts, or app-package relationships, the relevant `docs/*.xml` files are updated.
-- **AGENTS.md updates**: if the diff introduces new rules or patterns, the relevant `AGENTS.md` files are updated.
-- **Cosmic naming**: if the diff touches manifests or component/section/page contracts, the three-way alignment is maintained.
-- **Command lifecycle**: new commands are registered in the correct module; changed commands update their metadata; removed commands are explicitly deprecated.
-
-## Axis D — Forward-only compliance
-
-- No compatibility shims, bridges, or dual-paths that keep legacy behavior alive.
-- Deprecation means removal in the same change, not an indefinite grace period.
-- Legacy code paths are deleted, not maintained behind a flag.
-- If the diff amends an existing contract, it changes the contract directly — no parallel interpretation.
-
-## Axis E — Agent-facing clarity
-
-- **Compass scaffolding**: new non-trivial source files carry `MODULE_CONTRACT` and `CHANGE_SUMMARY`; high-risk files carry `@ai-invariant` lines.
-- **No ungrounded assertions**: code comments and docstrings reference real functions, types, and files — no invented APIs or phantom parameters.
-- **Readable by another agent**: variable names reveal what they hold; function names reveal what they do; no mysterious names.
-- **Log-driven development**: logs carry enough context for debugging; no bare `console.log` without context or structure. Prefer the repo's shared logging contracts when they exist.
-- **Anti-fabrication**: if the diff includes content claims (prose, business records), the code distinguishes between generated content and human-authored content.
-
-## Axis F — Pragmatism
-
-- **Minimal command surface**: each new command earns its existence — no command that could be a flag on an existing command.
-- **Lean contracts**: TypeScript types are the minimum needed — no speculative generality, no unused optional fields.
-- **Existing patterns**: the diff checks whether an existing command, schema, or pattern can be extended before introducing a new one.
-- **Scope discipline**: the diff touches only what's necessary; no scope creep into unrelated areas.
-
-## Axis G — Blind spots
-
-- **Performance**: new build-time commands specify their cost (file scan count, regex complexity, I/O patterns).
-- **False positives**: new validators estimate their false-positive rate and describe suppression during migration.
-- **Edge cases**: the diff considers empty states (new app with no content), concurrent execution, and interrupted operations.
-- **Migration path**: existing apps' path to compliance is documented.
-- **Security / privacy**: if the diff touches user data, PII, or external services, it addresses GDPR/privacy and secret management. No cookies (`document.cookie`, `Set-Cookie`). Client-side persistence is `localStorage` only; server-side is `unstorage`.