See who failed which mechanic, pull by pull

One rule, checked for every player on every pull. A watcher counts mistakes (being hit by what you should dodge, missing a soak), credit (a kick, a droplet taken, damage to the add), or a fact nobody is charged for, when the log cannot say who was at fault.

• Every mechanic of the boss's guide, read from its own instruction: dodge it, soak it, spread, pair up, kill the add. Boss rules fix the few the wording gets wrong (The Venomous Abyss).
• On every boss, guide or not: deaths, interrupts, dispels, consumables, preparation and personal defensives.
• Any other ability: pick one from the log and see who it hit.
• Your own watchers: damage taken, a debuff, an expected cast or an interrupt, with a time window and a role, shared with a code.

• Overview: the player with the most mistakes, pull by pull, the top issues and what killed the raid.
• Mechanics: each watcher as a card with its verdict and a strip per player showing the pulls they failed, so a habit stands out from a one-off.
• Players: a score per player, grouped by role, from how often they passed what they were given, weighted by severity. It compares players on these pulls only, not with other raids.
• Timeline: one pull minute by minute, with the boss's mechanics, deaths, taunts and cooldowns.

The last six by default, or this pull only, the last three, ten, or all of them. Each pull is counted until the wipe began, so a lost pull's last seconds are charged to nobody; that can be set to 1, 2, 3 or 5 deaths, or the whole pull (death cutoff).

Every count follows Warcraft Logs' own, hits and ticks apart, so you can open the same pull on the site and find the same number (hits vs ticks). Where LogSnitch counts differently on purpose, the card says so and why.

Yes, with a report logged live: LogSnitch checks it for new pulls on its own and flags each one as it lands. Each pull's summary can also be posted to a Discord channel through a webhook.