chore(release): 0.3.11 — the first baseline is the one check reads

[KayhanB21]

Release PR for 0.3.11. It carries #72 (init --with-baseline scores from the coverage that check reads, and exits 2 when pytest can't start) and #74 (a malformed coverage_map shard is exit 2, a map prefix can start with a dot, and a TypeScript report that matches 0 scanned files says so).

Changes

• The version moves to 0.3.11 in pyproject.toml, uv.lock, init.py ACTION_REF, and tests/test_release_integrity.py.
• The README updates its four v0.3.11 pins and the package version in the config show --json table.
• The CHANGELOG adds four Fixed entries and one Changed entry under [0.3.11] - 2026-10-10.

The release has no Breaking heading. The Changed entry is the malformed shard: a gate that passes with a corrupt shard, which needs missing_coverage = "optimistic" or "skip", starts failing with exit 2. This repository uses one coverage file, so its own scores don't move. The scoring model version and all nine JSON schemas are unchanged. action.yml didn't change since v0.3.10, so the wrapper bump is a patch (v1.1.5).

Verification

• pytest: 1413 passed, 2 skipped (scipy absent), coverage 93.46%.
• ruff check, ruff format --check, mypy src tests, and pre-commit run --all-files pass.
• riskratchet check: no regressions, Baseline: 577 entries · 577 compared · 0 not seen this run.
• uv build produces riskratchet-0.3.11 wheel and sdist. The wheel holds 0 tests/ files, and the runtime requirements contain no tree-sitter or jsonschema.

Baseline bump rationale

None needed. This PR changes only version strings and docs, and it touches no scored function.

🤖 Generated with Claude Code