chore(release): v0.5.1 — first-contact polish#235
Merged
Conversation
Workspace, vscode-rivet, and npm root package versions bumped to 0.5.1. Platform packages stay on the release-npm.yml override path (per the 0.5.0 convention). What's in 0.5.1 (post-0.5.0 dogfood polish): - docs(quickstart): rewrite for fresh-user clarity (#230). Two clean-room dogfood passes + three scenario-based passes surfaced six confusion points; all fixed. Wall-time wins: STPA bring-up 13min -> 36s; Polarion -> ASPICE overlay 7min -> 3.8min. - fix(aspice): seed validates clean after init (#233). Two real bugs in the shipped aspice preset (undeclared `allocated-from` link-type, missing stakeholder-req parent) — `rivet init --preset aspice && rivet validate` now returns PASS. - feat(mcp): discoverability (#231). New `rivet mcp --list-tools` and `rivet mcp --probe` flags (no JSON-RPC required to enumerate the tool catalog or smoke-test the server) plus a new ~1400-word `rivet docs mcp` topic covering wire format, handshake, tool catalog, and the response-envelope gotcha. Verified: cargo check, cargo clippy --workspace -- -D warnings, cargo test -p rivet-cli, `rivet init --preset aspice && rivet validate` returns PASS, `rivet docs mcp` prints the new topic. Trace: skip
PR #235's Docs Check failed because the 0.5.1 changelog mentioned aspice preset SEED artifact IDs (SWARCH-001, SWREQ-001, SYSREQ-001, STKHR-001) in prose. Those IDs live in the embedded preset string constant, not as artifacts in this repo's store, so the rivet docs check ArtifactIdValidity invariant correctly flagged them as broken references. Fix: replace the seed IDs with their artifact-type names (sw-arch-component, sw-req, system-req, stakeholder-req). Reads better as prose anyway; no information loss. Trace: skip
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps workspace, vscode-rivet, and npm root packages to 0.5.1.
Bundles three already-merged PRs as a release:
docs(quickstart): rewrite for fresh-user clarityfix(aspice): seed validates clean after initfeat(mcp): discoverability — --list-tools, --probe, rivet docs mcpTheme
Post-0.5.0 first-contact polish. Two clean-room fresh-user dogfood passes plus three parallel scenario-based dogfoods (safety engineer / STPA, compliance lead / Polarion-import, AI integrator / MCP) surfaced two real bugs and one big doc gap. All three fixed.
Highlights
Wall-time wins (round-3 dogfood vs round-1):
Aspice seed bug (would-have-failed-the-talk discovery):
rivet init --preset aspice && rivet validateshipped failing in 0.5.0 with 2 errors. Now returnsPASS.MCP discoverability: AI integrators no longer need to write JSON-RPC by hand to enumerate the tool catalog —
rivet mcp --list-toolsandrivet mcp --probeplus a newrivet docs mcptopic explain the protocol end-to-end.Test plan
rivet init --preset aspice && rivet validatereturns PASS in CIrivet docs mcpprints the new topic🤖 Generated with Claude Code