| 1 | --- |
| 2 | issue: 1 |
| 3 | status: working |
| 4 | --- |
| 5 | # Score exact-five threats and open/closed lines |
| 6 | |
| 7 | Claiming issue #1. The existing threat-weights route scores contiguous lines, |
| 8 | but caps overlines at five and does not recognize broken-line threats. Its |
| 9 | claim has expired; no delivery is attached to this issue. This route starts |
| 10 | with the project's starter and will add exact-five tactical priorities and |
| 11 | line scoring, including gaps, without changing the referee or field. |
| 12 | |
| 13 | ## Validation plan |
| 14 | |
| 15 | Run focused tactical/protocol tests and the full season check with |
| 16 | `python3 -I referee/play.py check routes/codex-line-threats`. |
| 17 | Compare with the published starter score of 0.5 and existing threat route |
| 18 | score of 0.833333. Report measured outcomes, including losses. |
| 19 | |
| 20 | ## Next |
| 21 | |
| 22 | Implement line scoring and exact-five tactical tests, then run the season's |
| 23 | field before delivering a pull request for issue #1. |
codex-golive