chore(release): bump workspace version to 0.12.0

[cscheid]

Prepares the v0.12.0 release (bd-ak4cnm44), per
claude-notes/instructions/release-runbook.md step 2.

The release workflow's preflight job fails unless the git tag exactly
equals [workspace.package].version, so the manifest is bumped before
v0.12.0 is tagged.

What's in the release

Scope is main as-is — no open PRs pulled in. Commits since v0.11.0:

• 0087da18 One glob semantics for q2: migrate every consumer onto the shared API (One glob semantics for q2: migrate every consumer onto the shared API #461)
• acf7ecac ci(release): assert linux binaries run with no glibc (bd-3b47pxmm) (ci(release): assert linux binaries run with no glibc (bd-3b47pxmm) #458)
• f12baae7 Listing contents: globs resolve against their declaring file's directory (Listing contents: globs resolve against their declaring file's directory #460)
• d3f3a60e Add minimal AGENTS.md
• 4d91cafe fix(preview): ephemeral hub secrets; no spurious persist warning (bd-tp1l6a0w) (fix(preview): ephemeral hub secrets; no spurious persist warning (bd-tp1l6a0w) #462)
• c9f6177f Listing diagnostics blame the wrong key: fix materialized container spans (bd-9yh3pzfu, bd-2mxo) (Listing diagnostics blame the wrong key: fix materialized container spans (bd-9yh3pzfu, bd-2mxo) #459)

Changes here

Cargo.toml [workspace.package].version 0.11.0 → 0.12.0, plus the
cargo update --workspace lockfile rewrite. Diffing Cargo.lock for
version lines that are neither 0.11.0 nor 0.12.0 returns nothing, so
no external dependency moved — only workspace members.

Verification

• cargo build --bin q2 --locked succeeds and prints q2 (quarto 2) 0.12.0.
  The --locked build is the real gate: CI builds --locked, so the
  lockfile had to already be in sync.
• cargo xtask verify --skip-hub-build: custom lints, clippy (-D warnings),
  and rustfmt all clean.
• cargo nextest run --workspace --no-fail-fast: 10997 passed, 0 failed,
  197 skipped.

One caveat worth recording: the first verify run hit a single failure in
quarto-hub::integration admin_collect_lifecycle::collect_reverification_skips_rereferenced_candidate,
asserting 3qAsj6GjtESfaUtgqp4UoUVG9GJN vs 3QAsj6GjtESfaUtgqp4UoUVG9GJN.
That is the known macOS-APFS case-insensitivity flake tracked in
bd-eb2wnxkp (doc ids that differ only in case collide in the 2-level
store layout) — not a version-bump regression. It passed on re-run and the
full no-fail-fast suite above is green. CI's Linux runners have
case-sensitive filesystems and do not hit it.

🤖 Generated with Claude Code

[posit-snyk-bot]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.