t27c 0.4.0: the registry crate predates its seventh backend #4503

Что

t27c on crates.io is 0.3.0. The compiler gained gen-ts in #4502, so the
version a user installs from the registry cannot emit TypeScript while the
compiler on master can. Same shape as #4490, one backend later.

Minor rather than patch: a new backend is added functionality, and additive —
the six existing targets are untouched.

Границы

Three files, and nothing else:

• bootstrap/Cargo.toml — version = "0.4.0"
• .zenodo.json — "version": "0.4.0"
• Cargo.lock — the mechanical consequence of the first

Both of the first two are read by the release pipeline's VERSION TRUTH gate for
a t27c-v* tag. The gate refuses a tag whose manifests do not already say what
the tag says, so a half-bumped pair fails the tag, not the PR — which is
why they move together.

ZENODO_DEPOSITION_T27C stays unset, so zenodo-publish.yml skips and mints no
DOI. A DOI cannot be withdrawn; enabling it is its own decision, not a side
effect of cutting a crate release.

Готово когда

t27c-v0.4.0 is published and the crates.io page shows a version that can emit
all seven targets.