fix(server): heal skipped 045 and warn on migration slot collisions

[ImBIOS]

Databases whose journal already occupied ID 45 (forks, nightlies, renumbered branches) silently skip 045_ProjectionProjectsAutoPull: effect's Migrator only runs IDs above the highest recorded one and never compares names. Every project query then fails with no such column: auto_pull and the backend crash-loops at startup without opening a window — the migrator half of #8896, reproduced again by nightly 0.0.39 after #9277.

This adds idempotent repair migration 047 (047_EnsureProjectionProjectsAutoPull) that adds the column only when absent, so it heals affected databases and is a no-op everywhere else. It also logs a loud non-fatal warning naming collided slots on every runMigrations — the production counterpart of the hard failure in scripts/migrate-dev-db.ts. Deliberately non-fatal: refusing to start would brick databases that are otherwise healed (e.g. by this repair migration).

Tests: new 047_EnsureProjectionProjectsAutoPull.test.ts encodes the collision (journal claims 45 under another name, column absent) plus the healthy no-op case; neighboring migration tests (027, 040–042, 046) still pass, typecheck and lint/fmt clean.

Built and verified with OpenCode + Muse Spark.

---

Note

Medium Risk
Changes SQLite schema repair at startup and migration journal behavior; low blast radius (one column, idempotent) but affects every database boot and could mask other slot collisions via warnings only.

Overview
Addresses startup crash-loops when projection_projects.auto_pull is missing because migration 045 was never applied: Effect’s migrator treats any journal row at ID 45 as “done,” so a fork/nightly that claimed slot 45 under another name permanently skips the real ProjectionProjectsAutoPull migration (#8896).

Adds 047_EnsureProjectionProjectsAutoPull, an idempotent repair that adds auto_pull only when absent (no-op on healthy DBs). Registers it in the migration manifest and wires warnOnMigrationSlotCollisions into runMigrations so production logs a non-fatal warning listing slots where the journal name disagrees with this checkout—loud visibility without refusing startup, since repair migrations can still heal the schema.

New tests simulate the collision (fake journal row at 45, column missing) and confirm healing plus repeat-run safety, plus the healthy no-op path.

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

Note

Add migration 047 to heal skipped 045 and warn on slot collisions

• Adds migration 047 to idempotently add the auto_pull column with NOT NULL DEFAULT 0 to projection_projects if it is absent, repairing databases that skipped migration 045.
• Introduces warnOnMigrationSlotCollisions which compares journal entries in effect_sql_migrations against the current manifest and emits a non-fatal warning if slot names differ.
• Behavioral Change: runMigrations now logs a warning when existing migration journal rows use different names for the same numeric slot.

📊 Macroscope summarized 7464886. 2 files reviewed, 1 issue evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[macroscopeapp]

🟠 Highpersistence/Migrations.ts:121

Databases whose journal already has migration ID 47 or a later foreign migration never execute Migration0047, leaving projection_projects.auto_pull absent and causing project queries to fail at startup. Because Migrator.make skips every loader entry with currentId <= latestMigrationId, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/persistence/Migrations.ts around line 121:
Databases whose journal already has migration ID `47` or a later foreign migration never execute `Migration0047`, leaving `projection_projects.auto_pull` absent and causing project queries to fail at startup. Because `Migrator.make` skips every loader entry with `currentId <= latestMigrationId`, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

[macroscopeapp]

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This is a focused, self-contained migration bug fix that restores the already-defined auto_pull column, adds collision diagnostics, and includes targeted tests without introducing a new capability or product-default policy. An unresolved high-severity finding identifies a separate edge case involving journals at migration ID 47 or later; that correctness risk is handled independently from this eligibility assessment.

Not approved because:

• 1 blocking correctness issue found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[ImBIOS]

Databases whose journal already occupied ID 45 (forks, nightlies, renumbered branches) silently skip 045_ProjectionProjectsAutoPull: effect's Migrator only runs IDs above the highest recorded one and never compares names. Every project query then fails with no such column: auto_pull and the backend crash-loops at startup without opening a window — the migrator half of #8896, reproduced again by nightly 0.0.39 after #9277.

This adds idempotent repair migration 047 (047_EnsureProjectionProjectsAutoPull) that adds the column only when absent, so it heals affected databases and is a no-op everywhere else. It also logs a loud non-fatal warning naming collided slots on every runMigrations — the production counterpart of the hard failure in scripts/migrate-dev-db.ts. Deliberately non-fatal: refusing to start would brick databases that are otherwise healed (e.g. by this repair migration).

Tests: new 047_EnsureProjectionProjectsAutoPull.test.ts encodes the collision (journal claims 45 under another name, column absent) plus the healthy no-op case; neighboring migration tests (027, 040–042, 046) still pass, typecheck and lint/fmt clean.

Built and verified with OpenCode + Muse Spark.

---

Note

Medium Risk
Changes SQLite schema repair at startup and migration journal behavior; low blast radius (one column, idempotent) but affects every database boot and could mask other slot collisions via warnings only.

Overview
Addresses startup crash-loops when projection_projects.auto_pull is missing because migration 045 was never applied: Effect’s migrator treats any journal row at ID 45 as “done,” so a fork/nightly that claimed slot 45 under another name permanently skips the real ProjectionProjectsAutoPull migration (#8896).

Adds 047_EnsureProjectionProjectsAutoPull, an idempotent repair that adds auto_pull only when absent (no-op on healthy DBs). Registers it in the migration manifest and wires warnOnMigrationSlotCollisions into runMigrations so production logs a non-fatal warning listing slots where the journal name disagrees with this checkout—loud visibility without refusing startup, since repair migrations can still heal the schema.

New tests simulate the collision (fake journal row at 45, column missing) and confirm healing plus repeat-run safety, plus the healthy no-op path.

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

Note

Add migration 047 to heal skipped 045 and warn on slot collisions

• Adds migration 047 to idempotently add the auto_pull column with NOT NULL DEFAULT 0 to projection_projects if it is absent, repairing databases that skipped migration 045.
• Introduces warnOnMigrationSlotCollisions which compares journal entries in effect_sql_migrations against the current manifest and emits a non-fatal warning if slot names differ.
• Behavioral Change: runMigrations now logs a warning when existing migration journal rows use different names for the same numeric slot.

📊 Macroscope summarized 7464886. 2 files reviewed, 1 issue evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[macroscopeapp]

🟠 Highpersistence/Migrations.ts:121

Databases whose journal already has migration ID 47 or a later foreign migration never execute Migration0047, leaving projection_projects.auto_pull absent and causing project queries to fail at startup. Because Migrator.make skips every loader entry with currentId <= latestMigrationId, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/persistence/Migrations.ts around line 121:
Databases whose journal already has migration ID `47` or a later foreign migration never execute `Migration0047`, leaving `projection_projects.auto_pull` absent and causing project queries to fail at startup. Because `Migrator.make` skips every loader entry with `currentId <= latestMigrationId`, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

[macroscopeapp]

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This is a focused, self-contained migration bug fix that restores the already-defined auto_pull column, adds collision diagnostics, and includes targeted tests without introducing a new capability or product-default policy. An unresolved high-severity finding identifies a separate edge case involving journals at migration ID 47 or later; that correctness risk is handled independently from this eligibility assessment.

Not approved because:

• 1 blocking correctness issue found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[ImBIOS]

Databases whose journal already occupied ID 45 (forks, nightlies, renumbered branches) silently skip 045_ProjectionProjectsAutoPull: effect's Migrator only runs IDs above the highest recorded one and never compares names. Every project query then fails with no such column: auto_pull and the backend crash-loops at startup without opening a window — the migrator half of #8896, reproduced again by nightly 0.0.39 after #9277.

This adds idempotent repair migration 047 (047_EnsureProjectionProjectsAutoPull) that adds the column only when absent, so it heals affected databases and is a no-op everywhere else. It also logs a loud non-fatal warning naming collided slots on every runMigrations — the production counterpart of the hard failure in scripts/migrate-dev-db.ts. Deliberately non-fatal: refusing to start would brick databases that are otherwise healed (e.g. by this repair migration).

Tests: new 047_EnsureProjectionProjectsAutoPull.test.ts encodes the collision (journal claims 45 under another name, column absent) plus the healthy no-op case; neighboring migration tests (027, 040–042, 046) still pass, typecheck and lint/fmt clean.

Built and verified with OpenCode + Muse Spark.

---

Note

Medium Risk
Changes SQLite schema repair at startup and migration journal behavior; low blast radius (one column, idempotent) but affects every database boot and could mask other slot collisions via warnings only.

Overview
Addresses startup crash-loops when projection_projects.auto_pull is missing because migration 045 was never applied: Effect’s migrator treats any journal row at ID 45 as “done,” so a fork/nightly that claimed slot 45 under another name permanently skips the real ProjectionProjectsAutoPull migration (#8896).

Adds 047_EnsureProjectionProjectsAutoPull, an idempotent repair that adds auto_pull only when absent (no-op on healthy DBs). Registers it in the migration manifest and wires warnOnMigrationSlotCollisions into runMigrations so production logs a non-fatal warning listing slots where the journal name disagrees with this checkout—loud visibility without refusing startup, since repair migrations can still heal the schema.

New tests simulate the collision (fake journal row at 45, column missing) and confirm healing plus repeat-run safety, plus the healthy no-op path.

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

Note

Add migration 047 to heal skipped 045 and warn on slot collisions

• Adds migration 047 to idempotently add the auto_pull column with NOT NULL DEFAULT 0 to projection_projects if it is absent, repairing databases that skipped migration 045.
• Introduces warnOnMigrationSlotCollisions which compares journal entries in effect_sql_migrations against the current manifest and emits a non-fatal warning if slot names differ.
• Behavioral Change: runMigrations now logs a warning when existing migration journal rows use different names for the same numeric slot.

📊 Macroscope summarized 7464886. 2 files reviewed, 1 issue evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[macroscopeapp]

🟠 Highpersistence/Migrations.ts:121

Databases whose journal already has migration ID 47 or a later foreign migration never execute Migration0047, leaving projection_projects.auto_pull absent and causing project queries to fail at startup. Because Migrator.make skips every loader entry with currentId <= latestMigrationId, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/persistence/Migrations.ts around line 121:
Databases whose journal already has migration ID `47` or a later foreign migration never execute `Migration0047`, leaving `projection_projects.auto_pull` absent and causing project queries to fail at startup. Because `Migrator.make` skips every loader entry with `currentId <= latestMigrationId`, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

[macroscopeapp]

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This is a focused, self-contained migration bug fix that restores the already-defined auto_pull column, adds collision diagnostics, and includes targeted tests without introducing a new capability or product-default policy. An unresolved high-severity finding identifies a separate edge case involving journals at migration ID 47 or later; that correctness risk is handled independently from this eligibility assessment.

Not approved because:

• 1 blocking correctness issue found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[ImBIOS]

Databases whose journal already occupied ID 45 (forks, nightlies, renumbered branches) silently skip 045_ProjectionProjectsAutoPull: effect's Migrator only runs IDs above the highest recorded one and never compares names. Every project query then fails with no such column: auto_pull and the backend crash-loops at startup without opening a window — the migrator half of #8896, reproduced again by nightly 0.0.39 after #9277.

This adds idempotent repair migration 047 (047_EnsureProjectionProjectsAutoPull) that adds the column only when absent, so it heals affected databases and is a no-op everywhere else. It also logs a loud non-fatal warning naming collided slots on every runMigrations — the production counterpart of the hard failure in scripts/migrate-dev-db.ts. Deliberately non-fatal: refusing to start would brick databases that are otherwise healed (e.g. by this repair migration).

Tests: new 047_EnsureProjectionProjectsAutoPull.test.ts encodes the collision (journal claims 45 under another name, column absent) plus the healthy no-op case; neighboring migration tests (027, 040–042, 046) still pass, typecheck and lint/fmt clean.

Built and verified with OpenCode + Muse Spark.

---

Note

Medium Risk
Changes SQLite schema repair at startup and migration journal behavior; low blast radius (one column, idempotent) but affects every database boot and could mask other slot collisions via warnings only.

Overview
Addresses startup crash-loops when projection_projects.auto_pull is missing because migration 045 was never applied: Effect’s migrator treats any journal row at ID 45 as “done,” so a fork/nightly that claimed slot 45 under another name permanently skips the real ProjectionProjectsAutoPull migration (#8896).

Adds 047_EnsureProjectionProjectsAutoPull, an idempotent repair that adds auto_pull only when absent (no-op on healthy DBs). Registers it in the migration manifest and wires warnOnMigrationSlotCollisions into runMigrations so production logs a non-fatal warning listing slots where the journal name disagrees with this checkout—loud visibility without refusing startup, since repair migrations can still heal the schema.

New tests simulate the collision (fake journal row at 45, column missing) and confirm healing plus repeat-run safety, plus the healthy no-op path.

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

Note

Add migration 047 to heal skipped 045 and warn on slot collisions

• Adds migration 047 to idempotently add the auto_pull column with NOT NULL DEFAULT 0 to projection_projects if it is absent, repairing databases that skipped migration 045.
• Introduces warnOnMigrationSlotCollisions which compares journal entries in effect_sql_migrations against the current manifest and emits a non-fatal warning if slot names differ.
• Behavioral Change: runMigrations now logs a warning when existing migration journal rows use different names for the same numeric slot.

📊 Macroscope summarized 7464886. 2 files reviewed, 1 issue evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[macroscopeapp]

🟠 Highpersistence/Migrations.ts:121

Databases whose journal already has migration ID 47 or a later foreign migration never execute Migration0047, leaving projection_projects.auto_pull absent and causing project queries to fail at startup. Because Migrator.make skips every loader entry with currentId <= latestMigrationId, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/persistence/Migrations.ts around line 121:
Databases whose journal already has migration ID `47` or a later foreign migration never execute `Migration0047`, leaving `projection_projects.auto_pull` absent and causing project queries to fail at startup. Because `Migrator.make` skips every loader entry with `currentId <= latestMigrationId`, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

[macroscopeapp]

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This is a focused, self-contained migration bug fix that restores the already-defined auto_pull column, adds collision diagnostics, and includes targeted tests without introducing a new capability or product-default policy. An unresolved high-severity finding identifies a separate edge case involving journals at migration ID 47 or later; that correctness risk is handled independently from this eligibility assessment.

Not approved because:

• 1 blocking correctness issue found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[ImBIOS]

Databases whose journal already occupied ID 45 (forks, nightlies, renumbered branches) silently skip 045_ProjectionProjectsAutoPull: effect's Migrator only runs IDs above the highest recorded one and never compares names. Every project query then fails with no such column: auto_pull and the backend crash-loops at startup without opening a window — the migrator half of #8896, reproduced again by nightly 0.0.39 after #9277.

This adds idempotent repair migration 047 (047_EnsureProjectionProjectsAutoPull) that adds the column only when absent, so it heals affected databases and is a no-op everywhere else. It also logs a loud non-fatal warning naming collided slots on every runMigrations — the production counterpart of the hard failure in scripts/migrate-dev-db.ts. Deliberately non-fatal: refusing to start would brick databases that are otherwise healed (e.g. by this repair migration).

Tests: new 047_EnsureProjectionProjectsAutoPull.test.ts encodes the collision (journal claims 45 under another name, column absent) plus the healthy no-op case; neighboring migration tests (027, 040–042, 046) still pass, typecheck and lint/fmt clean.

Built and verified with OpenCode + Muse Spark.

---

Note

Medium Risk
Changes SQLite schema repair at startup and migration journal behavior; low blast radius (one column, idempotent) but affects every database boot and could mask other slot collisions via warnings only.

Overview
Addresses startup crash-loops when projection_projects.auto_pull is missing because migration 045 was never applied: Effect’s migrator treats any journal row at ID 45 as “done,” so a fork/nightly that claimed slot 45 under another name permanently skips the real ProjectionProjectsAutoPull migration (#8896).

Adds 047_EnsureProjectionProjectsAutoPull, an idempotent repair that adds auto_pull only when absent (no-op on healthy DBs). Registers it in the migration manifest and wires warnOnMigrationSlotCollisions into runMigrations so production logs a non-fatal warning listing slots where the journal name disagrees with this checkout—loud visibility without refusing startup, since repair migrations can still heal the schema.

New tests simulate the collision (fake journal row at 45, column missing) and confirm healing plus repeat-run safety, plus the healthy no-op path.

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

Note

Add migration 047 to heal skipped 045 and warn on slot collisions

• Adds migration 047 to idempotently add the auto_pull column with NOT NULL DEFAULT 0 to projection_projects if it is absent, repairing databases that skipped migration 045.
• Introduces warnOnMigrationSlotCollisions which compares journal entries in effect_sql_migrations against the current manifest and emits a non-fatal warning if slot names differ.
• Behavioral Change: runMigrations now logs a warning when existing migration journal rows use different names for the same numeric slot.

📊 Macroscope summarized 7464886. 2 files reviewed, 1 issue evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[macroscopeapp]

🟠 Highpersistence/Migrations.ts:121

Databases whose journal already has migration ID 47 or a later foreign migration never execute Migration0047, leaving projection_projects.auto_pull absent and causing project queries to fail at startup. Because Migrator.make skips every loader entry with currentId <= latestMigrationId, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/persistence/Migrations.ts around line 121:
Databases whose journal already has migration ID `47` or a later foreign migration never execute `Migration0047`, leaving `projection_projects.auto_pull` absent and causing project queries to fail at startup. Because `Migrator.make` skips every loader entry with `currentId <= latestMigrationId`, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

[macroscopeapp]

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This is a focused, self-contained migration bug fix that restores the already-defined auto_pull column, adds collision diagnostics, and includes targeted tests without introducing a new capability or product-default policy. An unresolved high-severity finding identifies a separate edge case involving journals at migration ID 47 or later; that correctness risk is handled independently from this eligibility assessment.

Not approved because:

• 1 blocking correctness issue found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[ImBIOS]

Databases whose journal already occupied ID 45 (forks, nightlies, renumbered branches) silently skip 045_ProjectionProjectsAutoPull: effect's Migrator only runs IDs above the highest recorded one and never compares names. Every project query then fails with no such column: auto_pull and the backend crash-loops at startup without opening a window — the migrator half of #8896, reproduced again by nightly 0.0.39 after #9277.

This adds idempotent repair migration 047 (047_EnsureProjectionProjectsAutoPull) that adds the column only when absent, so it heals affected databases and is a no-op everywhere else. It also logs a loud non-fatal warning naming collided slots on every runMigrations — the production counterpart of the hard failure in scripts/migrate-dev-db.ts. Deliberately non-fatal: refusing to start would brick databases that are otherwise healed (e.g. by this repair migration).

Tests: new 047_EnsureProjectionProjectsAutoPull.test.ts encodes the collision (journal claims 45 under another name, column absent) plus the healthy no-op case; neighboring migration tests (027, 040–042, 046) still pass, typecheck and lint/fmt clean.

Built and verified with OpenCode + Muse Spark.

---

Note

Medium Risk
Changes SQLite schema repair at startup and migration journal behavior; low blast radius (one column, idempotent) but affects every database boot and could mask other slot collisions via warnings only.

Overview
Addresses startup crash-loops when projection_projects.auto_pull is missing because migration 045 was never applied: Effect’s migrator treats any journal row at ID 45 as “done,” so a fork/nightly that claimed slot 45 under another name permanently skips the real ProjectionProjectsAutoPull migration (#8896).

Adds 047_EnsureProjectionProjectsAutoPull, an idempotent repair that adds auto_pull only when absent (no-op on healthy DBs). Registers it in the migration manifest and wires warnOnMigrationSlotCollisions into runMigrations so production logs a non-fatal warning listing slots where the journal name disagrees with this checkout—loud visibility without refusing startup, since repair migrations can still heal the schema.

New tests simulate the collision (fake journal row at 45, column missing) and confirm healing plus repeat-run safety, plus the healthy no-op path.

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

Note

Add migration 047 to heal skipped 045 and warn on slot collisions

• Adds migration 047 to idempotently add the auto_pull column with NOT NULL DEFAULT 0 to projection_projects if it is absent, repairing databases that skipped migration 045.
• Introduces warnOnMigrationSlotCollisions which compares journal entries in effect_sql_migrations against the current manifest and emits a non-fatal warning if slot names differ.
• Behavioral Change: runMigrations now logs a warning when existing migration journal rows use different names for the same numeric slot.

📊 Macroscope summarized 7464886. 2 files reviewed, 1 issue evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[macroscopeapp]

🟠 Highpersistence/Migrations.ts:121

Databases whose journal already has migration ID 47 or a later foreign migration never execute Migration0047, leaving projection_projects.auto_pull absent and causing project queries to fail at startup. Because Migrator.make skips every loader entry with currentId <= latestMigrationId, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/persistence/Migrations.ts around line 121:
Databases whose journal already has migration ID `47` or a later foreign migration never execute `Migration0047`, leaving `projection_projects.auto_pull` absent and causing project queries to fail at startup. Because `Migrator.make` skips every loader entry with `currentId <= latestMigrationId`, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

[macroscopeapp]

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This is a focused, self-contained migration bug fix that restores the already-defined auto_pull column, adds collision diagnostics, and includes targeted tests without introducing a new capability or product-default policy. An unresolved high-severity finding identifies a separate edge case involving journals at migration ID 47 or later; that correctness risk is handled independently from this eligibility assessment.

Not approved because:

• 1 blocking correctness issue found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[ImBIOS]

Databases whose journal already occupied ID 45 (forks, nightlies, renumbered branches) silently skip 045_ProjectionProjectsAutoPull: effect's Migrator only runs IDs above the highest recorded one and never compares names. Every project query then fails with no such column: auto_pull and the backend crash-loops at startup without opening a window — the migrator half of #8896, reproduced again by nightly 0.0.39 after #9277.

This adds idempotent repair migration 047 (047_EnsureProjectionProjectsAutoPull) that adds the column only when absent, so it heals affected databases and is a no-op everywhere else. It also logs a loud non-fatal warning naming collided slots on every runMigrations — the production counterpart of the hard failure in scripts/migrate-dev-db.ts. Deliberately non-fatal: refusing to start would brick databases that are otherwise healed (e.g. by this repair migration).

Tests: new 047_EnsureProjectionProjectsAutoPull.test.ts encodes the collision (journal claims 45 under another name, column absent) plus the healthy no-op case; neighboring migration tests (027, 040–042, 046) still pass, typecheck and lint/fmt clean.

Built and verified with OpenCode + Muse Spark.

---

Note

Medium Risk
Changes SQLite schema repair at startup and migration journal behavior; low blast radius (one column, idempotent) but affects every database boot and could mask other slot collisions via warnings only.

Overview
Addresses startup crash-loops when projection_projects.auto_pull is missing because migration 045 was never applied: Effect’s migrator treats any journal row at ID 45 as “done,” so a fork/nightly that claimed slot 45 under another name permanently skips the real ProjectionProjectsAutoPull migration (#8896).

Adds 047_EnsureProjectionProjectsAutoPull, an idempotent repair that adds auto_pull only when absent (no-op on healthy DBs). Registers it in the migration manifest and wires warnOnMigrationSlotCollisions into runMigrations so production logs a non-fatal warning listing slots where the journal name disagrees with this checkout—loud visibility without refusing startup, since repair migrations can still heal the schema.

New tests simulate the collision (fake journal row at 45, column missing) and confirm healing plus repeat-run safety, plus the healthy no-op path.

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

Note

Add migration 047 to heal skipped 045 and warn on slot collisions

• Adds migration 047 to idempotently add the auto_pull column with NOT NULL DEFAULT 0 to projection_projects if it is absent, repairing databases that skipped migration 045.
• Introduces warnOnMigrationSlotCollisions which compares journal entries in effect_sql_migrations against the current manifest and emits a non-fatal warning if slot names differ.
• Behavioral Change: runMigrations now logs a warning when existing migration journal rows use different names for the same numeric slot.

📊 Macroscope summarized 7464886. 2 files reviewed, 1 issue evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[macroscopeapp]

🟠 Highpersistence/Migrations.ts:121

Databases whose journal already has migration ID 47 or a later foreign migration never execute Migration0047, leaving projection_projects.auto_pull absent and causing project queries to fail at startup. Because Migrator.make skips every loader entry with currentId <= latestMigrationId, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/persistence/Migrations.ts around line 121:
Databases whose journal already has migration ID `47` or a later foreign migration never execute `Migration0047`, leaving `projection_projects.auto_pull` absent and causing project queries to fail at startup. Because `Migrator.make` skips every loader entry with `currentId <= latestMigrationId`, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

[macroscopeapp]

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This is a focused, self-contained migration bug fix that restores the already-defined auto_pull column, adds collision diagnostics, and includes targeted tests without introducing a new capability or product-default policy. An unresolved high-severity finding identifies a separate edge case involving journals at migration ID 47 or later; that correctness risk is handled independently from this eligibility assessment.

Not approved because:

• 1 blocking correctness issue found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[ImBIOS]

Databases whose journal already occupied ID 45 (forks, nightlies, renumbered branches) silently skip 045_ProjectionProjectsAutoPull: effect's Migrator only runs IDs above the highest recorded one and never compares names. Every project query then fails with no such column: auto_pull and the backend crash-loops at startup without opening a window — the migrator half of #8896, reproduced again by nightly 0.0.39 after #9277.

This adds idempotent repair migration 047 (047_EnsureProjectionProjectsAutoPull) that adds the column only when absent, so it heals affected databases and is a no-op everywhere else. It also logs a loud non-fatal warning naming collided slots on every runMigrations — the production counterpart of the hard failure in scripts/migrate-dev-db.ts. Deliberately non-fatal: refusing to start would brick databases that are otherwise healed (e.g. by this repair migration).

Tests: new 047_EnsureProjectionProjectsAutoPull.test.ts encodes the collision (journal claims 45 under another name, column absent) plus the healthy no-op case; neighboring migration tests (027, 040–042, 046) still pass, typecheck and lint/fmt clean.

Built and verified with OpenCode + Muse Spark.

---

Note

Medium Risk
Changes SQLite schema repair at startup and migration journal behavior; low blast radius (one column, idempotent) but affects every database boot and could mask other slot collisions via warnings only.

Overview
Addresses startup crash-loops when projection_projects.auto_pull is missing because migration 045 was never applied: Effect’s migrator treats any journal row at ID 45 as “done,” so a fork/nightly that claimed slot 45 under another name permanently skips the real ProjectionProjectsAutoPull migration (#8896).

Adds 047_EnsureProjectionProjectsAutoPull, an idempotent repair that adds auto_pull only when absent (no-op on healthy DBs). Registers it in the migration manifest and wires warnOnMigrationSlotCollisions into runMigrations so production logs a non-fatal warning listing slots where the journal name disagrees with this checkout—loud visibility without refusing startup, since repair migrations can still heal the schema.

New tests simulate the collision (fake journal row at 45, column missing) and confirm healing plus repeat-run safety, plus the healthy no-op path.

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

Note

Add migration 047 to heal skipped 045 and warn on slot collisions

• Adds migration 047 to idempotently add the auto_pull column with NOT NULL DEFAULT 0 to projection_projects if it is absent, repairing databases that skipped migration 045.
• Introduces warnOnMigrationSlotCollisions which compares journal entries in effect_sql_migrations against the current manifest and emits a non-fatal warning if slot names differ.
• Behavioral Change: runMigrations now logs a warning when existing migration journal rows use different names for the same numeric slot.

📊 Macroscope summarized 7464886. 2 files reviewed, 1 issue evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[macroscopeapp]

🟠 Highpersistence/Migrations.ts:121

Databases whose journal already has migration ID 47 or a later foreign migration never execute Migration0047, leaving projection_projects.auto_pull absent and causing project queries to fail at startup. Because Migrator.make skips every loader entry with currentId <= latestMigrationId, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/persistence/Migrations.ts around line 121:
Databases whose journal already has migration ID `47` or a later foreign migration never execute `Migration0047`, leaving `projection_projects.auto_pull` absent and causing project queries to fail at startup. Because `Migrator.make` skips every loader entry with `currentId <= latestMigrationId`, this repair must run outside the max-ID-gated migrator path (or otherwise explicitly handle collided journals).

[macroscopeapp]

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This is a focused, self-contained migration bug fix that restores the already-defined auto_pull column, adds collision diagnostics, and includes targeted tests without introducing a new capability or product-default policy. An unresolved high-severity finding identifies a separate edge case involving journals at migration ID 47 or later; that correctness risk is handled independently from this eligibility assessment.

Not approved because:

• 1 blocking correctness issue found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}