Run after the required profile, loading and component work is available. Record actual results, versions and outstanding defects. Cover DA62/MSFS with manual departure and WingRally delivery; Phenom/XP12 with manual departure; selected radio/AI capabilities only where supported. Acceptance: preparation from tablet/phone requires no extra manual script starts; closing the browser is harmless; post-load cold-and-dark checks pass; no duplicate broker/Sim Agent is created; required failures prevent false Ready; optional failures identify degraded functionality; active-flight route arrival does not reset the aircraft; stopping respects process ownership. Do not mark this task complete without real runtime evidence. Radio-specific acceptance Qualify DA62/MSFS first. XP12/Phenom radio and dependent AI-ATC are not approved capabilities merely because an X-Plane 11 adapter exists; record their separate qualification result before including them as supported. Base XP12 sessions remain usable without radio. Verify separate process, simulator, gateway, audio-client and audio/PTT status. A connected wrong client must not satisfy a profile-required handheld. Missing/unusable radio dependencies prevent AI-ATC startup, with a clear cause. Test duplicate-instance avoidance and reuse. Multi-speaker synchronization is a separate RadioBridge follow-up; initial single-client acceptance does not imply synchronized speaker playback. Static audit is not runtime acceptance Task 201 is completed only for source/configuration/deployment inspection. No live simulator run or rebuild was performed. This task must remain incomplete until live evidence is recorded. Before integrated XP12/Phenom tests, establish a verified Phenom catalogue/mapping set; the current starter catalogue is Aerobask DA62. Checkpoint builds and reconcile source/deployment versions for reproducibility. Test the concrete broker defects: missing expected nodes must not disappear from the total, and catalogue-loaded ready must not imply simulator/outputs/nodes synchronized. Check the active FreeTrack/vJoy dependency with the launcher. Only test automatic bridge startup after its readiness contract exists. WingRally test matrix (knowledge items 113, 118, 119) Record source commit, built bridge/plugin versions, published/runtime versions and actual tested aircraft/simulator separately. Test missing/incompatible plugin, both sims running with an explicit target, component restart/reconnect, duplicate/stale requests and route arrival during an active flight. Verify no wrong-sim dispatch and no unrequested flight reset. Test MSFS native routes and imported SimBrief plans; XP imported original-.fms path; and, once implemented, XP native WingRally export without SimBrief. Until native export exists, rejection must explain the current limitation without presenting it as an X-Plane requirement. Exercise invalid/unresolved route data and relevant AIRAC/procedure mismatches. Verify transfer, avionics activation, placement and cold-and-dark independently. Windows-plugin testing, actual Phenom avionics behavior, Navigraph staging review and SimBrief v2 migration must not be marked complete based on source implementation claims.
.png)
09 - Integration & Migration
Incremental migration, cross-component tasks, end-to-end acceptance checks and unresolved integration questions.
First implementation-preparation task. Read Start Here and Architecture before inspecting the local cockpit repositories. Compare the user-supplied code investigation with current code; do not begin a broad rewrite. Deliver: repository/component map, build/start commands, host requirements, configurable runtime paths, ports, dependencies, readiness signals, simulator support and proven overlaps. Keep installation-specific addresses/paths in local configuration. Acceptance: all reported components including launcher, embedded Sim Agent, broker, RadioBridge, AI-ATC/Ollama, WingRally and instructor are covered; discrepancies and unknowns are explicit; propose the smallest next implementation step. Record relevant commit references when reporting results. Incorporate the handheld-radio Codex review: the repository reportedly contains an X-Plane 11 adapter; XP12/Phenom RadioBridge support remains unqualified. Inspect actual readiness signals and their gaps for process, simulator adapter, T-Dongle gateway, client identities and audio/PTT. Preserve RadioBridge ownership of all radio/audio/device logic. Distinguish unicast prototype functionality from demonstrated multi-speaker synchronization. Completed scope Completed based on the cockpit Codex report supplied by the user on 18 September 2026. Static source, configuration, deployment and contract audit only. Full findings: knowledge item 117; completion record: build log 3766. Inspected commits and dirty-working-tree qualifications are preserved there. No live simulator run or rebuild was performed. Completion does not qualify XP12/Phenom, radio/AI compatibility or end-to-end session readiness. Those remain in task 212 and component qualification tasks. Next: checkpoint task 215, then read-only preflight task 203 and broker readiness task 206. Phenom catalogue/mappings task 216 gates the integrated XP12 profile. Automatic orchestration task 217 follows usable readiness contracts.
Build Log
1 entryCockpit Codex completed the static cross-repository audit
The user supplied the cockpit Codex's completed review of source, configuration, deployment files and interface contracts. Results are recorded in knowledge item 117, including versions, ports, host roles, inspected commits, readiness defects and source/deployment gaps. No live simulator run or rebuild was performed. This activity completes the inventory scope of task 201 only. The existing Launcher is a suitable base; next steps are checkpointing current changes and read-only preflight. XP12/Phenom catalogue/mappings and complete runtime behavior remain unqualified. Buildory baseline notes and follow-up tasks were updated to reflect the report; no code or deployment changes were executed in this chat.
Knowledge
2 itemsEvidence and scope Source: cockpit Codex report supplied by the user on 18 September 2026. That Codex inspected source, configuration, deployment files and interface contracts across repositories. It performed no live simulator run and no rebuild. This is a verified static baseline reported by the component developer, not an independently repeated audit in this chat or runtime qualification. Cockpit Codex owns the general cockpit work; handheld-radio and WingRally changes require coordination with their respective Codex sessions. Conclusion The existing Session Launcher is a suitable Cockpit Manager foundation. No broad rewrite is needed. A reliable XP12/Phenom profile is not yet demonstrated. First preserve the current working tree, then add read-only profile/preflight observation. Integration map | Component | Reported implementation/version | Simulator scope | Existing readiness evidence | | --- | --- | --- | --- | | Session Launcher | .NET 8; 0.0.1.17; starts MSFS and broker; embeds Sim Agent | MSFS workflow only | Own status, broker status, /v1/health | | Embedded Sim Agent | In Launcher; standalone 0.0.1.14 must not run concurrently | MSFS/vJoy/head-tracking code; active vJoy path needs clarification | HTTP /v1/health on 8097 | | Broker | .NET 8; 0.0.1.353; simulator autodetection | MSFS and XP12 integration | /v1/session/status on 8096; semantics incomplete | | RadioBridge | .NET 10; 0.8.2 | MSFS; legacy X-Plane adapter, XP12 not formally qualified | No structured local health API | | AI-ATC | Python 3.12; 0.1.4 | Practically tested only with MSFS; scenarios/acceptance tests MSFS-oriented | /api/status on 8765 | | Ollama | Local LLM service | Simulator-independent | HTTP on 11434 | | WingRally | Source 0.4 vs deployed runtime 0.3 | Source supports MSFS and XP12 12.1+; deployed runtime explicitly MSFS2024-only | Server heartbeat; no local health API | | AI Flight Instructor | 0.26.0 | MSFS 2020/2024 adapter only | Remote last_seen; no local health API | | Cockpit Control (CC) | 0.0.3.415 | Simulator-independent | /up; optional for flying | | ESP nodes | Connect autonomously to broker TCP 8099 | Simulator-independent node protocol | Heartbeat/node state | | Tablet Agent | Android 0.2.11 build 14 | Simulator-independent | Discovery/commands on 8095 | Host requirements Use installation-specific host aliases in local configuration; no private LAN addresses are published here. Simulator PC: MSFS 2024 or XP12, Launcher and embedded Sim Agent; RadioBridge due to USB Radio Gateway/local simulator access; WingRally Bridge due to SimConnect/CommBus or local XP plugin; optional Instructor; optional AI-ATC and Ollama. Broker: may run on simulator PC or development host for MSFS; must currently run on simulator PC for XP12 because the Web API is 127.0.0.1:8086. WingRally XP12 plugin listens on loopback 127.0.0.1:19782. CC runs on a separate optional host and must not be a flight prerequisite. Port inventory | Port/transport | Role | | --- | --- | | 8099/TCP | ESP nodes to broker | | 8096/HTTP+WS | Broker runtime API, Sim Control and CC | | 8097/HTTP | Embedded Sim Agent | | 8095/UDP+TCP | Tablet Agent discovery and commands | | 500/TCP | Remote MSFS SimConnect | | 8086 | XP12 Web API, loopback | | 51000 | ExtPlane fallback/diagnostics; not normal XP12 startup requirement | | 49000-49002/UDP | RadioBridge legacy X-Plane adapter | | 49020/UDP | RadioBridge to AI-ATC context | | 8765/HTTP | AI-ATC diagnostics/status | | 11434/HTTP | Ollama | | 19782/UDP | WingRally XP12 plugin, loopback | Verified static discrepancies 1. Current broker configuration uses an Aerobask DA62/X-Plane starter catalogue. Phenom 300 catalogue/mappings are missing or not verified. 2. Launcher lacks an XP12 startup profile and local-broker rule, even though broker autodetection supports XP12. 3. nodes.connected and nodes.total in /v1/session/status currently use the same counter. They do not prove all expected nodes are present. 4. Broker ready means only the control catalogue is loaded, not simulator connection, correct aircraft mappings or synchronized nodes/outputs. 5. WingRally source 0.4 and deployed 0.3 differ; source XP12 capability is not deployed runtime support. 6. RadioBridge adapter remains xplane11 using legacy UDP; XP12 compatibility requires contract/runtime testing. 7. AI-ATC is practically MSFS-tested; Instructor has only an MSFS adapter. 8. Dirty repositories weaken traceability: existing commits do not identify all current builds or deployed files. Independent simulator connections and overlap Broker: SimConnect and XP12 Web API. RadioBridge: SimConnect and legacy X-Plane UDP. WingRally: SimConnect/CommBus and XP12 plugin. Instructor: its own SimConnect connection. Detection, reconnect and basic aircraft/COM/electrical data overlap. Different consumers, timing and failure handling justify preserving boundaries for now. Orchestrate and observe before deciding whether to consolidate. Inspected Git references | Repository | Inspected commit | Qualification | | --- | --- | --- | | Cockpit orchestration | 352cc02 | Relevant current changes mostly uncommitted | | Broker/Launcher | b6bb580 | Builds 353/17/14 mostly uncommitted | | RadioBridge | 7ae35ff | Current 0.8.2 changes mostly uncommitted | | WingRally | db427fa | XP12/source 0.4 changes mostly uncommitted | | Flight Instructor | 49f5320 | Clean; release 0.26.0 | | CC | 4fa8695 | Current build 415 changes mostly uncommitted | These are inspection anchors, not complete reproducible release identifiers. No checkpoint commit or rebuild was performed as part of this reported audit. Next implementation boundary First checkpoint the current relevant working trees in coordination with repository owners. Add configuration-driven read-only profiles msfs_da62 and xp12_phenom300 inside the existing Launcher. Each component describes required/optional, host, start command, readiness method and dependencies. Display running, reachable, sim connected, ready, unsupported and unknown as distinct aspects/evidence; unknown does not mean ready. For XP12, reject an incompatible broker location in preflight without moving/stopping/starting processes. Block the integrated XP12/Phenom profile with an explicit reason until catalogue/mappings are proven. Do not add automatic RadioBridge, WingRally or Instructor startup until usable readiness contracts exist. Preserve current working manual/existing startup paths. Resolve the discrepancy between the earlier FreeTrack-only/no-vJoy-required account and this audit's vJoy/head-tracking description by tracing active configuration/code, without assuming vJoy must be launched. Completion scope Task 201 can close as source/configuration/deployment inventory. Live profile qualification, rebuild validation and end-to-end session tests remain outstanding under their implementation tasks and task 212.
Proposed incremental sequence 1. Static source/configuration/deployment inventory is complete as reported by cockpit Codex; preserve the result in knowledge item 117. Checkpoint relevant uncommitted changes before new implementation. 2. Add read-only configuration-driven msfs_da62 and xp12_phenom300 profiles/preflight to the existing launcher. Fix broker readiness semantics and expected-node accounting. Gate the integrated XP12/Phenom profile on verified catalogue/mappings. 3. Coordinate usable readiness contracts with RadioBridge, WingRally and Instructor owners before adding automatic startup. Only then implement managed optional components and dependency-aware lifecycle. 4. Expose session control on tablet/phone, including manual departure choice or waiting for WingRally. 5. Implement and verify post-load aircraft-specific cold-and-dark preparation. 6. Investigate and consolidate demonstrated overlap only after a working integrated session exists. Acceptance goals A complete supported session can be prepared from a tablet/phone without manually starting extra scripts. Closing the web UI does not stop preparation. Readiness reflects actual simulator, flight, aircraft and required-component state. MSFS starts with launcher/FreeTrack in the required order. XP12 uses the local broker. Duplicate brokers and Sim Agent instances are prevented or reported clearly. Cold and dark is applied after loading and verified; physical switch synchronization must not silently undo it. A new route during an active flight cannot reset the session without an intentional action. Required dependency failures prevent a false Ready state; optional failures identify the degraded capability. Open decisions Repository locations and component contracts; readiness endpoints; supported airport/runway/parking data sources; exact cold-and-dark commands and physical-switch reconciliation for each aircraft; route handoff lifecycle; remote-broker transition; supported AI Instructor simulator profiles; update/rollback packaging. No wake-on-LAN, public internet access or new UI framework is assumed. The initial remote-control proposal assumes the simulator PC is powered on and the manager is reachable on the local network. Radio integration qualification and sequencing (handheld-radio Codex review, 18 September 2026) Start with DA62/MSFS as the concrete RadioBridge integration candidate. Qualify XP12/Phenom separately: only an X-Plane 11 adapter is reported in the handheld-radio repository. The base XP12 simulator/broker session must remain usable without radio; do not imply qualified RadioBridge or dependent AI-ATC support. The minimum manager integration is script launch or instance reuse plus separate process, simulator-adapter, gateway, client and usable audio/PTT status. RadioBridge owns these signals and all radio/device/audio logic. Required client identities follow the session profile. AI-ATC waits for the simulator connection and usable radio path, not merely a running process. Test missing/wrong clients and dependency failures explicitly. Multi-speaker synchronization is a separate RadioBridge follow-up and is not a prerequisite for initial single-client integration. Audit qualifications Broker ready currently means catalogue loaded only; nodes.connected equals nodes.total in the inspected implementation. The first preflight must not convert these weak signals to Cockpit ready. WingRally source 0.4 supports XP12 12.1+ but deployed 0.3 is MSFS2024-only. AI-ATC 0.1.4 is practically MSFS-tested; Instructor 0.26.0 has an MSFS-only adapter. Multiple independent simulator connections are confirmed, but differences in timing, consumers and error handling mean consolidation is deferred. No automatic bridge startup is added during read-only preflight. Reject an incompatible XP12 broker location without relocating or restarting it. Existing manual/base simulator workflows remain available; this is not approval of the integrated Phenom profile. Task 212 remains open for live acceptance evidence.