Paradox Haze — no extra upkeep, fires on wrong player

[matthewevans]

Bug Report

Source: Discord / Engine analysis
Discord thread: Things I experienced while deck testing

Cards

Paradox Haze

Actual Behavior

1. Paradox Haze does not provide an additional upkeep step for its controller.
2. The trigger fires during the wrong player's upkeep (opponent's upkeep instead of enchanted player's).

Expected Behavior

Paradox Haze should give its controller an additional upkeep step during each of their turns. It should not trigger during the opponent's upkeep.

Parser Status

has_gaps — the "additional upkeep" trigger and the correct controller-scope are not parsed.

[matthewevans]

Fixed in bc580d359.

Verification:

• Paradox Haze now parses without an Unimplemented effect. oracle-gen --filter Paradox Haze emits a Phase upkeep trigger with valid_target AttachedTo, constraint MaxTimesPerTurn { max: 1 }, and Effect::AdditionalPhase { target: TriggeringPlayer, phase: Upkeep, after: Upkeep }.
• Generalized the old combat-only extra phase effect into the CR 500.8 AdditionalPhase primitive rather than adding a Paradox-specific one-off.
• Runtime trigger matching now applies phase-trigger valid_target to the active player, so enchanted-player upkeep is scoped to the player the Aura is attached to.
• Ran targeted tests for additional phase handling, Paradox Haze trigger parsing, phase-trigger attached-player scoping, additional-upkeep parsing, plus CARGO_TARGET_DIR=target/codex-check cargo check -p engine.