Pinky MM: plan-selectable spawns (v1.43.0) #72
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/pinky-mm-plans"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plan-selectable spawns in the 🌱 genesis dialog (steer #32; rides zcode-dispatch v1.0.25
--provider)./api/genesis/modelsgains aplansfeed joined from three read-only sources — the registry snapshot (the dispatcher exit-2 validation set), the builtin provider config (display names + enabled models), and the credential store PRESENCE probe (key names only). One selection = a (provider, model) pair; the review step shows BOTH; default = the station config provider. Group labels derive from the data — never hardcoded plan names.POST /api/session/createtakes an optionalprovider(account:shape — anything else is an honest 400 before any spawn); it rides the fixed systemd-run script as a NINTH argv positional behind[ -n "$9" ]guards; absent/empty omits--provider(back-compat).providerDecline(credential exit 6 / unknown-id exit 2) in the status feed — an amber chip decorating the verbatim dispatcher text, exit-7 style.Validation: 423-test suite green (+29 new), Super-Linter station recipe green (all lanes), fake-HOME rig — all 27 legs green (grouped feed from fixture registry data, two-plan E2E with per-result
actualProvider+ per-plan ledger entries + the credential seam serving the CHOSEN plan key, honest exit-6/exit-2 declines), fixture CDP smoke green (picker, hint, review plan row). Live station untouched.