kandev/docs/plans/github-saved-query-defaults/task-02-apply-default-selection.md

id, title, status, wave, depends_on, plan, spec

id	title	status	wave	depends_on	plan	spec
02-apply-default-selection	Apply default saved-query selection	done	2	01-persist-default-saved-queries	plan.md	../../specs/ui/requirements/github-saved-query-defaults.md

Task 02: Apply Default Saved-Query Selection

Acceptance

• Dashboard entry resolves the pull-request default after hydration, including query and repository, unless the user already interacted.
• Kind switches resolve that kind's saved default or first configured query.
• Save/delete/default mutations preserve the current-view rules in the spec.

Files

• apps/web/components/github/my-github/use-sidebar-selection.ts
• apps/web/components/github/my-github/use-sidebar-selection.test.ts
• apps/web/components/github/my-github/use-saved-preset-actions.ts
• apps/web/components/github/my-github/use-saved-preset-actions.test.ts
• apps/web/app/github/github-page-client.tsx

Verification

cd apps && pnpm --filter @kandev/web exec vitest run components/github/my-github/use-sidebar-selection.test.ts components/github/my-github/use-saved-preset-actions.test.ts

Result

• RED: initial hydration remained on the first built-in PR query; kind switching selected the first issue query; action tests showed duplicate store ownership, no interaction marker, and no default mutation.
• GREEN: focused command passed 10 tests across 2 files.