Post-voyage analysis
Reports
Completed voyages across all workspaces
⚑Build note: QA Reports and Token Usage read real Maestro artefacts through the Hub backend. Acceptance Criteria, Voyage Summary and Security Review have no backend route yet, so they show no figures at all — each says what it will read and where that data sits on disk today.
Live data→
QA Reports
Per-voyage QA verdicts: test suites, acceptance criteria, defects, and sign-off.
…reading /api/v1/reports/qa
Live data→
Token Usage
Filterable token spend with drill-down: project → voyage → order → role/model. CSV export.
Liveforward-looking · FTR-0331+
No backend yet→
Acceptance Criteria
Met, partial, outstanding and not-recorded criteria, per order.
—no backend route
No backend yet→
Voyage Summary
Scope, duration, token spend by role, and crew contribution.
—no backend route
No backend yet→
Security Review
SEC crew findings by severity with remediation status.
—no backend route