…rator

`npm run lint:arch` failed with 7 circular store imports plus a renderer-
imports-main violation. Untangled without behavior changes:

- `src/store/focused-panel.ts` (new): the focus-registry getters/setters
  (`triggerFocus`, `getTaskFocusedPanel`, `setTaskFocusedPanel`,
  `isPanelFocused`, `defaultPanelFor`, `aiTerminalPanels`, etc.) live
  here. `focus.ts` keeps grid navigation and re-exports the moved
  symbols for backward compatibility with existing call sites.
- `src/store/project-cleanup.ts` (new): `removeProjectWithTasks` is now
  the lone orchestrator that depends on both projects and tasks, so
  `projects.ts` no longer needs to import `closeTask`.
- Updated `navigation`, `tasks`, `terminals`, `ui` (and `ui.test.ts`
  mock target) to import focused-panel helpers from the new module
  instead of round-tripping through `focus.ts`.

After this change the projects↔tasks, persistence chain, navigation↔
focus, and focus↔tasks cycles are gone.

- .dependency-cruiser.cjs: `electron/mcp/prompt-detect.ts` is a pure
  regex module already shared with the renderer task-status pipeline;
  whitelist it next to `electron/ipc/channels.ts` so the rule's intent
  (block Node/Electron-bound code) remains while the documented shared
  module is allowed.

Addresses finding 2 of issue johannesjo#157.

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>

…lete() path

`waitForSignalDone` had two terminal paths: the registered `wrapped`
resolver (which cleared the timer, wrote the replay cache, and
resolved) and the timeout callback (which removed the resolver,
finished the wait, but \*did not\* write the replay cache before
resolving). A client retry that reused the same requestId after a
timeout would therefore re-enter the wait path and register a fresh
resolver, inflating `activeSignalWaitCounts` and re-blocking the
coordinator's notification batching.

- Collapse both paths into a single idempotent `complete(result)` that
  clears the timer, removes itself from `anySignalResolvers`, calls
  `finishSignalWait`, writes the replay cache when `requestId` is set,
  and resolves the promise. The `settled` guard makes repeated calls a
  no-op so external callers can keep shifting the resolver out before
  invoking it.
- Drop the now-redundant `finishSignalWait` calls in the three external
  paths that consume a resolver (PTY exit, cleanupChildTask, signalDone)
  — `complete` handles bookkeeping itself, so leaving the manual call
  in place would double-decrement the wait count.
- In `unregisterCoordinator`, snapshot the resolvers before fan-out
  because `complete` now splices itself from the live array.
- Add a coordinator.test.ts case: same requestId after a timeout
  returns the cached timed-out result quickly instead of starting a
  new live wait.

Addresses finding 1 of issue johannesjo#157.

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>

CI previously ran only typecheck/lint/format and skipped both the
electron compile (`npm run compile` is the closest thing to a build
gate for main-process code) and the test suite. After the cycle fix
and knip cleanup, the static gates are green, so wire them in:

- `npm run check` — covers compile + typecheck + lint + format:check.
- `npm run lint:arch` — depcruise enforcement, now green.
- `npm run lint:dead` — knip, now green.
- `npm test` — vitest run across renderer and main suites.

Addresses finding 3 of issue johannesjo#157.

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>