2.1 KiB
Fleet Ops release acceptance
This file is release-scoped evidence, not a timeless claim. Older evidence under
artifacts/evidence/ is historical. Exact commands and production revisions are recorded
in PROJECT_STATE.md.
2026-08-21 release candidate
- Backend: 271/271 tests passed against an isolated clean PostgreSQL database.
- Browser acceptance: 155/155 Chromium tests passed in 4.6 minutes.
- Live-safe browser canary: 4/4 passed across Chromium and Firefox against the local deployed stack; unlike the acceptance suite, it never resets or mutates demo records.
- Accessibility: the principal login, dashboard, data-quality, knowledge, automation and audit routes have no automated critical/serious WCAG 2 A/AA/2.1 AA violations.
- Frontend: TypeScript, ESLint, production build, dependency audit and per-asset JS/CSS budgets passed; committed visual baselines cover the public entry and engineering story.
- Contracts: committed OpenAPI, event schema, MCP tools and all five n8n definitions match their code/manifest sources.
- Recovery: a custom-format PostgreSQL dump was restored into a disposable database; the Alembic revision and non-zero canonical table counts matched the source database.
- Operations: Prometheus/Alertmanager configuration validation passed, including the watchdog and authenticated n8n receiver route.
Evidence boundary
The complete local suite uses the deterministic provider and an isolated database so it is repeatable and safely destructive. Production verification is deliberately smaller and non-destructive; it verifies the real RAGcore/MCP/n8n health surfaces without resetting the shared demo. A successful local result is never presented as proof that an external service was live. The production subsection is added only after the exact committed release is deployed and observed.
Remaining product boundary
Fleet Ops remains a synthetic single-tenant PoC. It is not a production identity provider, payment system, accounting package or public reservation platform. External RAGcore, MCP Hub and n8n services remain independently operated dependencies and are accessed only through their documented adapters.