The static audit (knowledge item 117) finds an Aerobask DA62/X-Plane starter catalogue in current broker configuration. Phenom 300 catalogue/mappings are missing or unverified. Broker XP12 autodetection alone does not qualify the aircraft profile. Inspect available catalogues and mappings before creating replacements. Define and implement the Phenom 300 controls/state needed by the current physical cockpit and planned startup/cold-and-dark workflow. Record gaps explicitly. Acceptance: catalogue identity and aircraft compatibility can be checked by preflight; required controls, feedback, node/output synchronization and agreed initial-state behavior are verified in a live XP12/Phenom session with version/build evidence. Keep nodes simulator-independent. Until proven, the integrated xp12_phenom300 profile must show an explicit block. Do not disable unrelated existing manual XP12 use. RadioBridge, WingRally and Instructor capabilities require their own separate qualification.
03 - Cockpit Broker & Nodes
Physical cockpit I/O, node synchronization, simulator mappings, broker placement and single-instance operation.
Operator request6November2026: the optional power-lever brake mode may be removed for now. Braking will be assigned by the operator to TCA buttons1/2/3 directly in the simulator. Do not map them automatically. Administrative decision recorded; no runtime/configuration change yet. Installed Broker407 retains the XP guard2 integration; do not assume current saved opt-in or binding state. In a safely stationary session, establish actual mode and release only feature-owned braking/throttle overrides before persisting OFF. Remove/disable the optional activation path and native hold binding so it cannot unexpectedly re-enter BRAKE/WAIT_IDLE; do not delete an active plugin or just hide a still-enabled feature. Preserve PILOT/BOTH/COPILOT steering, ordinary center-console throttle, existing USB axis calibration, pedal/parking behavior and unrelated buttons. Back up exact affected files and verify normal throttle and no lever-brake intervention after restart. Keep the historical in-flight WAIT_IDLE incident as unproven, not fixed by administrative cancellation. No new lever-brake functionality or commissioning is required. GPU physical acceptance is deferred separately. Reference contracts/lever_brake_mode.md and contracts/flight_control_priority.md. IMPLEMENTATION CHECKPOINT — 6 NOVEMBER 2026 Explicit removal now implemented in Broker408 source and tested Windows package, not installed. Production removes relay/opt-in construction, lease/timer/subscription/node observation, throttle interception/status and tablet activation/mode UI. Old commands are rejected and saved remap catalog/input paths filtered. Historical relay/opt-in source excluded from production. Ordinary throttle and independent steering retained. Linux and SIM Windows full XP suites pass, including20retirement,41numeric-array,55steering,45G1000,153GPU checks;134FUEL,86audio/OTA and13browser+19DOM fixtures pass. Exact408 production PE identity and absence of retired symbols verified. Report reports/broker408-retire-lever-brakes-20261106.md. Live read-only preflight: no simulator,407broker active, opt-in already absent, native remap plugin and oneTS2global482 hold binding still installed. Installer's normal CloseMainWindow call from SSH returned false and aborted before runtime/plugin/preferences writes. Operator asked to close only broker. No forced termination, simulator start/flight or control changes. Safe eight-artifact install, plugin backup/removal, exact one-binding no-action edit and restart verification remain pending. Do not mark DONE yet. COMPLETED DEPLOYMENT — 6 NOVEMBER 2026 After operator confirms broker closed, exact tested408 eight-artifact install succeeds17:18:14CET;59protected files unchanged. Simulator absent and opt-in already absent before any removal. Native CockpitLeverBrakes moved outside plugin discovery into recoverable backup. Only old TS2global482 hold binding changed to native no-action; independent byte comparison proves every other preference byte preserved, including steering axes/calibration and all other buttons. New joystick SHA25683ee72def6d9036f4037388394148899c686cc0e3ffeb9c59e363911872bac0c. No brake buttons assigned on behalf of operator. Canonical broker408 reopened once, PID9760. Independent installed hashes/absence scan confirms no plugin/marker/legacy binding. Actual LAN runtime ready,14connected nodes, simulator disconnected; actual served HTML/JS/CSS match408 and contain no remap activation or mode labels; live status has no lever_brakes field. Exact package and Linux/Windows tests were accepted in the prior checkpoint. No simulator/flight/control/firmware/CC/launcher/Pi/power action. Runtime removal is complete; DONE supersedes the deployment-pending checkpoint above. Normal throttle physical smoke/airborne use was not tested here because simulator remains off; no claim of root-cause proof for the historical WAIT_IDLE incident. Operator owns direct TCA button1/2/3 braking; independent steering takeover is retained. GPU physical test remains explicitly deferred. Evidence: reports/broker408-retire-lever-brakes-20261106.md, reports/broker408-install-receipt-20261106.json, reports/broker408-live-postcheck-20261106.json. Prior407/plugin/preference backup retained; no unrecoverable deletion.
Use static audit knowledge item 117. Broker .NET 8 build 0.0.1.353 exposes /v1/session/status on 8096. Defects: nodes.connected and nodes.total currently use the same counter; ready only means catalogue loaded. Implement truthful reporting for the profile's expected nodes versus connected nodes, identify missing nodes, and distinguish catalogue loaded, correct aircraft catalogue/mappings, simulator connection, and node/output synchronization. Define the resulting functional readiness contract with the launcher; preserve compatibility for existing API consumers or version the change. Acceptance: a missing expected node is visible; only connected nodes cannot be treated as the total expected set; a loaded catalogue with no simulator or unfinished synchronization does not produce cockpit-ready. Report unknown when evidence is absent. Confirm retained simulator-neutral node protocol on TCP 8099. Preserve the single-broker constraint. MSFS can use simulator/development-host broker; XP12 currently requires the local broker and loopback Web API. During read-only preflight, reject an incompatible host without moving/stopping/starting a broker. Phenom catalogue/mapping qualification remains a separate prerequisite.
Build log
2 itemsBroker408 installed: optional TCA lever-brake mode retired, steering retained
Operator confirms broker closed. Installed exact tested408 eight-artifact package17:18:14CET;59protected files unchanged, no simulator running and opt-in already absent. Removed runtime relay/opt-in/timer/lease/interception/status and tablet remap UI; old commands/catalogs cannot re-enable it. Moved native remap plugin to recoverable backup outside X-Plane discovery. Changed only TS2global482 cockpit/lever_brakes/hold to native no-action; independent comparison proves all other joystick bytes unchanged. Operator will configure direct button braking themselves. Reopened canonical broker once, PID9760. Independent artifact and absence verification passes: no installed remap plugin, opt-in marker or hold binding. Actual LAN runtime ready/14nodes, simulator disconnected, no lever_brakes status field and all three served tablet assets match408 without remap UI. Linux/Windows20retirement/41array/full XP plus55priority/45G1000/153GPU,134FUEL/86audio and13browser+19DOM fixture results recorded in report. Task375 marked DONE for installed removal, not physical flight acceptance. Main DLL SHA256f36a5a6101a01bb882526d0cea86181c1bd7fc8211ce6858733d8bc8060b40cc; new joystick SHA25683ee72def6d9036f4037388394148899c686cc0e3ffeb9c59e363911872bac0c. Local reports broker408-retire-lever-brakes-20261106.md, broker408-install-receipt-20261106.json and broker408-live-postcheck-20261106.json preserve exact receipts/backup reference. No credentials/private account data recorded here. No simulator start/flight/control command, brake-button assignment, firmware flash, CC/launcher/Pi/power change. Original intermittent WAIT_IDLE cause remains unproven; the feature is now absent, not diagnosed. GPU physical test still deferred. Retap Sim Control on tablets to reload the new page if an old cached page remains.
Taak 206 — broker-readiness en expected nodes live geverifieerd
Broker 0.0.1.356 en Cockpit Session Launcher/Embedded Sim Agent 0.0.1.22 zijn gebouwd en op de sim-pc geïnstalleerd; rollbackkopieën en gebruikersconfig bleven behouden. De versieerde /v2/session/status geeft voor msfs_da62 8 verwachte fysieke nodes apart van verbonden TCP-sessies (View Control is geen verwachte node). Live disconnecttest: 7/8 en missing_ids=[da62-deice-panel], cockpit_ready=false; na herverbinden 8/8 en geen ontbrekende IDs. Simulatorverbinding, DA62-aircraft-match, catalogus en mappings worden apart gerapporteerd; catalogus alleen betekent niet cockpit-ready. Bestaande /v1/status-consumenten en simulatorneutraal TCP 8099-nodeprotocol bleven behouden. Contracttests voor missing node, ontbrekende sim, DA62-resource-alias en XP12 wrong-host/read-only preflight slagen; XP12/Phenom is niet live gekwalificeerd (aparte taak 216). Live automatische MSFS saved-flight-start werd ready met 4/4 pop-outs en beide I/O-gates open; operator bevestigt dat het werkt. Input/output-node-synchronisatie en algemene cockpit_ready blijven terecht null/unknown zolang end-to-end apply-ACKs in het nodeprotocol ontbreken; dit is geen bewezen hardware-synchronisatie. De 10s-stabilisatiebranch van Launcher 22 is in bron/contracttests aanwezig maar de exacte duur is niet afzonderlijk uit live launcherlogs bevestigd.
Kennis
2 items6 November 2026 — explicit operator decision: remove the optional TS2 + DA62 center-console power-lever brake mode from the desired setup for now. The operator will configure TCA button1/2/3 braking directly in the simulator themselves; do not assign those buttons or guess a brake command. Preserve ordinary power-lever mapping and independent PILOT/BOTH/COPILOT steering selection. This supersedes further commissioning/physical acceptance of the optional lever-brake feature as a current objective, not the historical tests or unresolved WAIT_IDLE cause. Installed Broker407 still contains the XP-only guard2/plugin integration and the saved opt-in/binding state has not been checked or changed during this administrative session. Do not claim it disabled or removed. Track safe retirement separately: with aircraft safely stationary, verify actual mode and release only this feature's brake/axis ownership, persist disabled, retire its activation UI/relay/native hold binding as appropriate, preserve unrelated USB axes/buttons/parking/pedals and normal throttle routing. No abrupt plugin removal while still opted in. Direct simulator button setup remains the operator's work. No MSFS lever-braking extension or further feature commissioning requested. GPU physical acceptance is explicitly deferred by the operator; keep Broker407 split-cable/supply implementation installed and pending its later ground test. No software, config, simulator, power or firmware change was performed for this decision.
Source: user-supplied cockpit-Codex static audit, 18 September 2026. Source/configuration/deployment were inspected; live runtime qualification and rebuild validation remain pending. See knowledge item 117. The broker translates physical cockpit-node I/O into simulator functions and synchronizes nodes. Keep nodes simulator-independent. Only one active broker is allowed in the reported setup. MSFS can use a broker on the simulator PC or an alternate host. For X-Plane 12, the broker currently must run on the simulator PC because it uses X-Plane's built-in Web API at 127.0.0.1:8086; the alternate host cannot access that loopback endpoint directly. ESP nodes connect automatically. SimConnect is an integration interface, not a separate program to launch. ExtPlane and a separate X-Plane REST/WebSocket bridge are not required for the reported XP12 setup. ProSimBridge is outside the initial MSFS/XP12 scope. Cockpit Control may remain off during normal operation. Manager implications Check broker location as well as liveness. If an incompatible remote broker is already active when starting XP12, report the conflict and implement an explicit coordinated transition; do not silently start a second broker. Verify the real discovery and readiness mechanisms in code before relying on them. Distinguish node connection from successful synchronization. Concrete readiness defects and profile gap Broker is .NET 8 version 0.0.1.353. Runtime API/Sim Control uses HTTP+WS 8096; /v1/session/status is available. ESP nodes use TCP 8099. In the inspected code nodes.connected and nodes.total use the same counter. They cannot establish that all expected nodes are present. Define expected nodes per profile and report absent and connected nodes truthfully. The current ready flag means only that the control catalogue is loaded. It does not establish simulator connection, correct aircraft mappings, node synchronization or output synchronization. Do not use it as Cockpit ready. Current XP configuration uses an Aerobask DA62 starter catalogue. Phenom 300 catalogue/mappings are missing or unverified. XP12 broker support does not imply a qualified XP12/Phenom cockpit profile. ExtPlane port 51000 remains fallback/diagnostic context, not a normal-start dependency. In the first read-only preflight phase, a wrong broker host is reported/rejected without process mutations.