From f339500911a6edd9e7adcfb8f6f72fe3b080bf7a Mon Sep 17 00:00:00 2001 From: Jinwoo-H Date: Mon, 21 Sep 2026 00:55:25 -0400 Subject: [PATCH] test(config): name the haptics module inside the merged session-closure reading (OTA phase C, C7.5b) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The merge's re-measured 4284 sat one above this branch's -40 added to PR B's +3, and the comment could only say main had drifted "a module of its own". It is `src/mobile-web-shell/bridge/bridge-haptics-notify.ts`, which C7.10 item E put on the session route after PR B recorded 4323 — so pristine main reads 4324 against the 4323 it holds, which is what #21908 re-pins. Named here as #21908 names it on main. Nothing measured changes: 4284 is the same number, and the module is in it by main's route rather than by anything this branch did. `haptics.web.ts` was already in the closure; the bridge module joins it. Verified by reading the closure's own module list rather than inferred from the count: both haptics modules are in `local`, with the artifact-level totals unchanged at 4284 / 934. Which is why the reading is re-measured and not summed. A merged number arrived at as -40 plus +3 would have read 4283 and been wrong about a module neither side of the merge touched. After #21908 lands, a further merge of main reconciles the two comments. Claude-Session: https://claude.ai/code/session_01JNnE9qzUZMMnqpZWCqM3nb --- .../mobile-web-app-session-terminal-closure.test.mjs | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/config/scripts/mobile-web-app-session-terminal-closure.test.mjs b/config/scripts/mobile-web-app-session-terminal-closure.test.mjs index 33fc2fc1b51..47d10c94d45 100644 --- a/config/scripts/mobile-web-app-session-terminal-closure.test.mjs +++ b/config/scripts/mobile-web-app-session-terminal-closure.test.mjs @@ -19,12 +19,20 @@ import { * * Re-anchored on the merge of main at 35005fb65c9 and re-measured there, because the two sides of * that merge do not add up: this branch reads -40 and main's own mermaid reading below reads +3, - * and the merged total is one above their sum. Main drifted a module of its own after recording - * 4323, which is exactly the kind of thing a summed number would have hidden. + * and the merged total is one above their sum. * * modules 4324 -> 4284 (-40) * local modules 974 -> 934 (-40) * + * The extra module is `src/mobile-web-shell/bridge/bridge-haptics-notify.ts`, which C7.10 item E + * put on the session route after the +3 below was recorded, so main itself reads 4324 against the + * 4323 it holds and #21908 re-pins it there. It is in this branch's 4284 for the same reason and + * by the same route, not as anything this branch did: `haptics.web.ts` was already in the closure + * and the bridge module joins it. + * + * Which is the point of re-measuring rather than summing. A merged number arrived at as + * -40 plus +3 would have read 4283 and been wrong about a module neither side of the merge moved. + * * Both sides read with `mobileWebAppRouteClosure(SESSION_ROUTE)` and the four postinstall * generators run first, main's in a scratch worktree detached at the same sha. *