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

Verify full and essentials recovery and implement bounded retention tooling
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
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 11:10:50 +02:00
parent 11322a5256
commit a3ca4b708f
16 changed files with 461 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

6
SCOPE.md
View file

@ -146,7 +146,11 @@ Forgejo native primary backup and isolated recovery now pass (45.08 seconds;
[Forgejo primary evidence](docs/evidence/forgejo-scaleway-restore-2026-09-06.json).
Coverage is per asset: net-kingdom-pg and state-hub-db still have no observed
native Barman destination. The Forgejo full-archive helper still targets
Nextcloud; no Forgejo blob/archive destination on Scaleway was evidenced.
Nextcloud. A full archive at `platform-pg/application-archives/forgejo/` now
passed Scaleway retrieval and isolated application recovery. A 273 MiB
Nextcloud essentials candidate also passed reduced recovery without primary
access. Recurring tiered scheduling, quota and owner retention activation
remain RPF-WP-0038-T04.
The account cutover and archive-integrity fix do not establish that coverage.
WP-0029 retains secondary credential invalidation/recovery; its completion
must not be presented as full primary-backup assurance.