Task 4 of Plan 01-11 attempted A1-A4 wiring. Empirical run reveals an
architectural blocker that needs orchestrator-level decision.
Current state after this commit (SKIP_PROD_REBUILD=1 npx tsx tests/uat/harness.test.ts):
- A0 [PASS]: production bundle hook-leak grep gate (17ms)
- A1 [FAIL]: SW bootstrap → setIdleMode — popup state never transitions
to '' despite keepalive ping + 3s waitFor. chrome.action.getPopup({})
from the popup page consistently returns the manifest default
(chrome-extension://<id>/src/popup/index.html), not the '' that
setIdleMode's chrome.action.setPopup({popup:''}) should produce.
- A2 [FAIL]: toolbar onClicked — badge never transitions to "REC" after
page.triggerExtensionAction(extension); 8s timeout. Either the
toolbar action isn't reaching the SW listener, OR getDisplayMedia's
picker isn't resolving in headless mode (despite the auto-select flag).
- A3 [FAIL]: offscreen target never appears (correlates with A2 — no
recording started, no offscreen document spawned).
- A4 [PASS]: trivially passes (offscreen count is 0 → 0, both before
+ after the click). Not a true assertion of behavior; would also pass
if the whole extension were broken.
- A5-A13: stubbed RED per plan.
Architectural blocker (Rule 4 — needs orchestrator decision):
- Puppeteer 25.0.2 + Chrome 148 + headless cannot reliably keep the MV3
SW alive long enough OR expose its real chrome.* state to a popup
page query. The popup-bridge architecture (Task 3 commit dbd977c)
works for synchronous bridge queries (snapshot, fire-on-startup)
but does NOT reliably reflect chrome.action.setPopup / setBadgeText
state changes initiated by the SW.
Three plausible paths forward (need orchestrator pick):
Option A — Content-script bridge: inject a content script that
bridges chrome.* queries to a webpage's window.* RPC surface;
harness uses page.evaluate against the content script instead of
popup.evaluate. Pros: content scripts have stable lifetime tied to
the page they're injected into. Cons: content scripts have
DIFFERENT chrome.* surface (no chrome.action API surface — they
can't read getBadgeText / getPopup at all). Likely DOESN'T solve
the underlying problem.
Option B — Headful with Xvfb on CI: relax the headless requirement;
accept Xvfb dependency. Per Plan 01-11 RESEARCH §3, RESEARCH
claimed headless works on Chrome 148 — empirical refutation here.
Pros: SW lifetime is more stable in headful mode; setPopup
propagation is reliable. Cons: introduces Xvfb dep that RESEARCH
explicitly said wasn't needed; CI complication.
Option C — Shrink harness scope to bridge-able assertions: A0 (grep
gate), A8 (Bug A onStartup via bridge), A9 (icon sizes via popup
fetch), A10 (manifest via popup), A13 (zip shape — operator runs
SAVE_ARCHIVE manually + drops zip to a known path; harness reads
it). Skip A1-A7, A11, A12 (the ones that require live SW state
observation through chrome.action API). Pros: ships the
bug-A-coverage portion of the harness today; keeps Plan 01-09's
Task 5 operator-checkpoint partly automated. Cons: doesn't retire
operator entirely; Plan 01-09 stays open on operator-empirical
A1-A7.
Option D — Switch to WebDriver BiDi (the Puppeteer 25 alternative
backend): Puppeteer 25 supports BiDi via {protocol: 'webDriverBiDi'}.
BiDi may handle extension SW evaluation differently (different
isolation model). Speculative — no empirical evidence either way.
What landed cleanly:
- Tier-1 hook-leak grep gate (T-1-11-01) GREEN: dist/ has zero
__mokoshTest / simulateUserStop / getSegmentCount / setCurrentStream
/ setSegmentCountGetter / __mokoshTestQuery / __mokoshKeepalive
occurrences after npm run build.
- Two-bundle infrastructure (dist/ vs dist-test/) operational.
- Bridge handler in sw-hooks.ts works for snapshot + fire-on-startup
+ handler-types ops (verified by no-hang on keepalivePing call).
- Existing 89-test vitest baseline preserved (no regression from any
Wave 0/1/2/3 work).
Verification:
- npx tsc --noEmit (src/): exit 0
- npx tsc --noEmit -p tests/uat: exit 0
- npm run build: exit 0; dist/ hook-free
- SKIP_BUILD=1 npx vitest run: 89/89 GREEN
- SKIP_PROD_REBUILD=1 npx tsx tests/uat/harness.test.ts:
2/14 passed (A0 + A4-trivially), 12 FAIL — non-zero exit as expected.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Mark
f44ca3afba