Simplify MiMo audit summary and report full-release timestamp findings

mimo_v1/README.md

@@ -36,23 +36,16 @@ Includes the full validation run and reruns of repaired tasks. Task `002797` als
 
 ## Reported reward hacks
 
-[Vals AI](https://www.vals.ai/blogs/mimo-reward-hacking) reported readable solution commits in 1,795 of the 2,698 original Code environments, plus file modification times that could reveal which files the reference patch changed. Our comparisons of old and re-uploaded images found that upstream had removed unreachable Git objects in the inspected images. 
+[Vals AI](https://www.vals.ai/blogs/mimo-reward-hacking) found solution commits in 1,795 of the 2,698 original Code environments. MiMo's re-upload appears to have addressed this: across our 2,509 released tasks, our Git cleanup found no remaining refs or unreachable objects to remove. Our new check looks for commits beyond the task's starting point, including commits hidden from normal Git history.
 
-All 2,509 task Dockerfiles in this release include a build-time repository repair: remove non-ancestor refs, expire reflogs, prune unreachable objects, and normalize tracked-file and directory modification times to the HEAD commit time. The release contains these Dockerfiles and pinned upstream image references, not rebuilt Docker images. In the saved 39-task repair pilot, 22 environments had timestamp outliers before repair; the history and timestamp checks passed for all 39 after repair. This pilot is separate from full datasource validation.
+**Timestamp hints remained in the re-upload:** our check flagged unusual file timestamps in **975 of the 2,509 tasks**, which could reveal where to make the fix. We added timestamp normalization to all released task Dockerfiles, alongside Git cleanup.
 
-We also revisited [Charlie Ruan's audit](https://github.com/CharlieFRuan/rl-env-cleaner/tree/836c6061a2d8605155c47041a1ee02e5e5554e6e/mimo_swe) against the re-uploaded images. The recorded disposition of the **27 reported cases** was:
+We also rechecked [Charlie Ruan's findings](https://github.com/CharlieFRuan/rl-env-cleaner/tree/836c6061a2d8605155c47041a1ee02e5e5554e6e/mimo_swe):
 
-- **21 resolved by the upstream re-upload.** The previously reported leakage was recorded as removed; this group includes the trajectory-only case `002607`.
-- **3 archived.** Image `000484` was removed upstream. Task `000092` still exposed feature-specific tests in an installed package, and `001397` still exposed the implementation fix.
-- **3 retained after inspection:** `000407`, `002070`, and `002517`. The inspected differences were older code or required package-release content, without the reported fix being identified.
+- **27 reported cases:** 21 were recorded as fixed by the re-upload; we excluded 3 (one missing image and two with solution or test hints), and kept 3 after inspecting the remaining files.
+- **56 additional tasks with leftover files:** 27 were clean. For 22, copying the installed code into the repository did not pass the verifier. Of the remaining 7, we excluded 1 containing the requested feature and kept 6 after inspection. These checks did not demonstrate an exploit in the retained cases, but do not rule out every possible shortcut.
 
-The **56 additional residue flags** were also rechecked on 2026-10-18; they are not 56 confirmed exploits or an outstanding backlog:
-
-- **27:** the reported leftovers were absent or matched the repository.
-- **22:** installed project files still differed. Copying those files into the repository and running the verifier returned reward 0 for every task. This specific transplant did not solve the tasks; it does not establish that every leftover is harmless.
-- **7:** cache or bytecode leftovers required content inspection instead. Task `000253` contained the requested feature's API in an installed package and was archived. The other six (`000046`, `000283`, `000556`, `000699`, `000114`, `001372`) were retained after the inspected leftovers did not contain the searched feature identifiers; no successful exploit was demonstrated by that inspection.
-
-These are the residue-review decisions. Other validation findings can independently exclude a task. The three content-residue exclusions in the release are `000092`, `001397`, and `000253`; the removed image `000484` is counted separately among missing upstream images.
+We excluded `000092`, `001397`, and `000253` for solution or test hints, plus `000484` because its upstream image was removed. Other validation failures are counted separately above.
 
 ## Runtime and validation time