ci / test (postgres) (push) Successful in 2m31s
ci / test (sqlite) (push) Successful in 2m8s
ci / image (push) Successful in 59s
ci / test (postgres) (pull_request) Successful in 2m23s
ci / test (sqlite) (pull_request) Successful in 2m4s
ci / image (pull_request) Successful in 9s
An error-page choice released the startup loop before resetting the services, so the loop could start the application and then lose its services while reporting ready. The reset now happens while the loop is still held, and moves the status back to Starting. A SQLite file could vanish between the existence check and the open; with create allowed, the open would put an empty database in its place. Once the file has been seen, connections open read-write only and fail on a missing file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>