Mark
2c477c3f6d
docs(03): research phase domain — Approach B verification + 4 scoped questions resolved
Phase 3 RESEARCH.md addresses the 4 user-scoped research questions:
Q1 puppeteer.Page.metrics() reliable for SW context? → NO (page-realm only;
SW is a separate Puppeteer target). Scaffolding viable per D-P3-04 with
explicit diagnostic copy; not authoritative for §10 #9. (Verified via
pptr.dev/api/puppeteer.page.metrics + Puppeteer issue #7536.)
Q2 rrweb 2.0.0-alpha.4 testing patterns? → Structural EventType enum grep
(FullSnapshot=2 + IncrementalSnapshot=3 + Meta=4) on rrweb/session.json
from latest archive. Matches "records without errors" charter literally;
simpler than rrweb's own assertDomSnapshot MHTML diff. (Verified via
node_modules/@rrweb/types/dist/index.d.ts grep.)
Q3 rrweb v2 stable release status / alpha.4 safety? → Stable v2 has NOT
shipped; npm `latest` tag still points at 2.0.0-alpha.4 (2023). Newest
alpha is 2.0.0-alpha.20 (2026-02-03) with breaking NodeType import-site
change. alpha.4 pin is safe for Phase 3 verification (9 closed plans +
29/29 UAT GREEN). Phase 4 upgrade research correctly deferred per
D-P3-03. (Verified via `npm view rrweb dist-tags`.)
Q4 New chrome.* patterns for §10? → None required. Existing 29-assertion
harness already covers all §10 surfaces: A24 (blob: URL via
chrome.downloads.onCreated), A28 (screenshot.png set-equality), A26 +
A27 (meta.json + multi-tab urls strict). Operator chrome://memory-internals
remains §10 #9 canonical per D-P3-04.
Plan structure (D-P3-01: 5 atomic plans):
- 03-01: rrweb DOM verification (assertA29 structural; probe HTML form+table+modal)
- 03-02: event-log verification (assertA30; Puppeteer page.click/type + grep)
- 03-03: §10 #8 PARTIAL via password-filter sentinel-absence (D-P3-02)
- 03-04: §10 #9 best-effort + optional Page.metrics scaffolding (D-P3-04)
- 03-05: §10 #1-#9 sweep VERIFICATION.md aggregator (Phase 2 frontmatter template)
Tier-1 FORBIDDEN_HOOK_STRINGS expected to stay at 12 entries (A29+ ride
production surfaces only). No new dependencies. Approach B template from
Plan 02-04 is direct precedent.
2026-05-20 18:19:27 +02:00
..
2026-05-20 18:00:08 +02:00
2026-05-20 17:55:48 +02:00
2026-05-20 17:55:48 +02:00
2026-05-20 18:19:27 +02:00
2026-05-20 18:04:00 +02:00