[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

MobileGL/MG_Backend/DirectGLES/Managers.cpp

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

docs/Disaggregated/README.md

@@ -16,7 +16,7 @@ MGPipe 是 MobileGL 前端（`MG_State` + `MG_Impl`）与后端（`MG_Backend`
 应用 GL 调用
   → MG_Impl（GL 语义、错误、shadow）
   → MG_Impl/Pipe/Tracker：在每条 verb 之前 validate，把变化推成 MGPipe 调用
-  → MGPipeScreen / MGPipeContext（两张函数指针表，76 条调用，单一真相源 PipeCalls.def）
+  → MGPipeScreen / MGPipeContext（两张函数指针表，79 条调用，单一真相源 PipeCalls.def）
       monolith：直调 backend 函数          split：发射器写 SEG_CMD ring → server applier（apply 线程）
   → server 对象表（按 {slot, gen} 句柄索引的数组）+ PipeInputs（后端被推送的状态块）
   → MG_Backend（Espryt / Magma），两个后端的 ring / pool / memo / lowering pass 原样不动