v0.3.2

0.3.2 — Invocation, cleanup, and click-feedback fixes

Release commit: 56008801945e42484d74f340392990e8e4e9cd97

Fixed

• Publish the canonical $codex-browser-recorder:record-browser invocation across starter prompts, documentation, support guidance, and submission evals.
• Verify that the exact owned recording tab disappears from Chrome's tab inventory after closure, with one bounded retry and an explicit manual-cleanup signal when absence cannot be confirmed.
• Hide click feedback between non-contiguous feedback windows instead of rendering a ghost ring at the viewport origin.

Verification

• 290 automated tests passed.
• Coverage: 92.10% lines, 84.52% branches, 91.97% functions.
• Official pinned OpenAI plugin and skill validators passed against both the source tree and packaged ZIP.
• GitHub Actions test, analyze, and CodeQL checks passed.
• Chrome 150.0.7871.181, ChatGPT desktop and Chrome plugin 26.715.72359.
• Live frame-contract gate passed with one received and acknowledged frame.
• Two sequential H.264/yuv420p MP4 recordings passed with distinct paths, 10 fps, at most 720p, and no audio.
• Public W3C Pointer Events click recording visibly confirmed the cursor and click ring, followed by cursor-only frames with no viewport-origin ghost ring.
• The release session retained no Chrome tabs, partial files, or Working Recordings.
• The Codex in-app Browser remains unsupported and fails closed during preparation with browser_surface_unsupported.

Assets

• codex-browser-recorder-v0.3.2.zip
• codex-browser-recorder-v0.3.2.zip.sha256
• SHA-256: 16b8f5063ec8b86548da9b93e39bd0b53e3b37358c5fb2c62e3b48ac679b827b

Generated recordings and browser diagnostics are intentionally not attached.