(CODUX-169) Document e2e runtime coverage

[numnx]

🧩 Task: Document e2e runtime coverage

Automated task PR opened by Code UX for T07.

📋 Summary

Sprint: Sprint 169 · Testsuite: e2e · Task: T07

Greatly expand Code UX end-to-end coverage with a deterministic cross-platform Playwright harness, product-focused dashboard workflows, filesystem save/upload checks, runtime invocation assertions, and fake-CLI sprint orchestration scenarios for full runs plus start/stop/retry controls.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-07 12:42:43 UTC
Finished	2026-07-07 12:46:55 UTC
Duration	4m 12s

📊 Token Usage

Metric	Value
Input tokens	107,656
Cached input tokens	552,704
Output tokens	7,946
Total tokens	668,306
Invocations	1
Tool calls	28
Active time	3m 17s

Included usage estimate (subscription/local login): $1.05

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

📝 Full Task Prompt

## Objective
Document how to run, extend, and troubleshoot the expanded e2e suite so future contributors can use the fake CLI and platform matrix correctly.

## Scope
- `docs/development/testing-and-quality.md`
- `docs/index.md` only if a new subsection or anchor is needed for discoverability
- `docs/SUMMARY.md` only if a new dedicated page is created
- Reference but do not edit Playwright specs from T01 through T06 unless documentation needs exact filenames

## Implementation Requirements
1. Add a section describing `pnpm run test:e2e`, the Playwright webServer behavior, isolated HOME/USERPROFILE state, and why the suite runs against `dist/index.js` after `pnpm run build`.
2. Document the fake CLI shim contract from T01, including the environment variable that enables it, supported prompt markers for success/failure/sleep/no-change, and the rule that it must never affect normal provider execution.
3. Document how the e2e fixture helpers create temporary git repositories, select projects, configure local-git HOST execution, and clean runtime state.
4. List focused commands for the new specs: product smoke, dashboard workflows, filesystem persistence, invocation runtime, full sprint orchestration, and sprint controls stress.
5. Document the CI platform matrix and any OS-specific caveats for path separators, file inputs, shell execution, and Chromium dependency installation.
6. Add troubleshooting notes for stale sprint runs, stuck fake CLI processes, missing build artifacts, and accidental real-provider execution.

## Constraints
- Do not claim the e2e suite covers real provider CLIs; describe it as deterministic fake-CLI orchestration coverage.
- Do not mark checks as passing unless the worker actually ran them.
- Do not duplicate large chunks of Playwright config or test source in docs; summarize behavior and point to exact paths.
- Keep documentation canonical under `docs/`; no `docs-web` mirror is required unless the implementation changes public user-facing dashboard behavior.

## Verification
- Run `pnpm run lint`.
- Run `pnpm run build` if docs links or package scripts were changed in a way that affects generated output.
- Success means the documentation names the exact new commands and files, explains the fake CLI safety guard, and remains consistent with the implemented e2e harness.

🌿 Branch Info

Base: feature/CODUX-169-testsuite-e2e
Head: task/feature-codux-169-testsuite-e2e-t07-codex-mran3031

---

🤖 Generated by Code UX