e2e: remove the browse/promote authoring loop#1205
Conversation
The browse -> promote pipeline (drive a flow, record the steps, codegen a test) was more than intended. Developing against the UI is just running Playwright, which is already in-repo and is the same thing a scenario() runs. Remove src/journey/ (steps/codegen/run), the browse/promote commands in scripts/cli.ts, and the "Authoring from a live browser" doc section. The cross-OS desktop targets are unaffected.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | bb751b9 | Commit Preview URL Branch Preview URL |
Jun 29 2026, 04:46 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | bb751b9 | Jun 29 2026, 04:48 AM |
Greptile SummaryThis PR removes the
Confidence Score: 5/5Safe to merge — straight deletion of an unused authoring layer with no remaining imports or consumers in the rest of the e2e suite. All three deleted source files have zero imports left in the codebase, the CLI switch statement and HELP text are consistently updated, and the .gitignore already covers the .dev/ artefacts the journey commands produced. The only leftover is a one-line comment nit in the file header. No files require special attention; the stale comment on line 15 of e2e/scripts/cli.ts is trivial. Important Files Changed
|
Cloudflare previewTorn down — the PR is closed. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
@executor-js/codemode-core
@executor-js/runtime-quickjs
executor
commit: |
Removes the
browse->promoteauthoring loop from the e2e dev CLI.It was an over-built path (drive a flow, record the steps, codegen a test). Developing against the UI is just running Playwright, which is already in-repo and is the same thing a
scenario()runs, so the recording/codegen layer earns nothing.Deletes:
e2e/src/journey/(steps.ts,codegen.ts,run.ts)browseandpromotecommands ine2e/scripts/cli.ts(back toup/identity/api/mcp/ledger/logs/down)e2e/AGENTS.mdThe cross-OS desktop targets (
desktop-macos/linux/windows) and everything else are untouched.