What problem does it solve? When debugging SparkEngine, engineers risk re-investigating bugs that were already solved or retrying approaches that already failed expensively. This Skill provides a chronological case-file of the engine's hardest historical bugs so you can check whether a symptom was fixed before, find the exact fix commit, and avoid repeating failed strategies. ## Core Features & Use Cases - Incident history with commit hashes: Each entry records the symptom, root cause, the exact fix commit (verifiable via git show), and current landed/open status across eras covering the Great Revert, ICF type-id folding, DLL/module lifetime crashes, editor undo convergence, and networking trust-boundary fixes. - Failed-approach registry: Documents approaches that must not be retried in the same shape, such as the big-bang abstraction migration reverted in 7851ee38. - Deferred-work ledger: Tracks which harden-fleet items remain open (e.g., the NetworkManager per-module fallback, ConsoleApp.cpp split) versus those already landed. - Use Case: A Windows Release-only CI failure reappears and feels familiar. Consult this Skill to discover it matches the /OPT:ICF type-id folding incident fixed in 21b1a689, then run git show 21b1a689 for the full reasoning instead of re-debugging from scratch. ## Quick Start Ask whether the bug you are investigating has happened before in SparkEngine and request the fix commit and current status for that incident.
