Fence private offhost backups and prove schema6 SMTP state recovery #20
Loading…
Reference in a new issue
No description provided.
Delete branch "ops/offhost-backup-proof-20261101"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Portal dumps now have an operator-only encrypted offhost path: durable private-KV fencing intents, exact owned runtime/private-listener checks before transfer, in-memory S3 credentials, and a dedicated private never-versioned bucket with canonical four-day expiry eligibility.
The post-trial 2026-11-01 02:17:27 UTC snapshot passed exact-object upload/readback, anonymous denial and fresh-vault offline recovery on main4f/schema6. The 32,127-byte ciphertext restores all six pinned SQLx checksums and exactly three sent SMTP rows with first-attempt metadata. Full saved assignment/contact/event and outbox metadata remain unchanged after scratch auth invalidation. The owned trial profile is present with zero active source sessions. Final exact receipt.
Temporary exporter/tasks/listener and scratch PostgreSQL were removed; the producer resumed, journalv114 is clean/released, and live main remained healthy. Permanent mode0600 operator state and private-KV CAS/readbackv5 retain the actual source/image/config/migrations, current cipher and prior schema5 history.
Validation: independent source and actual-receipt review, existing21 focused controller tests, hook syntax checks, and the actual schema5/schema6 capture/recovery checks. The final evidence-only SQL ran against the real restored schema6 object; no additional crypto tests or provider sends were introduced.
API/frontend/provider code is preserved. No unattended schedule is activated. Operator-host/VPN availability remains a coverage constraint, and reboot-safe coverage is not claimed.
Add fenced private offhost backups and verify current schema-5 recoveryto Fence private offhost backups and prove schema6 SMTP state recoveryParent integration verified exact reviewed head
24178c45f7f09b4d3bcced58ef3529625d94a4f9and independently accepted scoped actual evidence. No additional tests or sends were run for integration; full acceptance remains separately tracked for Telegram, chain activation and operator reboot availability. Source merge preserves the pinned live application image4fbe039.