Implement New Game Effect and Continue Work Queue

Summary

Read docs/work-queue.md and do the next unchecked batch. For each batch:

Read the engine files (mtg-engine/src/abilities.rs, mtg-engine/src/game.rs) to understand current Effect/StaticEffect variants
If the batch has a NOTE about uncertainty, investigate first and update the queue with findings before committing the fix
If engine work is needed: add the variant, constructor, and match arm, and look for the Java implementation to see the bigger picture
Add a test for any new engine effect (follow the pattern in game.rs mod tests)
Fix all cards listed in the batch (grep to find exact lines, fix across all 4 set files)
cargo check -p mtg-cards && cargo test --lib
Update docs: mark cards in docs/{fdn,tla,tdm,ecl}-remediation.md, update ROADMAP.md
Check off the batch in docs/work-queue.md with today's date
If you discover new cards that fit the current or a future batch while working, add them to the queue

If a batch turns out to be wrong or more complex than described, update the queue with what you learned and move on to the next one.

I'll start by reading the work queue to find the next unchecked batch.

The next unchecked batch is Batch 9: AddCountersAll. Let me read the engine files and find the card.

Let me search for the relevant sections in game.rs and the card in the ECL set file.

Let me see the full AddCounters match arm and the ECL card context.

Let me also check for any other cards across all sets that might use this same pattern.

Let me check the TDM card that also uses counters on each creature.

Let me check how matches_filter works to understand filter handling for the new effect.

Good. Now I have all the context I need. Let me also find where in execute_effects I should insert the new match arm — right after AddCounters seems logical. Let me also look at the test section of game.rs for the existing AddCounters test.

Now I have the full picture. Let me find the end of the execute_effects match block to know exactly where to insert the new arm. Let me look for the Custom catch-all:

Good. The catch-all _ => at line 1510 is the end of the execute_effects match. I'll add the new match arm before that. Now let me implement everything.

Now I have everything I need. Let me implement:

Add AddCountersAll variant to Effect enum in abilities.rs
Add add_counters_all() constructor
Add match arm in game.rs execute_effects
Add test in game.rs
Fix cards in ecl.rs and tdm.rs

Now add the constructor:

Now add the match arm in game.rs, right before the catch-all:

Now add the test. Let me find the end of the existing test section:

Now I'll add the test right before the closing } of the test module:

Now fix the cards. First, Darkness Descends in ecl.rs:

Now fix Barrensteppe Siege in tdm.rs:

Now let's build and test:

The test used the wrong constructor. Let me check how other tests in that file create a Game:

I see — it uses Game::new_two_player with GameConfig. Let me also check what make_deck does:

Now let me fix my test to use the correct constructor pattern:

All 254 tests pass. Now let me update the docs. First, check the remediation docs and update them.

Now update ROADMAP.md:

Now check off the batch in work-queue.md and update it with the TDM card:

Now let me proceed to Batch 10: Compound self-counter + target effects. Let me read the batch and investigate:

Let me check the current state of these cards:

Dream Seizer is already fixed from Batch 3. The key question is whether Warren Torchmaster's compound self-counter + target effect works correctly. Let me investigate how effect resolution handles targets when mixing self-counter and target effects:

Let me check how triggered ability resolution handles costs:

API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CY8AdB9bgCSEN5higyL9A"} · Please run /login