bf1eeee94f
Build an agent environment directly from retained capture_browser_scenario Evidence through the existing manifest, serve and export commands. Preserve request ordinals, source pointers, redaction markers, unavailable bodies, provenance and the default stdio MCP transport. Followups admit copied/transformed text before body validation or decoding, avoid request-text allocation in replay, normalize portable file inventories, select dependent CI lanes, retain the author's redaction/body-budget corrections, and count body coverage over represented requests. Validation: full pinned-toolchain static gate, source and public CLI/MCP regressions, canonical catalog checks, actual Chromium interactive and live GitHub API captures with exact HTTP replay and stdio parity, the generated non-root Docker image, and its smoke task through real agent-env 0.9.1334. Verification scopes, resource measurements and platform limits are recorded in the PR and feature verification document. Co-authored-by: gensokyo-dev <gensokyo-dev@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
648 B
648 B
Tasks
- Record the scenario-parent contract, requirements and non-goals.
- Project scenario transactions as HAR-shaped records and admit scenario parents.
- Route the manifest view through one capture-parent gate and widen its result schema.
- Load scenario Evidence in serve and export; name the capture kind in the README and help.
- Add the scenario capture fixture and domain and services tests.
- Document scenario parents and extend the tool contract text.
- Run static, formatting, duplication, documentation and test gates.
- Build environments from real browser scenario captures and record the results.