mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-07 18:13:23 +09:00
swung0x48
aba329cc53
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.
3.5 KiB
3.5 KiB
P5 / P5b docs close-out, Codex
Date: 2026-09-16. Branch p5b/docs-codex, independent worktree /home/swung/w7/p5b-docs-codex, base 2deca994.
Commit: dab238938eb55eec993d90ce1f5a9b753d8712bb — [Docs] (Disaggregated): record P5 final gate stop and scoped control evidence.
Only docs/Disaggregated/{README,ROADMAP,MEASUREMENTS}.md changed: 102 insertions / 32 deletions. No source, integration worktree, main progress note, device, build or test changes. No repeated tests or adversarial review.
What changed
- README and ROADMAP now distinguish landed P5 code, the historical reduced IPC-frame milestone, the stopped final-head gate, and the P5b real-workload exit. P5.5 is renamed P5b. P6 remains after P5b.
- MEASUREMENTS §27 retains historical joint readings and adds x2, v1-r3 and r2 corrections. Old 511 aborts are 505 class-C plus six P5 StageSnapshotTooNarrow defects fixed by v1-r3. The 27 wrong answers are 22 texture readbacks, three queries, one inspection and one FBO/RBO ReadPixels lifetime path; the last pixel causality remains unisolated.
- §28 replaces maxrec pending with measured 784 B SetVertexAttribDefaults on reduced/OpenRA, the default 4 MiB cap and the SmallRing ledger. Old x2 ringwaits was reclaim evidence, not an actual wait; r2's 1/8 MiB wait/wrap controls are separately attributed. Existing rsp is a lower bound and inproc RSS remains one shared-process measurement.
- §30 records Redmi A/B runner
eec0e836, APK sourcee61d0012, 40 groups / 27 completed / 13 failed; all ten split groups abort before benchmark. Five concise rows preserve useful frame-time readings. No barrier-tax estimate is invented; full tables and per-thread data remain in ab-v1.md. - New §31 records
37fc4fdbfinal gate: builds/G1/unit/reduced ran, E1 own diagnostics passed, then E3(a) 4 pixel failures + 2 designed skips was correctly rejected. Part 2 and Part 4 were not reached. Package, historical joint and APK evidence is not relabeled final merged-head proof. - r2 corrections #5–13 and package acceptance are summarized, including exact library restore, four own E3 pixel/private-log reds, all-skip rejection, REQUIRE_GPU, fresh/nonempty census, production G5 pins and the current-name c1f 15/15 mutation run. No new G1 measurement is claimed for r2. ROADMAP names r1's four remaining corrections, non-verb rsp, illegal reply status and tree-external runner propagation.
Evidence read
Under notes/p5/p5-results: joint-v1.md, x2-v1.md, x2m-v1.md, j0-v3.md, v1-v3.md, ab-v1.md, ap-v1.md, apkci-v1.md, p5-close-codex-review.md. Under notes/p5b/p5b-results: r2-v1.md. Also /home/swung/w7/p5-final-gate.log (741 lines at documentation time), which pins its own source HEAD on line 1 and ends with E3(a)'s selected-skip failure.
Final-gate log SHA-256: 51d15bd11d06851fa9f7934eeac1a162f8db45c8b81dc345dd76e77701c7531c.
Validation and handoff
git diff --check clean; UTF-8/replacement-character and final-newline checks on all three edited files passed. Changes were checked against the cited report tables and the final gate's stopping point. Committer identity before commit: Swung0x48 <swung0x48@outlook.com>; single-line commit without trailers; final tree clean. No binary testing was needed for this documentation-only change.
Integrator can cherry-pick dab23893 onto the evolving merge head. This report does not claim r1 is currently fixed or a later integration gate is complete; those need their own report/head. Existing §26 historical numbers and architecture text are retained. The main progress MD is owned by the integrator and was not edited.