feat(overlay-sync): wire OverlaySyncService into DI, IPC and renderer gating

.roo/rules.md

@@ -2,9 +2,14 @@
 
 ---
 
+## Never break these
+
+- Never run all tests together. Only work on the ones required for the task.
+- Never run the dev server or any other task that doesn't finish, like watchers and so on..
+- User instructions stay above all. The user is GOD.
+
 ## Prime Workflow
 
-- The Orchestrator always initiates the task and sequences Git (status/commit) → Architect → Ask (if clarification is required) → Debug (bugfix path only) → Code in strict RED then GREEN phases → Git (final commit), immediately scheduling the next delegation with zero idle gaps.
 - Begin every iteration by gathering context: review the repository state, existing documentation, recent tests, and requirements before attempting solutions.
 - Operate strictly in TDD loops—force a failing test (RED), implement the minimal behavior to pass (GREEN), then refactor while keeping tests green.
 - Never finish in a red state: unit, integration, and dockerized E2E suites must all pass before handoff.
@@ -58,15 +63,6 @@
 - Use Command Group tools to run automation and docker workflows; never depend on the user to run tests manually.
 - Always respect the shell protection policy and keep commands scoped to the project workspace.
 
-## Version Control Discipline
-
-- Git mode owns the repository state. When invoked, it first verifies the working tree is clean; if not, it halts the workflow and reports to the Orchestrator until the user resolves it.
-- Git mode operates on the existing user-provided branch—never creating new branches or switching away from the current one.
-- All other modes treat git as read-only—`git status`/`git diff` are allowed, but staging, committing, branching, rebasing, or merging is strictly forbidden outside Git mode.
-- Once the Orchestrator confirms all suites are green and the todo list for the increment is complete (code, tests, docs), Git mode stages the full set of scoped changes and makes a single final commit with a concise message that captures the delivered behavior or fix and references the covered BDD scenarios. Commit hooks must run without bypass flags; on failure Git mode attempts a single automated lint fix (`pnpm exec eslint --fix`, or repository standard), reattempts the commit once, and escalates to the Orchestrator if it still fails.
-- Git mode never merges, rebases, or pushes. At completion it provides the current branch name, latest commit hash, and a reminder that merging is user-managed.
-- Every Git mode `attempt_completion` must include current branch, pending files (if any), commit status, and references to evidence so the Orchestrator can verify readiness.
-
 ## Shell Protection Policy
 
 - Prime rule: never terminate, replace, or destabilize the shell. All writes remain strictly within the project root.