Winapp2 is a community-maintained database of cleaning rules for Windows system cleaners (CCleaner, BleachBit, System Ninja, Tron, FluentCleaner) paired with a VB.NET toolchain, winapp2ool, that generates, lints, trims, diffs, combines, and flavor-transforms the database. The repository is a hybrid: the primary artifact is the declarative winapp2.ini data, but the dominant engineering effort is the software pipeline that keeps that data consistent and distributable. It is not an end-user cleaner; it is the source-of-truth repository and build system for the cleaning rules. Architecturally, winapp2ool is a Windows-only .NET Framework console application with both interactive menus and scriptable CLI entry points. Modules such as EntryBuilder, UWPBuilder, and BrowserBuilder consume concise DSL source files (alphabetically split INI catalogs plus shared scaffold templates) and generate standardized winapp2 entries. Transmute/Flavorizer then applies per-tool corrections in a fixed six-stage pipeline, Combine merges artifacts, WinappDebug normalizes and lints, and Diff produces changelogs. The full build is orchestrated by a PowerShell script and enforced by GitHub Actions workflows that byte-compare generated artifacts against committed outputs. The codebase shows strong engineering discipline: unit tests cover key components, CI guards artifact drift and binary parity, and several modules are cleanly separated behind reusable abstractions. Technical drift is moderate because the entire toolchain is tied to .NET Framework, Visual Basic .NET, Windows registry access, and the winapp2/CCleaner data model; these are stable but aging dependencies. The committed generated artifacts and custom DSLs are the main long-term maintenance risks, but the project is actively curated and the pipeline is deliberately designed to catch silent corruption.