2 Commits

Include renames

Author	SHA1	Message	Date
swung0x48	99649a9087	[MG_Remote] (P6/lk): the pre-flight itemisation, and a correction to c6's regroup design ... CONTRACT-P6 §8.5 requires lk to publish its blast radius before it starts, because an earlier draft's ratchet baseline was wrong by a factor of three and a ratchet installed on the wrong number is red on its first CI run for reasons that have nothing to do with a leak. The itemisation is mechanical, per file, with the grep spelling stated: 250 seam-identifier references outside Transport/ across 23 files (127 production, 123 test), and 44 member-access sites that the regroup itself must rewrite, across 9 files - 17 of them in MG_IntegrationTest, which is why lk builds with the integration tests ON. The earlier build did not, and a missed edit there would have been green. THE CORRECTION. Measuring that radius turned up a mistake in c6, landed two commits ago. §8.3 and ILink.h both said lk should promote eventRingFull and eventDropped into the watermark group and called the result single-writer. eventRingFull has TWO writers: the server latches it with store(1) when SEG_EVENT fills (EventRing.h:140) and the CLIENT clears it with an exchange(0) on EVERY DRAIN (:200). Promoting it would put a per-drain read-modify-write by the client on the same cache line as appliedSeq - which the server release-stores every 64 records and the client's spin predicate reads 1e5-1e6 times a frame. That is new false sharing on the hottest line in the system, and it would land in exactly the numbers this package's gate has to hold constant. It is also the same class of error the earlier draft made with submittedSeq, one field over. So LinkProgress is now the four consumer-written watermarks and nothing else - genuinely single-writer - and the two flags stay in the doorbell/generation group, where mixed writers already live beside consumerParked/producerParked, crossing the seam through a separate EventFlags() accessor on its own line. The contract records the correction and its reasoning rather than quietly restating the rule. ALSO CORRECTED, from running the baseline suite: a6's link-experiment report said the silently-empty build stamp had "no log and no gate to say so". That is false. SessionHandshakeTest.cpp:140 asserts BuildStamp[0] != '\0' and :180 asserts that perturbing it changes the fingerprint, and BOTH GO RED in this configuration right now - the worktree's .git holds a Windows path WSL's git cannot resolve, so GIT_COMMIT_HASH_SHORT is "". The finding is therefore stronger, not weaker: the gate that catches it already exists and is already red. What is silent is the BUILD, and hs owes a named configure-time failure rather than a new gate. Baseline for lk, recorded: 3878 tests, two failures, both environmental and understood - the fingerprint one above, and PipeCatalogue.FrontendNeverTakes- AnApplierAddress, which walks up from cwd looking for MobileGL/MG_Impl and so fails for any out-of-source build directory. No behaviour change. The headers are still included by nothing.	2026-09-21 08:54:48 -04:00
swung0x48	c25a776090	[Docs] (Disaggregated): P6 a6 close-out, and the end-state review it was re-scoped from ... a6 is the read-only audit P6-SPAWN-PLAN puts first. Seven static items, each produced by one auditor and re-resolved line by line by one adversarial verifier; 198 rows, 65 of them contested, and only the surviving ones carry into the report. Item 5 - can the server link without MG_Impl - is the one experiment, and it is answered. The headline is that P6's transport half is smaller than the plan assumed (fc and fs really did land) and its process/role half is much larger. Four statements in P6-SPAWN-PLAN / P6-CONTRACT-DRAFT are false at this head: - `spawn` is not an observable state at all. ConfigLoader.cpp:339-346 recognises it and then writes Transport = Monolith, so "the child was forced to monolith" and "the parent fell back" are the same value and that named refusal cannot falsify itself. Meanwhile 226 live lines test `Transport != Monolith` to select the SERVER arm, 148 of them in MG_Backend - so ARCHITECTURE.md:488's rule, implemented literally, flips the whole backend to frontend glue in the one process with no frontend. - `cp` is not transport-only: the InitCapabilities REQUEST has no wire form, and the codec refuses to encode the kind a live client still calls. - the device-lost latch is not implemented; it was booked as carriage. - the server cannot link without MG_Impl: 184 symbols, 177 of them real function calls, owed 101 to P7 / 14 to P3b-P4b / 60 shared / 6 to P6. There is also no module target to link, so the question could not have been answered by editing a link line. Four more blockers the earlier review missed: the apply thread aborts in ConsumerDoorbell before popping its first record (contract 3.9's ruling, which lk should retire rather than amend); neither side of the control plane is wired to a socket; the control-reply wait has no deadline, so a frozen peer wedges the GL thread inside eglMakeCurrent; and SurfaceReply cannot carry a MobileGLResult, so a client cannot tell a dead server from a legitimate refusal. The abort census makes dl's funnel a redesign rather than a rename: 92 sites, 30 distinct family words against a 7-value wire enum, and three unbounded peer-driven allocations with no try/catch anywhere under MG_Remote. P6-ENDSTATE-REVIEW.md is the re-examination of P6 against the gfxstream-shaped end state that produced a6's three added items. a6 overturned four of its own claims - the MG_State eight's shape, the abort count, m_windowHandle's injection points and a predicate name collision - and those are corrected in place rather than left to be rediscovered. Docs only. No code, no gate, no behaviour.	2026-09-21 07:49:37 -04:00