document the references repair as an operation, and the unified operations block
rename the wiki to Scrinium
correct and dry the whole page set
document the general purpose resource locks
document the db context lock Add the "Db context lock" page covering the server side lease that serializes seeding and migrations of a db context across every application instance: scope, claim/lease/renewal, owner death, the per operation lease duration and where it is passed, and the read-only denial. Link it from the sidebar, Home and the related pages. Align the stale claims elsewhere: a migration start is denied by the lock held by another owner (not by a queued or running operation), the in-process guarantee is exclusive access while the cross instance one is the lock, a dry run holds the lock while skipping exclusive access, the seeding wait is bounded and throws on expiry, the dashboard pairs an open operation with a live lease before reporting a migration running, and Cancelled joins the reachable operation statuses.