chore(release): 0.7.0

[drewstone]

Cuts 0.7.0 for the game-over stop (#25).

An episode can now end because the game ended, not only because it ran out of turns or budget. advanceRollout gained a fourth stop condition returning 'gameOver' — an ordinary loop exit, so finalizeRecord runs and the attestation is built exactly as for a turn-limit stop. The pre-existing signal path could not be used for this: it throws before the record is finalized, destroying the evidence the grade is made of.

Game gained an optional over(state). Deriving the flag harness-side was rejected after checking: every substrate publishes a terminal concept in evidence().engineState, but under four different names (ALE terminal, Gymnasium terminated/truncated, stable-retro episodeDone, 2048 gameOver), so a central derivation would guess at field names and fail silently on the next adapter.

Measured on ALE Breakout, seed 0, maxTurns: 300, scripted policy:

run	decisions	stoppedBy	milestones
turn limit	300	maxTurns	4 of 6
stopAtGameOver: true	150	gameOver	4 of 6

Half the decisions, identical verdict. The dropped decisions were verified inert rather than assumed: every evidence channel is byte-identical from decision 150 to 300, while 149 to 150 did move the emulator.

Opt-in, so existing callers keep their fixed denominators. The offset is that stoppedBy and gameOver are recorded on every run whether or not the stop is armed — stoppedBy: 'maxTurns' beside gameOver: true can only come from an episode played past the end, which is now visible in any artifact.

Motivation: a consumer measured 163 of 300 decisions (54.3%) played after the game was over, and could not fix it from outside.