feat(ui): Campaign CT slice CT4 — header identity block retail-exact

Retires the rest of AP-109's UI half: the character panel's Name/Heritage/
PkStatus/Level header identity block is now live and DAT-faithful on both
Attributes and Skills pages (verified: CharacterStatController.Bind already
scopes Label/LabelAuthoredColor to the ONE physically-visible page container,
so both tabs share the same bound widgets).

- Name/Heritage/PkStatus/Level switch from hand-picked Body/Gold runtime
  colors to the widget's own authored DefaultColor (LabelAuthoredColor) —
  CT1's live-DAT pin (HeaderElements_AuthorExpectedFontsAndColors) confirmed
  all four already carry the correct FontColor (white/white/white/pale-gold
  with Outline); the former "runtime color, dat carries none" comment was
  false.
- PkStatus resolves through StringTable 0x23000001 by key
  (ID_StatManagement_Header_PKStatus_PK/_PKL/_NPK) with a bitwise
  IsPK/IsPKLite test (gmStatManagementUI::UpdatePKStatus @0x004F00A0) instead
  of the prior exact-equality switch, which silently dropped combined-flag
  PlayerKillerStatus values. Live-DAT-verified strings: "Player Killer" /
  "Player Killer Lite" / "Non-Player Killer" (new InstalledDat pin
  PkStatusKeys_ResolveExpectedAuthoredStrings).
- Level shows "%d"-formatted InqInt(0x19) or the PE-recovered literal "???"
  when absent (CharacterSheet.Level is now int?).
- Heritage line appends CT2/CT3's resolved RuntimeCharacterTitleState
  display title through CharacterTitleResolver, refreshing live on both
  TableReplaced (0x0029) and DisplayTitleChanged (0x002B) —
  CharacterSheetProvider's ChangeBinding now subscribes to both.
- Name-line ruling: ships the PLAIN-NAME case only. Retail's allegiance
  rank-title prefix (AllegianceData::GetFullName @0x005B6950 ->
  AllegianceSystem::GetTitle @0x005B8DD0) needs a ~200-string, 22-function
  heritage x gender table (verbatim decomp literals, e.g.
  GetAluvianMaleTitle @0x005B7BC0's Yeoman/Baronet/.../High King) judged out
  of reasonable size for this slice. RuntimeAllegianceState already carries
  the local player's own rank; only the string table is missing. Registered,
  not silently omitted.
- Luminance pair (0x100005C5/0x100005C6): CharacterSheet.AvailableLuminance/
  MaximumLuminance (PropertyInt64 6/7) already flow generically through both
  the PlayerDescription snapshot and the live 0x02CF private-update parsers
  (no wiring gap). The retail show/hide gate (Level >= 200 &&
  MaximumLuminance != 0, UpdateExperience @0x004F0A70) is wired and toggles
  Visible on both elements every sheet refresh; the exact caption/value text
  could not be recovered this slice (retail's SetText source resolves
  through a Binary-Ninja-mislabeled data pointer, not a StringTable key — a
  DAT string-table sweep found no match), so content stays unbound rather
  than guessed.
- AP-109 narrowed accordingly (register row amended in the same commit).

Tests: CharacterStatControllerTests (heritage composition + live title
update, name stays plain, level int/"???" with authored — not constant —
color across 3 cases, PK line shows resolved text in authored color across
3 statuses, luminance visibility across 5 level/luminance combinations) and
CharacterSheetProviderTests (PK key-by-status resolution including a
combined-flag case, no-resolver leaves PkStatus null, Level null-vs-present,
title resolution + live refresh on both title events + unsubscribe-on-
dispose, luminance Int64 read-through). Full hermetic solution suite green
under Release (0 failures across all 14 test projects); InstalledDat pins
green.

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

docs/plans/2026-08-24-character-panel-parity-campaign.md

@@ -265,12 +265,60 @@ row-template resolver already takes (`RetailUiRuntime.MountCharacter`),
 and set the list box's authored 24px row height so wheel/line scroll
 lands row-aligned.
 
-**CT4 — Header identity block.** Retail composition: name; "<Gender>
+**CT4 — Header identity block. CODE-COMPLETE 2026-08-24.** Retail composition: name; "<Gender>
 <Heritage> <DisplayTitle>"; PK status line — authored fonts/colors
 (pure white per probe), live refresh on display-title change and PK
 status, identical on Attributes AND Skills pages. Level color from the
 authored element. Retires the rest of AP-109's UI half.
 
+**CT4 landing notes (2026-08-24).** Verified the existing `Label(...)` seam
+already covers both Attributes/Skills page copies — `CharacterStatController`
+binds the SAME physically-visible container (contentPage = the Attributes
+page chain) for both tabs; the Skills-page duplicate header subtree is never
+shown (a test now pins this: `Bind_HeaderElements_UseVisibleAttributesPageWhenIdsAreDuplicated`).
+All four header identity elements (Name/Heritage/PkStatus/Level) switched
+from hand-picked `Body`/`Gold` runtime colors to the widget's own authored
+`DefaultColor` (`LabelAuthoredColor`), matching CT1's live-DAT pin exactly —
+the former "runtime color, dat carries none" comment was false. PK status now
+resolves through StringTable `0x23000001` by key with a bitwise IsPK/IsPKLite
+test (the prior exact-equality switch silently dropped combined-flag
+values); **live-DAT-verified authored strings**: `ID_StatManagement_Header_PKStatus_PK`
+→ "Player Killer", `_PKL` → "Player Killer Lite", `_NPK` → "Non-Player Killer"
+(pinned in `CharacterPanelLiveDatTests.PkStatusKeys_ResolveExpectedAuthoredStrings`).
+Level shows `"%d"`-formatted `InqInt(0x19)` or the PE-recovered literal
+`"???"` when absent (`CharacterSheet.Level` is now `int?`). The heritage
+line's appended title now comes from CT2/CT3's `RuntimeCharacterTitleState.DisplayTitleId`
+resolved through `CharacterTitleResolver`, refreshing live on both
+`TableReplaced` and `DisplayTitleChanged` (`CharacterSheetProvider`'s
+`ChangeBinding` now subscribes to both). **Name-line ruling:** ships the
+PLAIN-NAME case only — retail's allegiance rank-title prefix
+(`AllegianceData::GetFullName @0x005b6950` → `AllegianceSystem::GetTitle
+@0x005b8dd0`) needs a ~200-string, 22-function heritage×gender table
+(verbatim hardcoded literals in the decomp, not DAT-resolved — e.g.
+`GetAluvianMaleTitle @0x005b7bc0`'s "Yeoman"/"Baronet"/"Baron"/"Reeve"/
+"Thane"/"Ealdor"/"Duke"/"Aetheling"/"King"/"High King") judged out of
+reasonable size for this slice; `RuntimeAllegianceState` already carries the
+local player's own rank, so only the string table is missing. **Luminance
+(item 5):** the DATA (`CharacterSheet.AvailableLuminance`/`MaximumLuminance`,
+PropertyInt64 6/7) already flows generically through both the
+PlayerDescription snapshot parser and the live `0x02CF` private-update path
+— no wiring gap existed — and the retail show/hide gate
+(`Level >= 200 && MaximumLuminance != 0`, `UpdateExperience @0x004F0A70`) is
+wired and toggles `Visible` on both `0x100005C5`/`0x100005C6`, but the
+label's caption and the value's composed number format could not be
+recovered this slice (retail's `SetText` source resolves through a
+Binary-Ninja-mislabeled data pointer, not a StringTable key; a DAT
+string-table sweep found no match) — content stays unbound rather than
+guessed. AP-109 narrowed accordingly (register row updated in the same
+commit, not deleted — the two open items above remain). Tests:
+`CharacterStatControllerTests` (heritage composition + live update, name
+stays plain, level int/"???" with authored — not constant — color, PK line
+shows resolved text in authored color, luminance visibility across five
+level/luminance combinations) and `CharacterSheetProviderTests` (PK
+key-by-status resolution including a combined-flag case, no-resolver ⇒ null,
+Level null-vs-present, title resolution + live refresh on both title
+events + unsubscribe-on-dispose, luminance Int64 read-through).
+
 **CT5 — Row alignment + value gutter.** Reconcile our hand-built
 attribute/skill rows with the authored row templates from CT1: icon
 placement, name/value columns, the authored right margin that reserves