Repository navigation
bug: default session group is disabled when creating or linking a case #38
Description
The Add Case / Link Remote dialog shows Default session group as a disabled Ungrouped select. The control is wired only to edit-existing-case loading, so new cases cannot choose a group. Load the owner’s groups for creation, preserve the choice across creation tabs, and persist it before starting a session. Cover stale asynchronous responses, failed saves, and existing edit behavior in browser tests.
Activity
docs: show selectable new-case groups on desktop and mobile (#38)
johoja12 commentedon Nov 2, 2026
Implemented on fix/38-new-case-default-group: 3227bf3 (code/tests), 0ce8fd2 (sanitized desktop/mobile screenshots). Draft PR #39 targets the existing production keyboard candidate branch to keep the group fix scoped. New-case group options load from the owner layout, survive creation-tab switches, and save through the existing per-case endpoint before automatic startup. Existing edits and async stale-response fencing are retained. Nine browser regressions + seven unit tests passed, plus actual desktop/mobile modal rendering with the candidate module and production markup/styles; session connections and writes blocked. Typecheck/lint/format/lockfile/frontend syntax/public assets and pre-push checks pass with isolated locked dependencies. Initial shared-dependency mismatch (installed fflate 0.8.2 vs pinned 0.8.3) was resolved only in the isolated worktree. Shared WIP preserved. No service restart or production deployment for this issue.
johoja12 commentedon Nov 2, 2026
Merged and pushed as requested: PR #39 merged into the keyboard branch (da68e4e), then PR #37 merged into origin/local at b497746. The tested tree is preserved, local and origin/local match, and shared assistant WIP remains untouched. No production build/restart in this merge-and-investigation request; production deployment of the group-selector change remains pending.