[v0.1.0] Publish the immutable compatibility manifest and release evidence

[XnLemon]

Goal

Publish the first consumable NeKiro release train with one immutable compatibility manifest and reproducible product evidence.

Tracked work

• [v0.1.0] Freeze every NeKiro-owned HTTP boundary on v1 NeKiro#120 — unified Gateway and internal API v1, Core images, ADR, and migration guide
• [v0.1.0] Migrate the Console to the unified Gateway v1 API NeKiro-Console#14 — Console v1 client and production image
• [v0.1.0] Migrate the Go clients to the unified Platform v1 API nekiro-sdk-go#7 — Go SDK v1 client and module release
• [v0.1.0] Publish immutable sample Runtime images NeKiro-Samples#15 — immutable Runtime A/B images
• [v0.1.0] Add a Docker-only one-command product evaluation #16 — Docker-only one-command evaluation
• nekiro-a2a-transport-go v0.1.1 — existing immutable transport release

Release manifest

The release manifest must record, for every component:

• repository owner and name;
• semantic version tag;
• full commit SHA;
• every runtime image reference and sha256 digest;
• contract identity and supported dependency versions.

The validator must reject a missing tag, tag/SHA mismatch, floating reference, missing required image, digest mismatch, unknown field, local path, or branch.

Release evidence

• Core and component checksums and SBOMs;
• signed build provenance where supported by GitHub Actions;
• exact Go, PostgreSQL, Nacos, Docker, OS, and architecture support matrix;
• upgrade, teardown, and pre-release API migration notes;
• sanitized backend and browser logs;
• machine-readable evaluation summary and visible workflow result;
• explicit supported, experimental, and deferred capability table.

Ordering

1. Land and validate coordinated Core, Console, SDK, Samples, and Stack release candidates by exact commit SHA.
2. Publish Core, Console, SDK, and Samples tags/images; confirm every tag resolves to the reviewed commit.
3. Replace candidate references with released tags and image digests in Stack.
4. Run backend, browser, and Docker-only evaluation against the immutable manifest.
5. Tag Stack v0.1.0 only after every gate passes.
6. Publish the compatibility report and direct evaluation command from every repository README.

There is no fallback to an older Core revision or mutable image when any component fails.

Acceptance

• A released Stack tag contains only mutually compatible immutable component identities.
• Manifest resolution and all product acceptance gates pass from a clean environment.
• The release page links the migration guide, support matrix, evidence artifacts, and one-command evaluation.
• A failure in any component remains a visible release blocker.