feat(projects): automatically pull clean default branches

[maria-rcks]

Note

Written by gpt-5.6-sol on behalf of Maria

Adds an opt-in Automatically pull setting to each project so clean default-branch checkouts stay current without manual pull prompts. When enabled, T3 Code checks at server startup and during existing background remote-status refreshes, then performs only a fast-forward pull when the checkout has no local changes or commits. Verified with server, web, and contracts typechecks, targeted lint, diff checks, a fresh-database server boot, and direct runtime checks for startup and background safety gates. Built with gpt-5.6-sol in T3 Code through the Codex harness.

---

Note

Medium Risk
Opt-in background and startup git pull can change checkout state and hit the network, but only when gates pass and failures are non-blocking for startup and status refresh.

Overview
Adds an opt-in Automatically pull project setting so enabled checkouts can stay current without manual pulls.

Project model and persistence: New optional autoPull on orchestration project types and project.meta.update; new projects default to false. Migration 0045 adds auto_pull on projection_projects, wired through the decider, in-memory projector, SQL projection pipeline, and snapshot queries.

When pulls run: On server startup (projects.auto-pull after provider-session reconciliation), autoPullProjects loads the shell snapshot and fast-forwards only workspaces where autoPull is true, the repo is on the default branch with upstream, the tree is clean, there are no local commits, and the branch is behind (concurrency 4; failures are warnings). During VCS status refresh, VcsAutoPullPolicy resolves eligibility from the active project by workspace root; maybeAutoPull applies the same gates and refreshes cached status after a successful pull (pull errors do not fail the refresh).

UI and docs: A switch in project settings fans out to all group members; user docs describe behavior and skip conditions. Tests cover meta-update propagation, startup gating, and broadcaster auto-pull.

^{Reviewed by Cursor Bugbot for commit 9ba089e. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add autoPull project setting that pulls clean default branches on startup and status refresh

• Adds an optional autoPull boolean to project commands, events, projection rows, and the SQLite-backed projection repository; migration 045 adds a non-null projection_projects.auto_pull INTEGER column defaulting to 0
• Server startup runs a projects.auto-pull phase that loads project shells and concurrently pulls enabled repositories that are on the default branch, have an upstream, a clean working tree, no local commits ahead, and a positive behind count; failures are logged as warnings and do not abort startup
• VcsStatusBroadcaster evaluates an auto-pull policy on full and remote-only status refreshes, pulling qualifying clean default-branch checkouts and publishing the refreshed status
• The project settings UI renders an "Automatically pull" switch that writes the boolean to all member project records
• Risk: ProjectionProjectDbRowSchema now requires the auto_pull column during decoding; any out-of-tree snapshot readers that do not expect the optional autoPull field on OrchestrationProject or OrchestrationProjectShell must handle its absence

^{Macroscope summarized 9ba089e.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f5895cf. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a cross-cutting automatic Git-pull capability that performs network I/O and can mutate user checkouts during startup and background status refreshes. It also introduces a new product setting and default, so the change requires human review.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

^{You can add or adjust custom eligibility rules. Learn more.}