Expose an explicit hosted-model catalog in CLI model discovery

Overview

Harnesses consume hosted model metadata but models/list remain SDK/local registry oriented, leaving cloud discovery indirect.

Priority: P2 / post-mvp. Impact: roadmap improvement. Initial planning estimate: Medium; refine after inventory. This issue does not add a release blocker.

Current evidence

Harnesses consume hosted model metadata but models/list remain SDK/local registry oriented, leaving cloud discovery indirect.

• Source: src/commands/cmd_models.cpp#L1
• Source: src/harness/opencode.cpp#L230

Design and implementation plan

Add a clearly distinguished cloud catalog view through the pinned service contract; retain local model lifecycle semantics.

1. Reconcile the current implementation and any already completed work with the evidence above.
2. Record the owner, selected scope, dependencies and unresolved decisions before implementation.
3. Implement or execute the selected scope using existing components and artifacts.
4. Attach reproducible validation or outcome evidence and record any deferred work.

Acceptance criteria

• List entitled hosted IDs, context and price provenance without requiring local downloads.
• Distinguish unreachable/unauthorized/empty catalog and verify environment/profile selection.
• Use shared metadata; do not implement server-side compaction.

Related work and deduplication

No existing issue has this acceptance scope; existing release defects remain separate.

No exact existing issue found in the all-state inventory.

Requirement provenance

Reconciled September 13, 2026 against WALLY_CLOUD_PRODUCT_SOURCES.md (SHA-256 e601b7b154b750965fa8d25d4533d3542621bd00b3bb30038c1fae553a549e7b) and the consolidated requirements report. Historical proposals are not evidence of current delivery, customer agreement or approved pricing.

Start by reconciling src/commands/cmd_models.cpp and src/harness/opencode.cpp with the pinned service contract and record the scope, dependencies, owner, and unresolved decisions. Validate the selected implementation against the acceptance criteria: entitled hosted IDs, context and price provenance without downloads; distinct unreachable, unauthorized, and empty states; and environment/profile selection using shared metadata.