Release v3.44.0

Added

• cratis render --check plans exactly like a normal render. It then reports, per path, what a real render would write, delete, leave unchanged or refuse, and why. It writes nothing to the destination and does not recover an interrupted publication. It exits 0 when the destination is current, the new 6 (changes_pending) when a render would write, delete or rewrite the ownership manifest, and 5 when planning fails, the render would be refused or recovery is pending, so a CI step can gate on stale generated code (#245)