mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-20 00:11:56 +09:00
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.
40 lines
2.2 KiB
Markdown
40 lines
2.2 KiB
Markdown
# apkci v1 result
|
|
|
|
## Diagnosis
|
|
|
|
Run 35114525520 failed before compilation because `android-actions/setup-android@v4` drifted to cmdline-tools `14742923` (20.0) while its default `packages` input still requested the removed legacy `tools` package alongside `platform-tools`. Every `Setup Android SDK` step therefore failed at `sdkmanager tools`.
|
|
|
|
## `github/dev` check
|
|
|
|
`github/dev` did not contain a fix for this failure. Its recent workflow history was `5d51372c`, `bf376b23`, and `00a326ef`; the only `apk.yml` diff from the source branch removed the temporary `feat/disaggregated` push trigger. Nothing was ported from `dev`.
|
|
|
|
## Change
|
|
|
|
Commit `94ce2ee7` adds these inputs to all three `android-actions/setup-android@v4` steps in `.github/workflows/apk.yml`:
|
|
|
|
```yaml
|
|
packages: platform-tools
|
|
cmdline-tools-version: 13114758
|
|
```
|
|
|
|
`13114758` is cmdline-tools 19, the newest known-good release documented by the action from the supplied choices. The explicit package list drops only the missing legacy `tools` package. License handling, the temporary branch trigger, build targets, AVD setup, and retrace cases are unchanged. `.github/workflows/test.yml` does not use `android-actions/setup-android@v4`.
|
|
|
|
Diff stat:
|
|
|
|
```text
|
|
.github/workflows/apk.yml | 6 ++++++
|
|
1 file changed, 6 insertions(+)
|
|
```
|
|
|
|
## Validation
|
|
|
|
- Parsed `.github/workflows/apk.yml` successfully with `yaml.safe_load` using PyYAML in a temporary environment.
|
|
- `git diff --check` passed before commit.
|
|
- `actionlint` was not installed in WSL, so it was not run.
|
|
- Checked Google's current SDK repository metadata for `platform-tools`, `emulator`, `ndk;27.3.13750724`, `platforms;android-34`, `platforms;android-35`, `build-tools;34.0.0`, and `system-images;android-35;google_apis;x86_64`; all are present.
|
|
- Confirmed the committer identity was `Swung0x48 <swung0x48@outlook.com>` before committing.
|
|
|
|
## CI-only confirmation
|
|
|
|
The next GitHub Actions run must confirm that all three setup steps download cmdline-tools 19, install only `platform-tools`, proceed through license acceptance and package installation, and reach compilation. Emulator boot and retrace outcomes remain CI-dependent; isolated retrace failures are outside this repair.
|