🔖 Release 0.12.0

[taras]

Why

#762 merged as 14c23076. It adds a capability rather than fixing one, so the
next release is a minor: 0.11.0 → 0.12.0.

What changes

Before: every workspace manifest reads 0.11.0, and the site badge reads
v0.11.0.

After: all twenty manifests read 0.12.0, and the badge matches.

Nothing else. No source, spec, or site copy is touched.

Scope

Included

• The twenty deno.json / package.json version fields, stamped by
  deno task bump 0.12.0.
• site/routes/index.tsx's VERSION constant, the one place the site states it.

Intentionally unchanged

• No site copy. The homepage says nothing about the release's contents, and this
  PR does not change that.
• No changeset, per repository convention.
• Publishing itself. The draft release is published as v0.12.0 after this
  merges, per specs/release-process-spec.md §2.

Generated or mechanical changes

• Every manifest change is deno task bump 0.12.0 output — one field per file,
  no hand edits.

How to verify it

deno task lint
deno task check
cd site && deno task check
deno task test scripts/tests/bump-version.test.ts scripts/tests/workspace.test.ts

• bump-version.test.ts and workspace.test.ts pass (2 passed, 9 steps), so
  every workspace member was found and stamped rather than a subset.
• grep for 0.11.0 across the manifests returns nothing.

Scope confirmation

• Every changed file supports the purpose described above.
• Unrelated cleanup and formatting changes are excluded.
• Generated or mechanical changes are clearly identified.
• The description matches the final diff and test results.

[github-actions]

PR #793: 🔖 Release 0.12.0

21 files, +21 / -21

Scope

🟡 21 files changed. Are all changes related?

🟡 Changes span 11 directories.

🟡 PR mixes config and source changes.

🟡 package.json changed without dependency justification.

Structural

✅ No structural bloat detected.

Slop

✅ Slop indicators look low.

Static Analysis

✅ Oxlint found no issues.

Correctness

No extraneous code patterns detected.