[CLI-03] Package, sign, document, and test cross-platform releases

[jaavid]

Background

CoreLink is one product across multiple implementation repositories. This work is owned by cli under EPIC-05.

Goal

Package, sign, document and validate cross-platform CLI releases with retained provenance and sandbox/conformance evidence.

Parent

• Primary Product Epic: EPIC-05
• Backlog ID: CLI-03

Scope

• Package/version the accepted CLI-02 command surface.
• Sign/publish releases through the organization release/provenance path.
• Validate supported commands against MOCK-03 or equivalent accepted sandbox where applicable.
• Test supported operating-system/architecture targets and documented install paths.
• Retain artifact, source, dependency and conformance evidence.

Out of Scope

• Expanding command scope beyond CLI-02.
• Treating successful packaging as platform/runtime Product Acceptance.
• Stable support claims without accepted provenance and compatibility evidence.

Acceptance Criteria

• CLI artifacts are reproducible from immutable source/dependency revisions.
• Signing/provenance satisfies the accepted [CLI-03] Package, sign, document, and test cross-platform releases #4 release path.
• Supported platform/architecture packages install and execute the documented flows.
• Positive, denied, malformed and recovery behavior passes against the accepted API/mock path where relevant.
• Version/maturity and compatibility ranges are explicit.
• Rollback/deprecation/update behavior is documented.
• Retained evidence advances EPIC-05 CLI release criteria.

Dependencies and acceptance state

• Execution prerequisite: CLI-02 accepted CLI command behavior.
• Release-governance prerequisite: GH-04 accepted reusable CI/release/provenance path.
• Conformance input: MOCK-03 or equivalent accepted sandbox where CLI Beta/RC flows depend on it.
• Blocks: DOCS-04 CLI release/install guidance, WEB-03 supported-tool claims, and EPIC-05 CLI release acceptance.
• Current dependency state: See the CoreLink Product organization Project.

Planning Metadata

• Type: Technical Task
• Priority snapshot: P1
• Product milestone snapshot: Release Candidate
• Domain snapshots: devex, deployment
• Area snapshot: package
• Complexity: M
• Created in status: Triage
• Current status and DRI: See the CoreLink Product organization Project.
• Intended repository labels: type:technical-task

Definition of Done

• Acceptance criteria demonstrated.
• Artifact provenance/signing and reproducibility are verified.
• Supported target matrix and install paths are validated.
• Required sandbox/conformance checks pass.
• Documentation/release notes are updated.
• Pull request(s), release artifacts and retained evidence are linked.