🔖 Bump workspace packages to 0.10.0

[taras]

Why

Cut 0.10.0 so the release carries xmd prompt, merged in #657. Minor rather than patch because this adds a command: you describe an outcome, a readable Executable Markdown workflow turns it into a Plan, and the approved Plan goes to stdout, an --output file, or a --run.

What changes

Before: every publishable manifest declares 0.9.2.

After: every publishable manifest declares 0.10.0, and bun.lock's workspace entries agree.

Version numbers only. No source, specification or behavior change.

Scope

Included

• the ten publishable @executablemd manifests, deno.json and package.json each;
• the ten matching workspace version entries in bun.lock.

Intentionally unchanged

• packages/test-support stays outside the lockstep — it is private and never publishes, so it declares no version to bump.
• Nothing else in bun.lock. The ten edited entries were each confirmed to belong to an @executablemd member by name, because the release spec warns that an unrelated dependency happening to share 0.9.2 must not be swept along.

Generated or mechanical changes

• The manifests come from deno task bump 0.10.0.
• The bun.lock entries are restamped by hand: the bump task does not touch the lockfile, and bun install will not restamp them either, since they already satisfy it. Left alone they would keep the previous release's number.

Both are mechanical and contain no intended behavior change.

How to verify it

deno task test scripts/tests/release-targets.test.ts scripts/tests/bump-version.test.ts scripts/tests/workspace.test.ts

Results here: 4 passed (16 steps) and 2 passed (9 steps), zero failures.

Two checks worth stating, because a bump PR is exactly where a stray edit hides:

• every changed line in the diff is a "version" line — filtering the diff for anything else returns nothing;
• no 0.9.2 remains in any manifest or in bun.lock, and the ten 0.10.0 entries match the ten publishable packages.

Risks and limitations

• The tag published afterwards must be v0.10.0. Both release workflows refuse a tag the manifests do not declare, so a mismatch fails the release rather than shipping a wrong number.
• Nothing here is exercised until the draft release is published; merging this only changes what the manifests claim.

Scope confirmation

• Every changed file supports the purpose described above.
• Unrelated cleanup and formatting changes are excluded.
• Generated or mechanical changes are clearly identified.
• The description matches the final diff and test results.

https://claude.ai/code/session_015HcqB9kJM9KFnMNToAuZF6

[github-actions]

PR #669: 🔖 Bump workspace packages to 0.10.0

21 files, +30 / -30

Scope

🟡 21 files changed. Are all changes related?

🟡 Changes span 11 directories.

🟡 PR mixes config and source changes.

Structural

✅ No structural bloat detected.

Slop

✅ Slop indicators look low.

Static Analysis

✅ Oxlint found no issues.

Correctness

No extraneous code patterns detected.