mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
07f1b6ce92
The guardian's modules route and the setup flow's confirm both decide a record's modules, and each had its own copy of what that means: write the preference blob, write the delegated cycle column, invalidate the health score. Two copies of a three-step write drift, and the second one was added by this branch. They share one function now, keyed on the record, which is the carrier the managed-profile work needs. Authentication stays at the routes and stays different on purpose — the guardian route acts on a managed record, the setup routes refuse outright under a switch until a guardian's route into a record's setup lands with the rest of that record's configuration. So does the merge: what the answers imply and what somebody just ticked are different questions about what may be overwritten. The actor's own modules route keeps its own write, because that one is guarded on a concurrency token the record-keyed callers do not carry.