FLT-144 Build Report

Date: 2026-07-19 Worktree: wt/WT-6022/FLT-144

Backend gates

Command: dotnet build -warnaserror

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:04.29

The SDK also printed informational NETSDK1057 messages because this repository uses a preview .NET 10 SDK; these were not warnings.

Command: dotnet test --no-build

A total of 1 test files matched the specified pattern.

Passed!  - Failed:     0, Passed:   548, Skipped:     0, Total:   548, Duration: 8 s - FleetMissionControl.Api.Tests.dll (net10.0)

Frontend gates

Command: npx ng lint

Linting "frontend"...

All files pass linting.

Command: npx vitest run

Test Files  25 passed (25)
     Tests  264 passed (264)
  Duration  11.54s (transform 10.97s, setup 25.80s, import 11.67s, tests 9.26s, environment 151.20s)

Command: npx ng build

Initial chunk files | Names         |  Raw size | Estimated transfer size
main-UYDT3HDH.js    | main          | 410.84 kB |                97.14 kB
styles-2KKW5AWO.css | styles        |   1.92 kB |               631 bytes

                    | Initial total | 412.75 kB |                97.77 kB

Application bundle generation complete. [4.554 seconds] - 2026-07-19T08:03:10.442Z

Output location: C:\Users\fives\source\repos\fmc-flt144\frontend\dist\frontend

Command: npm run check:drift

> frontend@0.0.0 check:drift
> npm run generate:client && git diff --exit-code -- src/app/api/fleet-api.generated.ts

Executing file 'nswag.json' with variables ''...
Done.

The final exit status was 0 after the generated OpenAPI client was committed. The pre-commit invocation returned 1 solely because the required regenerated client differed from the previous HEAD; it emitted the expected FLT-144 client diff and no generation error.

Review gate

The multi-seat council invocation timed out without returning usable combined minutes. Per the council skill fallback, Clahadore Jones-Gaffney performed the commit review. All high/medium findings were fixed before the final gates, including validate-all-before-write, explicit-approved-and-visible UI promotion, CLI option-value validation, EOF-safe promote parsing, structured partial results, process timeout/cancellation handling, and generated API error surfacing.