29 lines
980 B
Markdown
29 lines
980 B
Markdown
# Leo Restart-Survival Proof
|
|
|
|
Generated UTC: `2026-07-13T04:26:23.955795+00:00`
|
|
Mode: `live_vps_leoclean_gateway_restart_survival`
|
|
Status: `pass`
|
|
Survives restart: `True`
|
|
|
|
## Safety
|
|
|
|
- Posted to Telegram: `False`
|
|
- Production DB apply ran: `False`
|
|
- DB counts changed: `False`
|
|
- Live profile changed by handler: `False`
|
|
|
|
## Service
|
|
|
|
- Before: `ActiveState=active`, `SubState=running`, `MainPID=2403328`, `NRestarts=0`, `ExecMainStartTimestamp=Sun 2026-07-12 09:14:10 UTC`
|
|
- After: `ActiveState=active`, `SubState=running`, `MainPID=1105322`, `NRestarts=0`, `ExecMainStartTimestamp=Mon 2026-07-13 04:26:31 UTC`
|
|
|
|
## Handler Smoke
|
|
|
|
- Handler skipped: `False`
|
|
- Handler pass runtime: `True`
|
|
- Handler results: `6`
|
|
- Temp profile removed: `True`
|
|
|
|
## Claim Ceiling
|
|
|
|
This proves restart-cycle service recovery plus DB-count stability and no-post handler behavior only when `survives_restart=true`. It does not prove Telegram-visible message delivery, production DB apply, or GCP parity.
|