feat(x): Phase 6 — schedulers & sync services boot in the standalone server - #905
Merged
Gagancreates merged 1 commit intoAug 25, 2026
Merged
Conversation
…e server SEPARATION_PLAN.md Phase 6: the headless-safe half of Rowboat's boot moves into core (boot/services.ts) — data repairs (runs migration, code-session backfill), retention sweep, mobile channels, live-note + bg-task schedulers, skills watcher, event processor + consumers, all knowledge sync services (gmail/outlook/calendars/fireflies/granola), graph builder, note tagging, inline tasks, agent runner, agent notes, calendar notifications, meeting prep, chrome-extension sync. Electron main and the standalone rowboat-server now call the same prepareCoreData()/initCoreServices() in the same order — main keeps only client-machine concerns (windows, tray, meeting detection, quick-ask, updater, capture) plus its window fan-out watchers. The standalone entrypoint is no longer a stub: it runs the full core, which is the child process the Phase 7 flip will spawn. Verified: standalone server on an isolated ROWBOAT_WORKDIR boots every scheduler/sync with no Electron (health + RPC answering, clean shutdown); Electron main boots identically to before on the shared module; split-brain lock correctly refused a second host during testing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 6 of SEPARATION_PLAN.md: the headless-safe half of boot extracts to core (
boot/services.ts) — Electron main and the standalone server now run the identical service set in the identical order.In the shared module: data repairs (runs migration, code-session backfill) · retention sweep · mobile channels · live-note + bg-task schedulers · skills watcher · event processor + consumers · every knowledge sync (gmail/outlook/calendars/fireflies/granola) · graph builder · note tagging · inline tasks · agent runner · agent notes · calendar notifications · meeting prep · chrome-extension sync.
Stays in main: windows/tray/quick-ask/updater, meeting detection (mic monitor), capture permissions, and the window fan-out watchers.
The standalone entrypoint is no longer a stub — it runs full core. This is the exact child process the Phase 7 flip spawns.
Verified:
ROWBOAT_WORKDIR: every scheduler/sync boots with no Electron, health + RPC answer, clean shutdown🤖 Generated with Claude Code