Refine victory result summary

docs/ARCHITECTURE.md

@@ -46,8 +46,8 @@
 11. Turn-start and movement-triggered scenario events run as phases change or units enter marked cells, and may update objectives, grant inventory pickups, or deploy reinforcements.
 12. On first-time victory, `CampaignState` snapshots player progression and the battle inventory, applies rewards once, advances `current_scenario_id`, and writes `user://campaign_save.json`.
 13. If the scenario defines post-battle dialogue, it plays once before the victory result panel opens.
-14. The victory result panel summarizes rewards plus saved player level-ups and promotions.
-15. If the scenario defines post-battle choices, the result panel waits for the player to select one, then saves the selected flags and optional choice rewards before enabling the next battle.
+14. The victory result panel splits rewards, roster changes, saved player growth, campaign status, and pending choices into sections.
+15. If the scenario defines post-battle choices, the result panel waits for the player to select one, previews choice rewards including officer join/leave effects, then saves the selected flags and optional choice rewards before enabling the next battle.
 16. The result panel can load the next scenario, passing saved roster and inventory overlays back into `BattleState`.
 17. Once all campaign scenarios are complete, the battle scene shows a campaign completion panel instead of loading another map.
 

docs/DATA_MODEL.md

@@ -555,7 +555,7 @@ After a first-time victory, `CampaignState` advances `current_scenario_id` to th
 
 During a battle, item consumption, event item pickups, and equipment swaps affect `BattleState.battle_inventory`. `CampaignState.apply_battle_result()` commits that inventory snapshot only for a first-time victory, then adds the victory rewards. Equipped gear is stored in the player roster snapshot together with the current derived stats; a later stat-model refactor should split base stats, growth, and equipment bonuses.
 
-`BattleState` records player-only `progression_events` when a unit levels up or promotes. `CampaignState.apply_battle_result()` includes those events in the victory summary only when the first-time victory save succeeds, so completed-scenario replays and failed saves do not present unsaved growth as campaign progress.
+`BattleState` records player-only `progression_events` when a unit levels up or promotes. `CampaignState.apply_battle_result()` includes those events in the victory summary only when the first-time victory save succeeds, so completed-scenario replays and failed saves do not present unsaved growth as campaign progress. The result panel presents saved rewards, roster changes, growth, campaign status, and pending choices as separate sections; failed saves explicitly show rewards as not applied.
 
 Physical attacks grant normal attack/counter EXP only on hit after the attack/counter exchange resolves. A missed physical attack or counter grants a small miss EXP value, while defeat bonuses still require the attack to hit and defeat the target.
 

docs/GODOT_4_6_MIGRATION.md

@@ -62,6 +62,7 @@ powershell -NoProfile -ExecutionPolicy Bypass -File tools\check_godot46_readines
 - Antidote can cure poison, Panacea can cure poison, seal, snare, or disarm, and neither consumes stock when used on a target without a matching status.
 - Enemy turn advances and AI acts, including damage-aware physical target selection.
 - Victory and defeat panels still appear.
+- Victory result panels split rewards, roster changes, saved growth, campaign status, and pending choices; failed saves do not present rewards as applied.
 - Briefings show victory/defeat text plus first-clear reward previews, while post-battle dialogue and post-battle choices still block progression until a choice is saved.
 - Opening and post-battle dialogue can show generated officer portraits from `art/portraits` in the expanded dialogue panel, the side HUD can show selected or hovered unit portrait thumbnails, dialogue shows sequence progress, stepping back to the previous line works, and speaker initials are used only when no portrait is available.
 - Next battle loads with saved roster, inventory, joined officers, and campaign flags.

docs/ROADMAP.md

@@ -22,7 +22,7 @@
 - Destination victory conditions and objective map markers exist.
 - Turn-limit conditions and HUD turn-limit display exist.
 - Active HUD and briefing objective panels split objective, progress, and risk details, including gated unlocks, destinations, defeated enemies, protected-unit safety, and turns remaining.
-- Victory reward summary is visible.
+- Victory result summary splits rewards, roster changes, saved growth, campaign status, and pending choices into readable sections.
 - Next-battle flow exists across the current sixty-seven-scenario campaign.
 - Campaign completion and new-campaign reset exist.
 - Reward inventory can be brought into the next battle.
@@ -47,7 +47,7 @@
 - Opening battle dialogue exists through event actions.
 - Post-battle dialogue exists before the victory result panel.
 - Reinforcements, objective changes, and inventory pickup events exist in a basic form.
-- Post-battle reward save, campaign choice flags, and first flag-driven briefing/shop/event branches exist in a basic form. Rich reward screens and wider branch support are still planned.
+- Post-battle reward save, campaign choice flags, first flag-driven briefing/shop/event branches, sectioned result summaries, and choice reward previews exist in a basic form. Richer reward screens and wider branch support are still planned.
 
 ## Milestone 4: Campaign Progression