2 Commits

Include renames

Author	SHA1	Message	Date
swung0x48	5617c5c3b3	[MG_IntegrationTest, docs] (P7): the texture upload shape becomes a gate, with the view remap inside the workload ... P3b/P4b R-11 / D-D4, landing under the P7 program (PLAN-PH-P34B-P7.md 1.2, wave 2-D package D2). P4a recorded the emission shape rather than gating it because the per-storage-owner cursor with view/owner remapping was the next phase's and gating an unfinished shape pins a non-answer. That work landed, so the RecordProperty block is now EXPECT_EQ against a gold row MEASURED on this cursor, and the workload carries a third texture written through a glTextureView so the remap is inside the counted window. The gold row, identical on monolith / inproc / spawn / tcp: emit=9 box=9 rect=0 jobs=9, client emitter 9 keyed on the workload constants by static_assert. P4a's emit=6 box=6 rect=0 jobs=6 was a two-texture workload with no client emitter and is not comparable. The client half is read from MGPipeTextureEmitter::SubDataCount() rather than from ctu=, and that is a correction: under spawn and tcp the two roles are two processes whose PipeStats windows close on different Present cadences (measured ctu=13 against emit=9, and usually not yet written when the case reads), so ctu == emit is not a well-posed comparison there. The log field is kept as a record and asserted only where the transport says the two are window-aligned - asking the NUMBER was the first mistake, because the server publishes a readable ctu=0 under spawn and the comparison silently became 0 == 9. PipeStatsWindow gains LastFromClientLog/LastFromServerLog. Split/spawn/tcp arms added as explicit per-arm blocks rather than through mgl_itest_register_split_arms: the macro hands every arm the shared environment, and this case needs a lane marker, PipeStats period 1, a push mask and above all a MOBILEGL_LOG_FILE_PATH private to the arm - the library opens the log "w", so two entries sharing a path truncate each other and the failure looks exactly like "the counter was never emitted". Red-once (R-16): the prescribed flip of summedArea*4 >= unionArea*3 leaves the gate GREEN, and that is a finding. Two gates downstream dominate it - the server needs dirtyRectCount >= 2, and UnpackRingAvailable() zeroes the rect list by design ("one box, one job", the existing Mali-cliff mitigation). So rect=0 is the policy's intended output, not an accident of the scatter pattern. The red-once that bites splits the union box in two AND disables the unpack ring: box=6 rect=3 jobs=12 against the gold, while 26 pixel cases stay green. Four attempts and their reasons are in the note. The Mali frame-time delta D-D4 asks for beside the gold is NOT schedulable - one Redmi, an Adreno, no Mali part - and is recorded as a declared deviation in the scenario header and MEASUREMENTS.md 13.3 rather than modelled. Also corrects the three places that said the client emitter had not landed: the scenario header, the CMake probe's comment, and gates-v1.md's re-run table. TextureEmit.h's EmitOneLevel has been incrementing it.	2026-09-22 17:31:51 -04:00
swung0x48	aba329cc53	[Docs] (Disaggregated): P6's plan and contract draft; the working notes move from a local directory into the repository ... Two things land together: the plan and contract draft P6 needs before it starts, and the working notes that until now existed on exactly one machine. 1. P6's plan and contract draft (neither started; not one line of code) docs/Disaggregated/P6-SPAWN-PLAN.md the package plan docs/Disaggregated/P6-CONTRACT-DRAFT.md the contract draft (moves to MG_Remote/CONTRACT-P6.md when c6 lands) The three findings that mattered, all written into the documents: a. P6 is SMALLER than its roadmap cell suggests. The transport primitives are already in the tree and already tested: SocketDoorbell including hangup detection and the two lost-wakeup fences (Doorbell.cpp:211-360, four cases in FdPassingTest), SCM_RIGHTS fd passing, ShmSegment::Adopt, and the SurfaceOp / WindowKind schema already defined in protocol.fbs. inproc uses a real second shm mapping rather than an alias, and SessionRings.h:22-28 says that was done so today is not the first time it runs. P6 is assembly plus a control plane plus a process, not "write a socket transport". b. The evidence for "P6 is only a transport swap" has EXPIRED. It was bought by P5c, whose audit found 59 direct memory accesses in a tree that already looked clean. P5e changed the tree again. So the first package, a6, is a read-only audit that writes no code, and every contract row that depends on it is marked PENDING a6 rather than decided in advance. c. P6 does not get a game running on the phone. ANativeWindow* is meaningless in the child, and protocol.fbs:186-196's own comment says Android transfers the window out of band - that band is P12. P6 lands pbuffer / surfaceless / offscreen, which is what HeadlessGL, the split-equivalent lane and trace replay need, and which is exactly what P6's own exit gate measures. A real window reaching the server is a named refusal. This gets its own section because "P6 is done" would otherwise read as "the game runs now". The contract adds rule G: a role may not name a process-local handle. It extends P5c's rule E (a role may not name the other role's memory) from memory to identity - EGLDisplay / EGLSurface / EGLContext / ANativeWindow* / fd number / pid / mapped address either cross as a token this contract defines or they do not cross, and a descriptor crosses only through SCM_RIGHTS, where the kernel renumbers it. What P5e left for P6 gets its own section. The latch semantics are already designed (ARCHITECTURE.md:504) and are copied unchanged. What is new is that after run-ahead the client no longer waits while the peer process can DIE: the client holds records that were published and will never be applied, and Android's freezer suspends the child without closing anything. So slow and dead must be distinguishable WITHOUT a timeout threshold. That is P6's only new design; everything else is carriage. It shares a predicate with E1's outstanding re-specification (ID-122), and the two should be designed together. Two gates carried over from P5e's lessons: G2 requires integration-spawn's test-name set to match integration-split's name for name, because a differing set means the lane is quietly running less; and the arm-proof gate requires every entry to record the child pid and transport=spawn in its OWN private log - ID-124 established that this kind of false green really happens, and a spawn lane that actually ran monolith would pass every other gate. S2's shape must be settled before it is written, and the document says why: E1 is the cautionary case. 2. The working notes move into the repository (docs/Disaggregated/notes/, 415 .md files) ROADMAP / CURRENT_STAGE_PROGRESS / MEASUREMENTS cite ruling numbers, audit line numbers and the provenance of gate figures from ~/w7/notes/, a directory that exists on one machine and is under no version control. A record cited hundreds of times that lives only locally is not a record, so it moves in whole, with its directory structure intact. Only .md moves. Scripts, run logs, census and gate result JSON, patches, APKs and nm dumps stay where they are: they are evidence DATA rather than documents - large, regenerated per run, and mostly carrying absolute paths and device serials that mean something only on the machine that produced them. The mapping and this split are written in docs/Disaggregated/notes/README.md. Two exceptions are recorded there too: P6's BRIEF has been promoted to a first-class document and keeps no copy under notes/, so the two cannot drift apart; and recovered/ holds material salvaged from failed workflow runs, which may duplicate the like-named phase directories and is kept because a few of those were the only complete version at the time. CI's citation lint takes docs/Disaggregated/*.md only (non-recursive), and notes/ is deliberately outside it: those notes' file:line citations were written against their own code heads, and resolving them against today's HEAD would fail wholesale - which is not an error, it is their correct state as a historical record. To check one, use the revision it declares (--rev). 3. Inconsistencies fixed in passing - README.md's status line still said P5e was in progress while the stage table already said closed. - CURRENT_STAGE_PROGRESS's next-step item 1 still listed the exit gate as pending, though (a) and (b) were run in the previous commit; rewritten to closed plus the one item that actually remains (E1). - ROADMAP's P6 row still had the pre-phase plan in three of its cells; it now carries the package order, the scope boundary and the two new gates. Checked with check_doc_citations.py: 125 citations across docs/Disaggregated/*.md, 0 problems.	2026-09-18 23:31:39 -04:00