SQLite projector fails with `no such savepoint: effect_sql_1`

Summary

T3 Code (Alpha) fails while starting a thread turn because the event projector cannot execute its SQLite statement.

Error

effect/sql/SqlError: Failed to execute statement
    at runProjectorForEvent (file:///Applications/T3%20Code%20(Alpha).app/Contents/Resources/app.asar/apps/server/dist/bin.mjs:24154:76)
    at runProjectorForEvent (definition) (Alpha)
    at orchestration.command.thread.turn.start (file:///Applications/T3%20Code%20(Alpha).app/Contents/Resources/app.asar/apps/server/dist/bin.mjs:21774:18) {
  [cause]: effect/sql/SqlError/UnknownError: Failed to execute statement
      at classifySqliteError (file:///Applications/T3%20Code%20(Alpha).app/Contents/Resources/app.asar/node_modules/effect/dist/unstable/sql/SqlError.js:446:10) {
    [cause]: Error: no such savepoint: effect_sql_1
  }
}

Expected behavior

Starting a thread turn should complete without a SQLite savepoint error.

Actual behavior

The turn fails before it can start, with SQLite reporting that savepoint effect_sql_1 does not exist.

Environment

• T3 Code (Alpha)
• macOS (application path: /Applications/T3 Code (Alpha).app)

I don’t yet have reliable reproduction steps beyond encountering the failure when a thread turn starts.

Start at the reported runProjectorForEvent entry point and the orchestration.command.thread.turn.start path in the stack trace, then locate their source files in the repository. Reproduce the thread-turn start failure and trace the SQLite savepoint lifecycle around the projector. Done means starting a thread turn completes without the effect_sql_1 savepoint error.