docs: refresh live product gap baseline

[seonghobae]

Summary

• record the 2026-09-09 live queue, exact presentation-identity boundary, and central owner dependency
• retain the fix(bidi): make reusable application scope explicit #298/test(bidi): align media authority contract #305 repair lineage without promoting its Draft state to runtime evidence
• merge the current baseline collector guidance and repair its named-checkpoint contract

Verification

• uv run pytest -q (220 passed; 988 subtests)
• git diff --check

Visual inspection

• GitHub-rendered exact head 43acca1f86784b3cae747d4b9cdd7a46676e5523, Edge desktop viewport: heading hierarchy, inventory, long SHA values, wrapping, contrast, and the controlled-browser boundary were readable; no clipping or overlap observed.
• Local loopback rendering was blocked by browser policy (ERR_BLOCKED_BY_CLIENT), so it was not treated as visual evidence.

Delivery boundary

• The exact-head Rust contracts and Production coverage jobs are currently queued. This is not release or protected-main acceptance.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 26d9f20c-493a-4b92-8e51-d105682dcb4a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Current-cut accuracy finding on 4c2ce60eefdc285b97ffb1ea928f5868c90ca37a: the 2026-09-09 presentation section says pinned Chromium application, page-observed post-conditions, and cleanup evidence “remain unimplemented and unreleased.” unreleased is correct, but unimplemented is now too broad for the live active-PR state this baseline is supposed to preserve. #299 has an implemented controlled pinned-Chromium evidence harness for fixed viewport/DPR/timezone apply, page-observed target, native interaction/outcome, explicit reset, page-observed baseline restoration, WebDriver session/profile/fixture cleanup, and three-trial gating. Its predecessor exact 7ebbe58d64d746aef751fdb2507593149d76ba2a had repository CI success and executed Chrome/ChromeDriver 150.0.7871.129, but the real browser lane failed 0/3 at session creation before navigation; its newer cleanup-provenance source lineage is not yet exact-head GREEN. The truthful buyer boundary is therefore “implemented in an active controlled evidence harness but not successfully executed through the application/post-condition sequence, not a product Browser Session adapter, and unreleased,” while #292 still owns product/runtime acceptance. Please preserve that distinction in the latest cut and add a current-section contract so later active browser-evidence implementation cannot silently regress back to unimplemented. Do not promote #299’s failed/predecessor browser result to product acceptance.