fleet-mission-control — local board note

No full local board exists for this repo yet. Canonical tracking is Jira project FLT (https://workwingman.atlassian.net) plus Vikunja project 2. This file exists only to record one collision so it isn't repeated.

⚠ Local ticket labels here are NOT Jira keys

The design/image capability-routing work in this repo (docs/DESIGN-capability-routing.md, docs/BRIEF-capability-routing.md, branch wt/WT-0026/FLT-19-capability-routing, and every commit/code comment referencing "FLT-19") used a locally-minted number, assigned when the work session started, never checked against real Jira.

Real Jira FLT-19 is a different, unrelated, already-Done ticket ("FLT-D7 token-roi: CPDT metering + Stop hook"). The actual record for this feature is FLT-102 (minted 2026-07-17 after the work had already landed), related to the umbrella epic FLT-46 ("FLT-13 Mission Control frontend").

This is the same collision class fleet-harness/docs/BOARD.md documents under "Board IDs and Jira keys are NOT the same numbering space" — a second instance, in a repo that had no board file to carry the warning. Before minting a new local ticket number in this repo, check it against real Jira first, or use the Jira key directly instead of inventing one.

Landed commits for FLT-102: API 60bb555/789a899/df554e7/1818d3f/aeb2bed, UI 1272dcf.