Refactor coach queue handoff signal decoding

docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md

@@ -3437,3 +3437,55 @@ Later same-day recommendation-history micro-follow-up (`2026-06-30`):
   - the next worthwhile continuation can move back to broader production
     hardening or another bounded training-repository reduction seam instead of
     carrying this tiny native uncertainty forward
+
+## Latest native queue-summary signal-bundle hardening follow-up (`2026-06-30`)
+
+- the next same-family continuation again stayed inside the existing
+  `HyperTwistTrainingRepositoryLibrary.cpp` native hardening seam:
+  - `UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRepositoryLibrary.cpp`
+- current ownership now centralizes the repeated queue-source label decoding
+  used by `Started`, `Promoted`, and `Completed` queue-summary history handling
+  into one bounded `FHyperTwistCoachDashboardHandoffSignals` helper bundle plus
+  two explicit application seams:
+  - `BuildCoachDashboardHandoffSignals(...)`
+  - `ApplyStartedCoachDashboardHandoffSignals(...)`
+  - `ApplyCompletedCoachDashboardHandoffSignals(...)`
+- that means the queue-summary event switch no longer reparses the same
+  dashboard-handoff source semantics inline across those branches, while the
+  sparse accepted-aligned reliable-suffix ladders remain preserved exactly as
+  they were before
+- local bounded tooling stayed green around the same packet:
+  - `scripts/run-hypertwist-sentrux-source-only.sh`
+  - `Quality: 6245`
+  - `scripts/run-hypertwist-gitnexus-analyze.sh`
+  - `Indexed commit: bad3216 (local CLI, post-index non-zero exit).`
+  - `scripts/run-hypertwist-gitnexus-status.sh`
+  - `Status: up-to-date`
+- reverse-SSH proof for this exact C++ slice stayed truthful on the maintained
+  primary `localhost:22022` lane:
+  - `scripts/run-hypertwist-remote-windows-file-sync.sh --file UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRepositoryLibrary.cpp`
+  - first Unreal rebuild surfaced a real compile seam instead of silently
+    masking it:
+    - the new helper sat above internal queue-source helpers that had never
+      needed forward declarations before
+    - the maintained Windows build failed with missing declarations for the
+      queue-source helper family
+  - the slice was repaired in-place by adding explicit forward declarations for
+    that internal helper family near the top of the file
+  - the file was resynced to maintained root
+    `C:\HyperTwist_worktrees\phase10validate\UnrealHyperTwist\Source\UnrealHyperTwist\Private\HyperTwistTraining\HyperTwistTrainingRepositoryLibrary.cpp`
+  - the rerun then passed:
+    - `scripts/run-hypertwist-remote-unreal-build.sh`
+    - maintained root `C:\HyperTwist_worktrees\phase10validate`
+    - `Result: Succeeded`
+    - UnrealBuildTool `Total execution time: 118.98 seconds`
+- current truthful reading after this follow-up:
+  - the queue-summary branch family is now easier to maintain because source
+    label semantics are decoded once per history event instead of being sprayed
+    inline across three switch branches
+  - the maintained Windows Unreal lane proved the structural change after a
+    real compile-time correction rather than a paper-only pass
+  - the next best same-family continuation is another bounded training-repository
+    ownership reduction seam, especially inside
+    `DeriveCoachRecommendationHistorySummary(...)`, rather than reopening a
+    different product family prematurely