feat: replace revision counters with domain state contracts
Use content digests, key fingerprints, binding and trust identities, immutable mutation receipts, and observation tokens instead of state-update ordinals across API, storage, Runtime, and Web contracts. Preserve historical replay and secret material through frozen migrations; preflight uncertain removals before cutover, resume provisioning receipts, validate encrypted migration candidates, and align fresh/upgraded schemas. Include reviewed regression fixes, generated artifacts, and validation evidence.
This commit is contained in:
@@ -181,7 +181,7 @@ Deno.test("Runtime detail keeps trust controls owner-only and conflict-safe", as
|
||||
"new RuntimeRemovalAttempt()",
|
||||
"runtimeRemovalAttempt.operationId()",
|
||||
"operation_id: operationId",
|
||||
"expected_binding_revision: trust.revision",
|
||||
"expected_binding_id: trust.binding_id",
|
||||
"The Backend removes Workspace trust and this Runtime registration as one guarded operation.",
|
||||
"deleteRuntimeConfirmation.trim() !== data.runtimeId",
|
||||
"Delete Runtime registration",
|
||||
|
||||
Reference in New Issue
Block a user