Motivation: The onboarding card backfills summaryModel with the chat model when the user enables auto-summary through the card, closing the "auto-summary on but no summary model → silent failure" gap. But the same gap still exists on the Settings path: if a user enables auto chapter summaries directly in Settings → Reading before ever configuring a summary model, resolveSummaryModel returns "not configured" and summaries silently fail.
Current behavior: summaryModel and the chat (assistant) model are two independent configs. resolveSummaryModel deliberately never falls back to the chat model. The SummaryModelPicker shows empty when unset.
Desired direction: In Settings, when summaryModel is unset, default the picker's displayed/effective value to the current chat (assistant) model — so a freshly-configured user who turns on auto-summary in Settings doesn't hit a silent failure. Keep resolveSummaryModel's no-implicit-fallback contract intact; this is a Settings-UI default (an explicit write when the user accepts it), not a runtime fallback.
Source: deferred §8 of docs/superpowers/specs/2026-06-09-onboarding-flow-design.md (onboarding card final review follow-up).
Motivation: The onboarding card backfills
summaryModelwith the chat model when the user enables auto-summary through the card, closing the "auto-summary on but no summary model → silent failure" gap. But the same gap still exists on the Settings path: if a user enables auto chapter summaries directly in Settings → Reading before ever configuring a summary model,resolveSummaryModelreturns "not configured" and summaries silently fail.Current behavior:
summaryModeland the chat (assistant) model are two independent configs.resolveSummaryModeldeliberately never falls back to the chat model. TheSummaryModelPickershows empty when unset.Desired direction: In Settings, when
summaryModelis unset, default the picker's displayed/effective value to the current chat (assistant) model — so a freshly-configured user who turns on auto-summary in Settings doesn't hit a silent failure. KeepresolveSummaryModel's no-implicit-fallback contract intact; this is a Settings-UI default (an explicit write when the user accepts it), not a runtime fallback.Source: deferred §8 of docs/superpowers/specs/2026-06-09-onboarding-flow-design.md (onboarding card final review follow-up).