[Release] Admit the next installable candidate after rebrand and live proof

[Sequela02]

Status

Blocked release-admission issue. This does not authorize a tag, package publication, rebrand implementation, or compatibility path.

Objective

Admit or reject the next installable Kiln release candidate from an exact supported source baseline, final product/package identity, live evidence, and clean-install proof.

Current facts

• The repository has no supported installable release and no authorized candidate.
• The historical 3.0.0-beta.1 candidate was not published and is no longer the target.
• The current product name, @kilnai/* coordinates, versions, and package URLs are provisional.
• Roadmap 00 and [Source Stability] Establish one supported source baseline #103 must first establish the exact supported source baseline and surfaces.

Admission sequence

1. Product and package identity

• Record the approved public product name and npm package coordinates.
• Replace provisional names and repository/package URLs atomically.
• Do not retain @kilnai/* aliases or compatibility packages without a demonstrated external consumer.

2. Candidate definition

• Select one exact SemVer and committed candidate.
• Name supported platforms, install boundary, operator surfaces, and explicit exclusions.
• Record required live-provider, native-harness, restore/recovery, and supported-platform evidence with executed, failed, skipped, and omitted cases.

3. Release proof

• Run the canonical typecheck, tests, build, documentation, release validation, pack, clean-install smoke, preflight, and registry-verification sequence from docs/operations/release.md.
• Verify npm trusted-publishing authority before pushing a tag.
• Verify registry state and provenance before documenting an install command.

Acceptance criteria

• Roadmap 00 and [Source Stability] Establish one supported source baseline #103 are complete.
• Public name and package coordinates are final and consistent across manifests, tooling, docs, and registry checks.
• The exact candidate passes all source and release gates on every admitted platform.
• Required live and recovery evidence is recorded without credentials, operator paths, or raw provider payloads.
• npm trusted-publishing authority and final registry coordinates are verified before a tag is pushed.
• Registry state and provenance are verified before install documentation claims availability.

Non-goals

• Making Connect, Capability Fabric, Prompt Governance, Stack Governance, inbound agents, Rust, or a native surface prerequisites unless the admitted release scope explicitly consumes them.
• Reusing the historical 3.0.0-beta.1 candidate.
• Keeping compatibility aliases for hypothetical consumers.

Dependencies

Blocked on Roadmap 00 and #103. The release runbook remains the canonical publication owner; this issue owns candidate admission and the missing product/package decisions only.