Kaoru0822 c3b79cebe6 feat(browser): validate browser scenarios with --dry-run before launching ...

Checking a scenario file meant running it, which discovers, launches or
attaches to a browser and can change page state before a typo surfaces.

`rea capture-browser-scenario <json> --dry-run` reuses the same JSON and
path resolution, the canonical scenario schema and its semantic rules, and
the secret-availability rule capture applies before acquiring a browser,
now shared from one domain owner. It returns the same projected input
errors, or a compact plan of steps, secret availability and the stages it
did not check, and never creates a provider or reads secret values.

Fixes #5488

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-25 09:58:02 +00:00

..

acceptance

fix(javascript): invalidate Electron reads after direct eval (#7053)

2026-10-25 11:29:45 +08:00

boundary

feat(browser): validate browser scenarios with --dry-run before launching

2026-10-25 09:58:02 +00:00

composition

feat: add FreeBuff agent support for REA setup (#2736)

2026-10-25 11:29:17 +08:00

conformance

feat(mcp): support runtime analysis limit recovery (#7049)

2026-10-25 09:45:26 +08:00

evaluation

fix(ci): own mock isolation and normalize Git patch directories

2026-10-25 09:49:26 +08:00

fixtures

feat(environment): serve creates whose answers show less than reads, and whole-object updates (#7080)

2026-10-25 15:06:27 +08:00

process-global

feat: add FreeBuff agent support for REA setup (#2736)

2026-10-25 11:29:17 +08:00

support

fix(mcp): normalize compact schemas for strict gateways (#3806)

2026-10-25 12:11:42 +08:00

ciTestSequencer.ts

…

processOwnershipRunner.ts

…