[Fix] (Espryt): re-sync a framebuffer's cross-object masks after an attachment's storage is redefined in place - a mutable texture regenerated on its driver id or a renderbuffer re-storaged on its moved neither the FBO memo's frontend versions nor the backend-id generation, so the pre-handle arm kept the widening masks of the storage the object was attached with; the renderbuffer half of the F-3 scenario asserts on the handle arm only, where the resource record closes D-D2 (found by the F-3 scenarios on the 0x1ff, 0 and pull lanes)

MobileGL/MG_IntegrationTest/Harness/P4aSeamPeek.h

@@ -36,6 +36,12 @@ namespace MGITest {
     // other. Written only on true.
     bool PeekEsprytSamplerHandleArmIsLive(bool* outLive);
 
+    // The same question for the FRAMEBUFFER family (bit 9): true when Espryt consumes
+    // set_framebuffer_state in this process. The renderbuffer half of the F-3 case asserts only
+    // there - on the pre-handle arm a renderbuffer re-storaged while attached moves nothing the
+    // FBO memo reads (D-D2's documented hole, pre-P4a code), and the record is what closes it.
+    bool PeekEsprytFramebufferHandleArmIsLive(bool* outLive);
+
     // ---- the applier's shader-image window, as last received ------------------------------
     //
     // MGPipeApplierState::ShaderImageStart / ShaderImageCount / ShaderImagesSerial. Count is