chore(release): v0.38.0

[avrabe]

Release bump for v0.38.0, following #424 (merged).

Scope

The field-plane guardrail, generalised to status (#375).

tools/check_release_plane.py hardcoded FIELD = "release", so a status: written into an artifact's fields: bag was valid YAML, tolerated by the schema, and invisible to status-allowed-values and to every lifecycle query — the #370 release: defect one field over. #371 had already measured six live cases in safety/stpa/architecture.yaml and named them as open hole (1) of REQ-GUARD-STATUS-VOCAB-001.

v0.38.0 generalises the constant to FIELDS = ("release", "status"), reported per plane, and moves the six from fields.status: planned to a top-level status: proposed (documented planned -> proposed mapping). A status-plane-violation fixture pins nested=1/visible=1, and dropping status from FIELDS reds the self-test.

What this PR changes

Version bump only — the feature landed in #424:

• Cargo.toml [workspace.package] version 0.37.0 → 0.38.0
• Cargo.lock — 23 workspace crates re-locked to 0.38.0 (cargo update --workspace, no other dependency churn)
• vscode-spar/package.json version 0.37.0 → 0.38.0
• REQ-GUARD-STATUS-PLANE-001 promoted implemented → verified (release v0.38.0), its V closed by TEST-GUARD-STATUS-PLANE

Hole (2) of REQ-GUARD-STATUS-VOCAB-001 — safety/requirements.yaml's 21 off-plane statuses in a file rivet never loads — remains open for a maintainer sources: decision.

🤖 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]

Merged — v0.38.0 is STAGED on main (1f1a19f). The one remaining step, pushing the signed v0.38.0 tag to fire release.yml, is blocked for this automated session: git push origin v0.38.0 returns HTTP 403 because refs/tags/v* are protected (maintainer-only). The tag is created and validly SSH-signed locally but cannot be pushed from here; I did not force or fake it.

To ship, please run locally:

git fetch origin main && git checkout main && git pull --ff-only
git tag -s v0.38.0 -m 'v0.38.0' && git tag -v v0.38.0 && git push origin v0.38.0

Full detail + rationale on the issue: #375 (comment above).

---

Generated by Claude Code