mathiasandClaude Sonnet 5.5
b66b45b8fd
From the independent review: - the archive dir is unique per run (-2, -3 ...): a second Apply the same day replaced the first run's archived original and rewrote its manifest - every Move/Delete carries the SHA-256 it was planned on; Apply skips and reports (Result.Changed) a page whose bytes changed since planning, so a note dropped again after PlanRaw is not deleted unprocessed - Rollback verifies all targets before changing anything, recognises pages already restored (so it can be run again), and refuses to delete a moved copy that was edited since the move - names whose flattened archive key exceeds NAME_MAX are skipped at planning time instead of wedging the run - a page that already has wing/hall keys, or whose type sits in a nested/block scalar line or an unterminated block, is not moved Each has a test that fails without it (mutation-checked). Residual: a swap between Apply's read and its remove; the archived copy is still the bytes read. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>