[Docs, MG_Backend] (Disaggregated): P5c housekeeping - the death-switch scope comment describes the landed ct shape (the NoSession arm only), and the README counts 79 calls after ct/rv

This commit is contained in:
2026-09-17 11:21:39 -04:00
parent c74de6b506
commit ab9250281b
2 changed files with 6 additions and 6 deletions
+5 -5
View File
@@ -248,11 +248,11 @@ namespace MobileGL::MG_Backend::DirectGLES {
}, &death);
return;
}
// P5c merge coordination: while the death notice still rides the mailbox it lands
// HERE, on the apply thread, and every arm's DestroyByLifetimeId probes the client
// allocator. That hop is exactly what ct's object_death record replaces (the sink
// then resolves by the record's handle and the scope dies with the mailbox); until
// ct lands the probes are named debt inside the G6 scope, not unwrapped violations.
// P5c merge coordination: the record arm above carries every death a real split
// sees; what still lands HERE through the mailbox is the NoSession server-only
// fixture arm, whose DestroyByLifetimeId probes the client allocator from the
// apply thread. Those probes ride inside the G6 scope (CONTRACT-P5C §5.2, the
// amended ruling) - named debt that dies with the mailbox hop.
const MG_Pipe::MGPipeFrontendKeyedRegistryScope frontendKeyedRegistry;
#endif
switch (kind) {