BililiveRecorder is a production-grade Bilibili live stream recorder. It polls room status, auto-starts recording when a stream goes live, captures FLV video and danmaku (bullet comments), and repairs stream corruption in real time. It ships as a Windows WPF desktop app, a headless CLI with multi-arch Docker images, and an ASP.NET Core web server exposing REST + GraphQL APIs, an embedded web UI, and a file browser. A ToolBox adds offline FLV analysis/repair, danmaku XML merging, and FLV-to-MP4 remuxing. The architecture is a layered .NET solution. BililiveRecorder.Flv provides low-level FLV tag parsing, a complete AMF0 codec, and a composable processing pipeline. Core manages room lifecycle, Bilibili API integration (WBI request signing, HTTP 412 handling), danmaku transport over TCP/WebSocket with protobuf plus deflate/brotli compression, v1/v2/v3 hierarchical configuration, webhook notifications, and a Jint-based user scripting sandbox. The Web, CLI, and WPF frontends consume these libraries. A TypeScript code-generation tool (config_gen) produces C# config classes, DTOs, GraphQL types, CLI instructions, and JSON schemas from a single data definition to keep layers in sync. The stand-out engineering is the FLV repair pipeline: composable rules correct timestamp jumps and offsets, remove duplicated and filler data, handle delayed audio headers, detect ffmpeg re-streaming, and rewrite keyframe metadata — the same pipeline powers both live capture and offline repair. The project is actively maintained with CI/CD (CodeQL, multi-arch Docker builds, Squirrel release packaging), four test projects with verified sample FLV expectations, and localization in four languages. Main risks are tight coupling to Bilibili's undocumented APIs, the WPF client still targeting .NET Framework 4.7.2, deprecated V2 config persistence, and bundled minified third-party JavaScript that is difficult to audit.