tooling(pm): price a destination's ordinary ruled raise apart from its move's (#15266)

`CROSS_FILE_MOVES` computed a move's raise as `ceiling − was`, so an ORDINARY
ruled raise later taken on the same destination was read as the move's: on this
tree the platform-readings entry measured `314 → 358 = +44 against −11` and went
red twice, for lines no source was ever asked to pay. The one lever available
was carrying `was` forward past the ruling, which keeps the arithmetic right by
making the field mean two things at once.

A declaration may now carry `ruledRaises` — one record per ordinary ruled raise
taken on the destination since the move, each quoting the ruling that authorised
it and dated — subtracted before the move's raise is measured, and restored
alongside `was` in the map-wide total. `was` goes back to one fact, so the
reviewer's completeness check keeps the single shape it has always had.

The live declaration migrates back to `was: 314` with the 2026-09-04 intake
ruling's +34 recorded and its words copied from the ceiling comment beside it.
The gate's whole output is unchanged but for that one verdict line.

Because the subtraction is a licence to grow, it carries two bars of its own: a
record quoting no ruling is red, and so is a set of records claiming more lines
than the ceiling stands above `was` — which is what stops an inflated record
from reading as paid down. Neither proves the maintainer said the words; that
stays the reviewer's check, as it already is for every `was` here.


Claude-Session: https://claude.ai/code/session_019RfFHiRCSs3JXLK4cwcfox

Co-authored-by: Claude <noreply@anthropic.com>

Author: claude[bot]