WIP: Rehearse complete D1 data preservation for Human sign-in #42
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/native-d1-rehearsal-20261025"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Human sign-in expands Commons from the existing 15-table baseline or 19-table identity schema to a 25-table schema. This adds opt-in native D1 rehearsals that prove complete preservation before that migration: every original column, row, storage class and multiplicity, plus account derivation, eligibility, credentials, binding tombstones and lineage.
The first rehearsal checks 36 typed values and REST transaction behavior. The graph rehearsal reuses the existing fixture builders and copyPreserved oracle, creates two fresh unbound synthetic databases per declared case, builds schema without replaying seeds, and performs one fixed copy batch. It verifies full source and target schemas, all values, foreign keys and ledger rows; the source must remain unchanged. Default execution is inert. There is no existing-database adoption, automatic write replay, HTTP DELETE, Worker binding or production route change.
Validation:
All five retained graph-test databases, including the empty source from the refused attempt, were separately checked against 185 fresh admitted primary queries and removed once. Individual GET404 checks and the complete account inventory confirm their absence; production was untouched. CI runs offline contracts only. Actual Worker Binding and Human session/resource behavior, a consistent production snapshot/write fence, recovery and live cutover remain separate gates. This PR stays draft and stacked on #40.
Current source CI passed.
Source head:
a9520d13a4009147d9be1db0a62d3f78cf2750d8Tree:
add14df11cc1705ead56bb48d3fdda6929d2610fWIP: Rehearse D1 typed copy and REST transaction behaviorto WIP: Rehearse complete D1 data preservation for Human sign-inView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.