What problem does it solve? When working on the TinySocs codebase, you often need to know whether a bug is a known recurrence or genuinely new, why code looks unusual, or how a subsystem reached its current state. This Skill provides a verified chronicle of every major investigation, revert, and recurring bug class across the repo's 366-commit history, so you avoid repeating past mistakes and misquoting superseded figures. ## Core Features & Use Cases - Episode-based failure catalog: Each entry follows a SYMPTOM -> ROOT CAUSE -> EVIDENCE -> STATUS structure with commit SHAs re-verified directly against the repository. - Recurring bug class tracking: Documents patterns like em-dash characters breaking PowerShell 5.1, stale MIT licence claims, doubled directories, and silently red CI, with their current status. - Timeline and pivot history: Maps commit-volume evidence across Oct 2025 to Jul 2026, including the April 2026 zero-commit gap and the v2 pivot restart. - Use Case: Before modifying the dashboard's inline script block, consult this Skill to learn that a two-script split was already tried and reverted (commit dd95fbd), and that a widget-load ordering test should be added first. ## Quick Start Ask the AI to check the TinySocs failure history to determine whether the bug you are investigating has occurred before and what its root cause was.
