teleo-infrastructure/docs/reports/leo-working-state-20260709/working-leo-cleanup-readback-current.md
twentyOne2x 3351d2d886
Some checks are pending
CI / lint-and-test (push) Waiting to run
Harden Leo apply runbook regression gates
2026-07-10 03:22:17 +02:00

27 lines
840 B
Markdown

# Working Leo Cleanup Readback
Generated UTC: `2026-07-10T01:22:00Z`
Mode: `read_only_cleanup_readback`
## VPS Readback
- Deploy checkout HEAD: `ad343933bf0cbd4ec17f1d75f0c0e648a2f44a1e`
- Last deploy SHA: `ad343933bf0cbd4ec17f1d75f0c0e648a2f44a1e`
- Postgres container: `teleo-pg`
- Gateway service: `active/running`
- Gateway `MainPID`: `1908033`
- Gateway `NRestarts`: `0`
- Gateway start: `Fri 2026-07-10 01:04:22 UTC`
## Cleanup Check
Read-only database-name query for `rehearsal|clone|staging` returned no rows.
- Leftover rehearsal/clone/staging DBs: `[]`
- Production DB mutated by this check: `false`
- Telegram posted by this check: `false`
## Claim Ceiling
This proves no database names matching `rehearsal`, `clone`, or `staging` were present at the time of the check. It does not prove production apply or GCP parity.