Files
reverse-engineering-anything/docs/specs/agent-environments/scenario-capture/plan.md
T
bf1eeee94f feat(environment): build environments from browser scenario captures (#5182)
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>
2026-10-20 06:07:15 +08:00

21 lines
1.1 KiB
Markdown

# Implementation plan
1. Add `src/domain/analysisView/scenarioCaptureRecords.ts`: index scenario
events by transaction, project each request event as a HAR-shaped
`WebNetworkCaptureRecord`, and admit a scenario parent for the manifest
view (clone budget, schema, network-content selection).
2. Route `projectEnvironmentManifestView` through one capture-parent gate that
selects the HAR or scenario admission by parent operation, and widen the
environment-manifest result's `parent_operation`.
3. Branch `parseCaptureEvidence` in `environmentSource.ts` on the Evidence
operation, carry the capture kind and digest on the source, and word the
bundle README and CLI help for both kinds.
4. Add a schema-valid scenario capture fixture and domain and services tests:
the record projection, the manifest from a scenario parent, the refusal,
replay of UTF-8 and binary bodies, and the bundle README.
5. Document scenario parents in `docs/agent-environments.md` and
`docs/web-network-captures.md`, extend the tool contract text, and record
the spec.
No new dependency is introduced and no command is added.