v0.3.1

v0.3.1 — republish v0.3.0 substance with LEVEL_TRACE fix on crates.io

PATCH RELEASE. Identical substance to v0.3.0 (Wave 1-3 LSP-parity +
all pre-v0.3.0 work) plus the critical shape-runtime LEVEL_TRACE
export-time fix that was present in HEAD at v0.3.0 tag time but never
reached crates.io due to a partial-publish lockout (see
docs/cluster-audits or commit cb8bd924 for the full root-cause).

Why this exists: shape-runtime v0.3.0 on crates.io is BUGGY (pre-fix);
crates.io rejects same-version republishing. v0.3.1 is the consumable
0.3.x release.

Action items for consumers:
- Bump shape-* deps from =0.3.0 to =0.3.1.
- shape-runtime v0.3.0 should be yanked on crates.io (UI:
  crates.io/crates/shape-runtime/0.3.0 → Settings → Yank). Cargo
  yank via CLI requires a token with yank scope.

All other v0.3.0 crates (shape-macros, shape-gc, shape-abi-v1,
shape-ast, shape-value, shape-wire, shape-diagnostics, shape-vm,
shape-jit, shape-viz-core, shape-lsp, shape-cli, shape-ext-python,
shape-ext-typescript) are equivalent at v0.3.0 and v0.3.1 — the fix
was scoped to shape-runtime. They are bumped together for
clean-lockstep semantics.

Gates at tag-time:
- smoke s1-s5 5/5 VM == JIT (canonical (ii) F' release-binary harness)
- verify-merge.sh 13/13 PASSED
- check-no-dynamic.sh exit 0
- check-clean exit 0
- `use std::core::log` loads cleanly (LEVEL_TRACE regression check)

Skill captured at ~/.claude/skills/shape-release/SKILL.md to prevent
recurrence of the partial-publish / no-republish lockout.