v0.94.481

Every offer-curve point is what a plan at its price would do.

• Every offer-curve point is what a plan at its price would do
  (#1990). The sweep
  moved only period 0's import or export cost, but a real plan at another price
  also moves the battery's loss tie-break (#732), the emergency-import markup
  (#390), the P2P shortfall rate and a price-derived soft SoC penalty, and it
  re-solves a plan that imports and exports at once one-way (#238). So some
  points, and the price range published with each, described plans no solve
  would make. All of these now move with the swept price, each point is made
  one-way the way build_plan does it, and each plateau's end is checked
  against the real solve (bisected when it ends sooner). Dispatch is unchanged.
  The sweep costs more solves: about 0.14 s on the 24-period test day (under
  #494's 0.5 s bar) and several times main's figure on a full horizon, inside
  the one-minute solver tick.
• Devhub validation: confirmed live on devhub (HA 2026.10.2) at f5579ba
  (release/0.94.481), installed via HACS and restarted at 15:17 AEST; Home
  Assistant was back at 15:17:43 and Nimbus loaded. Since then the solver has
  cycled with no solver failure, no #773 fallback and no new Nimbus ERROR or
  traceback against the pre-install log; the Forecaster sensors refreshed by 15:45.
  • Not observable on devhub: the offer curve itself. devhub's own
    offer-curve sensor cannot register (a mirrored entity holds its name), so
    the change this release makes is carried by #1993's tests, not by a devhub
    reading.
• Consumer check: on an install with the offer curve switched on, each
  published import and export point, and the price range shown with it, now
  matches what a plan at that price would do; the plan itself is unchanged.