[GH-ISSUE #728] [Docs] Add a browser interaction example that captures the visible result #326

New issue

Closed

opened 2026-10-15 18:23:55 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:23:55 +00:00

Owner

Originally created by @N0zoM1z0 on GitHub (Oct 6, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/728

Before submitting

I searched the open and closed issues and relevant pull requests for a related report.
I removed credentials, tokens, private paths, and sensitive target data.

Documentation location

docs/browser-scenario-contract.md; README.md (controlled browser behavior); public capture_browser_scenario examples.

Problem

The documented minimal browser scenario defaults to a final URL capture. A Search click on a controlled page succeeded but the URL stayed unchanged, so the default result could not answer what happened to search results. DOM/accessibility were correctly marked not_requested, and completeness=complete applied only to the requested sections.

Explicit DOM/accessibility capture answered the question inline and REA handled launch/cleanup. This is a guidance improvement, not a failed click or evidence omission.

Expected content

Add a small worked local-page interaction with useful artifacts selected explicitly:

{
  "browser": {"mode": "launch", "executable_path": "<CHROME_EXECUTABLE>"},
  "start_url": {"url": "<LOOPBACK_HTTP_URL>"},
  "actions": [{
    "step_id": "search",
    "action": "click",
    "locator": {"kind": "css", "selector": "#search"},
    "timeout_ms": 10000
  }],
  "capture": {"at_end": ["dom", "accessibility", "url"]}
}

Explain when to request DOM/accessibility, screenshots, or relevant event families, and how not_requested differs from complete requested coverage. Show the equivalent CLI scenario-file flow. Preserve the conservative default and analyst choice; do not automatically capture unrelated storage or response bodies.

Supporting evidence

On the original persistent connection, REA-owned Chrome launch -> local page -> Search click -> DOM/accessibility capture succeeded in 8.24 s and reported terminated-owned-process. Captured accessibility text showed {"matches":["One note"],"count":1}. Repeating the click with capture omitted succeeded in 583 ms and retained only the unchanged final URL. No leftover matching browser processes remained after cleanup.

Additional context

Hands-on public CLI/MCP evaluation, findings F10. Baseline: REA 4.0.1, source revision c3bc38bf6c74d2175a4680530dcadd6cab0e7791; evaluation date 2026-10-06.

Related completed browser contracts: #373 and #374. This requests a useful current-contract example, not a new action/origin-permission system.

Originally created by @N0zoM1z0 on GitHub (Oct 6, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/728 ### Before submitting - [x] I searched the open and closed issues and relevant pull requests for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Documentation location [docs/browser-scenario-contract.md](https://github.com/morluto/rea/blob/c3bc38bf6c74d2175a4680530dcadd6cab0e7791/docs/browser-scenario-contract.md); [README.md](https://github.com/morluto/rea/blob/c3bc38bf6c74d2175a4680530dcadd6cab0e7791/README.md) (controlled browser behavior); public capture_browser_scenario examples. ### Problem The documented minimal browser scenario defaults to a final URL capture. A Search click on a controlled page succeeded but the URL stayed unchanged, so the default result could not answer what happened to search results. DOM/accessibility were correctly marked not_requested, and completeness=complete applied only to the requested sections. Explicit DOM/accessibility capture answered the question inline and REA handled launch/cleanup. This is a guidance improvement, not a failed click or evidence omission. ### Expected content Add a small worked local-page interaction with useful artifacts selected explicitly: ```json { "browser": {"mode": "launch", "executable_path": "<CHROME_EXECUTABLE>"}, "start_url": {"url": "<LOOPBACK_HTTP_URL>"}, "actions": [{ "step_id": "search", "action": "click", "locator": {"kind": "css", "selector": "#search"}, "timeout_ms": 10000 }], "capture": {"at_end": ["dom", "accessibility", "url"]} } ``` Explain when to request DOM/accessibility, screenshots, or relevant event families, and how not_requested differs from complete requested coverage. Show the equivalent CLI scenario-file flow. Preserve the conservative default and analyst choice; do not automatically capture unrelated storage or response bodies. ### Supporting evidence On the original persistent connection, REA-owned Chrome launch -> local page -> Search click -> DOM/accessibility capture succeeded in 8.24 s and reported terminated-owned-process. Captured accessibility text showed `{"matches":["One note"],"count":1}`. Repeating the click with capture omitted succeeded in 583 ms and retained only the unchanged final URL. No leftover matching browser processes remained after cleanup. ### Additional context Hands-on public CLI/MCP evaluation, findings F10. Baseline: REA 4.0.1, source revision [c3bc38bf6c74d2175a4680530dcadd6cab0e7791](https://github.com/morluto/rea/commit/c3bc38bf6c74d2175a4680530dcadd6cab0e7791); evaluation date 2026-10-06. Related completed browser contracts: [#373](https://github.com/morluto/rea/issues/373) and [#374](https://github.com/morluto/rea/issues/374). This requests a useful current-contract example, not a new action/origin-permission system.

bsakaguchi

2026-10-15 18:23:55 +00:00