source-command-triage-player-report

To convert a Lorcana bug report into a failing simulator test, ingest the player issue, validate referenced cards, cross-check official rules, and generate a deterministic reproduction test before applying a minimal engine fix.

Replay analysis grounds debugging by pulling production evidence using a gameId and turn to pinpoint the exact step where gameplay behavior diverged from official rules, ensuring the reproduction test targets the root cause.

Yes, providing a Linear issue URL allows the triage process to extract the canonical title, description, context, and acceptance criteria, keeping progress updates aligned with the original player report throughout the workflow.

The best way to validate Lorcana cards and rules during bug triage is to deterministically resolve all referenced card identities and cross-check their interaction timing and legality against official rules before generating tests.

You do not need production replay context to generate a failing test, but providing a gameId and turn enhances debugging by grounding the reproduction in real evidence rather than relying solely on the issue description.

Player bug report fixes fail CI checks when the minimal root-cause implementation is not verified with targeted tests, requiring strict execution of the final verification phase to ensure engine changes pass repo checks.