coulomb-social/docs/release/identity-export-release-return-2026-10-31.md
tegwick b1b0a551a5
Some checks failed
Use-case regression gate / usecase-regressions (push) Failing after 6m56s
Verify founder image release and corrected-date recovery export
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a18e2d-f513-7742-b8e7-12af0b744ff3
2026-10-31 08:35:55 +01:00

3.9 KiB

Verified identity and client-export release

Founder execution of proposal 9f1daf6c5fb56b2b4fc9817f28f5ad090c884b0295f7d6f4469e42d48fa8d59f completed at 2026-10-31T07:15:24Z in 99.14 seconds. The durable node receipt and independent read-only verification agree: Helm revision 19 is deployed and one Ready pod is the sole content-PVC writer. The complete deployment specification and cluster/deployment/PVC identities match the proposal. All 80 packaged files match source 23ffe2cf4b214666754a2420558943438e54251a; live image is forgejo.coulomb.social/coulomb/coulomb-social@sha256:522bcd7fce92436765a60c1e4afa2598f3cc40913352153ff1c4319a99ca92ed.

All 12 business tables/92 rows, 86 content files and the complete migration-history fingerprint are unchanged. Migration 0003 and both slug constraints remain applied, with no duplicate slug group. Forty owner pages render and all 40 unsaved-outsider requests are denied. Public health, landing and static checks pass. The installed snapshot helper is dcc8dd2a…, matches the reviewed replacement and passes its server dry-run; paired worker and primary transport hashes remain unchanged.

Fresh recovery and export

The pre-upgrade capture at 07:13:52Z contains the corrected dates and the previous image pin. Its primary version is 1793430889823443; the independent mirror version is 1793431894338230, with retained receipt version 1793431895594035. The unchanged mirror worker's retry retains one ciphertext and one receipt version. An independent reader fetches both exact versions and verifies their hashes and receipt binding. Isolated decryption/restore completes in 5.164 seconds for this already-available workstation environment (not a complete cold-start/operator RTO). All 13 tables/114 rows, sequences and 86 content-file hashes match the capture. The recovered business/migration/content aggregates also match the release's post-date-correction baseline exactly.

The deployed package, without source overlays, exports 85 selected client content/revision files and four record sets with archive-member hashes verified. All source SQL/files remain unchanged; the temporary export ZIP is removed. Both current and previous images render 40 recovered owner pages and deny 40 outsider requests; synthetic viewer fixtures roll back. There are no published container ports or production restore. This proves coherent current-point export, not delivered client offboarding or user acceptance of productive journeys. The previous independently protected recovery kit is retained; it was not replaced by this drill. Its older point is not represented as the new one.

Records and remaining scope

Owner live Helm values, product release-unit source/image and snapshot source now match the verified release. The pending backup delivery bundle was resealed for revision 19 (see backup-operating-delivery-revision19-2026-10-31.json); the older bundle must not be installed. Both timers remain absent/inactive. Full make check after source-pin reconciliation passes 441 tests, zero skips.

RAPPS-WP-0015-T05 is complete. CSOC-WP-0012-T03 and CSOC-WP-0015-T04 remain open for recurring recovery/monitoring/retention/service evidence and productive flow verdicts. Source/rendering reviews, mail ownership, offboarding disposition and Bubble cutover retain their original acceptance gates. The release decision grants no timer activation, expiry, sender/grant changes or cutover.

The frozen node capsule contains the reviewed source files; it does not contain a second copy of manifest.json. Independent verification hashes every frozen file against the committed digest-bound proposal rather than reconstructing a launcher or running execution again. The proposal and return records must be retained together.

Evidence in this directory: identity-export-release-{receipt,independent-postflight, source-provenance,recovery,client-export}-2026-10-31.json, mirror-image-point-native- 2026-10-31.json and identity-export-release-return-2026-10-31.sources.txt.