chore(format): normalize repository Prettier baseline

[flyingrobots]

Context

pnpm format:check reports 81 tracked files that Prettier would rewrite on origin/main. None of those paths were changed by #766; this is repository-baseline formatting debt discovered while auditing that PR.

The root script is intentionally repository-wide (prettier --check .), so the debt belongs in a separate follow-up rather than the governance behavior change.

Refs #742.

Scope

• Run pinned Prettier 3.9.5 over the repository-owned formatting surface.
• Keep ordinary source, documentation, schemas, and fixtures formatting-only.
• Preserve compiler-emitted golden artifacts byte-for-byte and declare their exact ownership boundary in .prettierignore and formatter documentation.
• Verify the complete repository after the rewrite.

Audit finding

The initial formatter-only pass exposed seven files whose bytes are executable evidence rather than ordinary JSON/Markdown:

• test/fixtures/extension-generation/*.json participates in canonical serialization and digest tests.
• test/fixtures/weslaw/diff/ci-semantic-diff.{json,md} must equal emitted CLI output byte-for-byte.

Those files remain unchanged and are excluded from Prettier. Changing the emitters merely to match Prettier would alter canonical product output and is outside this maintenance slice.

Acceptance criteria

• pnpm format:check passes from a clean checkout.
• pnpm run preflight passes.
• pnpm lint and pnpm test pass.
• git diff --check passes.
• Golden fixture tests remain byte-for-byte green.
• Review confirms the remaining patch contains deterministic Prettier rewrites plus the explicit formatter-ownership boundary.

[coderabbitai]

🔗 Related PRs

#610 - Add runtime-neutral Continuum Edict packet [merged]
#655 - chore(release): prepare v0.2.0 [merged]
#720 - fix: run pre-push checks without shell strings [merged]
#731 - Publish extension generation provenance contract [merged]
#741 - Add IR-to-Brainfuck extension generator example [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!