Preserve local Kubuntu development, NAS publication and Windows simulator execution. Inventory the existing scripts and Debug output usage before choosing packaging changes. Deliver a concrete release proposal and implementation steps for component compatibility, local staging, activation between sessions and rollback to a known-good version. Acceptance: paths/hosts are configurable; publishing does not overwrite a running session's binaries; installed versions are visible; define behavior when the NAS is unavailable. Clearly label proposal versus implemented/tested mechanisms. Audit-driven prerequisites (knowledge item 117) Checkpoint the relevant dirty working trees before implementation, coordinated with each repository owner. Inspection commits alone do not identify current builds. Record source commit plus working-tree qualification/build identity and deployed version rather than assuming they match. In particular WingRally source 0.4 differs from deployed 0.3. Resolve that gap with the WingRally Codex; no new release or rebuild was performed in the static audit. Preserve the clean Instructor 49f5320 / 0.26.0 baseline.
.png?locale=nl)
08 - Deployment & Versions
Development on Kubuntu, publication through NAS, execution on the Windows simulator PC and proposed compatible releases.
Prerequisite for new Cockpit Manager implementation. The static audit (knowledge item 117) reports uncommitted changes in cockpit orchestration, Broker/Launcher, RadioBridge, WingRally and CC. Instructor commit 49f5320 / release 0.26.0 was clean. Coordinate with the respective repository owners, particularly handheld-radio and WingRally Codex. Review relevant current changes and create coherent checkpoint commits preserving the current working state. Do not blindly combine unrelated work or replace another session's changes. Record resulting commit IDs, component versions and the relationship to published/runtime files. Distinguish a source checkpoint from a verified rebuild or deployed release; the previous audit did neither. Acceptance: each affected repository has a traceable checkpoint or an explicit remaining gap; the reported inspected commits remain historical anchors; build/deployment uncertainty is documented before implementation. Do not claim commits exactly reproduce running binaries without evidence.
Build log
1 itemCheckpointed Cockpit Platform source baseline
Created coherent source checkpoints for cockpit orchestration/AI-ATC (b3c4d01), Broker/Launcher/Agent (a600935) and CC (5cf4c4f), then recorded the provenance report at df1f343. AI-ATC passed 24 tests. Broker cross-platform Windows-targeted Debug compilation passed with 0 errors and 211 existing warnings. CC ran 127 tests with 3 existing failures, so that commit is explicitly not a release candidate. Instructor remained clean at 49f5320. RadioBridge, WingRally and Tablet Agent were recorded as explicit provenance gaps rather than committing broad work owned by other trajectories. No runtime was published, copied or activated.
Kennis
2 itemsCheckpoint completed on 18 September 2026. Traceable source checkpoints: - Cockpit orchestration and AI-ATC: historical anchor 352cc02; functional checkpoint b3c4d01; provenance report commit df1f343. AI-ATC ran 24 unit tests, all passing. No runtime was republished. - Broker, Session Launcher and embedded Sim Agent: historical anchor b6bb580; checkpoint a600935. Versions remain Broker 0.0.1.353, Launcher 0.0.1.17 and Agent 0.0.1.14. Windows-targeted Debug build completed with 0 errors and 211 existing warnings. No publish or simulator-PC activation was performed. - Cockpit Control: historical anchor 4fa8695; checkpoint 5cf4c4f; source build 415. The suite ran 127 tests: 124 passed and 3 existing failures remained. This is a recovery/source checkpoint, not a release candidate, and was not deployed. - AI Flight Instructor remains clean at 49f5320 / release 0.26.0. Explicit remaining gaps: - RadioBridge 0.8.2 remains uncommitted on historical anchor 7ae35ff. Broad firmware, mobile, hardware, protocol and bridge changes belong to its dedicated development trajectory and were not combined blindly. - WingRally source 0.4.0 remains uncommitted on historical anchor db427fa. Its dirty tree combines application/Navigraph and XP12 bridge/plugin work; the last inspected deployed bridge remained 0.3.0 and MSFS-only. - Cockpit Tablet Agent 0.2.11 build 14 still has no Git commit. - Generated publish output, third-party binaries, APK packages, scratch files, local configuration backups and local runtime copies were excluded. These commits identify source state only. They do not prove that a previously deployed binary was built from the checkpoint or that live simulator behavior passed. Task 203 may build on Broker/Launcher checkpoint a600935.
Established workflow Develop on the local Kubuntu development machine. Publish runtimes through the NAS so the Windows simulator PC can run new versions. The user does not want development work moved to the simulator PC. The reported broker/launcher launch locations currently point into x64 Debug net8.0-windows output directories. Runtime helpers are launched through their existing CMD scripts. Resolve actual paths from local configuration during code inventory, rather than publishing user-specific absolute paths in this project. Proposed improvement Retain the development/publication workflow while defining compatible release versions for cooperating components. Stage a release locally on the simulator PC and activate it between sessions; preserve a known-good version for rollback. This release mechanism is a proposal, not reported current functionality. To investigate Map repositories, build commands, runtime folders, script arguments, host roles, ports and configuration sources. Separate developer build output from the installed runtime as implementation permits. Confirm behavior when the NAS is temporarily unavailable. Use configurable paths and host roles, with no embedded credentials in shared notes.