🔖 Bump workspace packages to 0.11.0 - #697

Why

v0.10.2 is published and every manifest still declares 0.10.2, so the
rolling draft release carries the "manifests need bumping" banner and no tag
can be cut. Six PRs have merged since — <Switch>/<Case>, <Plan> under
xmd run, <Verbose>, and host-declared Markdown for one execution — new
document surface rather than fixes, so the version moves a minor.

What changes

Before:

Every @executablemd manifest declares 0.10.2, bun.lock records 0.10.2
for each workspace member, and the home page's release badge reads v0.9.2 —
three releases behind.

After:

Every @executablemd manifest declares 0.11.0, the ten workspace entries in
bun.lock record 0.11.0, and the badge reads v0.11.0.

How it works

deno task bump 0.11.0 → 20 manifests stamped → bun.lock workspace entries restamped by hand → draft tag defaults to v0.11.0

deno task bump stamps the version field of each workspace member whose
deno.json names an @executablemd package — ten packages, deno.json and
package.json each. bun.lock records a version per workspace member and
the task does not touch it; bun install will not restamp those entries
either, since they already satisfy the lockfile. They are restamped here by
hand, per release spec §2.

What must stay true

• packages/test-support stays at 0.0.0 — it is private and outside the
  lockstep, and the bump task skips it because its deno.json declares no
  @executablemd name.
• Only @executablemd members change in bun.lock — each of the ten 0.10.2
  lines sat directly under an @executablemd member's name, so no unrelated
  dependency sharing that number was restamped. After the edit no 0.10.2
  remains anywhere in the tree.
• Manifests stay the single version source — packages/cli/src/cli.ts reads
  packages/cli/deno.json, and release.yml and publish-packages.yml both
  refuse a tag the manifests do not declare.

How to verify it

• grep -rn '0\.10\.2' over the tree returns nothing, which fails if a
  manifest or lockfile entry was missed.
• The ten changed bun.lock lines each follow an @executablemd name,
  which fails if a same-numbered third-party dependency were caught.
• After merge the draft release's banner clears and its tag defaults to
  v0.11.0, which fails if any manifest still declared 0.10.2.

Scope

Included

• Version stamp across the ten publishable manifests, bun.lock, and the home
  page badge.

Intentionally unchanged

• pnpm-lock.yaml and deno.lock record no workspace version, so neither
  moves.
• No release is cut here — publishing the draft is a separate maintainer
  action.