[CLI-01] Select implementation stack and define public versus operator command boundaries

[jaavid]

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 select implementation stack and define public versus operator command boundaries.

Goal

Select implementation stack and define public versus operator command boundaries, aligned with tagged contracts and the shared CoreLink release train.

Parent

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

Scope

• Deliver the title outcome inside cli.
• Reconcile contract version, authentication, tenancy, error, compatibility, packaging and documentation behavior where applicable.
• Retain evidence for the Developer Platform 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

• The outcome is reproducible from documented inputs and tagged dependencies.
• Expected, error, retry/recovery and compatibility behavior is verified.
• Authentication, tenant context and sensitive-data handling are safe where applicable.
• Installable artifacts or explicit scaffold status are documented accurately.
• Examples and documentation are versioned and runnable.
• Conformance evidence is linked to the parent Epic.

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

• Prerequisite completed: API-01 established the contract lifecycle baseline.
• Active blocker: security review of public versus operator command boundaries.
• Blocks: CLI stack selection, supported command-boundary decisions, and downstream CLI implementation work.
• Cross-repository: Link concrete contract, security, CLI, documentation and release Issues; do not duplicate implementation.
• Current dependency state: See the CoreLink Product organization Project.

Planning Metadata

• Type: Spike
• Priority: P1
• Product milestone: Developer Platform
• Domains: devex, security
• Area: package
• Complexity: S
• Created in status: Triage
• Current status and DRI: See the CoreLink Product organization Project.
• Intended repository labels: type:spike

Definition of Done

• Acceptance criteria demonstrated.
• Tests/conformance and required evidence pass.
• Contracts are updated or confirmed unaffected.
• Security and tenancy boundaries are reviewed.
• Packaging, provenance and rollback are verified.
• Documentation and release notes are updated.
• Pull request(s) are merged and linked.