Configure pstack with only the selected model providers #72

Activity

1. mast-factory commented on Sep 23, 2026

   

   mast-factorybot

   on Sep 23, 2026 – with mast-factory

   More actions

   Type	feature request — Support a role-assignment-derived provider subset instead of requiring the baseline four-family setup profile.
   Route	Plan fix
   Severity	🟡 medium — the supported setup path is blocked for users who intentionally lack any unused baseline provider CLI or subscription.
   Confidence	high — the mandatory four-family gates are explicit in setup, tests, and the PR that introduced per-family effort selection.
   Effort	medium — setup sequencing, role validation, alias handling, smoke behavior, structural tests, and user-facing docs must remain aligned.
   Impact	medium — this unblocks a meaningful subset-provider workflow, while existing four-provider installations continue to work and manual configuration remains a risky workaround.
   Next step	Plan around PR #73 as the focused implementation candidate, reconcile its alias-only/assignment-derived contract with #33 and PR #55, then require exact-head installed behavioral evidence before merge.

   Understanding

   This is a valid feature request rather than a regression. Merged PR #16 intentionally made effort reconfiguration deterministic by collecting and probing exactly Fable, Sol, Grok, and Opus, requiring every family in the final role map, and gating writes and smoke on all four. Those assumptions remain at plugins/pstack/skills/setup-pstack/SKILL.md:46, :50, :72, :112, and :118; plugins/pstack/skills/poteto-mode/scripts/runner/model-matrix.test.ts:24 and :55 structurally lock the same quartet. That conflicts with README.md:35, which says core workflows can run with fewer models.

   The requested direction should preserve the existing safety contract while changing its scope: normalize and retain a complete role map first, derive distinct concrete provider/model/effort probes from the resulting assignments, require a real inherited native-route probe for assigned aliases, write nothing until every required probe passes and the operator confirms, and smoke only configured descriptors without introducing an unassigned provider. Selected failures must require repair or explicit reassignment; silent substitution remains forbidden.

   Open PR #73 directly implements that contract across setup instructions, matrix tests, docs, changelog/notice, and a behavioral-test plan. Its head 7feabe1518ac680caa514e304d342d22733f12ca is directly based on current main, is GitHub-mergeable, and passed both automated reviews. Independent local verification at that exact head passed 159 Bun tests, strict TypeScript typechecks, manifest parsing, static invariants, and git diff --check. The remaining verification gap is live installed-candidate execution with actual provider CLIs; tests/setup-selected-providers.md is a plan, not evidence that those scenarios ran.

   Issue #33 and PR #55 overlap but are not exact duplicates. They model a non-empty concrete active-family set and treat alias-only configuration as invalid, while #72/PR #73 derive requirements directly from final role assignments and support alias-only sheets after native delegation validation. Planning should choose and document one coherent contract before either implementation lands.

   Assumptions

   • “Selected providers” means providers/models referenced by the complete final role assignments, not a second independently persisted active-family setting.
   • The current Fable/Sol/Grok/Opus role map remains the first-run default; this change makes families optional only after explicit role reassignment.
   • inherit-parent and auto may form a valid alias-only configuration only when a real native delegated marker probe succeeds; the parent answering directly does not count.
   • Optional new families or adapters such as Sonnet, Luna/Terra/Astra, or GLM/OpenCode are outside Configure pstack with only the selected model providers #72; this issue changes subset selection for whatever matrix is installed.
   • Configure pstack with only the selected model providers #72 is not closed as a duplicate of Support explicitly selected model-family subsets in setup-pstack #33 because their alias and active-set contracts materially differ.

   Open questions

   • Maintainers must choose whether the canonical contract permits assignment-derived alias-only configurations as in PR Allow setup with only assigned model providers #73, or requires at least one concrete active model family as proposed in Support explicitly selected model-family subsets in setup-pstack #33/PR feat(pstack): support optional Sonnet Astra Luna and Terra families #55. That decision also determines whether Support explicitly selected model-family subsets in setup-pstack #33 is superseded, narrowed, or remains separate.

   Reproduction

   At current main commit de67e6b40511814171e5e4c8ad7af3b79f07c9ee:

   grep -nE 'Ask exactly four|Probe only the four|at least one descriptor from each matrix family|all four probes|all four chosen descriptors' \
     plugins/pstack/skills/setup-pstack/SKILL.md

   The command returns mandatory gates at lines 46, 50, 72, 112, and 118. Therefore a role map that omits an unused baseline family cannot complete supported setup even if every selected route works. The declarative setup contract reproduces the limitation without external credentials.

   At PR #73 head, bun run test passed 159 tests, bun run typecheck passed all strict TypeScript projects, and the repository static/manifest checks passed. Live Claude/Codex/Grok setup scenarios were not executed in this sandbox because provider credentials and installed harness state are not available.
2. thisguymartin

   added a commit that references this issue on Sep 28, 2026

   feat(setup): assignment-first setup with flex families

   ...

   da63250
3. mergify

   closed this as completedin #98on Oct 1, 2026