You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
python compat_test.py --report-only # just regenerate the report
@@ -198,7 +199,7 @@ untested robot. Completed robots are never re-run unless `--force` (everything)
198
199
Full error details land in `errors/robocode/<robot>.log` and
199
200
`errors/tank-royale/<robot>.log`; the master table is `compatibility_report.md`.
200
201
201
-
`parity-registry.json` is the tracked evidence carrier. It appends each subject observation with its jar identity, setup, engine artifacts, normalized errors, and current diagnosis. `parity-registry.md` renders the current status of every subject for review. Import an existing checkpoint with `--sync-registry`; after a diagnosis, tag a case with `--set-cause <subject> <cause> <owner>` and rerun that cause with `--retest-cause <cause>`.
202
+
`parity-registry.json` is the tracked evidence carrier. It appends each subject observation with the exact jar identity, setup, engine artifacts, normalized errors, and focused retest link. It also retains an append-only diagnosis history, so a later triage decision cannot rewrite an earlier one. `parity-registry.md` renders the current status of every subject for review. Import an existing checkpoint with `--sync-registry`; after a diagnosis, tag a case with `--set-cause <subject> <cause> <owner>` and rerun that cause with `--retest-cause <cause> --repair <commit-or-PR>`.
202
203
203
204
**Every row states the setup it was measured at.** The report is regenerated from the state
204
205
file long after the battles ran, so a single header describing the current configuration
0 commit comments