coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record successful full offsite Forgejo recovery and remaining custody gate
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
codex 2026-09-06 01:36:39 +02:00
parent 603c2926fa
commit 5567fa979e
11 changed files with 187 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

6
workplans/RPF-WP-0038-forgejo-scaleway-primary-coverage.md
View file

@ -83,3 +83,9 @@ The existing 5.35 GB encrypted verified archive is available in private staging.
Keep Nextcloud's 10 GiB secondary budget separate. The current helper still
uploads only to Nextcloud until this task's full delivery is implemented and
verified; native database backup alone cannot close the workplan.
Secondary capacity observation (not a native-primary acceptance gate): after
the successful full recovery and rejected-fixture DELETE, immediate Nextcloud
metadata still reported 5,234,716,518 free bytes, below one current archive's
5,353,024,293 bytes. Recheck quota and settle bounded archive retention/capacity
with the owning package; do not automatically delete retained good backups.