test(browser): bind controlled result to semantic digest evidence

[seonghobae]

Partial implementation of #28, stacked on exact PR #100 head 13f49b7fc4f11d0fd851f51d816dc0cc94003b91.

Buyer-visible gap

The pinned-Chromium Agent Task already discovers the input and submit action by exact browser-computed role/name, but its post-condition result was still retrieved by fixture CSS and represented only as boolean success. The controlled workflow therefore lacked a bounded structured extraction artifact that can later compose with OriginWeave's typed source-node/network provenance boundary.

Dependency

This Draft targets PR #100 branch test/agent-task-semantic-role-name-locator at unchanged exact head 13f49b7fc4f11d0fd851f51d816dc0cc94003b91. Keep Draft while #100 and its browser-evidence prerequisites remain active. No prerequisite check, review, status, artifact, or mergeability result transfers.

TDD / RCA sequence

1. Exact test-only head 3eaf34bd1d146dd69351799c5812c07c7b3eb7f1 required the result node to carry an explicit accessible name, be discovered through exact browser-computed status / Task result semantics rather than #task-result, and produce bounded credential-safe structured-value evidence.
2. CI run 31559008579, Rust contracts job 93997236182, checked out that exact test-only head and failed at the intended Python repository-contract boundary with five missing-contract failures: absent result accessible name, absent MAX_AGENT_TASK_STRUCTURED_VALUE_BYTES, absent _hash_agent_task_structured_value, and absent result-semantic/structured-value evidence fields. This is the valid RED.
3. Fixture head d2e4086127922a96f12ca4fca7b4eef602f4020c added the explicit Task result accessible name.
4. Production head 6800ef029da0be98eac3699872b8ef0cc0856de0 added the smallest runner implementation: exact semantic result discovery, a 4096-byte UTF-8 extraction bound, canonical lowercase SHA-256 evidence, stable task_result field identity, and no raw extracted value in emitted evidence.
5. Current exact head bc1d22d6c4848a173c55fdd18054574299488067 adds only the truthful Unreleased changelog entry describing that implemented boundary.

Exact-current proof

On unchanged exact current head bc1d22d6c4848a173c55fdd18054574299488067 against unchanged exact prerequisite #100 head 13f49b7fc4f11d0fd851f51d816dc0cc94003b91:

• CI run 31559777436: success;
• Rust contracts job 93999549329: success, including Python repository contracts, canonical formatting, locked workspace/all-target check, full tests, strict Clippy and rustdoc;
• Production coverage job 93999549280: success, including exact owned production function/line/region/branch enforcement;
• Manifest V3 Compatibility run 31559777419: success against Chrome for Testing 150.0.7871.129 / revision r1639810;
• current-head evidence artifact mv3-compatibility-bc1d22d6c4848a173c55fdd18054574299488067, artifact ID 9127308443, archive digest sha256:68070752879b61a4a1c4f3b49a7edd25e7180594a6bf1a9ce46047b6008ea577;
• Agent Task repeats 3/3, pass rate 1.0; every trial reports result_semantics_verified=true, structured_value_field=task_result, and digest sha256:3f9d88d8df56ef344ef37877e568494065c2be33870053e5ad722de0367a3be5;
• independent artifact inspection confirms that digest equals SHA-256 of the controlled synthetic input while the raw string originweave controlled input is absent from emitted JSON evidence;
• GitHub reports the Draft mergeable against its exact prerequisite base; and
• no formal reviews or inline review threads are currently returned.

CodeRabbit's current draft status is not treated as independent review evidence. No predecessor-head proof is transferred to the current head.

Implemented boundary

The controlled result is now found by exact browser-computed status / Task result semantics, its exact synthetic text is checked transiently only to prove the deterministic post-condition, and the emitted trial evidence retains only a stable field identifier plus a bounded canonical SHA-256 digest. Empty, oversized, or non-text structured values fail closed at the hashing boundary.

Truth boundary

This is executable pinned-browser compatibility evidence, not the production browser adapter and not complete source/network provenance. It does not mint an OriginWeave node handle, authenticate a browser adapter, authorize an action, capture or retain raw network payloads, bind the digest to independently verified ProvenanceRecord instances, persist the extracted value, or claim the complete issue #28 chain. PR #104 independently defines the typed structured-value/node/network provenance composition contract on another active stack; this lane does not duplicate or promote that active-PR behavior to protected-main truth.

[coderabbitai]

Important

Review skipped

Draft detected.

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: Pro Plus

Run ID: 964e87fa-a72f-4e58-baf1-1d318354c63e

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.}