Bundle artifacts

Files written under ./qa-audit/ after `qa-audit bundle --path`.

What this means: after Test Coverage Review (`qa-audit bundle --job-id <id> --path ./your-app`), you get a folder of reports next to your project — start with `report.md` for a plain overview, then open the matching detail file. Nothing is committed into your source tree automatically.

File	What it contains
report.md	Human overview: crawl snapshot, repo detect summary, links to gap lists
coverage.csv	One row per crawled route — covered vs gap, match method, test files
per-page.md	Per-route summary when the server returns page-level coverage
bundle.json	Full machine-readable bundle (inventory, coverage, drafts)
manual-test-cases.md	Step-by-step checks a human can run
automation-snippets.md	Draft Playwright / Cypress snippets to review before committing
jira-tickets.md	Ticket-shaped work items with manual + automation sub-tasks
tests/gaps.md	Pages/routes without browser-suite evidence
tests/unit.md	Source ↔ `.test` / `.spec` file matches (not the same as visiting a URL)
tests/controls.md	Application Map buttons/forms without a matching test locator
tests/app-routes.md	Framework-declared routes not seen on the crawl
tests/hygiene.md	Dead or redundant locators harvested from test files
tests/smoke.md, a11y.md, …	Suggested scenarios grouped by kind (Engineering+)

Control and hygiene files need an Essential+ crawl with an Application Map on the job. Unit/component file matching runs from local files only.