v0.1.5

The Hundred: five-ball sets reach the chase rate and score parsing

mcp.go reported every Hundred chase 20% high: 'per over required' computed
against six when a set is five. Now uses the state's balls-per-over and
names the unit, so a Hundred chase reads 'per set'.

ParseScoreString was the worse one. ESPN reports some innings as '(N
balls)', and converting with a hardcoded six turned 30 balls of a Hundred
innings into 5.0 overs when it is 6.0 five-ball sets, making every ball
count derived from it wrong. ParseScoreStringBPO takes the format; the old
name keeps its six-ball meaning for existing callers.