[Remediation] Visually confirm the passive feedback surfaces (Stonewall/Iron Belly hud popup + combat-log line) (#78 FR-6)

[jarlbrak]

Summary

Close the last PARTIAL requirement of spec #78. FR-6's acceptance criteria require the floating HUD text and the combat-log line to be OBSERVED solo in-game for both procs. The emission code is proven firing (the Plugin.Log line emitted from the same block was observed for both traits, and the localized templates round-trip in the self-test), but the 2-second floating popups and the combat-log panel were never visually captured by the automated harness (screenshot latency).

Implements

• Spec: Passive Class Traits (Content.AddPassive) + Innkeeper showcase (Stonewall, Iron Belly) #78 (FR-6)

Acceptance Criteria

• "Stonewall!" floating text and the combat-log line "Solid as a doorpost, the Innkeeper turns the blow aside." observed in a solo combat when the negate fires
• "Iron Belly!" floating text and the combat-log line "The Innkeeper's cast-iron stomach shrugs it off." observed when a rum's enConfuse is vetoed
• Evidence attached (screenshot or a human eyeball noted on this issue)

Technical Approach

No code expected. This is a verification task: play one solo combat as the Innkeeper (start_run class ftkmf_innkeeper via the agent bridge, engage, take a hit, use_item conRum) and watch the two popups, or open the combat log panel afterward. If either surface does NOT render, that becomes a real code fix on Core/PassiveTriggerPatches.cs feedback emission.

Context

Requirement: FR-6
Current status: PARTIAL (emission proven at log level; visual render unobserved)
Evidence: two [passive] log lines in the final verification session; screenshots missed the 2s popups

[jarlbrak]

Automated capture attempt: strong corroborating evidence, literal glyph still needs a human eyeball

Ran multiple solo Innkeeper combats with a continuous screenshot burst (~1s cadence, 60-frame windows) trying to freeze the floating "Stonewall!" / "Iron Belly!" text. What was captured:

• Mechanical proof of the negate rendering: in the combat where the log recorded stonewall negated 7 dmg, a burst frame shows the Innkeeper at 39/39 HP with the enemy mid-attack: the negated hit dealt ZERO (HP never dropped). Later hits that turn show normal floating damage numbers (a -7 over the hero).
• The feedback CHANNEL is confirmed rendering: multiple SpawnHudTextRPC floating numbers were frozen (-4 over the enemy from the hero's own attack, -7 over the hero). Stonewall and Iron Belly emit their popups through this identical SpawnHudTextRPC path.
• Iron Belly: [passive] com.ftkmf.framework:iron_belly shrugged off enConfuse for Player 1. logged on the real rum-drink path, with the rum's buffs applied (armor/resist up-arrows on the panel) and no Confuse icon.
• Both procs' log lines fire from the exact same code block as the popup + combat-log emission.

What was NOT captured: the literal 2-second "Stonewall!" / "Iron Belly!" text glyph in a single screenshot. It triggers at an unpredictable sub-second moment and the external screenshot endpoint samples at ~1s, so the burst kept landing just before/after the glyph.

Recommendation: this is now a 5-minute human eyeball, exactly the disposition this issue's acceptance criteria already allow ("a human eyeball noted on this issue"). Play one solo combat as the Innkeeper (she starts with a rum), take a hit and drink the rum, and confirm the two popups plus the combat-log lines render. The mechanical behavior and the feedback channel are both already proven; only the cosmetic text glyph awaits a live watch. Leaving open for that.