release: the draft banner names the actual next version to bump to

[taras]

Motivation

The draft banner merged in #94 tells the maintainer to run
deno task bump <version> with a literal placeholder. The workflow knows the
current manifest version, so the banner should print the actual command.

Approach

Compute the next patch version from the already-released manifest version and
name it in the banner: Run deno task bump 0.3.1 (or the next minor/major) and merge the bump before publishing this draft. Verified the arithmetic
(0.3.0 → 0.3.1; a prerelease patch segment truncates to its numeric prefix)
and the workflow YAML + embedded script parse.

spec-reviewed: no changes needed — §3 describes the banner behaviorally
("saying the manifests need bumping"), which is unchanged.

Scope confirmation

• All changed files relate to the stated purpose
• No drive-by refactors or "while I'm here" cleanups
• No formatting changes mixed with functional changes

New abstractions (if any)

None.

New dependencies (if any)

None.

New tests (if any)

None — verified as described.

[github-actions]

Warning

This PR changes release configuration (.github/workflows/draft-release.yml) without touching
specs/release-process-spec.md. Review the spec and update it to match, or
state spec-reviewed: no changes needed in the PR description (AGENTS.md
rule 8).

PR #95: release: the draft banner names the actual next version to bump to

1 files, +4 / -2

Scope

✅ PR scope looks good.

Structural

✅ No structural bloat detected.

Slop

✅ Slop indicators look low.

Static Analysis

✅ Oxlint found no issues.

Correctness

✅ Small PR — correctness review skipped.