Cut the first release: tag, publish and the releases-page entry

[sameera]

Cut the first release of the one-package distribution: tag the version, publish it to the public registry, and create the releases-page entry from the changelog section — one semantic version named by all three.

Meta

• feature: docs/features/component-distribution
• estimate: S
• source: deferred from epic Publish the release as one package carrying both toolkits, the component payload and the changelog (Publish the release as one package carrying both toolkits, the component payload and the changelog #252) (2026-08-27), where it was the amended AC1 of story One tagged release publishes all three parts with an adopter-language changelog #312

Why it was deferred

Everything the release needs is built and proven: the manifest declares both binaries, the payload is a stated set with a committed fingerprint, the parity gate checks what is released, the changelog carries the 0.1.0 entry, and pack-release.spec.ts proves npm pack plus a real global install runs both binaries from outside the checkout.

What is missing is not release machinery — it is that decision record #334 invariant 15 forbids cutting the tail while a shipped component body reaches a toolkit capability by an in-repository script path. Those paths exist in no installed package, so a release cut today would put bodies on the registry that cannot work, and the changelog's own claim that a stage runs without a checkout would be false on the first release. pnpm nexus:release-gate enforces this and names twelve such references today, across nxs.epic.md, nxs.setup.md and nxs-epic-resolve/SKILL.md.

Revisit trigger

Epic #250 merged and pnpm nexus:release-gate exiting zero. Then follow docs/delivery/release-procedure.md from step 4.

Acceptance criteria

• pnpm nexus:release-gate exits zero before anything is tagged.
• One git tag, one version on the public registry and one GitHub release entry all name the same semantic version as VERSION, the published manifest and the newest changelog entry.
• The releases-page entry body is the changelog section for that version.
• Both binaries run from a directory that is not a checkout, installed from the registry rather than from a local pack.