[Release] Smoke-test CLI and Community install paths on AMD64 and ARM64

[mohit-nagaraj]

Context

#47 repaired project discovery, generated Compose configuration, ports, and the local source-development path in merged PR #49. The remaining release gate is not another CLI implementation rewrite: it is proof that a clean user can install the released CLI and start a compatible published Core/UI set on the two architectures named by the original report and Month 1 roadmap.

The release workflow already builds darwin/arm64 and linux/amd64 CLI binaries, and the npm installer maps those operating-system and architecture pairs to release assets. However, the current integration suite is opt-in, builds the CLI from source, and does not prove a fresh published installation. Generated production and hybrid Compose files are still pinned to the AMD64-only Core/UI v0.0.3 image indexes.

Outcome

A compatibility-pinned KubeOrch release set passes the documented Community install and first-start workflow from a clean environment on Linux AMD64 and macOS ARM64, with repeatable evidence suitable for closing #47.

Scope

• Consume released, digest-pinned Core and UI indexes that include linux/amd64 and linux/arm64.
• Exercise the documented primary CLI installation path using published artifacts rather than a source build.
• Verify the npm package downloads the correct released binary for Linux AMD64 and macOS ARM64.
• Run orchcli init, orchcli start -d, orchcli status, and the documented shutdown path from a clean directory.
• Verify generated production configuration uses one compatible Core/UI release set and the supported browser API URL.
• Prove Core, UI, MongoDB, and one browser-to-Core authentication/API request work through the started environment.
• Make the smoke procedure repeatable in release automation or documented architecture-specific test infrastructure.
• Publish bounded diagnostic evidence when the smoke fails.

Out Of Scope

• Reimplementing the project-discovery and runtime fixes already merged in PR fix: align the local runtime contract #49.
• Building or publishing the missing Core and UI multi-architecture images.
• Testing every CLI command, application feature, hybrid development mode, or Windows installation.
• Defining or signing the future organization-wide compatibility manifest.

Acceptance Criteria

• A clean Linux AMD64 environment completes the documented install, initialize, detached start, status, and stop flow without source checkouts or manual Compose commands.
• A clean macOS ARM64 environment completes the same flow using ARM64 Core and UI image manifests.
• The native installer selects a released CLI binary matching the host operating system and architecture and verifies its checksum.
• The npm installation selects the matching released binary on Linux AMD64 and macOS ARM64 rather than silently building from source.
• Generated Compose configuration references immutable, mutually compatible Core and UI release digests.
• Core, UI, and MongoDB become healthy within documented time bounds.
• A browser request reaches the configured Core API and does not fail because of an image architecture or browser API URL mismatch.
• Re-running initialization and startup is idempotent or returns the documented safe behavior.
• Smoke evidence records CLI, Core, UI, image digest, host architecture, duration, and failed component without credentials.
• [Runtime] Make orchcli start match the documented runtime contract on AMD64 and ARM64 #47 is closed only after this evidence passes.

Verification

• Linux AMD64 fresh-install smoke using published release artifacts.
• macOS ARM64 fresh-install smoke using published release artifacts.
• Native installer checksum and architecture assertions.
• npm post-install binary selection assertions on both target environments.
• OCI manifest selection assertion for Core and UI.
• Browser-to-Core authentication/API smoke.
• Failure-path test proving a missing or incompatible platform manifest produces an actionable error.

Dependencies

Blocked by KubeOrch/core#133 and KubeOrch/ui#110. Completion provides the final release evidence required by #47.

Documentation And Observability

Update the Community quickstart and CLI release documentation from the tested workflow. Retain architecture-specific smoke results with the release while redacting tokens, local credentials, and environment secrets.

[mohit-nagaraj]

/assign

[github-actions]

✅ Issue assigned to @mohit-nagaraj