Qa Precon Rerun

Optional: --deck <id> to target a specific deck.

Process

Step 1: Re-run Games

For each deck (5 max), run 5 games with --qa flag:

node scripts/run_precon_tests.js --qa --games 5 --deck decks/precons/<deck_file>.txt

Find deck files by scanning decks/precons/*.txt for filenames matching the deck ID.

Run all decks sequentially before moving to next step.

Step 2: Check Automated Gates

For each deck:

node scripts/qa_gate_check.cjs --deck <deck_id>

Record gate results but do NOT skip AI review for failures. Gates are informational.

Step 3: Prepare Logs

For each deck:

node scripts/prepare_qa_logs.cjs --deck <deck_id>

Creates results/qa_review/<deck_id>/game_1.md through game_N.md.

Step 4: AI Review

For each deck, read results/qa_review/<deck_id>/_summary.md then each game_N.md.

Focus the review on the PREVIOUSLY REPORTED issues for this deck. Check docs/PRECON_QA_ISSUES.md for the deck's prior issues (now status FIXED) and verify they no longer appear.

Also scan for any NEW issues using the standard 4 criteria:

1. Legal Magic - Mana math, zone transitions, illegal states
2. Deck Strategy - Commander use, win path advancement
3. Battlefield Activation - Permanents being used, abilities activated
4. Intelligent Play - Sequencing, ramp timing, discard choices

Skip detailed analysis of repeated ability activations (e.g., 20x PUMP lines). Just note the pattern if it looks wrong.

Step 5: Archive Verified-Fixed Issues

When a prior issue is confirmed fixed during re-review, move it from docs/PRECON_QA_ISSUES.md to docs/PRECON_QA_ISSUES_ARCHIVE.md:

1. Cut the full issue block (from ## QA-NNN through the end of its content) from PRECON_QA_ISSUES.md
2. Append it to PRECON_QA_ISSUES_ARCHIVE.md (create the file if it doesn't exist)
3. Update the Summary counts table in PRECON_QA_ISSUES.md (decrement FIXED count, keep total accurate for active issues only)
4. WONT_FIX issues should also be archived

This keeps PRECON_QA_ISSUES.md clean — it should only contain OPEN and IN_PROGRESS issues.

The archive file header (create if missing):

# Precon QA Issues — Archive

Resolved issues moved here from `PRECON_QA_ISSUES.md` after verification.
Issues are append-only. Do not edit archived issues.

---

Step 6: Determine Verdict

For each deck:

• PASSED: Zero CRITICAL or MAJOR issues found in re-review
• HAS_ISSUES: Still has CRITICAL or MAJOR issues (log new issues)

Step 7: Log New Issues (if any)

If NEW issues are found (not previously reported), append to docs/PRECON_QA_ISSUES.md using the standard format:

## QA-NNN
- **Status**: OPEN
- **Deck**: <deck_id>
- **Commander**: <commander_name>
- **Game/Turn**: Game N, Turn M
- **Category**: <LEGAL_MAGIC|DECK_STRATEGY|BATTLEFIELD_ACTIVATION|INTELLIGENT_PLAY>
- **Severity**: <CRITICAL|MAJOR|MINOR>
- **Summary**: <one-line description>
- **Evidence**:
  - Turn X: <what happened>
  - Turn Y: <what should have happened>
- **Root Cause**: TBD
- **Fix**: TBD
- **Verified**: TBD

Update the Summary counts table.

Step 8: Update QA Index

Update results/qa_index.json for each deck:

• If PASSED: set status: "PASSED", clear issues: []
• If still HAS_ISSUES: keep status: "HAS_ISSUES", update issues array with new issue IDs
• Update lastChecked to today's date
• Update summary with fresh statistics
• Update gates with fresh gate results

Step 9: Update Process Log

Append to Changelog in docs/PRECON_QA_PROCESS.md:

### Rerun: <deck_id> (YYYY-MM-DD)
- Previous status: HAS_ISSUES (issues: QA-NNN, QA-NNN)
- New status: PASSED / HAS_ISSUES
- Prior issues verified fixed: [list]
- New issues found: [list or "none"]

Step 10: Report

QA Rerun: N decks re-reviewed
  <deck_1>: HAS_ISSUES -> PASSED / HAS_ISSUES
  <deck_2>: HAS_ISSUES -> PASSED / HAS_ISSUES
  ...
Prior issues verified fixed: X/Y
New issues found: N (X critical, Y major, Z minor)
Progress: N/202 PASSED (X.X%)
Remaining HAS_ISSUES: N decks

Key Files

What NOT to Flag

• Goldfisher limitations (no blocking, no opponent interaction)
• Opponent rotation being simple/predictable
• MANA_REUSE integrity warnings (known engine limitation)
• Win rate or speed alone (unless something is clearly broken)
• MINOR issues that are suboptimal but not wrong (don't block PASSED status)
• Conformance grade being low due to scorer calibration (if the deck IS playing well)

Windows Bash Rules

NEVER use inline node -e or complex bash one-liners. Write .temp/lookup_qa.cjs scripts instead.