chore(release): bump publishable packages to 0.0.51

[blove]

Summary

Version bump 0.0.50 → 0.0.51 for the 7 publishable @threadplane/* libs ahead of cutting the release. Inter-lib peerDeps are "*" so no range updates needed; verify-release-versions --tag v0.0.51 passes (atomic).

Ships the lib work merged since v0.0.50 (structured AgentError, injectThreadRouting, subagent cards, TS DX pass, JSDoc). The tag push after merge triggers npm publish (provenance) + the now-verified SLSA release-provenance flow.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
threadplane	Ready	Preview, Comment	Jun 19, 2026 11:14pm

[github-actions]

Automated approval: this PR received an intelligent (AI) code review. See the review comments on this PR.

[github-actions]

Claude finished @blove's task in 1m 11s —— View job

---

PR Review: chore(release): bump publishable packages to 0.0.51

• Gather context
• Read CLAUDE.md for repo guidelines (none found)
• Review PR diff
• Check version consistency across all package.json files
• Post findings

---

This PR is clean. Seven publishable @threadplane/* libs uniformly bumped from 0.0.50 → 0.0.51. All diffs are single-line version changes; no peerDep ranges, exports maps, or publish configs were altered.

Version consistency check: All 7 packages are at 0.0.51 ✓. Non-@threadplane libs (cockpit-*, design-tokens, middleware, etc.) correctly remain on their independent versioning tracks.

Two low-severity observations:

1. package-lock.json is stale — it still records 0.0.50 for all 7 packages (7 hits). The root lockfile isn't used by npm publish for workspace packages, so this won't block the release, but running npm install after the bump would keep the lockfile in sync and avoid confusion during local dev post-merge.

2. CHANGELOG.md has no 0.0.50 or 0.0.51 entry — the latest entry is 0.0.47. Since 0.0.50 also wasn't recorded, this appears intentional (changelog tracks milestone releases only, not every patch bump). No action needed unless the team wants to document the shipped features (structured AgentError, injectThreadRouting, subagent cards, TS DX pass, JSDoc) mentioned in the PR description.

No correctness bugs, security issues, type-safety problems, or API regressions found. ✅