Observed (SE run #633 production rollout, 2026-08-11)
Installer pgschema plan/apply failed or skipped destructive changes on all three peer prod hosts, with different drift per host:
- newhart:
relation "agent_model_denylists_id_seq" does not exist
- victoria:
relation "entity_credibility" does not exist (42P01)
- graybeard: destructive changes skipped — entity_credibility + agent_model_denylists both flagged
Pre-existing drift, unrelated to PR #572, but it means schema apply is effectively a no-op on these hosts and the drift set differs per host — needs an audit (compare each peer memory DB against canonical schema.sql) and a reconciliation plan rather than assuming uniform state.
Evidence
SE #633 step-11 canary reports (agent_chat msgs 1004360-1004376).
Observed (SE run #633 production rollout, 2026-08-11)
Installer pgschema plan/apply failed or skipped destructive changes on all three peer prod hosts, with different drift per host:
relation "agent_model_denylists_id_seq" does not existrelation "entity_credibility" does not exist(42P01)Pre-existing drift, unrelated to PR #572, but it means schema apply is effectively a no-op on these hosts and the drift set differs per host — needs an audit (compare each peer memory DB against canonical schema.sql) and a reconciliation plan rather than assuming uniform state.
Evidence
SE #633 step-11 canary reports (agent_chat msgs 1004360-1004376).