Thanks again for the clarification — it helped a lot.
I updated CAVS after your comment. It now includes real `butler offline` comparisons using `butler diff/apply/verify`, plus SteamPipe-style analysis, pack layout diagnostics, route comparisons, Godot PCK certification, and a new `cavs certify` command that generates a full update report.
The project is still local-only — not a CDN or hosted service. The goal is to help developers test and understand game update behavior before shipping.
Website and guide:
https://orelvis15.github.io/cavs/
I’d really appreciate help testing it with real game builds. I don’t have enough varied game content to cover all cases, especially larger projects, different pack layouts, Godot PCKs, folders, DLC-like structures, or frequent content changes.