From fa02f1a32360a3a0b823a5ff357e20ae07836c3c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=9B=B7=E7=94=B5=E8=8A=BD=E8=A1=A3?= Date: Wed, 14 Oct 2026 22:41:49 -0400 Subject: [PATCH] R4.11: round 1 verdict Co-Authored-By: Claude Opus 5.5 (1M context) --- tasks/reviews/R4.11-r1.md | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 tasks/reviews/R4.11-r1.md diff --git a/tasks/reviews/R4.11-r1.md b/tasks/reviews/R4.11-r1.md new file mode 100644 index 0000000..4fd8147 --- /dev/null +++ b/tasks/reviews/R4.11-r1.md @@ -0,0 +1,3 @@ +FAIL + +1. `.work/R4.11/lib.ps1:28` — [P2] The acceptance driver's backup does not preserve an originally absent configuration file. All five scripts reuse `run/kept`; `Keep-Data` overwrites existing files but leaves old snapshots when a source file is missing, and `Restore-Data` restores those snapshots unconditionally. Run the driver once with `settings.json` present, delete that file to reset the settings, then run it again: the second run restores the first run's obsolete settings instead of leaving the file absent. The same applies to session, recent-file and view state. Reproduced using the unchanged backup/restore functions with disposable directories; evidence: `.work/R4.11-r1/backup-probe.log`. Use a fresh backup directory for each run, or record each file's original presence and clear stale snapshots for absent files; add a two-run regression that verifies both bytes and absence are restored.