Repository navigation
Choose the first developer distribution path #314
Description
Activity
Resolution
Linear already fixes the first developer distribution path; Wayfinder should route to it rather than create a parallel packaging decision.
Linear source of truth
- KEL-141 — macOS: distribute prebuilt CLI and host with no Rust runtime dependency owns the first developer-facing distribution path.
- KEL-103 — Spec: signed macOS prebuilt host binary (T1) is the signing/provenance prerequisite for KEL-141.
- KEL-139 — minimum macOS product spine consumes that prebuilt path as part of the product proof.
- KEL-19 and KEL-9 remain earlier CLI/distribution research/spec context; they should not be reopened for this slice.
Decision
The first supported developer distribution slice is:
prebuilt macOS arm64 KELD CLI + matching no-flag host + host-selected pinned Bun, installable/runnable without Cargo, rustc, rustup, repository checkout, or local framework compilation.
Boundaries:
- macOS arm64 is the claimed first platform for this product slice.
- No claim for macOS x64 until separately verified.
- No requirement for DMG/pkg/App Store, Windows/Linux installers, updater rollout, or broad package-channel coverage in this decision.
- Artifact hashes/provenance and trusted runtime selection are part of the contract, not optional polish.
- Existing KEL-141/KEL-103 owners remain authoritative; no new implementation issue is created from this Wayfinder ticket.
Wayfinder should continue from the remaining unresolved Linear frontier rather than revisiting CLI-distribution format choices.
Parent map: https://github.com/gyldlab/keld/issues/311
Question
For the first developer-facing preview, should KELD ship as a source-built path, prebuilt CLI/host binaries, package-manager entrypoint, or another bounded form, and exactly which OS/architectures should be claimed?