[PLATFORM] Zoom unsigned guest joins depend on browser generation; stock Chromium 141 is policy-blocked

[DmitriyG228]

Objective

Make the stock Vexa Zoom Web lane reliably join as an unsigned guest without disguising Zoom policy denials, force-clicking disabled controls, leaking browser contexts, or claiming teardown before the bot has actually left.

This issue is the prepared successor to #345. It is scoped to the meet-join brick plus the browser runtime-shape and service adapters required to carry that brick in bot, Lite, Compose, and Helm. Post-admission audio/consent work in #515 is a parked dependency, not part of this issue.

Where we are — evidence, then reading

External platform facts

• Zoom's July 20, 2026 release note says unsigned guests are evaluated through invisible CAPTCHA and guests assessed as automated are asked to sign in; rollout is July 22–August 5: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0066432
• Zoom documents support for the current browser and the two preceding versions: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0064261

Research observations

Probe	Browser/session	Actual	Verdict
One protected legacy room, 6 fresh profiles	stock Chromium 141	6/6 rendered the conjunction “detected a bot” + “automated bots are not allowed” + “use Zoom RTMS” before host admission	deterministic failure for that room/browser cohort; not a universal Zoom claim
Same protected room	current Chrome/Chromium 149	reached guest prejoin/waiting-room; one macOS run was admitted and visually left	browser generation/product affects classification; not stock-image proof
Zoom-owned official test meetings, 3 fresh profiles	stock Chromium 141	Clara Khan, Sofia Patel, and Sofia Khan were admitted	ordinary test rooms are a negative control only; they do not exercise the protected policy cohort
Zoom-owned official test meeting	current browser, Elena Costa	admitted; browser teardown completed	one observation, not the protected-room sequence
Old/current binary × old/current UA	four crossover combinations	all reached ordinary prejoin	UA-only is not demonstrated as the policy fix
https://zoom.us/test, disposable current Firefox container	Playwright 1.61.1 + Firefox 151 rev 1532	page title loaded; webdriver=true; mediaDevices=true	ordinary page compatibility only; no participant joined
Same probe under amd64 emulation	Firefox 151	exceeded the 120-second bound and was terminated	no amd64 verdict; native amd64 proof is owed

The current reading is that the RTMS wording is a terminal Zoom policy wall, not evidence that the meeting requires RTMS. Classification must require all three clauses so an isolated title/chat string cannot trigger it. The defect is introduced at the browser/runtime contract: the stock image carries a browser generation Zoom can classify differently. The join consumer must not spoof around its own runtime mismatch.

A second independent defect is React-controlled guest-name entry: Zoom may replace/reset the input after a write, leaving Join disabled although an earlier read appeared correct. The prepared behavior is bounded entry attempts, post-settle double verification, node-replacement handling, at most one repair, and a typed terminal result—never a forced click on a disabled button.

Selected browser/driver fork

Use Playwright 1.61.1 with its matched, unmodified Firefox 151.0 revision 1532, only for unsigned Zoom guests.

Preserve the existing Playwright 1.56/Chromium lane for authenticated profiles and every non-Zoom platform. Preserve an operator-supplied executable path as an explicit advanced override; it cannot prove the stock image works.

Upstream identity:

• Playwright driver/core: 1.61.1, Apache-2.0: https://raw.githubusercontent.com/microsoft/playwright/v1.61.1/LICENSE
• Browser manifest: Firefox 151.0, revision 1532: https://raw.githubusercontent.com/microsoft/playwright/v1.61.1/packages/playwright-core/browsers.json
• Probed arm64 source-image digest: mcr.microsoft.com/playwright@sha256:7b86926fff94374389e8e1f4fdc5c76d050d4a06a7886bb537bf412b20e2b71e
• Probed Firefox application.ini BuildID: 20260611122632
• Embedded notice: omni.ja!/chrome/toolkit/content/global/license.html, 308,060 bytes, SHA-256 276c0a63176234c8aa3108e415a9e336c590ecf600bc24af7d6809d5af75436e
• Separate runtime library named in dependentlibs.list: liblgpllibs.so; probed arm64 SHA-256 e09a057e89519b24f1dd8c26b29df9175c3233b86d8102ad9e13c2e9041acc66

P17 / MPL / LGPL / SBOM contract

The selected fork is admissible only when all of these are true:

1. Final bot/Lite images copy only the matched Firefox artifact (/ms-playwright/firefox-1532) from the current Playwright source image; they do not adopt that whole image as the final base.
2. THIRD_PARTY_LICENSES.md identifies Firefox, its exact version/revision, source, images, and in-image notice paths.
3. The complete MPL 2.0 and embedded Firefox third-party notice inventory travels with the artifact. The source-retrieval reference is retained as required by MPL executable-form distribution.
4. license-exceptions.json logs the Category-B allowance for clearly demarcated, unmodified, separately shipped/dynamically loaded LGPL components. Static bundling is not accepted.
5. scripts/sbom.mjs emits a root CONTAINS relationship to Firefox and Firefox CONTAINS relationships to separately identified LGPL runtime components. The Apache-licensed npm package is not used as a proxy for browser bytes.
6. Final-image gates prove Firefox rev 1532 and the notices exist and prove current Chrome-for-Testing revision 1228 paths/bytes are absent.
7. Both native release architectures are inventoried and hashed. Emulation is not release evidence.

Rejected forks:

• Whole-base Playwright 1.61.1 or Chrome-for-Testing as Vexa's stock browser: rejected because the manifest's current chromium is Google Chrome for Testing 149/rev 1228, and npm's Apache licence does not cover those browser bytes.
• Debian Chromium 150: rejected under current P17 because the disposable runtime exposed LGPL FFmpeg code without the required clean separate-link boundary.
• Raw Chromium snapshot: rejected because its chrome://credits was a sample placeholder (generate_about_credits absent), so it lacked a redistributable notice/source inventory.
• Meeting SDK/RTMS: valid only as a separate authorized product contract, not as proof that the unsigned Web guest lane works.

Source and custody

Repository: Vexa-ai/vexa
Milestone: v0.12.20 — meeting lifecycle and operator truth
Module: pkg:meet-join
Human bar: protected solo meeting, host-visible admission and leave
Preferred validator: Dmitriy Grankin as meeting host plus a fresh non-author agent validating the immutable source/image tuple

Research provenance:

• Research base: 6a50a2320b797919f54af9a434ae8ecdf35973fe
• Research branch/worktree: codex/zoom-robust-join at /Users/dmitriygrankin/dev/vexa-zoom-robust
• Codex task: 019f9070-de4b-7002-bc4b-ca698f5488b8
• Draft state: 42 dirty paths (32 modified, 10 untracked), no commit, push, or PR

Current provisional source candidate

Draft PR: #957
Fresh non-author review: CLEAN on the exact P1/P2 repair head; no findings
Review candidate head: 2235a2c8cc61409c613b6c4f21f26bbd5203d9fb
Tree: 5e4ae0e7b5c20dbe618a633bf3923914b1256773
Provisional base: 72ecb679761fc49668b8d48d54062868832ac1c9
Branch/worktree: codex/938-zoom-firefox-source at /Users/dmitriygrankin/dev/vexa-938-zoom-firefox-source

Exact nine-file base→head manifest:

1. core/meetings/modules/join/package.json
2. core/meetings/modules/join/src/__fixtures__/README.md
3. core/meetings/modules/join/src/__fixtures__/browser-product.contract.v1.json
4. core/meetings/modules/join/src/browser-product-custody.test.ts
5. core/meetings/modules/join/src/browser-product.test.ts
6. core/meetings/modules/join/src/browser-product.ts
7. core/meetings/modules/join/src/index.ts
8. core/meetings/modules/join/src/zoom/__fixtures__/README.md
9. core/meetings/modules/join/src/zoom/__fixtures__/official-test-page.v1.json

Commit 588c689682f2b5cfefa123970c07f7791389cebe remains historical P12-failure evidence. Head 26914ea8219f9c00b6a5df4715faaf3d00c21748 is superseded because review found P1/P2. All current review, PR, and further evidence bind only to 2235a2c8… / 5e4ae0e7….

That dirty tree is evidence, not an implementation candidate. No patch is to be copied wholesale from it.

Provisional source-car implementation base: exact immutable staged assembly 72ecb679761fc49668b8d48d54062868832ac1c9 (tree 627cfb4625ca802e3f377100c135837da1320a46). The 2026-07-24 yard ruling authorizes offline development from this base so #938 does not idle behind the separate causal-speaker-attribution car. This is not a delivered-base or shipping claim. Before composition, the source car must rebase onto the exact public delivered v0.12.19 ref/SHA, recompute collisions, and rerun every gate invalidated by that rebase.

Collision map

Fresh active-car audit at 72ecb679761fc49668b8d48d54062868832ac1c9 (2026-07-24T14:10Z):

Active owner	Exact active/reserved paths relevant to the audit	Intersection with #938 first offline RED
#956 telemetry/binder car	current worktree has only core/meetings/services/bot/src/telemetry-custody.red.test.ts; future custody/binder scope remains telemetry, captured-signal corpus, and mixed-pipeline	none
#839 lifecycle handshake car	clean provisional worktree at this same base; reserved/PR #944 scope is join-driver.ts, orchestrator.ts, lifecycle HTTP/contracts, meeting-api stop/cascade, seals/docs	none
#938 first source slice	new core/meetings/modules/join/src/browser-product.ts, its test, one offline official-test-page fixture, and only the package-local test registration if required	self-owned

Future #938 service/runtime propagation may approach @vexa/bot package/config and deployment files. Those are excluded from the first RED and must be re-audited after #839/#956 advance; shared hot files are sequenced rather than edited in parallel.

The provisional local v0.12.19 planning ref is 102 commits ahead of the research base and intersects the dirty research paths at nine exact files:

Overlap	Incoming behavior that must win/be re-localized
core/meetings/modules/join/package.json	#600/#846/#852/#856/#915 tests/deps and locale/redirect behavior
core/meetings/modules/join/src/index.ts	typed Teams auth-redirect export (#915)
core/meetings/modules/remote-browser/package.json	hot-bot browser runtime A/B (#164958f6)
core/meetings/modules/remote-browser/src/browser.test.ts	runtime A/B browser contract tests
core/meetings/modules/remote-browser/src/browser.ts	locale pin + runtime A/B behavior
core/meetings/services/bot/package.json	mixed-lane attribution/capture changes
core/meetings/services/bot/src/capture-bridge.ts	#852 watcher/injection work, capture-time work, runtime A/B, and #934 bounded teardown
deploy/compose/docker-compose.yml	current recorder/front-door deployment wiring
deploy/helm/charts/vexa/values.yaml	current recorder configuration

The public rc/0.12.18 already overlaps four of these (join/package.json, join/src/index.ts, remote-browser/src/browser.ts, compose/docker-compose.yml). deploy/lite/Dockerfile.lite, release/SBOM surfaces, and Helm tests are mandatory logical rebase points even where they are not dirty-path intersections.

When v0.12.19 is delivered, recompute this table against its peeled SHA before the ready stamp. Create a fresh worktree from that SHA, re-derive each change at its point of introduction, and preserve all incoming tests/behavior. #515 must revalidate its exact image/DOM fixtures only after this browser fork freezes.

Live-resource custody

• Never publish a meeting URL/passcode, participant screenshot, or meeting content. Public evidence is redacted counts, states, timestamps, hashes, and image digests only.
• Use one newly created protected meeting; never reuse the earlier user rooms.
• Every attempt uses a fresh ephemeral profile and a new random human name.
• Record source SHA, image digest, architecture, egress/region, participant name, start/end time, outcome, and cleanup verdict for each attempt.
• Any temporary VM/browser builder records provider resource ID, owner, purpose, region, hourly price, creation time, and a deletion deadline of at most one hour. Shutdown is not deletion; billing custody ends only after provider-side deletion is verified.
• Stop at first failure or after the exact accepted count. No retry-as-flake. Confirm no participant, bot process, browser context, profile directory, or billable temporary resource remains.

Components / implementation waypoints

1. @vexa/join: unsigned-Zoom-only browser-product contract; bounded React name entry; exact three-clause wall; route-aware admission and verified leave.
2. @vexa/remote-browser: matched engine dispatch, Firefox fake-media preferences, persistent-context ownership, and cleanup on initial-page/launch failure.
3. @vexa/bot capture bridge: select/log browser product + exact version/platform without changing authenticated/non-Zoom lanes.
4. Runtime shape: core/meetings/modules/join/Dockerfile.env, bot image, and Lite/Compose/Helm propagation; one declared brick shape consumed by services.
5. Packaging governance: THIRD_PARTY_LICENSES.md, licenses/, license-exceptions.json, scripts/sbom.mjs, release SBOM sanity, and final-image artifact assertions.
6. Docs: join/remote-browser READMEs, operator configuration/troubleshooting, and one docs/changelog.d/ fragment.

No wire-contract or architecture graph change is expected. If implementation changes a module/data-flow boundary, stop and update the prepared scope before coding further.

Rehearsal / bounded harness

Offline first

Run on the clean delivered base before any live traffic:

pnpm --filter @vexa/join test
pnpm --filter @vexa/join build
pnpm --filter @vexa/join check:isolation
pnpm --filter @vexa/remote-browser test
pnpm --filter @vexa/remote-browser build
pnpm --filter @vexa/remote-browser check:isolation
pnpm --filter @vexa/bot test
pnpm --filter @vexa/bot build
node scripts/sbom.mjs --version v0.12.20 --output /tmp/vexa-938.spdx.json
node scripts/gates.mjs licenses

The focused research draft previously reported 36/36 Zoom tests, green join/remote-browser builds and isolation, green bot capture-launch tests, 23 runtime config/profile tests, Helm render, Lite environment hygiene, Compose config, config-contract gate, and git diff --check. Those are research evidence only and must be re-earned on the clean delivered base.

Native stock-image negative controls

Build the actual bot linux/amd64 image and Lite linux/amd64 + linux/arm64 images. For each native artifact:

1. prove source SHA, image digest, Firefox rev 1532, full notice/SBOM inventory, and absence of CfT rev 1228;
2. start with a fresh profile and random name;
3. reach https://zoom.us/test guest prejoin with media APIs available;
4. leave/close and prove process/profile cleanup.

This phase never targets the protected meeting.

Protected-room witness

Only after every offline and native-image row is green:

1. Human host creates one fresh protected Zoom meeting and keeps it open.
2. Run exactly three consecutive unsigned guest attempts from the same immutable stock candidate image, each with a fresh profile and new random human name.
3. Each attempt must show host-visible admission, then verified leave confirmation, recording drain, terminal about:blank or closed context, no bot process, and profile cleanup.
4. Stop immediately after 3/3 or on the first failure. Preserve the first failure privately; do not retry it as a flake.

Acceptance table

ID	Expected	Required observation / oracle	Negative control / rejection	Status at preparation
A1 Browser selection	only unsigned Zoom selects Firefox 151/rev 1532	unit matrix: unsigned Zoom → Firefox; authenticated Zoom + Meet/Teams/Jitsi → existing Chromium; operator override is explicit	any default change outside unsigned Zoom	open
A2 Browser ownership	fresh Firefox profile launches with fake media and is closed/removed on every failure path	launch, initial-page-failure, normal-close tests; product/version/platform log	leaked context/profile or reuse of Chromium auth profile	open
A3 React name entry	settled DOM value equals requested random name before Join becomes actionable	replacement-node fixture + delayed-reset fixture; bounded attempt/repair counts	force-click disabled Join or unbounded fill loop	open
A4 Policy wall	denial requires all three Zoom clauses and returns a typed terminal outcome	conjunction fixture; route/page/wall logs	isolated RTMS/bot text in title/chat must not block	open
A5 Admission/leave	polling is bounded and route-aware; success means host-visible admission and terminal exit	admission fixtures + leave confirmation → recording drain → about:blank/closed context	route loss, popup, or button click alone cannot mean success	open
A6 P17/browser bytes	final images contain governed Firefox/notices/SBOM and no CfT 1228	licence gate, SBOM relationships, per-arch hashes, final-image file assertions	npm licence green alone; static LGPL; CfT path/bytes present	open
A7 Native negative control	every native stock image reaches ordinary Zoom test prejoin and cleans up	amd64 bot + amd64/arm64 Lite evidence bound to source/image digest	emulation or operator browser is not product proof	open
A8 Protected reliability	3/3 consecutive fresh-profile admissions and 3/3 verified leaves	host ledger + machine states + zero remaining process/profile	stop on first failure; no retries; no earlier rooms	open
A9 Docs/operator truth	governed default, override, denial semantics, limits, and cleanup are documented	README/config/troubleshooting + changelog fragment	any CAPTCHA-bypass or universal-admission claim	open

Explicitly unclaimed

• CAPTCHA bypass, evasion, or stealth.
• Guaranteed unsigned admission across every Zoom account, geography, policy cohort, or future rollout.
• Authenticated Zoom account provisioning.
• Meeting SDK or RTMS authorization.
• Post-admission audio, transcription, attribution, consent-dialog, or recording quality (zoom bot: in-meeting audio/consent dialogs are never driven — click-gated meetings sit active with zero transcripts (#409 audio half; happy path proven) #515 and related work own those).
• Support or P17 compliance for an arbitrary operator Chrome binary.

Ready and composition predicates

Source-car readiness: satisfied on 2026-07-24. The exact provisional base is 72ecb679761fc49668b8d48d54062868832ac1c9; the active #956/#839 collision audit is file-safe for the bounded first slice; the selected Playwright 1.61.1 + unmodified Firefox 151 rev 1532 P17 contract is unchanged; and the quarantined 42-path research tree remains evidence only.

One public claim may begin from fresh worktree /Users/dmitriygrankin/dev/vexa-938-zoom-firefox-source, branch codex/938-zoom-firefox-source, at that exact base. Initial authority is limited to the offline native browser/profile-selection RED, no-CfT/artifact-custody contract, and the offline official Zoom test-page fixture. No protected-room participant traffic, image publication, stage, or prod mutation is authorized until the offline and native-stock-image rows select a candidate.

Composition remains blocked until public delivered v0.12.19 exists, this source car rebases onto its peeled SHA, the collision map is recomputed against then-active owners, and all invalidated acceptance/gate rows are rerun. The provisional base must never be described as delivered or shippable.

[DmitriyG228]

Scope research update — selected browser/driver fork (2026-07-24)

This is preparation evidence only. The issue remains state: incoming; no product implementation, commit, push, protected-room traffic, or robustness claim follows from this comment.

Expected

Find a current Playwright-compatible browser lane that (a) reaches Zoom's ordinary Web entry surface, (b) can be distributed under P17 with explicit notices/SBOM coverage, and (c) does not silently bake Google Chrome for Testing into Vexa. Reject any fork that cannot meet those three conditions.

Actual — bounded compatibility probe

The exact Playwright 1.61.1 metadata says:

• driver: playwright@1.61.1 / playwright-core@1.61.1, Apache-2.0;
• browser: Firefox 151.0, Playwright revision 1532;
• upstream manifest: https://raw.githubusercontent.com/microsoft/playwright/v1.61.1/packages/playwright-core/browsers.json
• driver licence: https://raw.githubusercontent.com/microsoft/playwright/v1.61.1/LICENSE

A disposable native-architecture container probe against only https://zoom.us/test (no participant join) returned:

{
  "browserVersion": "151.0",
  "url": "https://zoom.us/test",
  "title": "Join a Test Meeting | Zoom",
  "userAgent": "Mozilla/5.0 (X11; Linux x86_64; rv:151.0) Gecko/20100101 Firefox/151.0",
  "webdriver": true,
  "mediaDevices": true
}

The launch used the fake-media/autoplay preferences needed by the bot lane. An amd64-under-emulation retry exceeded its 120-second bound before producing page evidence and was terminated. That timeout is not counted as a Firefox pass or Zoom denial; native amd64 image build/start remains owed during development.

Artifact evidence from mcr.microsoft.com/playwright:v1.61.1-jammy:

• local arm64 source-image digest: sha256:7b86926fff94374389e8e1f4fdc5c76d050d4a06a7886bb537bf412b20e2b71e;
• /ms-playwright/firefox-1532 is 270 MB and reports Mozilla Firefox 151.0;
• application.ini BuildID is 20260611122632;
• the shipped omni.ja contains chrome/toolkit/content/global/license.html (308,060 bytes, SHA-256 276c0a63176234c8aa3108e415a9e336c590ecf600bc24af7d6809d5af75436e); its opening notice says most source is MPL 2.0 and it carries MPL 2.0, LGPL 2.1, and LGPL 3.0 notices;
• dependentlibs.list names liblgpllibs.so as a separate runtime library. SHA-256: e09a057e89519b24f1dd8c26b29df9175c3233b86d8102ad9e13c2e9041acc66 in the probed arm64 artifact.

Mozilla states that its executable binaries are made available under MPL and that LGPL product code is acceptable when clearly demarcated and dynamically linked:

• https://www.mozilla.org/en-US/foundation/licensing/
• https://www.mozilla.org/en-US/MPL/license-policy/
• https://www.mozilla.org/en-US/MPL/2.0/

Selected fork for dispatcher preparation

Select Playwright 1.61.1 + its matched, unmodified Firefox 151.0 revision 1532 for unsigned Zoom guests only. Preserve the existing Playwright 1.56/Chromium behavior for authenticated profiles and other meeting platforms. Preserve the operator executable path as an advanced override, not as stock-image proof.

The prepared implementation must satisfy all of these P17 conditions together:

1. Obtain/copy only /ms-playwright/firefox-1532 into final bot/Lite images; do not adopt the entire current Playwright runtime as the final base.
2. Add the Firefox artifact to THIRD_PARTY_LICENSES.md; ship MPL 2.0 plus the artifact's complete embedded third-party notices alongside it.
3. Log a Category-B exception for the clearly separated LGPL runtime component(s), with exact image scope and unmodified/dynamic disposition.
4. Emit the Firefox artifact as CONTAINS in scripts/sbom.mjs, plus a nested entry/relationship for the separated LGPL component rather than hiding it behind the Apache-licensed npm driver.
5. Add final-image assertions for Firefox revision 1532 and the absence of current Chrome-for-Testing paths/revision 1228.
6. Prove both release architectures: native amd64 bot image and amd64+arm64 Lite images. The bounded probe above proves only ordinary Zoom-page compatibility, not a protected join.
7. Use a fresh ephemeral profile for every unsigned Zoom attempt; Firefox does not inherit a Chromium profile.

Rejected forks

• Whole-base bump to Playwright 1.61.1: rejected. Its official manifest labels current chromium revision 1228 as Chrome for Testing 149.0.7827.55. That would introduce a Google browser artifact merely by changing the base; npm's Apache-2.0 licence does not cover those browser bytes.
• Chrome-for-Testing as the stock unsigned-guest browser: rejected absent a separate complete redistribution/licence inventory compatible with P17. It may remain external/operator supplied, but cannot establish stock-image compliance.
• Debian Chromium 150 shortcut: rejected under current P17. The disposable artifact exposed FFmpeg/LGPL code inside the Chromium runtime rather than a clean separately linked package boundary; it did load Zoom's test page, but compatibility does not cure the licence boundary.
• Raw Chromium snapshot: rejected. The current snapshot launched, but its chrome://credits was a sample placeholder because generate_about_credits was not enabled; it therefore lacked the notice/source inventory needed for a governed redistributed artifact.
• Zoom Meeting SDK/RTMS: not rejected as product direction, but not selected for this browser-join issue. It requires a distinct authorization/product contract and cannot be used to claim an unsigned Web guest join works.

Verdict

The Firefox fork is suitable for issue preparation, conditional on the explicit P17 packaging checks above. It is not implemented and is not yet shippable. The remaining acceptance sequence stays unchanged: after ready stamp, public claim, implementation, image proof, and an ordinary official-test negative control, run exactly 3 protected unsigned joins + 3 verified leaves from the exact stock candidate and stop on first failure or after 3/3.

[DmitriyG228]

Preparation decision — selected fork, prepared but not implementation-ready

The governed preparation fork is Playwright 1.61.1 + its matched Firefox 151.0 rev 1532, for the unsigned-Zoom lane only.

P17 permits this only as a logged Category-B exception: Firefox must remain unmodified and separately shipped; MPL and every embedded third-party notice must be present; nested LGPL components must be isolated rather than statically bundled and represented as explicit SBOM CONTAINS relationships. Whole-base Playwright/CfT, Debian Chromium, and raw Chromium snapshot forks are rejected on the evidence already posted.

Admission/acceptance contract:

1. Build native linux/amd64 and linux/arm64 stock images with the matched Firefox artifact; emulation is not product proof.
2. Assert the final image contains Firefox rev 1532 and its MPL/third-party notice inventory, plus the logged Cat-B LGPL exception and Firefox→nested-component SBOM relationships.
3. Assert the final image contains no current Chrome-for-Testing rev 1228 path or bytes; an npm-only license gate is insufficient.
4. Preserve the bounded React name-entry, exact three-clause policy-wall, route-aware admission, and verified leave/teardown rows already specified in this issue.
5. Before protected traffic, pass the official Zoom test-page negative control from each native stock image. Then run exactly 3 consecutive protected-room joins/teardowns or stop on first failure; no retry-as-flake and no earlier user rooms.
6. Fresh non-author agent validates the immutable source/image tuple before this car can compose into v0.12.20.

Source/custody gate: the current 42-path worktree at 6a50a232 is research evidence, not an admitted candidate. The accepted v0.12.19 line changes overlapping Zoom/join surfaces, so implementation must start in a fresh worktree from the exact delivered v0.12.19 ref/SHA, re-localize the diff, and publicly claim this issue only after a maintainer ready stamp. No implementation, commit, PR, image, or live protected traffic is authorized from the dirty research tree.

Issue is therefore state: prepared, not ready or claimed. Remaining admission gate: delivered v0.12.19 base plus a clean-worktree collision recheck.

[DmitriyG228]

v0.12.20 dependency record (2026-07-24): ready issue #515 is now a parked source input, not part of the active six-item candidate and not added to #938 implementation scope. #515’s post-admission audio/consent behavior can be exercised independently in an ordinary Zoom room, but any #938 browser/Playwright/P17 decision may invalidate its DOM fixtures or stock-image evidence. Therefore #515 must either wait for the #938 fork to freeze or repeat its exact image/DOM validation afterward. No source, claim, candidate, stage, or prod change follows from this routing receipt.