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

Verify Scaleway primary recovery and distinguish secondary backup coverage
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 00:34:43 +02:00
parent 9269d9d8f4
commit d05c3000c5
10 changed files with 170 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

15
workplans/RPF-WP-0029-backup-credential-default-removal.md
View file

@ -113,3 +113,18 @@ invocations use the integrity checks without editing the host checkout.
Fresh encrypted archive: 5,353,024,293 bytes; 142 repository HEAD entries.
Local drill plaintext and producer temporary files were removed. Owner login
and the two remaining acceptance results above are still required.
## Primary/secondary boundary correction — 2026-09-06
User reaffirmed Scaleway as the primary backup provider. Nextcloud remains the
independent secondary lane. An actual isolated apps-pg recovery from Scaleway
passed in 42.64 seconds, including expected databases and consumer connection
limits; production stayed Ready and scratch resources were deleted. This is
primary database recovery evidence, not Forgejo or Nextcloud recovery proof.
The live primary covers apps-pg/platform-pg/platform-pg-2; forgejo-db has no
Barman destination and the Forgejo full-archive uploader still targets Nextcloud.
Do not conflate this coverage gap with the old-share incident or silently move
archives into a database-owned prefix. WP-0029's secondary acceptance gates
remain explicit. Source/platform assurance records now name the correct primary.