McGarrah Technical Blog

Losing a primary phone number tied to decades of professional history, resumes, and account recovery flows is a technical emergency, not a mild inconvenience.

Kiro is AWS’s AI-native IDE — a Code OSS fork with agentic coding capabilities baked in.

The first five articles in this series documented the development path from problem statement through operational deployment of the Media Integrity Scanner plugin.

The plugin is built — scanner core, SQLite persistence, REST API, admin dashboard.

Two months ago I wrote about managing context across multiple AI coding assistants and documented the reference guide for every agent’s file format.

The scanner core handles the detection work — finding corrupt files and recording results in SQLite.

The architecture article laid out the design decisions — two-phase scanning, I/O throttling, SQLite persistence, event-driven updates.

Part 3 laid out the planned migration procedure.

Part 1 covered replacing a failed drive with one of the same size.

The first article introduced the problem: media files rot silently, and Jellyfin doesn’t validate stream integrity.

Your Jellyfin library looks healthy.