Plan v1.11 Risk & Reliability: 11 tasks, one outage model

Turns the approved design into an executable plan. Task order front-loads
the risk exactly as spec §13 asks: the config boolean type, then the pure
integral, then evaluation wiring that proves zero outages changes nothing,
then each source in turn, with the breaking Overclock rework deliberately
late and the goals suite as its net.

Two things worth flagging for whoever executes it:

- The Overclock conversion is defined as a RATIO of the Racks lane
  (1 + gain * ocOutput/racksOutput). At the default gain of 1 that is
  algebraically racksOutput + ocOutput, so goalCtx.totalOutputPerSec is
  unchanged on the deploy and the existing goals/contracts/achievements
  suites pass untouched - which is what de-risks "the highest-risk edit in
  the release". The balance pass becomes one tunable.

- effectiveFactor takes (outages, lane, index, from, to) rather than the
  spec's (outages, scope, from, to). Stated as a deviation in the plan;
  every call site is a loop over a lane's indices and the sketched
  signature would allocate a throwaway scope object per tier per
  evaluation. Semantics identical.

Every signature in the plan was re-verified against this branch first
(req.user.sub, the `tiers` lane name, scheduleAnomaly's shape), and the
integral, the derivation hash, the conversion algebra and the cure's
price floor were all checked numerically before the plan was committed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: Evan Phyillaier