chore(release): v0.37.0

[avrabe]

Release bump for v0.37.0.

Bumps [workspace.package] version 0.36.0 → 0.37.0 (with Cargo.lock and vscode-spar/package.json) and promotes REQ-GUARD-CONTEXT-TIMEOUT-001 to verified.

Ships the required-context timeout guardrail from #398, merged in #411 (df4a64f):

• tools/check_job_timeouts.py — every gateable (required) job must declare a static timeout-minutes in (0, 360), reusing check_required_contexts.py's cross-checked workflow reader.
• timeout-minutes on the 15 previously-unbounded required jobs, sized from run history.

No code changes beyond the version strings; the feature itself already landed and went green on main.

🤖 Generated with Claude Code

---

Generated by Claude Code

[github-actions]

Rivet verification gate

✅ 20/20 passed

	count
Passed	20
Failed	0
Skipped (no steps)	0

Filter: (and (= type "feature") (or (has-tag "v093") (has-tag "v0100")))

Failed artifacts

(none)

_{Updated automatically by tools/post_verification_comment.py. Source of truth: artifacts/verification.yaml.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[avrabe]

🤖 Autonomous run — overlap guard + stranded-release handoff

This release-bump PR (from a prior autonomous run) has been open since 2026-08-08 and is now stranded. Flagging because it needs a maintainer decision — I did not touch the branch.

Current state

• mergeable_state: behind — main has advanced 5 commits since this bump (merged: feat(guard): an artifact claiming evidence must carry a runnable step (#403) #413 which lands Verification Gate is green having executed zero commands: run_verification.py counts 'skipped' as pass #403's evidence-step guard feature, and fix(ci): the tag-point gate must fetch the tag OBJECT, not judge the ref #415 CI fixes). main is still at 0.36.0; no v0.37.0 tag exists yet.
• The three workflows that ran on the head SHA (CI, Lean Proofs, Verification Gate) were all success on 08-08, but branch protection requires an up-to-date branch, so "behind" blocks the squash-merge.

Why I'm not auto-advancing it

• Simply updating the branch would restart the full ~2h required-check set, and it would silently fold Verification Gate is green having executed zero commands: run_verification.py counts 'skipped' as pass #403's guard feature + fix(ci): the tag-point gate must fetch the tag OBJECT, not judge the ref #415 into v0.37.0. That contradicts this PR's stated scope ("No code changes beyond the version strings") and would ship Verification Gate is green having executed zero commands: run_verification.py counts 'skipped' as pass #403 without promoting its REQ — an artifact/release-notes inconsistency I shouldn't resolve by guessing.

Decision needed (maintainer) — pick one:

1. Re-scope this PR: merge main in, then update the body + promote Verification Gate is green having executed zero commands: run_verification.py counts 'skipped' as pass #403's REQ to verified (release v0.37.0) so the release notes match what actually ships; then merge + cut the signed tag.
2. Re-cut fresh: close this PR and open a new release/vX.Y.0 from current main covering both 15 of 18 required contexts declare no timeout-minutes — a hung merge gate is a 6-hour blind wait #398 (timeout guard) and Verification Gate is green having executed zero commands: run_verification.py counts 'skipped' as pass #403 (evidence-step guard).

Either way the tag itself needs to be cut locally with your signing key (git tag -s vX.Y.0 && git push origin vX.Y.0) — the autonomous env has no signing key.

Exiting this run per the overlap guard (open PR present → no new work).

---

Generated by Claude Code