Align CLI documentation with shipped installers and model IDs

Overview

Public docs contain Linux source-only language despite artifacts, slash-containing editor model examples rejected by validation, and stale skill harness/login behavior.

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

Current evidence

Public docs contain Linux source-only language despite artifacts, slash-containing editor model examples rejected by validation, and stale skill harness/login behavior.

• Source: docs/ENGINES.md#L34
• Source: docs/EDITORS.md#L1
• Source: src/harness/opencode.cpp#L230

Design and implementation plan

Generate or mechanically check supported examples against command/model validation and release metadata; preserve secondary local/SDK docs.

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

• Exercise documented commands against fixture catalog; remove rejected IDs.
• Accurately describe interactive versus piped installer login and current harness support.
• Align platform table with public versus private-overlay capabilities.

Related work and deduplication

Marketing43/45 own public release and retired command copy. This issue owns Wally repository skill/editor/platform docs mismatching current CLI behavior; cross-link without duplicating website fixes.

• https://github.com/RunanywhereAI/runanywhere-marketing/issues/43
• https://github.com/RunanywhereAI/runanywhere-marketing/issues/45

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 with docs/ENGINES.md, docs/EDITORS.md, and src/harness/opencode.cpp, then inspect the fixture catalog, command/model validation, and release metadata. Reconcile the documented examples, installer login behavior, harness support, and platform table with current artifacts. Done means rejected IDs are removed and reproducible validation evidence is attached, with deferred work recorded.