Files
felhom.eu/documentation/audits/DRILL-r379-rollback-2026-08-22/evidence/09-step1-verify.txt
T
admin a8caa0fdde
gates / gates (push) Successful in 17s
R-379/R-380 docs: the failure ladder, the drill record, register housekeeping
07-backup-architecture.md 6.3 gains a dated [DESIGN] paragraph on replay ->
rollback -> hold, including why no engine flag closes it: --single-transaction
makes Postgres atomic, MariaDB DDL is not transactional, so the rollback is the
fix and the flag is a belt.

Drill record for the live walk, including the TWO defects the walk found in the
fix itself (a rollback into a re-created container; an operator route that
cleared the file while the running controller kept refusing) and the ONE
red-proof that PASSED, which is reported rather than omitted.

R-379..R-382 compressed into CLOSED-ITEMS.md. OPEN-ITEMS 330683 -> 325236 bytes.

STATUS.md restates the outcome and names the next operator step.
2026-08-22 18:40:22 +02:00

12 lines
443 B
Plaintext

=== app state:
docmost | Up 29 seconds (healthy)
docmost-redis | Up 39 seconds (healthy)
docmost-postgres | Up 43 seconds (healthy)
=== POST-RESTORE data (must equal the pre-restore state exactly):
4
ALTERED-VALUE-B
8ec1fa8710c5ca08589161a2d930ede24a98c6b8ad3395308a90def21b68be19 -
expected: 4 / ALTERED-VALUE-B / 8ec1fa8710c5ca08589161a2d930ede24a98c6b8ad3395308a90def21b68be19
=== was a hold written? (must be none)
restore_holds = None