Background
CoreLink is one product across multiple implementation repositories. This work is owned by cli under EPIC-05.
Problem
The repository does not yet provide a supported, reproducible and acceptance-tested way to package, sign, document, and test cross-platform releases.
Goal
Package, sign, document, and test cross-platform releases, aligned with tagged contracts and the shared CoreLink release train.
Parent
- Primary Product Epic: EPIC-05
- Backlog ID:
CLI-03
Scope
- Deliver the title outcome inside
cli.
- Reconcile contract version, authentication, tenancy, error, compatibility, packaging and documentation behavior where applicable.
- Retain evidence for the Release Candidate gate.
Out of Scope
- Hand-written divergence from the normative contracts.
- Unsupported production claims before an artifact and conformance evidence exist.
- A separate repository roadmap.
Acceptance Criteria
Technical Notes
Generated artifacts must identify immutable contract provenance. Security-sensitive tools use least privilege, explicit consent, audit and safe token handling. Package channels must distinguish prerelease from stable.
Dependencies
Planning Metadata
- Type: Technical Task
- Priority: P1
- Product milestone: Release Candidate
- Domains: devex, deployment
- Area: package
- Complexity: M
- Initial status: Triage
- DRI: Unassigned
- Intended labels:
type:technical-task, priority:p1, domain:devex, domain:deployment, area:package
Definition of Done
Background
CoreLink is one product across multiple implementation repositories. This work is owned by
cliunder EPIC-05.Problem
The repository does not yet provide a supported, reproducible and acceptance-tested way to package, sign, document, and test cross-platform releases.
Goal
Package, sign, document, and test cross-platform releases, aligned with tagged contracts and the shared CoreLink release train.
Parent
CLI-03Scope
cli.Out of Scope
Acceptance Criteria
Technical Notes
Generated artifacts must identify immutable contract provenance. Security-sensitive tools use least privilege, explicit consent, audit and safe token handling. Package channels must distinguish prerelease from stable.
Dependencies
Planning Metadata
type:technical-task,priority:p1,domain:devex,domain:deployment,area:packageDefinition of Done