Skip to content

e2e/README.md spec inventory documents 7 of 12 Layer-3 specs — 5 undocumented #551

Description

@rosscado

Problem: e2e/README.md's "Specs" section (the architecture diagram, lines ~118–136) inventories only 6 runtime specs, but e2e/specs/ contains 11 *.e2e.ts specs (plus the on-demand settings.visual.ts) — 5 specs are undocumented in the harness's own README.

Scope: Documentation only (e2e/README.md). The suite itself is healthy — all 13 tests across the 11 specs pass locally (46s, verified 2026-07-07 during the #535 constitution audit). Out of scope: adding/changing any spec, and the coverage roadmap already tracked in #291.

Reproduction / verification:

  1. ls e2e/specs/*.e2e.ts → 11 specs.
  2. Read the "Specs" block in e2e/README.md → it lists decoration, dictation-stt, mock-isolation, tooltip-contrast, sw-recycle, offscreen-shutdown (and covers settings.e2e.ts / settings.visual.ts in prose above).
  3. Missing entirely (grep returns nothing): opus-upload.e2e.ts (feat(transcribe): WebM/Opus upload where supported (#414 Phase 2) #422), pi-action-buttons.e2e.ts, pi-call-button.e2e.ts, synthetic-audio-stt.e2e.ts (the spec doc/synthetic-voice-turn.md and CLAUDE.md tell readers to copy), telemetry-gate.e2e.ts.

Expected: AGENTS.md says "Read e2e/README.md before running or extending" the harness, so its spec inventory should account for every spec in the suite. Actual: 5 of 11 are invisible to a reader following that instruction.

Acceptance criteria:

  • Every e2e/specs/*.e2e.ts file is discoverable from e2e/README.md (one-line purpose each is enough; the diagram or a table, whichever reads better).
  • The required-vs-on-demand posture per spec stays explicit (settings.visual.ts remains documented as NOT in the CI gate).

Found by the 2026-07-07 constitution-vs-reality audit (#535); report in doc/audit-reports/2026-07-07.md once the audit PR lands.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions