dev_agentandClaude Opus 5.5 459ee6ec28 Decide the rollback path from applied migration versions ...

The rollback check diffed all of migrations/, so a change to the sqlc
queries in migrations/queries/ sent the operator down the restore path and
discarded household changes made since the pre-deploy point. Compare the
versions in the live database's schema_migrations with the top-level *.sql
files at the previous SHA instead, the rule internal/store/migrate.go
enforces at start-up.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-07 17:54:42 -04:00

..

searxng

Feature 10: Recipe grounding and photos (#78)

2026-10-06 07:27:58 -04:00

systemd

Feature 07: Deployment, identity and backups (#75)

2026-10-05 20:59:47 -04:00

.env.example

Feature 11: Settings home and Admin AI assistant (#86)

2026-10-06 12:45:05 -04:00

compose.dev.yaml

Feature 10: Recipe grounding and photos (#78)

2026-10-06 07:27:58 -04:00

compose.yaml

Feature 10: Recipe grounding and photos (#78)

2026-10-06 07:27:58 -04:00

known_hosts

Feature 07: Deployment, identity and backups (#75)

2026-10-05 20:59:47 -04:00

litestream.yml

Feature 07: Deployment, identity and backups (#75)

2026-10-05 20:59:47 -04:00

RUNBOOK.md

Decide the rollback path from applied migration versions

2026-10-07 17:54:42 -04:00