feat: enforce schema readiness and optimistic resources

docs/architecture.md

@@ -197,6 +197,12 @@ The first vertical release deliberately supports a small set of endpoints with
 complete stateful semantics. All other imported endpoints remain visibly
 unsupported until their handlers and compatibility tests exist.
 
+Database readiness includes the latest packaged migration version, not merely a
+successful connectivity query. Workers tolerate the documented container-first
+startup sequence by retrying failed claims until migration tables exist.
+Normalized resource writes use compare-and-swap version updates through a typed
+repository, so stale writers receive a domain conflict.
+
 ## Deployment model
 
 One Uvicorn process runs per container. Horizontal replicas coordinate through

docs/original-prompt-gap-plan.md

@@ -29,7 +29,7 @@ live admin report renders the same evidence deterministically.
   LXC, disks, NICs, snapshots, backups, pools, users/groups/roles/ACLs/tokens and
   observed contracts. Preserve version, metadata, timestamps, and cluster-wide
   VMID uniqueness.
-- [ ] Make migration readiness explicit so workers cannot become permanently
+- [x] Make migration readiness explicit so workers cannot become permanently
   unhealthy before schema creation.
 - [x] Match the required `small` profile (one node, two QEMU, one LXC, two
   storages, administrator, completed tasks).