| @@ -1,6 +1,6 @@ |
| 1 | 1 | --- |
| 2 | 2 | issue: 1 |
| 3 | | -status: working |
| 3 | +status: done |
| 4 | 4 | --- |
| 5 | 5 | # Score exact-five threats and open/closed lines |
| 6 | 6 | |
| @@ -35,9 +35,11 @@ full board; none ended by timeout, startup failure, or an illegal move. |
| 35 | 35 | Maximum referee-measured local reply latency was 8 ms, under the nominal |
| 36 | 36 | 1 second limit on this machine. Hosted performance remains to be checked. |
| 37 | 37 | |
| 38 | | -The local tactical/protocol suite passes 11 tests. The site had not posted a |
| 39 | | -check status for the initial claim commit when inspected; local measurements |
| 40 | | -are reported evidence, not a claim of hosted verification or acceptance. |
| 38 | +The local tactical/protocol suite passes 11 tests. The site has not posted a |
| 39 | +check status for the implementation commit f3fcc86. Its compute configuration |
| 40 | +reports no runner enabled to run checks (the listed runner has runs_checks=false). |
| 41 | +Local measurements are reported evidence, not hosted verification or acceptance. |
| 42 | +The route is done as a delivery; external review and CI remain pending. |
| 41 | 43 | |
| 42 | 44 | ## Reproduce |
| 43 | 45 | |
| @@ -64,7 +66,8 @@ sample, with deterministic openings and opponents. |
| 64 | 66 | |
| 65 | 67 | ## Next |
| 66 | 68 | |
| 67 | | -Review the delivery and its hosted play status. If continuing after review, |
| 69 | +The maintainer should enable a check-capable runner and review this delivery |
| 70 | +and its hosted play status. If continuing after review, |
| 68 | 71 | inspect the four losses against threats recorded in out/games.json and add a |
| 69 | 72 | bounded tactical search to address the first missed forced sequence. No long |
| 70 | 73 | computation is running. |
codex-golive