feat(chat): Campaign CH slice CH6b — floating chat windows 1-4

Mounts retail's four floating chat windows as always-resident, born-hidden
children per gmGamePlayUI::SetupChildren @0x004E9EC0, all sharing LayoutDesc
0x2100005B (window ids 0x10000505/0x1000050E/0x1000050F/0x10000510). New
FloatingChatWindowController (AcDream.App/UI/Layout) binds each window's own
widget tree — built fresh per instance from one shared imported ElementInfo
— reusing ChatWindowController's word-wrap + retail color-carry algorithm via
the extracted ChatTranscriptRenderer instead of duplicating it. A floaty
window has no talk-focus menu (research doc §2.2), so its entry field always
sends on Say; the mismatch against retail's possible shared-channel behavior
is UNVERIFIED and filed as #369/AP-188.

Runtime owns the per-window filter/open state: ChatWindowState (new,
AcDream.Core.Chat) seeds retail's exact PostInit defaults per window
(window 1 0x0000101C Speech/Tell/DirectSend/Emote, window 2 0x00040C00
Social/SocialSend/Allegiance, window 3 0x00080000 Fellowship, window 4
0x78000000 Turbine General/Trade/LFG/Roleplay) and implements the full
ShouldDisplay(windowId, targetWindowId, logTextType) display predicate from
ChatInterface::RecvNotice_DisplayFinalStringInfo @0x004F4640. It lives on
RuntimeCommunicationState.ChatWindows so every host borrows the same
instance. The main window's filter (0xFBFFFFFF, "no user filter") never
actually gates anything because its own explicit-address branch already
covers every broadcast line — that's why UpdateFromPlayerModule early-returns
for window 0 in retail, ported here by construction rather than a special
case.

Keybind wiring: InputAction.ToggleFloatingChatWindow1..4 and their
KeyBindings.RetailDefaults() chords already existed since Phase K.1c
(unwired until now). The MetaKeys table confirms retail's default is Alt+1
through Alt+4 (index 3 = bit 0x00000004, cross-checked against the same
file's Alt+A/D strafe and Alt+Enter/Tab/F4 rows). Routes through
GameplayInputCommandController -> RetainedGameplayWindowCommands ->
RetailUiRuntime.ToggleFloatingChatWindow -> the generic UiHost.ToggleWindow,
whose visibility-change event is the single chokepoint that syncs
ChatWindowState.SetOpen and mirrors the main window's 1-4 indicator button
regardless of what changed a window's visibility (keybind, close button, or
a restored layout).

A direct decomp read of gmMainChatUI::ListenToElementMessage @0x004CDA80 —
the only function in the whole binary that branches on a click message —
settles what the research doc had left as a hedge: it handles exactly
0x1000046f (max/min) and the talk-focus menu's selection message, with NO
case for 0x10000522-0x10000525. The four indicator buttons are PURE
one-directional mirrors in retail; clicking them does nothing.
ChatWindowController.SetIndicatorOpen ports this with no OnClick at all.
Corrected research doc §1.4 accordingly.

Persistence is local-only (register row AP-187; the retail 0x1000008C
GameplayOptions wire remains deferred to CH6f): window geometry and
open/visible state ride the existing generic RetailWindowLayoutPersistence
path for free once each window registers under its own WindowNames entry;
the four filter masks get a dedicated ChatSettings round-trip
(ChatWindow1Filter..ChatWindow4Filter, defaulting to the retail PostInit
constants) loaded at mount and saved alongside SaveLayout().

Tests: ChatWindowStateTests (defaults, TypeIsActive, the full display-rule
matrix, toggle/reset, revision counter), FloatingChatWindowControllerTests
(bind smoke tests against a synthetic 0x2100005B tree, per-window filter
routing, filter-change cache invalidation, fixed-Say submit), new
ChatWindowController.SetIndicatorOpen tests (Highlight/Normal state,
cross-window isolation, range validation), GameplayInputCommandController
routing for the four toggle actions, and a SettingsStore filter round-trip.
Full Release suite: 12,392 passed / 4 skipped / 0 failed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/ISSUES.md

@@ -284,6 +284,37 @@ no-workarounds rule forbids without explicit approval.
 collision generation spans more than a couple of scheduler ticks (the
 default case against a real DAT-loaded landblock).
 
+## #369 — Unconfirmed whether retail's floating chat windows share the main window's currently-selected talk-focus channel
+
+**Status:** OPEN — filed 2026-08-10, Campaign CH slice CH6b (register row
+AP-188). The floating chat window LayoutDesc (`0x2100005B`) authors no
+talk-focus menu (`docs/research/2026-08-09-chat-retail-window-shell.md`
+§2.2 — only the main window's `0x2100006F` has one, element `0x10000014`),
+so acdream's `FloatingChatWindowController` hardcodes every floaty window's
+chat entry to send on `ChatChannelKind.Say`. What is UNVERIFIED is retail's
+actual send path: does a floaty `ChatInterface` instance's typed message go
+out on a per-window channel (also always Say, since there's nothing to pick
+from), or does it read the single globally-current talk-focus
+channel/target the MAIN window's menu (and `gmMainChatUI::UseTime
+@0x004CDB20`'s selected-target tracking) last set? If the latter, a real
+retail floaty window sends on whatever channel the player most recently
+picked from the main window — acdream would then need to promote
+`ChatWindowController`'s private `_activeChannel` to a shared owner all
+five window controllers read, rather than each owning its own (the main
+window keeps its own local state; the four floaties currently have no
+state at all, just the Say constant).
+
+**Where:** `src/AcDream.App/UI/Layout/FloatingChatWindowController.cs`
+(`Bind`'s `OnSubmit`); `src/AcDream.App/UI/Layout/ChatWindowController.cs`
+(`_activeChannel`, the eventual shared-state candidate).
+
+**Fix shape (needs research first):** trace `gmCCommunicationSystem`'s
+send-command path starting from a floaty `ChatInterface` instance (not the
+main window) to confirm which channel/target it actually uses; if it's
+shared, wire a single shared active-channel owner (Runtime-level, matching
+the J4.1 pattern the rest of chat state now follows) that all five
+controllers read instead of the main window's private field.
+
 ## #366 — Chat window's new-unseen-text indicator (0x1000048C) imports but is never independently wired
 
 **Status:** OPEN — filed 2026-08-10, Campaign CH slice CH6a. The retail main