v0.5.3

Closes the audit 0.5.2 left open. Its notes listed Explorer and Duel as unchecked against a strategy run; this is that check.

Duel — audited, no change needed

It was already right, and in the ways that matter:

• the authored side gets an explicitly empty selection plus the compiled program, so nothing can read a bet rail by accident
• the combo name omits the progression rather than printing a placeholder
• it reports no per-dollar edge for a rule set, because one has no closed form — the spec's own rule about not drawing a fabricated analytic line

Fixed

The Explorer called a written strategy flat, in four places.

A written strategy enters the Explorer as four rows pinned to Progression::Flat — deliberately, because the Explorer does not cross a strategy with the twelve progressions, and the engine has a test holding it to that. The pin is a placeholder, not a reading.

Four sites rendered it anyway: the dot tooltip, the results table, the copied text, and the dot's ring, which encodes pressing class and drew nothing at all — the legend's word for flat. A strategy that Martingales its don't pass was described, four ways, as pressing nothing. The same sentence the Findings histogram carried until 0.5.2, in a screen the 0.5.2 notes had listed as unaudited.

The three text sites now ask the strategy, and say "as written" when the compiled program in hand cannot be proved to be the one that produced the rows on screen. The ring is classified from what the strategy declares, ringing for the heaviest system it declares — three classes cannot say more than that, and "flat" was the one answer that was wrong.

The Explorer was correct everywhere someone had already thought about the sentinel: it never indexes the curated list with it, the authored lane is placed rather than computed, and the edge column reads a dash.

Added

• Program::declared_pressing — the structured form behind Program::pressing_label, for callers that classify rather than print.

Also confirmed

Neither screen reads the bet rail's selection at all. That was the defect behind all six of the 0.5.2 fixes, and it is not present in either.