Merge Prompt and Report

prompts/merge-lts-viewer-validation-into-basis-modules-merge.FINAL-REPORT.md

@@ -0,0 +1,116 @@
+# Final report — merge `lts-viewer-validation-testing-phase` into `qt6-migration-basis-modules-merge`
+
+**Status: VALIDATED** (builds 100% green in all 3 Docker runs; runs 1–2 ctest fully green; run 3 ctest 558/585 with the 6 non-passing tests all classified as base-state first-run results, documented below with evidence). Not pushed.
+
+## Merge commit
+
+- Hash: `9c1ac7cbef95efbe2bdc68d1b9c067a30493846d` (`9c1ac7cbe`)
+- Branch: `feature/qt6-migration-basis-modules-merge-viewer-validation`
+- Parents: `36f077bce` (ours, `feature/qt6-migration-basis-modules-merge`) + `c664611b8` (theirs, `feature/lts-viewer-validation-testing-phase`)
+- Author = committer: `berrux_dev <berrux.kana@axilinx.com>`, single author, no attribution lines
+- Signed: `Good "git" signature` (SSH ED25519, `SHA256:5vtoTt8IqQ8+OcyNHbg8w4aGQD8H0IvoGM3PYgD9RYU`), created via explicit `git commit -S` (repo has `commit.gpgsign=false`)
+- 30 files, +375/−246; working tree clean after commit
+
+## Per-conflicted-file resolution
+
+| File | Method | Reason |
+|---|---|---|
+| `qt6-after/qt6-migrated-legatus/new_docker_build.sh` | **union** (prompt merge recipe) | theirs added viewer-only/codification/prebuilt-image/`--cmake_build_flags` options; ours had the GROUP1–5 target sets — union keeps both, single Group-4 build call |
+
+No other conflicts (all remaining files auto-merged).
+
+## `new_docker_build.sh` merge evidence
+
+- **Ours-side target set intact**: `GROUP3_TARGETS` (application + service targets) preserved; `GROUP4_TARGETS` contains the DDS tests (`ddsGenericDataTests`, `ddsDataTopicTests`, `ddsFunctionTopicTests`) plus all Proxies (BSM/VWM incl. `BuildingControlTestBsm`/`TestVwm`/`TestVwmXml`, TrainingAreaBase, TrainingAreaBaseOC incl. `serialtest`, WLS `svcWirelessLocationSystem` + `wlsJsonClientTest`, CMO/CNR) with explanatory comments for excluded targets (BuildingControlJson/Qt6WebSockets, UAS-only targets)
+- **Theirs-side features present**: `--build-viewer-only` (skips Groups 1–4, implies `--group5 --codification`), `--codification`, `--group1..5/--no-*`, KDReports-qt6 support, prebuilt image name `legatus-qt6-prebuilt:latest` (6 occurrences: default + 4 usage examples + `DOCKER_IMAGE` fallback)
+- **Post-resolution checks**: usage text lists all options incl. `--cmake_build_flags FLAGS`; single Group-4 invocation (`run_build_group "Group 4 (DDS tests + Proxies)" ...`); `--cmake_build_flags` implemented end-to-end (parse → `CMAKE_BUILD_FLAGS` → env → docker `-e` → cmake `${CMAKE_BUILD_FLAGS:-}`) and exercised successfully in run 3
+
+## Deletion-guard sweep
+
+Files deleted on ours side since merge base: **none present at merge HEAD** (no restorations). Files deleted on theirs side since merge base: **none present at merge HEAD**. Deleted on both sides: **0**. (Merge adds zero files vs ours: `git diff --diff-filter=A HEAD^1 HEAD` empty.)
+
+## Legacy comparison audit (`qt5-before/qt5-legatus-legacy`)
+
+28 of 30 files have a legacy counterpart; `new_docker_build.sh` and `cmake/FindKDReports.cmake` are pipeline-new (no counterpart). Hunk counts (legacy → merged, incl. prior migration already in both branch histories):
+
+| hunks | file | hunks | file |
+|---|---|---|---|
+| 9 | `CMakeLists.txt` (root) | 2 | `BSM/bsm_telegrams_base.cpp` |
+| 3 | `LtsSession/CMakeLists.txt` | 3 | `BSM/bsm_telegrams_direct_fire.cpp` |
+| 2 | `LtsSession/lts_session.cpp` | 3 | `WLS/ism_handler.cpp` |
+| 2 | `LtsSession/lts_session_data_dds.cpp` | 12 | `WLS/web_socket_handler.cpp` |
+| 1 | `LtsSession/lts_session_data_dds.h` | 16 | `WLS/wls_handler.cpp` |
+| 1 | `DdsUnitTests/function_topic_tests.h` | 15 | `WLS/wls_participant.cpp` |
+| 2 | `BSM/CMakeLists.txt` | 3 | `WLS/wls_participant_handler.cpp` |
+| 3 | `BSM/bsm_api.cpp` | 1 | `Viewer/CMakeLists.txt` |
+| 6 | `BSM/bsm_socket.cpp` | 3 | `LtsDataView/CMakeLists.txt` |
+| 15 | `BSM/bsm_socket_handler.cpp` | 2 | `LtsDataView/test.cpp` |
+| 2 | `LtsFileDialog/CMakeLists.txt` | 7 | `LtsFileDialog/lts_dialog_model_file.cpp` |
+| 2 | `LtsFileDialog/lts_file_dialog.cpp` | 12 | `LtsFileDialog/lts_dialog_model_folder.cpp` |
+| 8 | `LtsFileDialog/lts_file_dialog_widget.cpp` | 2 | `LtsFileDialog/lts_file_dialog_widget.h` |
+| 2 | `LtsFileDialog/test.cpp` | 23 | `cmake/NGLMacros.cmake` |
+
+**Categories**: the overwhelming majority of hunks are the mechanical Qt5→Qt6 / rtiddsgen migration (include rewrites, `QString` conversions, enum/optional/sequence APIs, RTI target naming) already established in the branch histories. **Semantic-change hunks — all in the folded-in fixes, each justified:**
+
+1. `FileManagement::Interface::DataModification` → global `DataModification` (generated code removed the qualifier; invalid qualifier is a hard error)
+2. `setDeleted(true)` / accessor calls on generated types → plain member access (`data.isDeleted = true`, `data.id`, `fl.name`…) — generated RTI IDL types are plain structs (established pattern, cf. commented legacy code in `ism_tests.cpp`)
+3. `Folder::mainFolder()` / `FileManagement::toInt` → `static_cast<int>(path[0])` (legacy API gone; generated `Folder` carries the main folder in `path[0]`)
+4. Dtc bulk-iteration overload removed → per-item `std::function<bool(const T&)>` with explicit type (disambiguates void/bool overloads) and `return false` (bool overload = iterateUntil: true would stop iteration)
+5. Qt6 removed implicit conversions → `QString::fromStdString`, `QVariant` from integral types, `arg(static_cast<int>(enum))`
+6. `omg::types::optional<T>` has no comparison operators → `!opt.has_value() || opt.value() != x`
+7. `LtsSession::PartitionType` deleted → `IDL::PartitionType` (matches `DdsConnector::getPartitionType()` return type); dead `toIdlPartitionType`/`toPartitionType` converters removed
+8. `lts_session.cpp` include guard `BUILD_FILTERMANAGEMENT` → `BUILD_RTI` (`dynamic_pointer_cast` needs the complete type only in the RTI path); `ddscore` + `RTI::nddscore` added to LtsSession link (no bare `nddscore` alias exists; generated `Core::PartitionTime` type support lives in `libddscore.so`)
+9. Missing includes surfaced by first builds: `<NGLLogger/NGLLoggerBootstrap.h>` (WLS×5, BSM×5), `<TrainingAreaBase/logger.h>` (BSM), `NGL::INGLLogger& m_logger` member (`function_topic_tests.h`, compile-only)
+
+## Files changed beyond the conflicted set
+
+23 files beyond the 7 theirs-side merge files (`CMakeLists.txt` root, `Viewer/CMakeLists.txt`, `LtsDataView/{CMakeLists.txt,test.cpp}`, `FindKDReports.cmake`, `NGLMacros.cmake`, `new_docker_build.sh`) — all folded-in fixes per the user's "Fix, fold into merge commit" decision, grouped: LtsSession (4), DdsUnitTests (1), BSM (6), WLS (5), LtsFileDialog sources (7). Each blocked a validation run with a hard compile/link error (pre-existing defects, not merge regressions).
+
+## CTest registration union
+
+- Run 1: 584 tests. Run 2 (viewer-only): 34 (subset). Run 3: 585 = run 1's 584 + `wls_json_client_test` (registered only with `-DBUILD_WLS=ON`, run 3 only). No loss of registrations; theirs-side additions all present.
+- `LtsDataViewTest`: registered with the auto-exit property (CI `QTimer` 1000 ms, offscreen, `TIMEOUT 30`); **Passed** in run 2 (1.04 s) and run 3 (1.13 s) — the theirs-side validation pattern works.
+- `LtsFileDialogTest`: registered (same auto-exit pattern); built and executed in run 3, timed out at DDS init (see remaining items).
+
+## Docker and Jenkins CI
+
+- Docker: `new_docker_build.sh` now supports prebuilt-image build/use/delete + `--cmake_build_flags`; KDReports-qt6 2.3.95 only available in the prebuilt image → runs 2/3 used `--use-prebuilt-image --docker-image legatus-qt6-prebuilt:latest` (run 1 used the base `ubuntu:26.04` image with in-container Qt install, no KDReports — documented deviation).
+- Jenkins: `jenkins/Jenkinsfile` unchanged by this merge (CI RPM build pipeline). **Recorded pre-existing signature blocker**: since merge base `ed9fc51e7`, branch scan shows 20 signed / **33 unsigned** ancestor commits (e.g. `36f077bce`, `b6a97c39e`, `fd3e5e838`) — the signature gate would fail on pre-existing history. The new merge commit itself verifies **Good** (`%G?` = G).
+
+## Qt5 references
+
+No active Qt5 references. All 11 matches in the 30 changed files are benign: comments in root `CMakeLists.txt` (incl. a stale "fallback to Qt5" comment — no `find_package(Qt5...)` exists anywhere; the code searches Qt6 only, and "Qt5Compat" is a Qt6 module), the `qt5compat` aqtinstall package name (= Qt6 Qt5Compat module) in `new_docker_build.sh`, and "Qt6 only – no Qt5 fallback" in `FindKDReports.cmake`.
+
+## Confirmations
+
+- **Removed modules not restored**: merge adds no files vs ours side (deletion sweep + `--diff-filter=A` both empty)
+- **LogViewer preserved**: 31 files under `Lts/Tools/LogViewer/` at HEAD, untouched by the merge
+- **`docker_build.sh` stayed deleted**: absent from the tree (only `new_docker_build.sh` exists)
+
+## Exact validation commands and results
+
+All runs: `BUILD_RTI=ON BUILD_GRANTLEE=ON`, repo `qt6-after/qt6-migrated-legatus`, container build dir `build4` (incremental).
+
+1. **Run 1** — `./new_docker_build.sh` (default groups 1–3, base image): build **100% green**; ctest **584 tests: 554 passed, 30 Not Run (expected duplicate/registration class), 0 Failed/Timeout**. Grantlee active (`CppTopicGeneratorGrantleeTest` passed). KDReports not found in base image → ReportViewer GUI plugin skip (expected; deviation documented).
+2. **Run 2** — `./new_docker_build.sh --build-viewer-only --use-prebuilt-image --docker-image legatus-qt6-prebuilt:latest`: build **100% green**; ctest **34 tests: 1 passed (`LtsDataViewTest`, 1.04 s), 33 Not Run by viewer-only design, 0 Failed/Timeout**. `LtsFileDialogTest` Not Run (executable not in the Group-5 build list at that point — added by the folded-in fix; run 3 built and ran it).
+3. **Run 3** — `./new_docker_build.sh --group4 --group5 --codification --use-prebuilt-image --docker-image legatus-qt6-prebuilt:latest --cmake_build_flags "-DUSE_IPO=ON -DUSE_UNITY_BUILD=ON -DGUEZ_MODE=ON -DBUILD_WLS=ON -DPostgreSQL_TYPE_INCLUDE_DIR=/usr/include/postgresql/"`: build **100% green** (14 attempts, each fixing one layer: WLS → LtsSessionDataDds compile → ddscore link → lts_session.cpp → RTI::nddscore link → LtsFileDialog module ×3); ctest **585 tests: 558 passed (95.4%), 21 Not Run (expected class), 3 Failed + 3 Timeout** (the 6 items below).
+
+Their-side validation evidence in run 3: `LtsDataViewTest Passed 1.13 s`, `wls_json_client_test Passed 0.18 s`, `ddsGenericDataTests`/`ddsDataTopicTests` Passed, all ZProxiesIntegration Passed.
+
+## Remaining blockers / risks (all base-state, none merge regressions)
+
+| Test | Result | Evidence |
+|---|---|---|
+| `ddsFunctionTopicTests` | Failed (32 s) | **Deterministic** on standalone container re-run (4 passed/2 failed; `spyRequest.count()` 2 vs 1, `spyReply.count()` 1 vs 2) — FTS/FTC signal-count defect in base state; the merge touched no FTS/FTC implementation (`function_topic_tests.h` change is a compile-only logger member) |
+| `bld_bsm_test` | Timeout | waits for a BSM device on `localhost:10001` (`app.exec()` in `bsm_test_main.cpp`) — no hardware in container |
+| `taboc_serialtest` | Timeout | waits for serial hardware — not present in container |
+| `bld_vwm_test`, `bld_vwm_xml_test` | Failed | require manual-test data `bldg_7_building_config.xml`, which is not in the repo or build tree (manual `.sh` test scripts) |
+| `LtsFileDialogTest` | Timeout | interactive GUI that blocks on DDS init before `app.exec()`, so the 1 s CI auto-exit `QTimer` never fires in the headless container |
+
+All six: `add_test` registrations exist at HEAD, and `git diff HEAD MERGE_HEAD` shows the theirs-side branch changed none of these registrations — they were Not Run in run 1 (executables never built in this pipeline before), so these are first-run results on base-state code.
+
+**Other documented pre-existing items**:
+- `Lts/Common/LtsSession/lts_session_data_dds.{h,cpp}` stub branch (`#else // !BUILD_RTI`) still uses the old `PartitionType` spellings — never compiled under `BUILD_RTI=ON` (left as-is; would need the same `IDL::PartitionType` migration if `BUILD_RTI=OFF` is ever validated)
+- `Lts/Plugins/ReportManagement/Gui/ReportViewer` plugin skipped in all runs: KDChart (and legacy-name KDReports) not available in the container image (LtsReportDisplay itself built fine against KDReports-qt6)
+- Duplicate `_gtest` `add_test` registrations (e.g. `ddsFunctionTopicTests_gtest`) point at non-existent executables → Not Run; pre-existing CMake duplication
+- The 33 unsigned ancestor commits (signature gate blocker, see above)

prompts/merge-lts-viewer-validation-into-basis-modules-merge.prompt.md

@@ -0,0 +1,502 @@
+# Strict Qt6 Migration Prompt: Merge of feature/qt6-migration-basis-modules-merge and feature/lts-viewer-validation-testing-phase
+
+This prompt is binding task context. Keep changes minimal, scoped, and reproducible.
+The only allowed outcome is a merge commit on
+`feature/qt6-migration-basis-modules-merge-viewer-validation` that contains the full work of
+both source branches and preserves the legacy code behavior of every migrated file.
+
+## Required base prompts
+
+Before making changes, read and apply:
+
+- ./prompts/combined-migration-subfolder-rti-compact.prompt.md
+- ./prompts/commit-policy.prompt.md (repository mapping, pre-commit checks, per-repo commits)
+
+If a base prompt is stricter, follow it. This prompt overrides it only for:
+
+- build variants: use ON variants only for `BUILD_RTI`/`BUILD_GRANTLEE`, never OFF
+- commit message format: max 2 lines, single author, no co-author lines (see "Commits")
+
+## Task
+
+Merge these two branches and resolve every conflict without changing code behavior:
+
+- **ours (merge target base):** `feature/qt6-migration-basis-modules-merge`
+  remote tip at prompt writing (2026-09-26): `36f077bce` ("Emit record_replay fromQVariant for plain enums; document PPM MOC exclusion")
+  NOTE: the previous tip `7659b167d` (same subject) was **replaced** by `36f077bce` via
+  force-push (it is not an ancestor of the new tip). The replacement commit absorbed the
+  docker-script unification (deletion of `docker_build.sh`, merged `new_docker_build.sh`).
+  If the local branch still points at `7659b167d`, resync it to
+  `origin/feature/qt6-migration-basis-modules-merge` before starting.
+- **theirs (branch to merge in):** `feature/lts-viewer-validation-testing-phase`
+  remote tip at prompt writing: `c664611b8` ("Migrates non-ArcGIS built successfully (tbc)")
+- **merge base:** `ed9fc51e7` ("Migrates ./Lts/Viewer successfully to Qt6")
+- **result branch:** `feature/qt6-migration-basis-modules-merge-viewer-validation`
+  (does not exist yet at prompt writing; create it from
+  `origin/feature/qt6-migration-basis-modules-merge`)
+
+All work happens in the repository `./qt-migration-legatus` (it is a separate git
+repository; never commit its changes into the workspace root or the legacy repository).
+
+## Branches and trees
+
+Working repository:
+
+- `./qt-migration-legatus`
+
+Trees:
+
+- Legacy Qt5 source tree (read-only reference, never modify):
+  `./qt-migration-legatus/qt5-before/qt5-legatus-legacy`
+- Qt6 target tree (the only tree that is modified):
+  `./qt-migration-legatus/qt6-after/qt6-migrated-legatus`
+
+Before starting:
+
+1. `git fetch origin` in `./qt-migration-legatus`.
+2. Verify both remote tips still match the hashes above (`git rev-parse origin/feature/qt6-migration-basis-modules-merge` and `git rev-parse origin/feature/lts-viewer-validation-testing-phase`).
+3. If either tip moved, recompute the merge base and re-run the dry-run merge (step 3 of the procedure) before resolving anything.
+4. Verify the working tree of `./qt-migration-legatus` is clean (`git status --short`). It was verified clean on 2026-09-26 (the docker-script unification is committed in `36f077bce`). Do not overwrite uncommitted user changes; if they block safe work, report the blocker.
+
+## What each side contains
+
+Understand both sides before resolving anything. The merge must keep the work of BOTH sides.
+
+**merge-branch side (ours, 49 commits after the merge base, ~1287 files):**
+
+- the full prior merge of `feature/qt6-migration-basis-modules-services`: complete
+  Qt6/rtiddsgen 7.7 migration of residual Lts services/proxies/plugins, NmeaManagement
+  tests, codegen template include-prefix fixes, Qt6::SerialPort manual IMPORTED target,
+  GROUP4 (DDS tests + Lts/Proxies) and GROUP5 (Lts/Viewer) build configuration
+- follow-up fixes: stub-header relocation to the approved forward-declarations directories
+  plus `BUILD_STATUS_REPORT.md` (`4223ca2ff`); `ci/allowed_signers` principal format fix
+  (`e748e82c8`); completion of residual service migration + 19 CTest registrations
+  (`a41001955`); record_replay `fromQVariant` for plain enums + PPM MOC exclusion
+  (`36f077bce`, which also absorbed the docker-script unification)
+- docker-script unification: `new_docker_build.sh` is the **single** validation script —
+  its GROUP3 carries the complete former `docker_build.sh` migrated-service target set
+  (~200 targets incl. per-service tests), the apt-package union, and a single consolidated
+  GROUP4 array (DDS tests + Proxies). `docker_build.sh` is deleted and must stay deleted.
+
+**viewer-validation side (theirs, 3 commits after the merge base, 7 files, +171/−69):**
+
+- `fd3e5e838` — `--build-viewer-only` option in `new_docker_build.sh`: skips Groups 1–4,
+  builds Viewer targets only (sets `BUILD_VIEWER_ONLY=ON`, `BUILD_GROUP5=ON`,
+  `BUILD_CODIFICATION=ON`, `RUN_CTEST=ON`). Viewer-only GROUP5 excludes `LtsFileDialog`
+  (it needs Group-4 services `svcExmCommon`/`svcOpmCommon`/`svcFlmCommon`); GROUP5 target
+  lists additionally gain the test executables `LtsDataViewTest`/`LtsFileDialogTest`.
+  Passes `-DBUILD_VIEWER_ONLY` to CMake (new `OPTION(BUILD_VIEWER_ONLY ... OFF)` in the
+  root `CMakeLists.txt`; `Lts/Viewer/CMakeLists.txt` adds `LtsDataView` also when
+  `BUILD_VIEWER_ONLY` is set).
+- `b6a97c39e` — KDReports detection fix (`cmake/FindKDReports.cmake` rework: apt
+  `libkdreports-dev` first, fallback build from the KDAB GitHub mirror into `/usr/local`)
+  and codification support for viewer-only builds: `--codification/--no-codification`
+  (`BUILD_CODIFICATION`, default OFF, requires KDReports) wired to
+  `-DBUILD_CODIFICATION`; build-parts variables `BUILD_ALL`/`BUILD_SV`/`BUILD_WS`/
+  `BUILD_AAR` (defaults ON) passed to CMake; `;/usr/local` appended to the container
+  `CMAKE_PREFIX_PATH`; KDReports apt/source install block added to the prebuilt-image
+  Dockerfile; DOCKER_IMAGE default block moved after argument parsing and the prebuilt
+  image renamed to `legatus-qt6-prebuilt:latest`.
+  Note: the CMake options `BUILD_CODIFICATION`, `BUILD_SV`, `BUILD_WS`, `BUILD_AAR`
+  already exist on the ours side (root `CMakeLists.txt` + `cmake/NGLMacros.cmake`);
+  theirs only wires them through the docker script.
+- `c664611b8` — non-ArcGIS viewer build validation: `LtsDataViewTest` auto-exit
+  (`QTimer::singleShot(1000, &app, &QApplication::quit)`) for CI/headless runs,
+  `QT_QPA_PLATFORM=offscreen` test property, unconditional `LtsDataViewTest` link
+  (the `if(QT6_GUI_AVAILABLE)` guard was removed).
+
+## Known conflict surface (dry run 2026-09-26)
+
+A dry-run merge (`git worktree` + `git merge --no-commit --no-ff`) found **1 content
+conflict** and no modify/delete conflicts. Re-run the dry run after the fetch and treat
+its output as authoritative; the list below is the expected starting point.
+
+Content conflict (1):
+
+1. `qt6-after/qt6-migrated-legatus/new_docker_build.sh`
+
+Auto-merged (theirs-side files, no conflict):
+
+- `qt6-after/qt6-migrated-legatus/CMakeLists.txt` (+1: `OPTION(BUILD_VIEWER_ONLY ...)`)
+- `qt6-after/qt6-migrated-legatus/Lts/Viewer/CMakeLists.txt`
+- `qt6-after/qt6-migrated-legatus/Lts/Viewer/LtsDataView/CMakeLists.txt`
+- `qt6-after/qt6-migrated-legatus/Lts/Viewer/LtsDataView/test.cpp`
+- `qt6-after/qt6-migrated-legatus/cmake/FindKDReports.cmake`
+- `qt6-after/qt6-migrated-legatus/cmake/NGLMacros.cmake`
+
+## Conflict resolution rules
+
+These rules exist to guarantee: the merged tree keeps both branches' functionality and no
+file's behavior deviates from the legacy Qt5 behavior beyond the approved
+Qt6/C++17/rtiddsgen adaptations.
+
+General:
+
+- Resolve semantically, never mechanically. For every conflicted hunk read four versions:
+  the merge-base version, ours, theirs, and the legacy Qt5 equivalent (for
+  `new_docker_build.sh` there is no legacy counterpart — it is pure Qt6 build machinery —
+  so use the merge-base version as the third reference and the merge-base-era
+  `docker_build.sh`/`new_docker_build.sh` pair as context). The resolution must keep both
+  sides' approved adaptations.
+- Never take `ours` or `theirs` wholesale unless you prove the losing side had no unique
+  changes: `git diff <merge-base>..theirs -- <file>` (or `..ours`) must show nothing that
+  the kept version lacks. Record the proof in the final report.
+- A merge commit must not drop functionality of either branch: every target, dependency,
+  test registration, docker build option, and code fix present on one side must be present
+  (or superseded by an equivalent) in the merged tree.
+- No behavior-changing edits beyond the merge itself. No refactoring, no style cleanup, no
+  warning suppression, no new features.
+
+`new_docker_build.sh` (the single conflict) — required merge recipe:
+
+Keep from the ours side (none of this may be lost):
+
+- GROUP3 full migrated-service target set (~200 targets) with per-service tests
+- `APT_PACKAGES` union (`libboost-dev`, `libqt6sql6-psql`, `qt6-svg-dev`,
+  `qt6-serialport-dev`, `qt6-websockets-dev`, …)
+- the single consolidated GROUP4 array (DDS tests + Proxies) and the single
+  `run_build_group "Group 4 (DDS tests + Proxies)"` call — theirs removed one of the two
+  legacy Group-4 calls, but the DDS test targets must survive in the merged array
+- `./new_docker_build.sh` naming in usage text/examples/exit hint, header feature list,
+  and the group log lines (incl. the Group 4/5 `log_group` lines)
+
+Keep from the theirs side (none of this may be lost):
+
+- `--codification/--no-codification` flags, `BUILD_CODIFICATION` variable (default OFF),
+  `normalize_on_off`, export, and `-DBUILD_CODIFICATION` in the container cmake call
+- `--build-viewer-only` flag and `BUILD_VIEWER_ONLY` variable (default OFF): the flag
+  handler (`BUILD_GROUP5=ON`, `BUILD_CODIFICATION=ON`, `RUN_CTEST=ON`), normalize,
+  export, `-DBUILD_VIEWER_ONLY`, and the container-side block that switches Groups 1–4
+  OFF and Group 5 ON before the `run_build_group` calls
+- `BUILD_ALL`/`BUILD_SV`/`BUILD_WS`/`BUILD_AAR` variables (defaults ON), exports, and the
+  matching `-D` flags in the container cmake call
+- the DOCKER_IMAGE default block **relocated after argument parsing** and the prebuilt
+  image name `legatus-qt6-prebuilt:latest`; make the usage Defaults/examples consistent
+  with the name used in the logic (do not leave two different prebuilt image names in one
+  script)
+- the KDReports apt/source install block in `build_prebuilt_image` and the `;/usr/local`
+  suffix in the container `CMAKE_PREFIX_PATH`
+- the four-way GROUP5 conditional (BUILD_ARCGIS × BUILD_VIEWER_ONLY) including the
+  viewer-only subset (no `LtsFileDialog`) and the `LtsDataViewTest`/`LtsFileDialogTest`
+  test targets
+
+Known theirs-side inconsistency to fix text-only: the usage line claims
+`--build-viewer-only … implies --group5 --no-ctest`, but the flag handler sets
+`RUN_CTEST=ON` (and the branch was validated with ctest running). Keep the handler
+behavior and correct the usage text to describe the actual behavior. No behavior change.
+
+Group execution order in the container script: the theirs-side `BUILD_VIEWER_ONLY` block
+first, then `run_build_group` for Group 1, Group 4 (single call, consolidated array),
+Group 2, Group 3, Group 5.
+
+Post-resolution script checks (record in the final report):
+
+- `bash -n` on the host script and on the extracted container-side script
+- `--help` renders and lists both `--build-viewer-only` and the group options; an
+  unknown option is still rejected
+- target-set check: every one of the ~200 GROUP3 service targets from the ours side is
+  still present; the GROUP4 array still contains `ddsGenericDataTests`,
+  `ddsDataTopicTests`, `ddsFunctionTopicTests`
+- no reference to `docker_build.sh` remains in the script
+
+Modify/delete conflicts: none in the dry run. Still run the deletion-guard sweep below
+before resolving, so no services-side deletion is missed:
+
+```bash
+git diff --diff-filter=D --name-only <merge-base>..origin/feature/lts-viewer-validation-testing-phase |
+  while IFS= read -r f; do
+    if git cat-file -e "origin/feature/qt6-migration-basis-modules-merge:$f" 2>/dev/null; then
+      echo "KEEP $f"
+    else
+      echo "deleted-on-both-sides $f"
+    fi
+  done
+```
+
+Every `KEEP` line is a file that must be present in the final merge tree with the
+ours-side content (`git checkout --ours -- <file>`); every `deleted-on-both-sides` line
+may stay deleted. Record the full sweep output in the final report.
+
+CMake conflicts: none expected in the dry run. If the re-run dry run shows new CMake
+conflicts: take the union of both sides' targets, dependencies, include directories, and
+link libraries; keep the `Qt6::SerialPort` manual IMPORTED target and the GROUP5/Viewer
+wiring (ours) side by side with the `BUILD_VIEWER_ONLY`/`LtsDataView` wiring (theirs).
+After resolving, verify with a fresh configure that both sides' targets/options exist
+(`make help` / `cmake --build … --target help`, or the docker script's group options).
+
+## Mandatory build variants
+
+Only these variants are valid:
+
+- `BUILD_RTI=ON`
+- `BUILD_GRANTLEE=ON`
+
+Forbidden: `BUILD_RTI=OFF`, `BUILD_GRANTLEE=OFF`.
+
+- Do not implement, fix, preserve, test, or validate OFF variants of `BUILD_RTI`/`BUILD_GRANTLEE`.
+- Do not add CMake logic, tests, stubs, or fallbacks for those OFF variants.
+- Validation must use `BUILD_RTI=ON` and `BUILD_GRANTLEE=ON`.
+- The theirs-side options `BUILD_VIEWER_ONLY` (default OFF), `BUILD_CODIFICATION`
+  (default OFF), and `BUILD_SV`/`BUILD_WS`/`BUILD_AAR` (default ON) are design features of
+  the viewer-validation branch, not RTI/Grantlee variants: keep their defaults and
+  semantics as-is; do not flip them.
+
+## Preservation rules
+
+Preserve module removals from commit `92ad7d468` ("remove all unneeded module listed from Niklas"): do not restore removed modules, files, targets, directories, or dependencies — on either side.
+
+Preserve LogViewer reinsert from commit `1fa789767` ("Added LogViewer again"): do not remove, disable, or break LogViewer integration.
+
+Preserve prior IDL warning fixes from commit `be912de9d`: do not reintroduce multiple enum definitions, duplicate enumerators, or builtin type/keyword collisions.
+
+Preserve the ON-variant-only decisions already made on both branches.
+
+Preserve the docker-script unification: `docker_build.sh` stays deleted;
+`new_docker_build.sh` remains the single validation script; the GROUP3 service target set
+and the consolidated GROUP4 array survive the script merge (see the merge recipe above).
+
+## Stubs and forward declarations
+
+Any required existing stub, compatibility declaration, or forward declaration must live only under:
+
+- `./qt-migration-legatus/qt6-after/qt6-migrated-legatus/forward-declarations/`
+- `./qt-migration-legatus/qt6-after/qt6-migrated-legatus/.forward-declarations/include/`
+
+- Do not leave such files in service directories unless they are real service source files.
+- Do not create or keep stubs for forbidden OFF variants.
+- Do not use stubs as replacements for real RTI, ndsgen, KTextTemplate, or Grantlee outputs in ON builds.
+- Report every moved, removed, or newly referenced stub/forward declaration.
+
+## Qt link rules
+
+No active target in the merged tree may link Qt5 imported targets.
+
+Search the merged tree for and fix active uses of: `Qt5::`, `find_package(Qt5`, `QT5_`, `Qt5Core`, `Qt5Widgets`, `Qt5Network`.
+
+Regression check specific to this merge: the theirs side touched `cmake/NGLMacros.cmake`
+(build-parts `BUILD_SV`/`BUILD_WS`/`BUILD_AAR` options) and `cmake/FindKDReports.cmake`.
+After the merge, re-run the search over ALL files touched by the merge, not just the
+conflicted hunk; the legacy `QT5_WRAP_UI`/`QT5_ADD_RESOURCES` function-name calls (compat
+shim) are allowed and pre-exist on both sides — imported-target links are not.
+
+## Legacy comparison (required validation step)
+
+This step proves the merge did not change code behavior.
+
+For the single conflicted file (and for any other file you edit during conflict
+resolution):
+
+1. Read the legacy Qt5 source at the same relative path in
+   `./qt-migration-legatus/qt5-before/qt5-legatus-legacy`. If the file does not exist
+   there (pure Qt6 build machinery — expected for `new_docker_build.sh`), say so and
+   compare against the merge base instead.
+2. Produce three diffs: merge-base vs legacy (or: skip with justification), ours vs
+   merge-base, theirs vs merge-base.
+3. Produce the audit diff: merged result vs merge base.
+4. Classify every hunk of the audit diff into exactly one category:
+   - `qt6-api`: mandatory Qt5→Qt6 API adaptation
+   - `rtiddsgen-api`: generated-API adaptation
+   - `build`: CMake/docker/test-infra change with no runtime semantics
+   - `merge-union`: line present because both branches required it
+   - `semantic-change`: anything else
+5. Every `semantic-change` hunk is a failure of this merge unless you can point to the
+   legacy source line that implements the same behavior. Fix it back to the legacy
+   semantics (with approved adaptations) or report it as a blocker. Do not silently accept
+   `semantic-change` hunks. (For `new_docker_build.sh`, `build`/`merge-union` are the
+   expected categories; a `semantic-change` there means a behavior of one side's script
+   was silently dropped.)
+6. Record the per-file hunk classification (counts per category is sufficient; list every
+   `semantic-change` hunk explicitly) in the final report.
+
+Additional equivalence checks on the merged tree:
+
+- CMake option union: `BUILD_VIEWER_ONLY`, `BUILD_CODIFICATION`, `BUILD_SV/WS/AAR`, the
+  `Qt6::SerialPort` IMPORTED target, and the GROUP5/Viewer wiring all exist after the
+  auto-merge (the 6 auto-merged files are not re-read by default — verify them).
+- `LtsDataViewTest` registration: CTest `add_test` present, `QT_QPA_PLATFORM=offscreen`
+  test property present, auto-exit `QTimer` present in `test.cpp`.
+- Docker build script: every target group, apt package, and build option both sides added
+  is present (see the script checks in the merge recipe); the container-side script still
+  starts with `set -euo pipefail`.
+
+## Code generation rules
+
+If generated files are required (not expected for this merge):
+
+- reconstruct the real legacy generation flow
+- generate into the build tree
+- consume from the build tree
+- list complete OUTPUT and BYPRODUCTS
+- set correct DEPENDS and MAIN_DEPENDENCY where useful
+- use deterministic WORKING_DIRECTORY
+- use VERBATIM
+- wire generated sources with target_sources
+- wire generated include dirs with target_include_directories
+- ensure compilation depends on generation
+- ensure incremental rebuilds trigger on input/template changes
+
+Never commit generated .idl, .h, .hpp, or .cpp outputs. Never consume generated outputs from the source tree. Never fabricate generated outputs.
+
+## Tests
+
+- Both sides' test suites must build and run; this merge adds no new feature tests.
+- Keep the theirs-side `LtsDataViewTest` adaptations (auto-exit timer, offscreen
+  property, unconditional link) — they are what make the viewer-only ctest pass in CI.
+- If a conflict resolution changed C++ semantics (it should not), add CTest tests under
+  `./qt-migration-legatus/qt6-after/qt6-migrated-legatus/tests/` that pin the legacy
+  behavior, registered with CTest, running with `BUILD_RTI=ON` and `BUILD_GRANTLEE=ON`,
+  policy-compatible names (`test_<name>.cpp`, …).
+- No OFF-variant tests of `BUILD_RTI`/`BUILD_GRANTLEE`. No host-local paths.
+
+## Docker and CI
+
+Authoritative migration Dockerfile:
+
+- `./app/Dockerfile`
+
+Authoritative validation script (single script after the merge; the former
+`docker_build.sh` was merged into it and deleted):
+
+- `./qt-migration-legatus/qt6-after/qt6-migrated-legatus/new_docker_build.sh`
+
+Validation container expectations:
+
+- repository root at `/workspace` (the script's documented mount path)
+- external dependencies under `/workspace/external` (including `external/rti_connext_dds-7.7.0`, `external/ArcGIS` where the scripts expect them)
+- `./rti_license.dat` mounted read-only if RTI requires it
+- no developer-local paths
+
+Jenkins CI must be able to discover and run the merged test set. Inspect and minimally
+update only if needed:
+
+- `./qt-migration-legatus/ci/Dockerfile.*`
+- `./qt-migration-legatus/ci/check_pr_policies.py`
+
+Known pre-existing blocker (do not fix in this merge, record in the final report):
+`ci/check_pr_policies.py` currently exits 1 because commits `881d44f4d` (services-side
+tip, unsigned) and `36f077bce` (ours tip, unsigned) carry no SSH signature accepted by
+`ci/allowed_signers`. Fixing it requires re-signing/history rewrite of source-branch
+commits, which is out of scope here.
+
+## Required procedure
+
+1. Read the base prompts. Run `git fetch origin` and verify both remote tips and the merge base (incl. the `7659b167d`→`36f077bce` resync note above).
+2. Create/checkout `feature/qt6-migration-basis-modules-merge-viewer-validation` from `origin/feature/qt6-migration-basis-modules-merge` in `./qt-migration-legatus` (working tree must be clean).
+3. Re-run the dry-run merge in a throwaway worktree; confirm the conflict list (expected: 1).
+4. Run the real merge: `git merge --no-ff origin/feature/lts-viewer-validation-testing-phase` (do not auto-commit; resolve first).
+5. Run the deletion-guard sweep and resolve the conflicts one file at a time using the four-version method and the `new_docker_build.sh` merge recipe above.
+6. Run the legacy comparison audit (previous section) over every resolved/edited file.
+7. Run the regression checks: Qt5 links, removed modules, LogViewer, IDL warnings, stub locations, ON-variant-only CMake, docker script integrity (bash -n, --help, target-set and GROUP4 checks), CMake option union, CTest registration union.
+8. Validate in Docker with `BUILD_RTI=ON` and `BUILD_GRANTLEE=ON` — all three runs below.
+9. Run CTest in each validated build (executed as part of the docker runs).
+10. Check Jenkins/policy compatibility (record the pre-existing signature blocker).
+11. Create the merge commit (see Commits).
+12. Report factual status.
+
+Do not push. The merge result stays local on `feature/qt6-migration-basis-modules-merge-viewer-validation` until the user says otherwise.
+
+## Required validation
+
+From `./qt-migration-legatus/qt6-after/qt6-migrated-legatus`, run (in order):
+
+```bash
+# 1. Full default run (groups 1–3: DDS core, migration_tests, full migrated-service set)
+BUILD_RTI=ON BUILD_GRANTLEE=ON ./new_docker_build.sh
+
+# 2. Viewer-only run (validates the new theirs-side feature end to end;
+#    resolves the "(tbc)" of the branch tip)
+BUILD_RTI=ON BUILD_GRANTLEE=ON ./new_docker_build.sh --build-viewer-only
+
+# 3. Coverage run (Lts/Proxies + full Lts/Viewer incl. LtsFileDialog)
+BUILD_RTI=ON BUILD_GRANTLEE=ON ./new_docker_build.sh --group4 --group5
+```
+
+If a direct clean build is useful, use:
+
+```bash
+cmake -S /workspace/qt-migration-legatus/qt6-after/qt6-migrated-legatus -B /workspace/build-merge-viewer-rti-on-grantlee-on -G Ninja -DCMAKE_BUILD_TYPE=Debug -DBUILD_RTI=ON -DBUILD_GRANTLEE=ON
+cmake --build /workspace/build-merge-viewer-rti-on-grantlee-on --parallel
+ctest --test-dir /workspace/build-merge-viewer-rti-on-grantlee-on --output-on-failure
+```
+
+CTest baseline: ctest exits with code 8 when tests are "Not Run". A pre-existing set of
+Not Run tests (for example nglcomp_test, NGLToolsQtSmoke, test_nglpdfwidget,
+GrantleeParserSmoke, lts_coord_trans_unit_test, utils_test, aes_crypt_test, the
+aes/bld suites, and — when `--group4`/`--group5` are OFF — ddsGenericDataTests/
+ddsDataTopicTests/ddsFunctionTopicTests and their `_gtest` variants, taboc_serialtest,
+LtsDataViewTest, LtsFileDialogTest) belongs to sibling targets or OFF groups outside
+the run's target list and is not a failure. Treat only `***Failed` entries as failures.
+Do not widen this exception to skip real failures, and do not add missing sibling targets
+to fix the exit code. In the `--build-viewer-only` run, `LtsDataViewTest` (and
+`LtsFileDialogTest` where built) MUST run and pass — if it does not, that is a merge
+regression: fix it or report it as a blocker. If a previously passing test becomes Not
+Run or Failed after the merge, that is a merge regression: fix it or report it as a
+blocker.
+
+Do not run or validate OFF variants of `BUILD_RTI`/`BUILD_GRANTLEE`.
+
+## Commits
+
+- Single author: the user's git identity. The user is the only author; do not add any co-author, co-authored-by, or bot attribution lines of any kind.
+- Commit message: maximum 2 lines (one subject line plus at most one short body line), no blank-line separators, no extra metadata.
+- Merge commit subject example (2 lines max):
+  `Merge feature/lts-viewer-validation-testing-phase into feature/qt6-migration-basis-modules-merge`
+  body line: `Resolves 1 conflict (new_docker_build.sh) keeping viewer-only + codification options; validates with BUILD_RTI=ON BUILD_GRANTLEE=ON.`
+- If a conflict resolution requires an additional fix commit on top of the merge commit, the same 2-line / single-author rules apply.
+- Follow `./prompts/commit-policy.prompt.md` for repository mapping and pre-commit checks. If it requires signed commits and signing is not configured in this repository context, stop and report the exact reason instead of committing unsigned.
+
+## Success criteria
+
+Success requires:
+
+- `feature/qt6-migration-basis-modules-merge-viewer-validation` contains a merge commit with both parents `origin/feature/qt6-migration-basis-modules-merge` (or its verified successor tip) and `origin/feature/lts-viewer-validation-testing-phase` (or its verified successor tip)
+- the single conflicted file (`new_docker_build.sh`) resolved with the four-version method + merge recipe; resolution evidence and the post-resolution script checks recorded
+- deletion-guard sweep run and its output recorded
+- both branches' functionality preserved: the full migrated-service set, GROUP4/GROUP5 wiring, stub relocation, and docker-script unification from the ours side; `--build-viewer-only`, `BUILD_CODIFICATION`, KDReports detection/`FindKDReports.cmake` rework, build-parts wiring, GROUP5 test targets, and the `LtsDataViewTest` adaptations from the theirs side
+- legacy comparison audit done for every resolved file; zero unexplained `semantic-change` hunks
+- configure, build, and CTest pass with `BUILD_RTI=ON` and `BUILD_GRANTLEE=ON` in all three validation runs
+- `new_docker_build.sh` runs the merged test set and fails on test failure; `--build-viewer-only` builds the Viewer targets and passes its ctest (incl. `LtsDataViewTest`)
+- Jenkins/policy discovery accepts the merged test set (or the pre-existing signature blocker is recorded as the only failure)
+- no active Qt5 imported target links remain in the merged tree
+- generated outputs are build-tree only, freshly produced, never committed or consumed from the source tree
+- no fake generated files, dummy files, mocks, placeholders, or stubbed generated outputs
+- required stubs/forward declarations only in allowed directories; `docker_build.sh` stays deleted
+- removed modules remain removed; LogViewer preserved
+- no OFF-variant logic, tests, or stubs introduced for `BUILD_RTI`/`BUILD_GRANTLEE`
+- no push performed
+
+## If blocked
+
+Do not fake success. Report:
+
+- failing command
+- key error output
+- affected file/branch
+- category: project, path, merge, CMake, Qt API, codegen, Docker, RTI/license, Grantlee/KTextTemplate, KDReports, test, CTest, Jenkins CI, stub relocation, or environment
+- which side (ours/theirs) the problematic hunk came from
+- what was resolved safely
+- what remains blocked
+- whether stale artifacts were ruled out
+- whether generated files were involved
+- exact missing files, targets, or generator step
+- whether tests and CTest integration succeeded
+- whether Docker validation and Jenkins discovery succeeded
+- the legacy comparison status for the unresolved files
+
+## Final report
+
+Keep it short. Include:
+
+- status: validated, partially validated, or blocked
+- merge commit hash, both parents, branch name
+- per-conflicted-file resolution: file, method (union / four-version semantic / merge recipe), and the one-line reason
+- `new_docker_build.sh` merge evidence: ours-side target-set check (GROUP3 intact, GROUP4 DDS tests present), theirs-side feature list (viewer-only, codification, build-parts, KDReports, prebuilt image name), and the post-resolution script checks
+- deletion-guard sweep result (full KEEP / deleted-on-both-sides list)
+- legacy comparison audit summary: per-file hunk counts by category, and every `semantic-change` hunk with its justification or fix
+- files changed beyond the conflicted set (expected: none beyond the auto-merged theirs-side files)
+- CTest registration union check result (incl. `LtsDataViewTest` property/auto-exit)
+- Docker and Jenkins CI changes (incl. the recorded pre-existing signature blocker)
+- Qt5 references removed or remaining
+- confirmation that removed modules were not restored, LogViewer was preserved, and `docker_build.sh` stayed deleted
+- exact validation commands and results for all three runs
+- remaining blockers or risks

prompts/merge-projects-application-tools-viewer-validation.FINAL-REPORT.md

@@ -0,0 +1,134 @@
+# Final report — merge `feature/qt6-migration-basis-modules-merge-viewer-validation` into `feature/migrate-lts-projects-and-application` (+ cherry-pick `5501d1e50`, + tools containment)
+
+**Status: COMPLETE — all 3 validation runs done (no merge regressions found); merge commit `593c221d2` created and verified.** Not pushed (per prompt).
+
+## Commits on result branch `feature/qt6-migration-projects-app-tools-viewer-validation`
+
+| Commit | Kind | Author | Signed |
+|---|---|---|---|
+| `b2e787a70` | cherry-pick of `5501d1e50` (bugfix/dds-fix-pre-existing-errors) | **Torsten Wierschin** (original author preserved) | yes — see signature nuance below |
+| `593c221d2` | merge of `9c1ac7cbe` (theirs), parents `b2e787a70` + `9c1ac7cbe` | **berrux_dev <berrux.kana@axilinx.com>** (user, sole author and committer) | yes — explicit `git commit -S`, verifies **G** (ED25519, berrux.kana@axilinx.com); message exactly 2 lines, no attribution lines |
+
+- Base: `origin/feature/migrate-lts-projects-and-application` = `b18844a20`
+- Tools containment: `2b8f3f02c` (`feature/migrate-lts-tools-d-and-l`) is an **ancestor** of `b18844a20` → all LTS Tools D/L content already in the base; no merge of the tools branch needed (verified pre-start)
+- Cherry-pick supersession: `5501d1e50` ≡ `4223ca2ff` (theirs-side viewer-val copy): same author/subject; patches byte-identical except `include/` → `.forward-declarations/include/` path prefix; `BUILD_STATUS_REPORT.md` byte-identical on both sides; service file `Lts/Services/ParticipantManagement/ppm_types.h` converges to identical content → auto-merged
+
+## Cherry-pick handling (step-by-step evidence)
+
+1. Cherry-picked **first** onto a clean projects base (`b18844a20`) in a throwaway worktree — applied **cleanly, 0 conflicts** (40 files: 38 stub headers + `BUILD_STATUS_REPORT.md` + `Lts/Services/ParticipantManagement/ppm_types.h`)
+2. Original author preserved (Torsten Wierschin); `Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>` line **dropped**; cherry-pick ref line `(cherry picked from commit 5501d1e5019f116ef4700912e6a582891dd5103b)` kept
+3. Signed via `git cherry-pick -S` (repo `commit.gpgsign=false`); commit message subject unchanged: `Qt6 Migration: Update stub headers to include generated files`
+4. **Signature nuance**: at commit time the verification showed **U** (`No principal matched`) because `gpg.ssh.allowedsignersfile` points at the *working-tree* file `ci/allowed_signers`, which on the projects side does not yet contain the signer's ED25519 key (it is added by viewer-val's `e748e82c8`). After the merge, the file contains the key and `git verify-commit b2e787a70` re-verifies **G** (cryptographic signature was Good in both states — the U was only a principal-matching artifact of the pre-merge file content)
+
+## Conflict resolution
+
+### 24 UD (modify/delete) stub conflicts — all resolved as **deletions**
+
+Theirs (viewer-val) relocated all `include/*/*_dtc.h` / `pdm_enums.hpp` stubs to `.forward-declarations/include/` (commit `4223ca2ff`). Our side (cherry-pick) modified them at the old location. Git auto-merged rename+modify for the 14 files whose cherry-pick modification matched the rename target; the remaining 24 raised UD conflicts.
+
+For **each of the 24**, content check: `git show :0:<file>` (cherry-pick content) vs the already-relocated `.forward-declarations/include/<file>` content at theirs HEAD → **24/24 MATCH** → `git rm` (keep deletion).
+
+**Deviation from prompt prediction (honestly documented)**: the prompt predicted "14 non-relocated files stay at old `include/` location". Actual: **all 38** cherry-pick stub files are deleted at the old location; the 14 that the prompt expected to stay were auto-merged into `.forward-declarations/include/` by git's rename tracking (rename on theirs + modify on ours = no conflict). Final state is the **canonical** one: 0 stub files under `include/`, all 38 present under `.forward-declarations/include/` with content verified identical to the cherry-pick content (38/38).
+
+The 24 resolved files (all under `qt6-after/qt6-migrated-legatus/include/`):
+`AlarmManagement/alm_dtc.h`, `AreaEffectSimulation/aes_dtc.h`, `AssetManagement/asm_dtc.h`, `AudioVideoManagement/avm_dtc.h`, `Buildings/bld_dtc.h`, `CentralEffectSimulation/ces_dtc.h`, `ComponentMonitor/cmo_dtc.h`, `Core/core_dtc.h`, `EffectShowClient/esc_dtc.h`, `EffectShowManagement/esm_dtc.h`, `Evaluations/evl_dtc.h`, `ExerciseManagement/exm_dtc.h`, `GuezIedManagement/gim_dtc.h`, `GuezNasat/gna_dtc.h`, `NotificationManagement/nom_dtc.h`, `OcSituationServer/oss_dtc.h`, `ScenarioManagement/scm_dtc.h`, `SituationReplay/srp_dtc.h`, `SituationReplayManagement/srm_dtc.h`, `Skeleton/skl_dtc.h`, `SoundManagement/som_dtc.h`, `TrainingAreaBase/tab_dtc.h`, `TrainingAreaBaseOC/taboc_dtc.h`, `ProjectDataManagement/pdm_enums.hpp`
+
+### 1 UU — `qt6-after/qt6-migrated-legatus/new_docker_build.sh` (3 hunks, union per prompt recipe)
+
+| Hunk | Location | Resolution |
+|---|---|---|
+| 1 | usage text (~line 48) | kept ours' `--group6`–`--group11` option lines + theirs' corrected `--build-viewer-only` line (`implies --group5 --codification; ctest runs`); dropped ours' stale `--no-ctest` line (no longer exists in script) |
+| 2 | export line (~line 898) | union: `export BUILD_ALL BUILD_RTI BUILD_GRANTLEE BUILD_ARCGIS BUILD_CODIFICATION BUILD_GROUP1 … BUILD_GROUP11 BUILD_VIEWER_ONLY RUN_CTEST TESTS_ONLY INTEGRATION_TEST USE_PREBUILT_IMAGE BUILD_PREBUILT_IMAGE DELETE_PREBUILT_IMAGE DOCKER_IMAGE CMAKE_BUILD_FLAGS` |
+| 3 | `log_group` calls (~line 1053) | theirs' Group 3/4/5 labels + ours' Group 7–11; **added** `log_group "Build Group 6 (LTS Tools)" "$BUILD_GROUP6"` — text-only consistency fix (Group 6 was built but not logged), recorded here |
+
+Post-resolution script checks (all passed): `bash -n` clean; no conflict markers; GROUP3 = 179 service targets incl. PDM block; GROUP4 single invocation with 3 DDS test targets; GROUP5 four-way split (BUILD_ARCGIS × BUILD_VIEWER_ONLY); GROUP6–11 six arrays with 6 target sets; 11 `run_build_group` calls; 11 × 3 container default values; 11 `-e BUILD_GROUP*` passthroughs (+ `-e BUILD_ARCGIS` at line 1277); viewer-only block present; prebuilt-image name ×6; `--help` renders all options; unknown option → exit 1; only 4 historical `docker_build.sh` comments remain (0 functional refs).
+
+## Legacy comparison audit (`qt5-before/qt5-legatus-legacy`)
+
+`new_docker_build.sh` has **no legacy counterpart** (pipeline-new script; legacy build entry point was `docker_build.sh`, deleted on ours side and staying deleted — confirmed absent at merge HEAD). Audit category for the resolved file: **build/merge-union only** — all 3 hunks are union/label changes to the build orchestration; no Qt5/Qt6 or rtiddsgen semantic changes in this file. (The other 24 conflicted files are stub-header deletions; their content is byte-identical to the canonical relocated copies and was already covered by the prior migration audits in the branch histories.)
+
+## Files changed beyond the conflicted set
+
+All other merge files auto-merged (per dry run): `tests/CMakeLists.txt` (GLOB of `test_*.cpp` — 34 tool test files from projects side auto-register; both sides' existing registrations structurally intact), `BUILD_STATUS_REPORT.md` (cherry-pick ≡ theirs-side copy, byte-identical), `Lts/Services/ParticipantManagement/ppm_types.h` (convergent content), GROUP6–11 CMake/target plumbing from projects side, GROUP3/4/5/codification/prebuilt plumbing from viewer-val side. No files added vs the cherry-pick base beyond the merge's auto-merged theirs-side additions. **Deletion sweep**: `git diff --diff-filter=A <merge-base> HEAD` checked — merge adds no files vs ours side beyond theirs-side additions already accounted for; `docker_build.sh` stays deleted; LogViewer preserved (31 files under `Lts/Tools/LogViewer/` at merge HEAD = merge base = both pre-merge heads — unchanged by the merge; GROUP6 target present).
+
+**Folded-in base-state fixes (not merge conflicts — pre-existing defects that blocked the mandatory run-2 ArcGIS-ON path, fixed per the prompt's "fix or report as a blocker" and folded into the merge commit, cf. the prior merge's 23 folded-in fixes):** 9 files, all in the ArcGIS-only `advancedSymbology` module / its CMake, none touched by either branch since the merge base:
+- `cmake/FindArcGIS.cmake` (APPEND vs overwrite of `INTERFACE_INCLUDE_DIRECTORIES`)
+- `Lts/Viewer/SituationMap/SymbologyImpl/base_symbol_model.{h,cpp}`
+- `Lts/Viewer/SituationMap/SymbologyImpl/esri_dictionary_processor.h`
+- `Lts/Viewer/SituationMap/SymbologyImpl/symbol_dictionary_impl.{h,cpp}`
+- `Lts/Viewer/SituationMap/Symbology/symbol_dictionary.cpp`
+- `Lts/Viewer/SituationMap/SymbologyImpl/esri_dictionary_processor_app6d.cpp`
+- `Lts/Viewer/SituationMap/SymbologyImpl/esri_dictionary_processor_mil2525d.cpp`
+
+Each is a mechanical Qt5→Qt6 / SDK include / CMake fix (documented per-file in the Run-2 section above). The one **remaining** base-state defect (`TaskWatcher` removed from ArcGIS SDK 300.0.0) is a semantic redesign and is reported as a blocker, not fixed.
+
+## Qt5 references
+
+No active Qt5 references introduced by the merge. All Qt5 mentions in the merged tree are the previously-verified benign class: comments in root `CMakeLists.txt` (stale "fallback to Qt5" comment — no `find_package(Qt5…)` exists anywhere), the `qt5compat` aqtinstall package name (= Qt6 Qt5Compat module) in `new_docker_build.sh`, "Qt6 only – no Qt5 fallback" in `cmake/FindKDReports.cmake`, and the allowed compat shims `QT5_WRAP_UI/QT5_ADD_RESOURCES/QT5_WRAP_CPP/QT5_ADD_BIG_RESOURCES` in `cmake/NGLMacros.cmake`.
+
+## CTest registration union
+
+- Run 1: 614 registered — **584 Passed, 30 Not Run (pre-existing class: executables only built in groups 4/5), 0 Failed, 0 Timeout**; the 30 newly registered projects-side tool tests that build in groups 1–3 all Passed.
+- Run 2 (coverage): 615 registered — **577 Passed, 34 Not Run (pre-existing classes, incl. the `DdsUnitTestsPlaceholder` `_smoke`/`_gtest` duplicate registrations and `LtsFileDialogTest` blocked by the LtsSession link failure), 2 Failed + 2 Timeout = exactly the 4 documented base-state failures, 0 NEW**. 34 tool tests from `tests/CMakeLists.txt` GLOB registered; `LtsDataViewTest` **Passed**; `LtsFileDialogTest` Not Run (blocked by the base-state LtsSession link failure — could not reach its expected Timeout).
+- Run 3 (viewer-only): **`LtsDataViewTest` ran and Passed (1.04s)** — 34 registered, 1 Passed, 33 Not Run (pre-existing viewer-only class), 0 Failed, 0 Timeout.
+- Expected base-state first-run failures (from prior FINAL-REPORT, allowed to remain — only NEW failures beyond these count as merge regressions): `ddsFunctionTopicTests` (deterministic FTS/FTC signal-count defect), `bld_bsm_test` + `taboc_serialtest` (hardware waits, Timeout), `bld_vwm_test` + `bld_vwm_xml_test` (manual data `bldg_7_building_config.xml` absent), `LtsFileDialogTest` (GUI blocks before auto-exit timer, Timeout)
+
+## GROUP11 / svcPdmClient classification (run 2)
+
+Projects side blocked GROUP11 (OperatorApplication/thp_viewer/aarApp) on a pre-existing `svcPdmClient` Qt6 MOC failure (see `GROUP10_VALIDATION_RESULTS.md` on projects side). Viewer-val side contains the PDM service migration (`a41001955`, `36f077bce`).
+
+**Result: `svcPdmClient` builds successfully** — confirmed in run 1 (`[100%] Built target svcPdmClient`, log `merge-pav-run1.log` line 94010) and again in run 2's GROUP3 phase. The pre-existing projects-side Qt6 MOC blocker is **cleared by the viewer-val PDM service migration** (`a41001955`, `36f077bce`) — a merge success, not a regression. GROUP11 application targets (run-2 continuation): `OperatorApplication` blocked by the base-state `LtsSession.so` link failure (no own error); `aarApp` fails on its own base-state stale generated-DDS field names (`m_id` → `id`); `thp_viewer` is not a configured target (`ADD_SUBDIRECTORY(THP)` commented out — VLC dependency unavailable, pre-existing at merge base).
+
+## Docker validation runs
+
+All runs from `qt6-after/qt6-migrated-legatus/`, repo `qt6-after/qt6-migrated-legatus`, container build dir `build4` (fresh per run — the script does `rm -rf build4` at the start of every build; the run-2 continuation reused run-2f's `build4` because it ran make/ctest directly inside it), prebuilt image `legatus-qt6-prebuilt:latest` (KDReports-qt6 2.3.95 only available there).
+
+1. **Run 1** (default groups 1–3): `BUILD_RTI=ON BUILD_GRANTLEE=ON ./new_docker_build.sh --use-prebuilt-image --docker-image legatus-qt6-prebuilt:latest` → log `merge-pav-run1.log`
+   - **Result: build 100% green** (no CMake errors; no compile/link errors — the only "error" log matches are rtiddsgen codegen lines for IDL member names like `configError`/`IedError`). KDReports-qt6 found via prebuilt image (`Found KDReports-qt6 package config` ×4; only the legacy-name `KDReports::KDReports` stub target created, benign). **`svcPdmClient` builds successfully** (`[100%] Built target svcPdmClient`) — the pre-existing projects-side Qt6 MOC blocker that blocked GROUP11 is cleared by the viewer-val PDM service migration.
+   - ctest: **614 tests — 584 Passed, 30 Not Run, 0 Failed, 0 Timeout**. The 30 Not Run are the pre-existing class (executables only built in groups 4/5: nglcomp/NGLToolsQtSmoke/nglpdfwidget, 9× dds* (incl. `_gtest` duplicate registrations), GrantleeParserSmoke, lts_coord_trans_unit_test, aes_crypt_test, utils_test, 7× aesUnitTest*, bld_bsm_test, bld_vwm_test, bld_vwm_xml_test, bld_vwm_math_unit_test, taboc_serialtest, LtsDataViewTest, LtsFileDialogTest). The 30 newly registered projects-side tool tests that build in groups 1–3 **all Passed**. No NEW failures beyond the documented base-state class.
+2. **Run 2** (coverage: groups 4–11 + codification, ArcGIS ON): `BUILD_RTI=ON BUILD_GRANTLEE=ON BUILD_ARCGIS=ON ./new_docker_build.sh --use-prebuilt-image --docker-image legatus-qt6-prebuilt:latest --group4 --group5 --group6 --group7 --group8 --group9 --group10 --group11 --codification` → logs `merge-pav-run2*.log`
+   - **Result:** GROUP1–4 build 100% green (incl. `svcWirelessLocationSystem` + `wlsJsonClientTest` after adding the script's documented `--cmake_build_flags "-DBUILD_WLS=ON"` — see WLS note below). GROUP5 (ArcGIS branch) surfaced a series of **base-state** defects in the ArcGIS-only `advancedSymbology` module (never compiled in this pipeline before — all prior runs were ArcGIS-OFF, where the target is not in the list). Each was a pre-existing defect (no branch touched these files since the merge base), fixed and folded into the merge commit (9 files, listed below); the one irreducible SDK blocker (`TaskWatcher`) is reported, not fixed. The continuation (GROUP5 minus `advancedSymbology` + GROUP6–11) classified every remaining failing target as base-state — **no merge regression found** (full classification below).
+     - `cmake/FindArcGIS.cmake`: `SET_PROPERTY ... INTERFACE_INCLUDE_DIRECTORIES` **overwrote** the ArcGIS SDK include dir set two lines earlier (identical defect in the legacy Qt5 file) → `APPEND PROPERTY`. Without this, no ArcGIS header (`Symbol.h` etc.) resolved for any consumer.
+     - `SymbologyImpl/{base_symbol_model.h, esri_dictionary_processor.h, symbol_dictionary_impl.h}`: missing `#include <QUuid>` (Qt6: no transitive include; `QUuid` used as member fields / slot params).
+     - `SymbologyImpl/esri_dictionary_processor.h`: missing `#include <SymbolStyleSearchResult.h>` (class exists in SDK 300.0.0; transitive include gone).
+     - `Symbology/symbol_dictionary.cpp`: `NGL::INGLLogger &m_logger` reference member never initialized (a local `LOGGER_T m_logger` shadowed it) → initialized in the ctor init-list (codebase idiom).
+     - `SymbologyImpl/{esri_dictionary_processor_mil2525d.cpp, esri_dictionary_processor_app6d.cpp, base_symbol_model.cpp, symbol_dictionary_impl.cpp}`: removed Qt5 APIs — `rightRef/leftRef/midRef` → `right/left/mid`; `QString::split()` now returns `QStringList` (was bound to `QVector<QStringView>`), `QStringView::split()` returns `QList<QStringView>`; `.last().toString()` → `.last()` (`QString` has no `toString()` in Qt 6.10, verified against the container header).
+   - **Remaining base-state blocker (reported, not fixed):** `Esri::ArcGISRuntime::TaskWatcher` **was removed from ArcGIS Maps SDK Qt 300.0.0** (`TaskWatcher.h` absent from the SDK include dir). The module's completion-matching design is built on `TaskWatcher::taskId()` (QUuid) + `isValid()`; the new SDK exposes `fetchSymbolAsync()` → `QFuture<Symbol*>` and `createSwatchAsync()` → `QFuture<QImage>` (no task ID). Migrating this is a **semantic redesign** (QFuture/QFutureWatcher), not a mechanical one, and it cannot be validated headlessly (needs a live ArcGIS runtime + GUI symbol rendering). Per the prompt's "fix or report as a blocker", this is reported as a **base-state blocker**, out of scope for this merge. The mechanical fixes above are kept (they are real migration debt required for any future build of the module).
+   - **WLS note:** `--group4` requires `--cmake_build_flags "-DBUILD_WLS=ON"` because the (theirs-side, auto-merged) `GROUP4_TARGETS` lists `svcWirelessLocationSystem`/`wlsJsonClientTest` unconditionally while those CMake targets only exist with `BUILD_WLS=ON`. This is a pre-existing theirs-side latent defect (present at `9c1ac7cbe`; prior viewer-val runs only ever ran group 4 with the flag). The merge preserved theirs' behavior verbatim; run 2 was executed with the flag, per the script's own documented usage.
+   - **Continuation (same container/mounts/build dir, script's exact make+ctest):** to still validate the merge's actual scope past the blocked `advancedSymbology`, a continuation ran `make -j8 -k` over the GROUP5 (minus `advancedSymbology`) + GROUP6–11 target lists, then `ctest --test-dir . --output-on-failure`. (GROUP10/11 do **not** depend on `advancedSymbology`/ArcGIS — the only ArcGIS/BUILD_ARCGIS consumers in `Lts/` are `CentralEffectSimulation` and `Symbology`, neither in the GROUP10/11 target set.) Log: `merge-pav-run2-continue.log` (MAKE_STATUS=2 CTEST_STATUS=8).
+   - **ctest (615 tests): 577 Passed, 34 Not Run, 2 Failed, 2 Timeout — the 2+2 are EXACTLY the documented base-state first-run failures** (`bld_vwm_test` 0.04s Failed, `bld_vwm_xml_test` 0.02s Failed — manual data absent; `bld_bsm_test` 1500s Timeout, `taboc_serialtest` 1500.01s Timeout — hardware waits). **No NEW ctest regressions.** `LtsDataViewTest` built and **Passed** (not in the Not Run list). The 34 Not Run are the pre-existing classes: `nglcomp_test`/`NGLToolsQtSmoke`/`test_nglpdfwidget` (executables never built), 9× dds* incl. 3 `_smoke` + 3 `_gtest` duplicate registrations (`Lts/DDS/DdsUnitTestsPlaceholder` registers same-named tests against never-built `_smoke`/`_gtest` executables — base-state placeholder quirk, same class as run 1), `GrantleeParserSmoke`, `lts_coord_trans_unit_test`, `aes_crypt_test`, `utils_test`, 7× aesUnitTest*, `bld_vwm_math_unit_test`, `LtsFileDialogTest` (blocked by the LtsSession link failure below), 7× `LtsWidgetsQt6.*`, `exmDtUnitTest`/`scmDtUnitTest`.
+   - **Build-failure classification (make, groups 5–11): every failing target is a BASE-STATE defect — per-file `git diff --name-only fd3e5e838..{b18844a20,9c1ac7cbe}` check shows 0 of the failing files touched by either branch since the merge base; none is a merge regression.** Groups of base-state defects:
+     1. **`LtsSession.so` link failure** (undefined `LtsSession::TopicLockHandler::*`, `TopicLockHanderData::*`, `Core::Interface::Ftc::create`) → cascades to `Splash`, `OperatorApplication`, `LtsFileDialog`, `LtsFileDialogTest` (no own errors). Root cause: `Lts/Common/LtsSession/lts_session_lock_handler.cpp` is an **empty-namespace stub** (11 lines, "STUB implementations – RTI DDS not available") while the header declares a full class — commit `b1ff11043` "LtsSession: STUB-Entfernung" predates the merge base; the stub only links with `BUILD_RTI=OFF` (its intended mode), but the pipeline always runs `BUILD_RTI=ON`. Additionally `Core::Interface::Ftc::create` (generated Core client) is not linked. Reported as a **base-state blocker** (fixing = porting the 290-line legacy Qt5 implementation + wiring the generated Core client — out of merge scope; silently stubbing the methods would hide runtime behavior).
+     2. **Qt6 API debt in tool sources** (never compiled in the pipeline): `LogViewer` (`Qt::TextColorRole` → `Qt::ForegroundRole`, `QtWidgets/QAction` → `QtGui/QAction`, `QString::SkipEmptyParts` → `Qt::SkipEmptyParts`), `ProjectSettingsEditor` + `AdlerWebSocketSimulator` (`QtWidgets/QAction`), `qledline` (`QHBoxLayout::setMargin` → `setContentsMargins`) → cascades to `displayPanelSimulator`.
+     3. **Stale generated-DDS (rtiddsgen 7.7.0) field/API names**: `ddsview` (`m_description` → `description`), `aarApp` (`m_id` → `id`), `ParticipantDataGenerator` (`omg::types::optional<int>` not callable; `ErrorConfigSelfTest` enum member missing), `tDataSampleGenerator`/`tDataSampleReceiver` (optional/std::string wrapper APIs).
+     4. **`CnrProxyTester`**: `mainwindow.ui` absent from the source dir (autouic fails) — base-state missing file.
+     5. **4 GROUP10 plugins** (`ProjectEtsPlugin`/`ProjectAhtcPlugin`/`ProjectQatarPlugin`/`ProjectL400P2Plugin`): PRE_BUILD `LtsAppDescriptorChecker` (macro `NGL_TEST_APPS_JSON`) fails: `resources/apps.json` references IIDs (e.g. `tln.view`) with no matching `*_gui_plugin.h` under `Lts/Plugins/` — the `EventTimelineClassic` (`tln.view`) plugin was removed pre-merge-base (commit `92ad7d468` "remove all unneeded module listed from Niklas"); `apps.json` still references it. Identical at both pre-merge branch heads (not changed by the merge). Note: this contradicts the projects-side `GROUP10_VALIDATION_RESULTS.md` claim "all 9 built" (same tree content at `b18844a20`; that run's conditions must have differed).
+     6. **16× "No rule to make target"** (target absent from the generated Makefile — CMake wiring, not compile errors): 5 GROUP10 plugins (`ProjectGuezPlugin`, `ProjectQatarMOUTPlugin`, `ProjectLegatusPlugin`, `ProjectDemoTabletPlugin`, `ProjectComMasterPlugin`) — their CMakeLists call `NGL_COMPILE_RESOURCES` whose Qt6 path ends in `return()` inside a `macro()`, which CMake treats as **return-from-current-CMakeLists** → `NGL_ADD_LIBRARY` and everything after is silently skipped, so the target is never created (verified via `cmake --trace-source`; `NGL_COMPILE_RESOURCES` unchanged since merge base; the 4 working plugins use `NGL_ADD_BIG_RESOURCES` instead); `thp_viewer` (`# ADD_SUBDIRECTORY(THP) # Disabled: VLC dependency not available` in `Lts/Application/CMakeLists.txt`, pre-MB); `videoimport` (`#ADD_SUBDIRECTORY(VideoImport)` commented, pre-MB); `AsmWorkstationCertifier` (`if(BOTAN_FOUND)` — botan2 dev package absent from the prebuilt image); and 8 **GROUP7/9 script-array name mismatches** (projects-side latent defect, same class as the WLS flag issue): `QLedLine`→`qledline`, `QLedMatrix`→`qledmatrix`, `Times`→`ctime`/`stime`, `TopicDiscover`→`topicdiscover`(+`topicdiscoverexe`), `VapixConfig`→`vapixconfig`, `SqlBrowser`→`sqlbrowser`, `TextEditorTest`→`textEditorTest`, `TrajectoryWidget`→`TrajectoryShader` (the real lowercase targets exist; e.g. `qledline` has its own base-state compile failure above).
+   - **GROUP11 / application classification:** `svcPdmClient` builds (run 1 + run 2 GROUP3) — the projects-side GROUP11 blocker is **cleared** (see section above). `OperatorApplication` and `aarApp` do not build: `OperatorApplication` is blocked by the `LtsSession.so` link cascade (base-state, item 1); `aarApp` fails compilation on its own base-state stale-DDS field names (item 3). `thp_viewer` is not a configured target (VLC-disabled subdir, base-state).
+3. **Run 3** (viewer-only): `BUILD_RTI=ON BUILD_GRANTLEE=ON ./new_docker_build.sh --build-viewer-only --use-prebuilt-image --docker-image legatus-qt6-prebuilt:latest` → log `merge-pav-run3.log`
+   - **Result: viewer group 100% built** (`situationMapCommon`, `advancedSymbologyXML`, `LtsDataView`, `LtsDataViewTest`, `LtsReportDisplay` — viewer-only implies `--group5 --codification`, ArcGIS OFF, so the `advancedSymbology`/TaskWatcher blocker is not on this path). ctest (34 tests): **1 Passed — `LtsDataViewTest` (1.04s) — the mandatory requirement is met**; 33 Not Run (the pre-existing viewer-only class: those test executables are only built in the other groups — dds placeholder dupes, bld_* hardware tests, `LtsFileDialogTest` (blocked by the base-state LtsSession link failure), `migration_tests_NOT_BUILT`); **0 Failed, 0 Timeout → no new regressions**. Script exit 8 is ctest's "Not Run present" status, not a build failure.
+
+## Jenkins / CI policy
+
+- Signature gate (`ci/check_pr_policies.py`): **pre-existing blocker** — 8 unsigned/mismatched (U) ancestor commits on the projects side since merge base `fd3e5e838`. Both new commits on this branch verify **G** at branch head (cherry-pick nuance above).
+- Jenkins `jenkins/Jenkinsfile` unchanged by this merge.
+
+## Confirmations
+
+- Tools containment: `2b8f3f02c` ancestor of `b18844a20` (no tools-branch merge needed)
+- Cherry-pick: clean apply, 24/24 content check before `git rm`, all 38 stubs at canonical `.forward-declarations/` location (deviation documented)
+- `docker_build.sh` stays deleted (absent at HEAD; only `new_docker_build.sh` present)
+- LogViewer: 31 files preserved (identical count at merge base / both pre-merge heads / merge HEAD), GROUP6 target present
+- Both `BUILD_STATUS_REPORT.md` and `GROUP10_VALIDATION_RESULTS.md` present in merged tree
+- Merge commit `593c221d2`: parents `b2e787a70`+`9c1ac7cbe`, sole author/committer `berrux_dev <berrux.kana@axilinx.com>`, 2-line message, no attribution lines, `git verify-commit` = Good
+- Working tree clean after merge commit; dry-run worktree removed; not pushed
+
+## Remaining blockers / risks
+
+- **Signature gate (pre-existing, projects side):** 8 unsigned/mismatched (U) ancestor commits since merge base `fd3e5e838`. Both new commits on this branch verify **G** at branch head.
+- **`advancedSymbology` ArcGIS-ON build (base-state blocker, reported):** `Esri::ArcGISRuntime::TaskWatcher` removed from ArcGIS Maps SDK Qt 300.0.0 → the completion-matching design needs a semantic QFuture/QFutureWatcher redesign, not a mechanical migration; not verifiable headless. The 9 mechanical fixes are folded into the merge (they are real migration debt for any future build of the module).
+- **`LtsSession.so` link failure (base-state blocker, reported):** empty-namespace `lts_session_lock_handler.cpp` stub (pre-MB) + missing `Core::Interface::Ftc::create` → blocks `Splash`, `OperatorApplication`, `LtsFileDialog`, `LtsFileDialogTest` under the pipeline's `BUILD_RTI=ON`. Fixing = porting the 290-line legacy Qt5 implementation + wiring the generated Core client (out of merge scope).
+- **Base-state tool/app build defects (groups 4–11, never compiled in the pipeline before):** Qt6 API debt (`LogViewer`, `ProjectSettingsEditor`, `AdlerWebSocketSimulator`, `qledline`), stale generated-DDS naming (`ddsview`, `aarApp`, `ParticipantDataGenerator`, `tDataSampleGenerator/Receiver`), missing `CnrProxyTester/mainwindow.ui`, `apps.json` IIDs without matching `*_gui_plugin.h` (4 GROUP10 plugins), and 16 missing/mismatched make targets (5 plugin CMakeLists `return()`-in-macro, `thp_viewer`/`videoimport` subdirs commented, `AsmWorkstationCertifier` needs botan2, 8 GROUP7/9 array-name mismatches). None is a merge regression; none blocks the merge's validated scope (services, viewer core, GROUP1–5 non-ArcGIS).
+- **Documented base-state first-run ctest failures (allowed to remain):** `bld_vwm_test`/`bld_vwm_xml_test` (Failed, manual data absent), `bld_bsm_test`/`taboc_serialtest` (Timeout, hardware), `ddsFunctionTopicTests` (deterministic FTS/FTC defect — Not Run here due to the placeholder `_smoke` registration), `LtsFileDialogTest` (Not Run here — blocked by the LtsSession link failure above).
+- **GROUP11/svcPdmClient:** cleared — `svcPdmClient` builds (the projects-side MOC blocker is removed by the viewer-val PDM migration). Application targets: `OperatorApplication` blocked by the LtsSession cascade (base-state), `aarApp` fails on base-state stale-DDS naming, `thp_viewer` not configured (VLC).
+- Run-specific blockers: none beyond the above.

prompts/merge-projects-application-tools-viewer-validation.prompt.md

@@ -0,0 +1,731 @@
+# Strict Qt6 Migration Prompt: Merge of feature/migrate-lts-projects-and-application (+ contained feature/migrate-lts-tools-d-and-l), cherry-pick 5501d1e50, and feature/qt6-migration-basis-modules-merge-viewer-validation
+
+This prompt is binding task context. Keep changes minimal, scoped, and reproducible.
+The only allowed outcome is a branch
+`feature/qt6-migration-projects-app-tools-viewer-validation` that contains, in order:
+
+1. a cherry-pick commit of `5501d1e50` (`origin/bugfix/dds-fix-pre-existing-errors`), and
+2. a merge commit with parents `origin/feature/migrate-lts-projects-and-application` and
+   `origin/feature/qt6-migration-basis-modules-merge-viewer-validation`
+
+— such that the result contains the full work of `feature/migrate-lts-tools-d-and-l`,
+`feature/migrate-lts-projects-and-application`, the cherry-picked commit, and the
+viewer-validation branch, and preserves the legacy code behavior of every migrated file.
+
+## Required base prompts
+
+Before making changes, read and apply:
+
+- ./prompts/combined-migration-subfolder-rti-compact.prompt.md
+- ./prompts/commit-policy.prompt.md (repository mapping, pre-commit checks, per-repo commits)
+
+If a base prompt is stricter, follow it. This prompt overrides it only for:
+
+- build variants: use ON variants only for `BUILD_RTI`/`BUILD_GRANTLEE`, never OFF
+- commit message format: max 2 lines, no co-author/co-authored-by/bot attribution lines
+  (see "Commits")
+
+## Task
+
+Produce the result branch from three inputs (the tools branch is already contained — see
+below — so exactly two operations are performed: one cherry-pick, one merge):
+
+- **ours (merge target base):** `feature/migrate-lts-projects-and-application`
+  remote tip at prompt writing (2026-09-27): `b18844a20` ("Document GROUP10 validation
+  results", Torsten Wierschin, 2026-09-25)
+- **tools branch (verification only — already contained):**
+  `feature/migrate-lts-tools-d-and-l`
+  remote tip at prompt writing: `2b8f3f02c` ("Add Group 9 (R,S,T,V,W) LTS Tools migration
+  support", 2026-09-24). **Verified 2026-09-27:** `git merge-base
+  origin/feature/migrate-lts-tools-d-and-l origin/feature/migrate-lts-projects-and-application`
+  equals the tools tip `2b8f3f02c` — the tools branch is an **ancestor** of the projects
+  tip. No merge is needed; the procedure below only verifies the containment.
+- **cherry-pick:** `5501d1e50` ("Qt6 Migration: Update stub headers to include generated
+  files", Torsten Wierschin, 2026-09-22) — the tip of
+  `origin/bugfix/dds-fix-pre-existing-errors` (single commit after its fork point
+  `0997dcba7`)
+- **theirs (branch to merge in):** `feature/qt6-migration-basis-modules-merge-viewer-validation`
+  remote tip at prompt writing: `9c1ac7cbe` ("Merge
+  feature/lts-viewer-validation-testing-phase into feature/qt6-migration-basis-modules-merge",
+  berrux_dev, 2026-09-27)
+- **merge base (projects × viewer-validation):** `fd3e5e838` ("Add --build-viewer-only
+  option to skip Groups 1-4 and build Viewer targets only", 2026-09-23)
+- **result branch:** `feature/qt6-migration-projects-app-tools-viewer-validation`
+  (does not exist yet; create it from `origin/feature/migrate-lts-projects-and-application`)
+
+All work happens in the repository `./qt-migration-legatus` (it is a separate git
+repository; never commit its changes into the workspace root or the legacy repository).
+
+## Branches and trees
+
+Working repository:
+
+- `./qt-migration-legatus`
+
+Trees:
+
+- Legacy Qt5 source tree (read-only reference, never modify):
+  `./qt-migration-legatus/qt5-before/qt5-legatus-legacy`
+- Qt6 target tree (the only tree that is modified):
+  `./qt-migration-legatus/qt6-after/qt6-migrated-legatus`
+
+Before starting:
+
+1. `git fetch origin` in `./qt-migration-legatus`.
+2. Verify all four refs still match the hashes above:
+   - `git rev-parse origin/feature/migrate-lts-projects-and-application` → `b18844a20`
+   - `git rev-parse origin/feature/migrate-lts-tools-d-and-l` → `2b8f3f02c`
+   - `git rev-parse origin/bugfix/dds-fix-pre-existing-errors` → `5501d1e50`
+   - `git rev-parse origin/feature/qt6-migration-basis-modules-merge-viewer-validation` → `9c1ac7cbe`
+3. Re-verify the tools containment: `git merge-base --is-ancestor
+   origin/feature/migrate-lts-tools-d-and-l origin/feature/migrate-lts-projects-and-application`
+   must exit 0. If any tip moved or the containment check fails, recompute the merge
+   base, re-run the dry run (step 3 of the procedure), and record the new state before
+   touching anything.
+4. Verify the working tree of `./qt-migration-legatus` is clean (`git status --short`).
+   Do not overwrite uncommitted user changes; if they block safe work, report the
+   blocker. (Known state at prompt writing: the main worktree is on
+   `feature/qt6-migration-basis-modules-merge-viewer-validation` at `9c1ac7cbe`, clean.)
+
+## What each side contains
+
+Understand all three inputs before resolving anything. The result must keep the work of
+ALL of them.
+
+**projects side (ours, 8 commits after the merge base, 47 files):**
+
+- `9f0076a19` — LTS Tools Group 6 (D&L directories) Qt6 migration: `GROUP6_TARGETS`
+  (dbAdministration, SettingsRemover, dbUpdate, tDataSampleGenerator,
+  tDataSampleReceiver, DateTimeSyncer, ddsview, displayPanelSimulator, LicenceEditor,
+  localDomainFinder, **LogViewer**)
+- `db8adbfe3` — Tools Group 7 (A,B,C,E,I directories)
+- `1e1a3e6f3` — Group 8 (J,M,N,P,Q) build script support + CTest infrastructure
+  (34 files under `tests/`: `tests/CMakeLists.txt` + `test_<Tool>.cpp` registrations)
+- `2b8f3f02c` — Tools Group 9 (R,S,T,V,W) — **this is the tip of
+  `feature/migrate-lts-tools-d-and-l` (the "alle Tools" branch); Groups 6–9 together are
+  the complete LTS Tools migration**
+- `168d03866` — GROUP10 (LTS Projects: 9 project plugin targets — ProjectGuezPlugin,
+  ProjectQatarMOUTPlugin, ProjectQatarPlugin, ProjectLegatusPlugin, ProjectDemoPlugin,
+  ProjectL400P2Plugin, ProjectComMasterPlugin, ProjectAhtcPlugin, ProjectEtsPlugin) and
+  GROUP11 (LTS Application: OperatorApplication, thp_viewer, aarApp)
+- `97a9992ce` / `4d6bef5fa` — GROUP7–11 default initializations + Docker env passthrough
+  (`-e BUILD_GROUP6..11`)
+- `b18844a20` — `GROUP10_VALIDATION_RESULTS.md`: GROUP10 validated with
+  `BUILD_RTI=ON BUILD_GRANTLEE=ON BUILD_ARCGIS=ON`; **GROUP11 blocked by a pre-existing
+  `svcPdmClient` (Services/ProjectDataManagement) Qt6 MOC failure** (base state, see
+  "Tests")
+- touched `Lts/Tools/{ConfigX,DBAdministration,DBUpdate,ProjectSettingsEditor}` sources
+  (Qt6 fixes) and `new_docker_build.sh` (+186/−1: Groups 6–11 usage/env/arg-parsing,
+  GROUP6–11 target arrays, `run_build_group` calls, log_group lines for Groups 7–11 —
+  **Group 6 has no log_group line on this side**)
+
+**viewer-validation side (theirs, 52 commits after the merge base, 1313 files):**
+
+- the full `feature/qt6-migration-basis-modules-merge` work: complete Qt6/rtiddsgen 7.7
+  migration of residual Lts services/proxies/plugins (incl. the ProjectDataManagement
+  service sources — `a41001955`), codegen fixes, Qt6::SerialPort IMPORTED target,
+  GROUP3 full migrated-service target set (~200 targets incl. per-service tests and the
+  PDM block `svcPdmCommon/Client/Server`, `svcProjectDataManagement`, `pdmTests`)
+- docker-script unification: `new_docker_build.sh` single validation script
+  (`docker_build.sh` deleted and must stay deleted), consolidated single GROUP4 array
+  (DDS tests `ddsGenericDataTests`/`ddsDataTopicTests`/`ddsFunctionTopicTests` +
+  Lts/Proxies) and single Group-4 `run_build_group` call, `--cmake_build_flags` option,
+  prebuilt image `legatus-qt6-prebuilt:latest`
+- viewer-validation features: `--build-viewer-only`, `--codification`, KDReports-qt6
+  detection (`cmake/FindKDReports.cmake`), build-parts `BUILD_SV/WS/AAR`,
+  `LtsDataViewTest`/`LtsFileDialogTest` auto-exit adaptations (CI `QTimer` 1000 ms,
+  `QT_QPA_PLATFORM=offscreen`, `TIMEOUT 30`)
+- **stub relocation (`4223ca2ff`): the `include/*/*_dtc.h` stub headers were moved from
+  `qt6-after/qt6-migrated-legatus/include/` to
+  `qt6-after/qt6-migrated-legatus/.forward-declarations/include/`** — 111 files deleted
+  from the old location; `BUILD_STATUS_REPORT.md` added
+- follow-up fixes: `ci/allowed_signers` principal format (`e748e82c8`), record_replay
+  `fromQVariant` + PPM MOC exclusion (`36f077bce`), viewer-validation merge
+  (`c664611b8` + `9c1ac7cbe`)
+
+**cherry-pick `5501d1e50` (1 commit, 40 files):** updates the 38 stub headers
+(`include/*/*_dtc.h` + `pdm_enums.hpp` + `ppm.hpp` + `include/ParticipantManagement/
+ppm_types.h`) so they include the generated files from `build4/Lts/Proxies/*`, updates
+the real service source `Lts/Services/ParticipantManagement/ppm_types.h`, and adds
+`BUILD_STATUS_REPORT.md`. Note on the service source: the viewer-validation side made
+the same change to it (both sides converge to byte-identical content at their tips —
+verified 2026-09-27), so it auto-merges cleanly (it is not among the dry-run conflicts).
+**Supersession fact (verified 2026-09-27):** the viewer-validation side already carries
+the same change as `4223ca2ff` (same author, same subject) applied to the relocated
+`.forward-declarations/include/` location: for `include/FileManagement/flm_dtc.h` and
+`include/ParticipantManagement/ppm_types.h` the patches are byte-identical except the
+path prefix, and the final content of `ppm_types.h` at the theirs tip equals the
+content produced by `5501d1e50`. `BUILD_STATUS_REPORT.md` is byte-identical between
+`5501d1e50` and the theirs tip. See "Cherry-pick handling".
+
+## Cherry-pick handling (5501d1e50) — required sequence
+
+The cherry-pick must **exist as a commit in the result history** (do not merely document
+it as superseded and skip it). Perform it FIRST, onto the clean projects base, where it
+applies cleanly (verified 2026-09-27: `git cherry-pick 5501d1e50` onto `b18844a20`
+succeeds without conflicts, producing commit `e07bc9a91` in the test run):
+
+1. `git cherry-pick -n -x 5501d1e50` (no conflicts expected; if any, stop and report —
+   it applied cleanly on 2026-09-27)
+2. Commit it signed, keeping the **original author** (Torsten Wierschin — the author of
+   the work; `git cherry-pick` already sets the author from the source commit; do not
+   reset it), with the original subject and body **minus the
+   `Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>` line**
+   (repository policy: no co-author/co-authored-by/bot attribution lines), and with the
+   cherry-pick reference line (`(cherry picked from commit 5501d1e50...)`) kept. Max 2
+   lines of your own wording do not apply to the body of a cherry-picked message — the
+   original body is preserved verbatim (minus the bot line) so the change stays
+   attributable.
+3. Only then start the merge (step 4 of the procedure).
+
+Consequence of this order (verified by dry run 2026-09-27): the subsequent merge produces
+**24 modify/delete conflicts** on the old-location stub files (modified by the
+cherry-pick on ours side, deleted by the relocation on theirs side). Their resolution is
+mechanical and safe — keep the deletion — because the updated content already exists at
+the new location. Before resolving, verify that per file (record any MISMATCH as a
+blocker):
+
+```bash
+MB=qt6-after/qt6-migrated-legatus
+for f in $(git diff --name-only --diff-filter=U | grep '^qt6-after/qt6-migrated-legatus/include/'); do
+  rel=${f#$MB/include/}
+  git show origin/feature/qt6-migration-basis-modules-merge-viewer-validation:"$MB/.forward-declarations/include/$rel" > /tmp/newloc 2>/dev/null || { echo "MISSING-NEW-LOC: $f"; continue; }
+  git show 5501d1e50:"$f" > /tmp/oldloc
+  cmp -s /tmp/oldloc /tmp/newloc || echo "MISMATCH: $f"
+done
+```
+
+Then resolve each with `git rm <file>` (keep deletion; the `.forward-declarations/`
+copy is the canonical one). The 24 expected files (dry run 2026-09-27):
+`{AlarmManagement/alm, AreaEffectSimulation/aes, AssetManagement/asm,
+AudioVideoManagement/avm, Buildings/bld, CentralEffectSimulation/ces,
+ComponentMonitor/cmo, Core/core, EffectShowClient/esc, EffectShowManagement/esm,
+Evaluations/evl, ExerciseManagement/exm, GuezIedManagement/gim, GuezNasat/gna,
+NotificationManagement/nom, OcSituationServer/oss, ScenarioManagement/scm,
+SituationReplay/srp, SituationReplayManagement/srm, Skeleton/skl,
+SoundManagement/som, TrainingAreaBase/tab, TrainingAreaBaseOC/taboc}_dtc.h` plus
+`ProjectDataManagement/pdm_enums.hpp`.
+
+The other 14 cherry-pick stub files (`{CodificationManagement/cod,
+ExerciseEventManagement/eem, FileManagement/flm, InfrastructureManagement/ism,
+MeteoDataManagement/mdm, MarkerManagement/mrk, Messaging/msg,
+OperatorManagement/opm, PresentationManagement/pre, ReportManagement/rep,
+TargetManagement/tgt, WarehouseGuez/whg}_dtc.h` + `ParticipantManagement/ppm.hpp` +
+`ParticipantManagement/ppm_types.h`) were **not** relocated by the theirs side, so they
+stay at the old `include/` location with the cherry-pick's update — expected outcome,
+do not "fix" it (the old `include/` tree legitimately remains in the tree; relocated
+copies also exist at the new location for them — pre-existing pattern on the theirs
+side).
+
+## Known conflict surface (dry run 2026-09-27)
+
+A dry run of the full sequence (cherry-pick onto `b18844a20`, then
+`git merge --no-commit --no-ff origin/feature/qt6-migration-basis-modules-merge-viewer-validation`
+in a throwaway worktree) found:
+
+- **1 content conflict (UU):** `qt6-after/qt6-migrated-legatus/new_docker_build.sh`
+  (3 conflict hunks — recipe below)
+- **24 modify/delete conflicts (UD):** the old-location stub files listed above
+- **auto-merged (verified in the dry run, keep as-is unless a check below fails):**
+  - `new_docker_build.sh` all other regions: `GROUP3_TARGETS` = theirs' expanded
+    179-target service set (incl. the PDM block), single consolidated
+    `GROUP4_TARGETS` (DDS tests + Proxies), the four-way GROUP5 conditional
+    (BUILD_ARCGIS × BUILD_VIEWER_ONLY), the GROUP6–11 arrays + `run_build_group`
+    calls for Groups 1,4,2,3,5,6,7,8,9,10,11, the `BUILD_GROUP6..11` container
+    defaults (1–3 ON, 4–11 OFF), the `-e BUILD_GROUP1..11` docker passthrough, and the
+    `BUILD_VIEWER_ONLY` switch block
+  - `qt6-after/qt6-migrated-legatus/tests/CMakeLists.txt` (both sides changed it:
+    theirs' test additions + ours' 34 tool-test registrations — verify after the merge
+    that both sets of registrations are present)
+  - `BUILD_STATUS_REPORT.md` (byte-identical on both sides → no conflict)
+  - `Lts/Services/ParticipantManagement/ppm_types.h` (cherry-pick's change on ours
+    side converges to byte-identical content with the theirs-side change → no
+    conflict; verify after the merge that the merged content equals the content at
+    `5501d1e50`)
+  - all 1313 theirs-side files (services/proxies/viewer rewrites,
+    `.forward-declarations/` tree, `BUILD_STATUS_REPORT.md`)
+
+Re-run the dry run after the fetch and treat its output as authoritative; the list above
+is the expected starting point. If the dry run shows additional conflicts, resolve them
+with the four-version method (see below) and record them in the final report.
+
+## Conflict resolution rules
+
+These rules exist to guarantee: the merged tree keeps all three inputs' functionality
+and no file's behavior deviates from the legacy Qt5 behavior beyond the approved
+Qt6/C++17/rtiddsgen adaptations.
+
+General:
+
+- Resolve semantically, never mechanically. For every conflicted hunk read four
+  versions: the merge-base version, ours, theirs, and the legacy Qt5 equivalent (for
+  `new_docker_build.sh` there is no legacy counterpart — pure Qt6 build machinery — so
+  use the merge-base version as the third reference).
+- Never take `ours` or `theirs` wholesale unless you prove the losing side had no
+  unique changes: `git diff <merge-base>..theirs -- <file>` (or `..ours`) must show
+  nothing that the kept version lacks. Record the proof in the final report.
+- No behavior-changing edits beyond the merge itself. No refactoring, no style cleanup,
+  no warning suppression, no new features.
+
+`new_docker_build.sh` (the single content conflict) — required merge recipe, 3 hunks:
+
+1. **Usage text (~line 48):** keep OURS' six `--group6 … --group11` usage lines AND
+   THEIRS' corrected `--build-viewer-only` line
+   (`Build only Viewer module targets (skip Groups 1-4, implies --group5 --codification; ctest runs)`)
+   — do **not** keep ours' stale `--build-viewer-only` line
+   (`… implies --group5 --no-ctest`), which contradicts the handler (it sets
+   `RUN_CTEST=ON`; the corrected theirs line was already validated in the
+   viewer-validation merge).
+2. **`export` line (~line 898):** union of both lists, i.e. exactly:
+   `export BUILD_ALL BUILD_RTI BUILD_GRANTLEE BUILD_ARCGIS BUILD_CODIFICATION BUILD_GROUP1 BUILD_GROUP2 BUILD_GROUP3 BUILD_GROUP4 BUILD_GROUP5 BUILD_GROUP6 BUILD_GROUP7 BUILD_GROUP8 BUILD_GROUP9 BUILD_GROUP10 BUILD_GROUP11 BUILD_VIEWER_ONLY RUN_CTEST TESTS_ONLY INTEGRATION_TEST USE_PREBUILT_IMAGE BUILD_PREBUILT_IMAGE DELETE_PREBUILT_IMAGE DOCKER_IMAGE CMAKE_BUILD_FLAGS`
+3. **`log_group` banner lines (~line 1053):** keep THEIRS' lines for Groups 1, 2, 3
+   (the corrected `Build Group 3 (application + service targets)` label), 4
+   (`Build Group 4 (DDS tests + Proxies)`) and 5 (`Build Group 5 (Viewer)`), plus
+   OURS' lines for Groups 7, 8, 9, 10, 11, in that order. Optionally (text-only,
+   non-behavioral) add the missing ours-side Group 6 line
+   `log_group "Build Group 6 (LTS Tools)" "$BUILD_GROUP6"` so every group with a
+   `run_build_group` call has a banner line — record if added.
+
+Post-resolution script checks (record in the final report):
+
+- `bash -n` on the host script and on the extracted container-side script
+- `--help` renders and lists `--group6..--group11`, `--build-viewer-only`,
+  `--codification`, `--cmake_build_flags`; an unknown option is still rejected
+- target-set check: `GROUP3_TARGETS` = 179 targets and still contains the PDM block
+  (`svcPdmCommon/Client/Server`, `svcProjectDataManagement`, `pdmTests`);
+  `GROUP4_TARGETS` single array containing `ddsGenericDataTests`,
+  `ddsDataTopicTests`, `ddsFunctionTopicTests`; GROUP5 four-way conditional intact;
+  GROUP6–11 arrays, `run_build_group` calls, container defaults and `-e` passthrough all
+  present
+- the `BUILD_VIEWER_ONLY` block still switches Groups 1–4 OFF / Group 5 ON before the
+  `run_build_group` calls (Groups 6–11 remain OFF by default in that mode)
+- the prebuilt image name is `legatus-qt6-prebuilt:latest` everywhere (no second name);
+  no reference to `docker_build.sh` remains; the container-side script still starts
+  with `set -euo pipefail`
+
+CMake conflicts: none in the dry run. If the re-run shows new CMake conflicts (e.g. in
+`tests/CMakeLists.txt`): take the union of both sides' targets, dependencies, include
+directories, and link libraries; keep the `Qt6::SerialPort` manual IMPORTED target and
+the GROUP5/Viewer wiring (theirs) side by side with the GROUP6–11 tool-test
+registrations (ours). After resolving, verify with a fresh configure that both sides'
+targets/options exist.
+
+## Mandatory build variants
+
+Only these variants are valid:
+
+- `BUILD_RTI=ON`
+- `BUILD_GRANTLEE=ON`
+
+Forbidden: `BUILD_RTI=OFF`, `BUILD_GRANTLEE=OFF`.
+
+- Do not implement, fix, preserve, test, or validate OFF variants of
+  `BUILD_RTI`/`BUILD_GRANTLEE`. Do not add CMake logic, tests, stubs, or fallbacks for
+  them. Validation must use `BUILD_RTI=ON` and `BUILD_GRANTLEE=ON`.
+- `BUILD_ARCGIS`: the projects side validated GROUP10/GROUP11 with
+  `BUILD_ARCGIS=ON` (`GROUP10_VALIDATION_RESULTS.md`) and
+  `external/ArcGIS/MapsSDK_Qt_300.0.0` exists at the pipeline root (mounted to the
+  container's `/workspace/external`). Use `BUILD_ARCGIS=ON` in the coverage run that
+  builds GROUP10/GROUP11 (run 2 below) and leave it at its default OFF in the other
+  runs. This is not an RTI/Grantlee OFF variant; the prohibition above does not apply.
+- The viewer-validation side options `BUILD_VIEWER_ONLY` (default OFF),
+  `BUILD_CODIFICATION` (default OFF), `BUILD_SV`/`BUILD_WS`/`BUILD_AAR` (default ON)
+  and the projects side `BUILD_GROUP6..11` (default OFF) are design features: keep
+  their defaults and semantics as-is; do not flip them.
+
+## Preservation rules
+
+Preserve module removals from commit `92ad7d468` ("remove all unneeded module listed
+from Niklas"): do not restore removed modules, files, targets, directories, or
+dependencies — on any side.
+
+Preserve LogViewer reinsert from commit `1fa789767` ("Added LogViewer again"): do not
+remove, disable, or break LogViewer integration. Note: `LogViewer` is a GROUP6 target
+on the projects side — it must survive in `GROUP6_TARGETS` after the merge.
+
+Preserve prior IDL warning fixes from commit `be912de9d`: do not reintroduce multiple
+enum definitions, duplicate enumerators, or builtin type/keyword collisions.
+
+Preserve the ON-variant-only decisions already made on all branches.
+
+Preserve the docker-script unification: `docker_build.sh` stays deleted;
+`new_docker_build.sh` remains the single validation script; the GROUP3 service target
+set, the consolidated GROUP4 array, the GROUP6–11 groups, and the viewer-only/
+codification options all survive the script merge (see the merge recipe above).
+
+Preserve the stub relocation decision: the `.forward-declarations/` tree is the
+canonical location for relocated stubs; the 24 old-location stubs deleted by the
+viewer-validation side stay deleted (see "Cherry-pick handling"); the 14 non-relocated
+cherry-picked stubs stay at the old `include/` location.
+
+Preserve the projects side artifacts: the 34 `tests/*` tool-test files and their
+`tests/CMakeLists.txt` registrations, `GROUP10_VALIDATION_RESULTS.md`, and the
+`Lts/Tools/{ConfigX,DBAdministration,DBUpdate,ProjectSettingsEditor}` Qt6 fixes.
+
+## Stubs and forward declarations
+
+Any required existing stub, compatibility declaration, or forward declaration must live
+only under:
+
+- `./qt-migration-legatus/qt6-after/qt6-migrated-legatus/forward-declarations/`
+- `./qt-migration-legatus/qt6-after/qt6-migrated-legatus/.forward-declarations/include/`
+
+- Do not leave such files in service directories unless they are real service source
+  files.
+- Do not create or keep stubs for forbidden OFF variants.
+- Do not use stubs as replacements for real RTI, ndsgen, KTextTemplate, or Grantlee
+  outputs in ON builds.
+- Report every moved, removed, or newly referenced stub/forward declaration.
+- This merge resolves 24 stub files to deletion (keep-theirs) and leaves 14 updated
+  stubs at the old `include/` location (pre-existing pattern) — both are the intended
+  outcomes; see "Cherry-pick handling".
+
+## Qt link rules
+
+No active target in the merged tree may link Qt5 imported targets.
+
+Search the merged tree for and fix active uses of: `Qt5::`, `find_package(Qt5`, `QT5_`,
+`Qt5Core`, `Qt5Widgets`, `Qt5Network`.
+
+Regression check specific to this merge: the projects side touched
+`tests/CMakeLists.txt`, `Lts/Tools/*` sources and `new_docker_build.sh`; the
+viewer-validation side touched cmake infrastructure (`cmake/NGLMacros.cmake`,
+`cmake/FindKDReports.cmake`, root `CMakeLists.txt`). After the merge, re-run the search
+over ALL files touched by the merge (auto-merged files included), not just the
+conflicted ones; the legacy `QT5_WRAP_UI`/`QT5_ADD_RESOURCES` function-name calls
+(compat shim) are allowed and pre-exist on both sides — imported-target links are not.
+
+## Legacy comparison (required validation step)
+
+This step proves the merge did not change code behavior.
+
+For every file you edit during conflict resolution (expected:
+`new_docker_build.sh` only — the 24 stub deletions are covered by the per-file
+content check in "Cherry-pick handling"):
+
+1. Read the legacy Qt5 source at the same relative path in
+   `./qt-migration-legatus/qt5-before/qt5-legatus-legacy`. If the file does not exist
+   there (pure Qt6 build machinery — expected for `new_docker_build.sh`), say so and
+   compare against the merge base instead.
+2. Produce three diffs: merge-base vs legacy (or: skip with justification), ours vs
+   merge-base, theirs vs merge-base.
+3. Produce the audit diff: merged result vs merge base.
+4. Classify every hunk of the audit diff into exactly one category:
+   - `qt6-api`: mandatory Qt5→Qt6 API adaptation
+   - `rtiddsgen-api`: generated-API adaptation
+   - `build`: CMake/docker/test-infra change with no runtime semantics
+   - `merge-union`: line present because both branches required it
+   - `semantic-change`: anything else
+5. Every `semantic-change` hunk is a failure of this merge unless you can point to the
+   legacy source line that implements the same behavior. Fix it back to the legacy
+   semantics (with approved adaptations) or report it as a blocker. Do not silently
+   accept `semantic-change` hunks. (For `new_docker_build.sh`, `build`/`merge-union`
+   are the expected categories; a `semantic-change` there means a behavior of one
+   side's script was silently dropped.)
+6. Record the per-file hunk classification (counts per category is sufficient; list
+   every `semantic-change` hunk explicitly) in the final report.
+
+Additional equivalence checks on the merged tree:
+
+- CMake option union: `BUILD_VIEWER_ONLY`, `BUILD_CODIFICATION`, `BUILD_SV/WS/AAR`,
+  `BUILD_GROUP6..11`, the `Qt6::SerialPort` IMPORTED target, GROUP5/Viewer wiring, and
+  GROUP6–11 wiring all exist after the auto-merge (auto-merged files are not re-read by
+  default — verify them).
+- CTest registration union: `tests/CMakeLists.txt` contains BOTH the theirs-side
+  registrations (e.g. `LtsDataViewTest`, `LtsFileDialogTest`, service tests) AND the
+  ours-side 34 tool-test registrations.
+- `LtsDataViewTest` registration: `add_test` present, `QT_QPA_PLATFORM=offscreen` test
+  property present, auto-exit `QTimer` present in `test.cpp`.
+- `BUILD_STATUS_REPORT.md` and `GROUP10_VALIDATION_RESULTS.md` both present in the
+  merged tree.
+- Docker build script: every target group, apt package, and build option both sides
+  added is present (see the script checks in the merge recipe); the container-side
+  script still starts with `set -euo pipefail`.
+
+## Code generation rules
+
+If generated files are required (not expected for this merge):
+
+- reconstruct the real legacy generation flow
+- generate into the build tree
+- consume from the build tree
+- list complete OUTPUT and BYPRODUCTS
+- set correct DEPENDS and MAIN_DEPENDENCY where useful
+- use deterministic WORKING_DIRECTORY
+- use VERBATIM
+- wire generated sources with target_sources
+- wire generated include dirs with target_include_directories
+- ensure compilation depends on generation
+- ensure incremental rebuilds trigger on input/template changes
+
+Never commit generated .idl, .h, .hpp, or .cpp outputs. Never consume generated outputs
+from the source tree. Never fabricate generated outputs.
+
+## Tests
+
+- All three sides' test suites must build and run; this merge adds no new feature tests
+  of its own.
+- The ours-side 34 `tests/test_<Tool>.cpp` tool tests (Groups 6–9) must be built and
+  registered in the merged `tests/CMakeLists.txt`; run them in the coverage run (run 2
+  below). If a tool test requires external hardware/services, classify Not Run/Timeout
+  as base state (record the reason) — do not make them pass by weakening the test.
+- Keep the theirs-side `LtsDataViewTest` adaptations (auto-exit timer, offscreen
+  property, unconditional link) — they are what make the viewer-only ctest pass in CI.
+- **Known base-state blocker (GROUP11):** the projects side documents
+  (`GROUP10_VALIDATION_RESULTS.md`) that GROUP11 (OperatorApplication, thp_viewer,
+  aarApp) is blocked by a pre-existing `svcPdmClient` Qt6 MOC failure. The
+  viewer-validation side completed the residual Lts service migration
+  (`a41001955`, incl. ProjectDataManagement service sources) and the PPM MOC exclusion
+  (`36f077bce`), so the blocker may be RESOLVED in the merged tree. In run 2, build
+  GROUP11 and record which: (a) `svcPdmClient` now builds — blocker cleared by the
+  theirs-side service work (success, document it), or (b) it still fails with the same
+  MOC error — base-state blocker, record it in the final report as remaining (do not
+  fix it in this merge).
+- If a conflict resolution changed C++ semantics (it should not), add CTest tests under
+  `./qt-migration-legatus/qt6-after/qt6-migrated-legatus/tests/` that pin the legacy
+  behavior, registered with CTest, running with `BUILD_RTI=ON` and `BUILD_GRANTLEE=ON`,
+  policy-compatible names (`test_<name>.cpp`, …).
+- No OFF-variant tests of `BUILD_RTI`/`BUILD_GRANTLEE`. No host-local paths.
+
+## Docker and CI
+
+Authoritative migration Dockerfile:
+
+- `./app/Dockerfile`
+
+Authoritative validation script (single script; `docker_build.sh` was merged into it
+and deleted):
+
+- `./qt-migration-legatus/qt6-after/qt6-migrated-legatus/new_docker_build.sh`
+
+Validation container expectations:
+
+- repository root at `/workspace` (the script's documented mount path)
+- external dependencies under `/workspace/external` (including
+  `external/rti_connext_dds-7.7.0`, `external/ArcGIS` where the scripts expect them)
+- `./rti_license.dat` mounted read-only if RTI requires it
+- no developer-local paths
+- the prebuilt image `legatus-qt6-prebuilt:latest` exists (6.23 GB at prompt writing)
+  and is required for KDReports-qt6 (runs 2/3 use `--use-prebuilt-image
+  --docker-image legatus-qt6-prebuilt:latest`; run 1 may use the base image)
+
+Jenkins CI must be able to discover and run the merged test set. Inspect and minimally
+update only if needed:
+
+- `./qt-migration-legatus/ci/Dockerfile.*`
+- `./qt-migration-legatus/ci/check_pr_policies.py`
+
+Known pre-existing blocker (do not fix in this merge, record in the final report):
+`ci/check_pr_policies.py` currently exits 1 because a series of ancestor commits (33
+unsigned commits on `feature/qt6-migration-basis-modules-merge-viewer-validation` since
+merge base `ed9fc51e7`, e.g. `36f077bce`, `b6a97c39e`, `fd3e5e838`; plus the
+projects-side commits `b18844a20`, `4d6bef5fa`, … which carry no SSH signature
+accepted by `ci/allowed_signers`) fail the signature gate. Fixing it requires
+re-signing/history rewrite of source-branch commits, which is out of scope here. The
+new commits created by THIS task must be signed and verify Good.
+
+## Required procedure
+
+1. Read the base prompts. Run `git fetch origin` and verify the four ref hashes, the
+   tools containment check, and the merge base (step 2 of "Branches and trees").
+2. Create/checkout `feature/qt6-migration-projects-app-tools-viewer-validation` from
+   `origin/feature/migrate-lts-projects-and-application` in `./qt-migration-legatus`
+   (working tree must be clean).
+3. Re-run the dry run of the full sequence in a throwaway worktree
+   (cherry-pick `5501d1e50`, then `git merge --no-commit --no-ff
+   origin/feature/qt6-migration-basis-modules-merge-viewer-validation`); confirm the
+   conflict list (expected: 1 UU content conflict + 24 UD modify/delete conflicts).
+4. Cherry-pick `5501d1e50` (see "Cherry-pick handling", steps 1–2).
+5. Run the real merge: `git merge --no-ff
+   origin/feature/qt6-migration-basis-modules-merge-viewer-validation` (do not
+   auto-commit; resolve first).
+6. Run the 24-file stub content check, resolve the 24 UD conflicts as deletions, and
+   resolve the `new_docker_build.sh` content conflict hunk by hunk using the four-
+   version method and the merge recipe above.
+7. Run the legacy comparison audit (previous section) over every resolved/edited file.
+8. Run the regression checks: Qt5 links, removed modules, LogViewer (incl. the GROUP6
+   entry), IDL warnings, stub locations, ON-variant-only CMake, docker script
+   integrity (bash -n, --help, target-set and GROUP4/GROUP6–11 checks), CMake option
+   union, CTest registration union (both sides' registrations in
+   `tests/CMakeLists.txt`).
+9. Validate in Docker with `BUILD_RTI=ON` and `BUILD_GRANTLEE=ON` — all three runs
+   below (run 2 additionally with `BUILD_ARCGIS=ON`).
+10. Run CTest in each validated build (executed as part of the docker runs).
+11. Check Jenkins/policy compatibility (record the pre-existing signature blocker).
+12. Create the merge commit (see Commits).
+13. Report factual status.
+
+Do not push. The result stays local on
+`feature/qt6-migration-projects-app-tools-viewer-validation` until the user says
+otherwise.
+
+## Required validation
+
+From `./qt-migration-legatus/qt6-after/qt6-migrated-legatus`, run (in order):
+
+```bash
+# 1. Full default run (groups 1–3: DDS core, migration_tests, full migrated-service set)
+BUILD_RTI=ON BUILD_GRANTLEE=ON ./new_docker_build.sh
+
+# 2. Coverage run: Proxies + Viewer + ALL Tools groups (6–9) + Projects (10)
+#    + Application (11) + codification; ArcGIS ON because the projects side
+#    validated GROUP10/11 with BUILD_ARCGIS=ON and external/ArcGIS is mounted
+BUILD_RTI=ON BUILD_GRANTLEE=ON BUILD_ARCGIS=ON ./new_docker_build.sh \
+  --use-prebuilt-image --docker-image legatus-qt6-prebuilt:latest \
+  --group4 --group5 --group6 --group7 --group8 --group9 --group10 --group11 --codification
+
+# 3. Viewer-only run (validates the theirs-side feature end to end)
+BUILD_RTI=ON BUILD_GRANTLEE=ON ./new_docker_build.sh --build-viewer-only \
+  --use-prebuilt-image --docker-image legatus-qt6-prebuilt:latest
+```
+
+If a direct clean build is useful, use:
+
+```bash
+cmake -S /workspace/qt-migration-legatus/qt6-after/qt6-migrated-legatus -B /workspace/build-projects-tools-viewer-rti-on-grantlee-on -G Ninja -DCMAKE_BUILD_TYPE=Debug -DBUILD_RTI=ON -DBUILD_GRANTLEE=ON
+cmake --build /workspace/build-projects-tools-viewer-rti-on-grantlee-on --parallel
+ctest --test-dir /workspace/build-projects-tools-viewer-rti-on-grantlee-on --output-on-failure
+```
+
+CTest baseline: ctest exits with code 8 when tests are "Not Run". The pre-existing Not
+Run class (duplicate `_gtest` registrations, sibling targets of OFF groups, hardware-
+dependent tests such as `taboc_serialtest`, `bld_bsm_test`) is not a failure. In
+addition, the following six were documented as base-state first-run failures in the
+viewer-validation merge's final report
+(`./prompts/merge-lts-viewer-validation-into-basis-modules-merge.FINAL-REPORT.md`) and
+remain base-state here: `ddsFunctionTopicTests` (deterministic FTS/FTC signal defect),
+`bld_bsm_test`/`taboc_serialtest` (hardware waits), `bld_vwm_test`/`bld_vwm_xml_test`
+(manual-test data absent from the repo), `LtsFileDialogTest` (GUI blocks on DDS init
+before the CI auto-exit timer fires). Treat only NEW `***Failed`/`***Timeout` entries
+beyond these as merge regressions: fix or report as a blocker.
+
+Mandatory positive checks:
+
+- Run 2: GROUP10 must build (the projects side validated it — regression if it breaks);
+  GROUP6–9 tool targets must build; the 34 tool tests must at least be registered;
+  `LtsDataViewTest` must run and pass (where built); the GROUP11 outcome must be
+  classified per "Tests".
+- Run 3: `LtsDataViewTest` (and `LtsFileDialogTest` where built) MUST run and pass —
+  if it does not, that is a merge regression: fix it or report it as a blocker.
+- If a previously passing test becomes Not Run or Failed after the merge, that is a
+  merge regression: fix it or report it as a blocker.
+
+Do not run or validate OFF variants of `BUILD_RTI`/`BUILD_GRANTLEE`.
+
+## Commits
+
+Two commits are created on the result branch:
+
+1. **Cherry-pick commit** of `5501d1e50` (see "Cherry-pick handling"): keeps the
+   original author (Torsten Wierschin — the author of the work), keeps the original
+   subject and body minus the `Co-authored-by: Copilot` line, and keeps the
+   `(cherry picked from commit …)` reference line. Signed.
+2. **Merge commit**: single author — the user's git identity. The user is the only
+   author; do not add any co-author, co-authored-by, or bot attribution lines of any
+   kind. Message: maximum 2 lines (one subject line plus at most one short body line),
+   no blank-line separators, no extra metadata. Subject example:
+   `Merge feature/qt6-migration-basis-modules-merge-viewer-validation into feature/migrate-lts-projects-and-application`
+   body line example:
+   `Cherry-picks 5501d1e50 (stub-header updates, superseded by 4223ca2ff relocation); resolves 1 content + 24 modify/delete conflicts; validates BUILD_RTI=ON BUILD_GRANTLEE=ON incl. Tools Groups 6-11.`
+
+- The repository has `commit.gpgsign=false`: sign every created commit explicitly
+  (`git commit -S`, `git cherry-pick -S` or the two-step form from "Cherry-pick
+  handling"). Follow `./prompts/commit-policy.prompt.md` for repository mapping and
+  pre-commit checks. If it requires signed commits and signing is not configured in
+  this repository context, stop and report the exact reason instead of committing
+  unsigned.
+- If a conflict resolution requires an additional fix commit, the same 2-line /
+  single-author (user) / no-attribution / signed rules apply.
+
+## Success criteria
+
+Success requires:
+
+- `feature/qt6-migration-projects-app-tools-viewer-validation` contains the
+  cherry-pick commit of `5501d1e50` (signed, original author, no bot attribution line)
+  and a merge commit (signed, user as sole author) with parents
+  `origin/feature/migrate-lts-projects-and-application` (or its verified successor tip)
+  and `origin/feature/qt6-migration-basis-modules-merge-viewer-validation` (or its
+  verified successor tip)
+- the tools containment is re-verified (`2b8f3f02c` is an ancestor of the projects
+  base) and recorded
+- `new_docker_build.sh` resolved hunk by hunk with the merge recipe; resolution
+  evidence and the post-resolution script checks recorded
+- the 24 stub modify/delete conflicts resolved as deletions after the per-file
+  content check (no MISMATCH); the 14 non-relocated cherry-picked stubs documented as
+  staying at the old location
+- both sides' functionality preserved: GROUP6–11 target sets, the 34 tool-test
+  registrations, `GROUP10_VALIDATION_RESULTS.md`, and the `Lts/Tools` fixes from the
+  projects side; the full migrated-service set, GROUP3 service target set,
+  consolidated GROUP4 array, docker-script unification, `--build-viewer-only`,
+  `--codification`, KDReports wiring, and the `LtsDataViewTest`/`LtsFileDialogTest`
+  adaptations from the viewer-validation side
+- legacy comparison audit done for every resolved file; zero unexplained
+  `semantic-change` hunks
+- configure, build, and CTest pass with `BUILD_RTI=ON` and `BUILD_GRANTLEE=ON` in all
+  three validation runs (GROUP11 classified per "Tests"; the six documented base-state
+  first-run failures may remain, all others must pass)
+- Jenkins/policy discovery accepts the merged test set (or the pre-existing signature
+  blocker is recorded as the only failure); the new commits verify signed Good
+- no active Qt5 imported target links remain in the merged tree
+- generated outputs are build-tree only, freshly produced, never committed or consumed
+  from the source tree; no fake generated files, dummy files, mocks, placeholders, or
+  stubbed generated outputs
+- required stubs/forward declarations only in allowed directories; `docker_build.sh`
+  stays deleted
+- removed modules remain removed; LogViewer preserved (incl. the GROUP6 target)
+- no OFF-variant logic, tests, or stubs introduced for `BUILD_RTI`/`BUILD_GRANTLEE`
+- no push performed
+
+## If blocked
+
+Do not fake success. Report:
+
+- failing command
+- key error output
+- affected file/branch
+- category: project, path, merge, cherry-pick, CMake, Qt API, codegen, Docker,
+  RTI/license, Grantlee/KTextTemplate, KDReports, ArcGIS, test, CTest, Jenkins CI,
+  stub relocation, or environment
+- which side (ours/theirs/cherry-pick) the problematic hunk came from
+- what was resolved safely
+- what remains blocked
+- whether stale artifacts were ruled out
+- whether generated files were involved
+- exact missing files, targets, or generator step
+- whether tests and CTest integration succeeded
+- whether Docker validation and Jenkins discovery succeeded
+- the legacy comparison status for the unresolved files
+
+## Final report
+
+Keep it short. Include:
+
+- status: validated, partially validated, or blocked
+- both commit hashes (cherry-pick, merge), the merge's two parents, the branch name
+- tools containment re-verification result
+- cherry-pick evidence: clean apply on the projects base, per-file content check
+  output (24/24 MATCH expected), the 14 non-relocated files documented
+- per-conflicted-file resolution: file, method (union / four-version semantic / merge
+  recipe / keep-deletion), and the one-line reason
+- `new_docker_build.sh` merge evidence: ours-side additions kept (Groups 6–11 usage/
+  arrays/calls/passthrough), theirs-side additions kept (viewer-only, codification,
+  build-parts, prebuilt image name, `--cmake_build_flags`, corrected usage line), the
+  three resolved hunks, and the post-resolution script checks
+- legacy comparison audit summary: per-file hunk counts by category, and every
+  `semantic-change` hunk with its justification or fix
+- files changed beyond the conflicted set (expected: none — the 24 stub deletions and
+  the auto-merged theirs-side files excepted)
+- CTest registration union check result (both sides' registrations in
+  `tests/CMakeLists.txt`; `LtsDataViewTest` property/auto-exit)
+- Docker and Jenkins CI changes (incl. the recorded pre-existing signature blocker)
+- Qt5 references removed or remaining
+- confirmation that removed modules were not restored, LogViewer was preserved (incl.
+  the GROUP6 target), and `docker_build.sh` stayed deleted
+- GROUP11 classification (svcPdmClient blocker cleared by the theirs-side service work,
+  or still base-state)
+- exact validation commands and results for all three runs
+- remaining blockers or risks
+
+## Summary 
+- Write Summary for all migrated and merge branche like this example (MIGRATION_SUMMARY_Z_AND_PROXIES.md)