docs(e2e): correct terminal layout parity and workspace layout checker script paths (#42427)

The E2E agent guide linked the terminal layout parity runner and the
workspace layout checker at their old config/scripts locations, so the
link was broken and the inspection command failed with MODULE_NOT_FOUND.
Point both at their current locations and update the checker's own
usage comment to match.

Fixes #42426

Co-authored-by: Neil <neil@stably.ai>
This commit is contained in:
mia-ambr
2026-11-14 14:23:50 -08:00
committed by GitHub
co-authored by Neil
parent 9a5c859cdb
commit 5ddac03e1b
2 changed files with 4 additions and 4 deletions
@@ -1,6 +1,6 @@
#!/usr/bin/env node
// Validate saved layout against shared structural rules, including live dev profiles; print breaches and exit 1.
// Usage: node config/scripts/check-workspace-layout-rules.mjs <userDataDir>
// Usage: node config/scripts/static-analysis/repository-layout/check-workspace-layout-rules.mjs <userDataDir>
import { build } from 'esbuild'
import { mkdir, mkdtemp, rm } from 'node:fs/promises'
+3 -3
View File
@@ -23,8 +23,8 @@
- Terminal-topology refactors must preserve behavior or fix a named bug. Run
`ORCA_BACKGROUND_LAUNCH=1 pnpm run test:e2e:terminal-layout-parity` to compare the working
tree with its merge-base on `origin/main`. See the
[runner](../../config/scripts/run-terminal-layout-parity.mjs) for commit comparisons
and scenario filters. The head's journeys must work against both builds.
[runner](../../config/scripts/runtime-verification/terminal-e2e/run-terminal-layout-parity.mjs)
for commit comparisons and scenario filters. The head's journeys must work against both builds.
- Declare intended fixes in [declared differences](terminal-layout-parity-declared-differences.ts)
with scenario, bug ID, and report path prefixes; undeclared or unmatched declarations fail.
Preserve PTY-binding and main/renderer agreement waits before quitting. Unstable-on-main
@@ -37,4 +37,4 @@
`ORCA_LAYOUT_ORACLE_REPEAT=<n>` for repeats and `ORCA_LAYOUT_ORACLE_REPORT_DIR` for JSON
reports. `ORCA_LAYOUT_ORACLE_RECORD=1` records without failing; do not use it as a passing gate.
- Inspect any profile with
`node config/scripts/check-workspace-layout-rules.mjs <userDataDir>`.
`node config/scripts/static-analysis/repository-layout/check-workspace-layout-rules.mjs <userDataDir>`.