Three docs that answer "where should my new test go?" for CLI-related e2e:
- cli/test/e2e/README.md: decision tree across 5 test tracks, Track B
boundary, env var setup (SKILLHUB_E2E_*), new-test checklist, CI status
- web/e2e/auto-generated/README.md: marks directory as pipeline output,
naming convention, boundary with hand-written specs
- e2e-automation/README.md: output location convention, module subdirectory
layout, boundary clarification (pipeline only produces browser-subject specs)
