Total grade cutover + the ceiling stated as a position

PHASE 0 caught my own repeat of the failure I diagnosed one order ago.
91927a4 attached `served_grade` BESIDE the old letter and left `grade`
alone -- so the honest grade reached nobody, exactly as gradeBands had
been built-correct-and-unread. grep showed served_grade appearing in one
file (where I set it) and all 14+ consumers -- scan route, dashboard,
parlay, newsletter, desk, content templates, retention -- still reading
`.grade`, i.e. still the dishonest letter.

CUTOVER IS NOW TOTAL: legacy.grade IS the honest letter. Overwriting the
one field every consumer already reads cuts every surface over at once
instead of editing fourteen call sites and missing one. engine1's index is
preserved as `engine_grade` and verified read by ZERO serving code.

Confidence follows the letter: it came from a grade-band midpoint of the
OLD letter, so leaving it would have paired a served B+ with a C's
confidence. Both now derive from p_win, kept on the existing 0-100 scale.

MEASURED BLAST RADIUS before shipping: 303 of 47,991 non-refused
snapshots (0.6%) have a grade but no p_win, and now render NO READ instead
of a letter. That is correct -- their old letter came from the retired
index carrying 0.48% resolution, i.e. noise -- and NO READ is a rendered
state with a reason, so never-blank holds.

PHASE 1 — the ceiling is now a STATED POSITION, not a confusing absence.
servedGrade.SCALE_LEGEND plus web GradeScaleLegend.tsx say it plainly: we
do not issue A grades, no band has hit at a rate that would justify one,
our honest ceiling is a strong B+ (~66% realized vs ~60% baseline), and if
the model earns an A the legend changes and we say why. The
separates_from_base_rate flag renders per band -- C+/C/C- are labelled
"we cannot separate this from the baseline", which is most of any slate.

PHASE 3 hand-verified across every state: B+ with 3 factors (basis
forecast_plus_matchup_factors), B+ with none (forecast_only), C flagged
not-separable, F, and three refusal states rendering NO READ with reasons.
never-blank PASS, no-manufactured-A PASS.

Test fallout was real and is documented rather than papered over: engine
BEHAVIOUR assertions moved to engine_grade, suppression assertions stayed
on grade (a suppressed prop has no letter either way), and the confidence
78 -> 95 change is the grade-band midpoint being replaced by p_win.

No A-threshold loosening. No calibrated number leaks (deployed set empty).
p_win never mutated. Ten frozen modules verified unchanged including
engine1 and probabilityEstimator. No Bonferroni slot.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9

web/src/components/vyndr/GradeScaleLegend.tsx

@@ -0,0 +1,61 @@
+'use client';
+
+/**
+ * The grade scale, stated as a position.
+ *
+ * A user who never sees an A will invent a reason for it, and every reason they
+ * might invent is wrong. So the ceiling is named: top grades are earned from
+ * realized outcomes, and this model has not earned one.
+ *
+ * Mirrors `src/services/model/servedGrade.js` SCALE_LEGEND. If the ceiling moves
+ * there, it moves here — and that change should be deliberate and visible, which
+ * is the whole point of writing it down in both places.
+ */
+
+const BANDS = [
+  { letter: 'B+', realized: '~66%', separates: true, note: 'the strongest read this model produces' },
+  { letter: 'B', realized: '~65%', separates: true, note: 'above the baseline' },
+  { letter: 'C+', realized: '~62%', separates: false, note: 'not separable from the baseline' },
+  { letter: 'C', realized: '~59%', separates: false, note: 'a base-rate read' },
+  { letter: 'C-', realized: '~55%', separates: false, note: 'at or below baseline' },
+  { letter: 'D', realized: '~51%', separates: true, note: 'below baseline' },
+  { letter: 'F', realized: '~45%', separates: true, note: 'well below baseline' },
+];
+
+export default function GradeScaleLegend({ compact = false }: { compact?: boolean }) {
+  return (
+    <div className="mono" style={{ fontSize: 11, lineHeight: 1.6, color: 'var(--text-2)' }}>
+      <div style={{ fontWeight: 800, letterSpacing: '.08em', color: 'var(--text-1)', marginBottom: 6 }}>
+        WHAT A GRADE MEANS
+      </div>
+      <p style={{ margin: '0 0 8px' }}>
+        Grades are earned from realized outcomes, not issued on confidence. Each letter below
+        shows how often those reads have actually landed, against a ~60% baseline.
+      </p>
+
+      {!compact && (
+        <div style={{ display: 'grid', gap: 2, margin: '0 0 10px' }}>
+          {BANDS.map((b) => (
+            <div key={b.letter} style={{ display: 'flex', gap: 8, alignItems: 'baseline' }}>
+              <span style={{ minWidth: 26, fontWeight: 800, color: 'var(--text-1)' }}>{b.letter}</span>
+              <span style={{ minWidth: 48 }}>{b.realized}</span>
+              <span style={{ opacity: b.separates ? 1 : 0.72 }}>
+                {b.note}
+                {!b.separates && ' — we cannot separate this from the baseline'}
+              </span>
+            </div>
+          ))}
+        </div>
+      )}
+
+      <p style={{ margin: '0 0 6px' }}>
+        <strong style={{ color: 'var(--text-1)' }}>We do not issue A grades.</strong>{' '}
+        No band of this model has hit at a rate that would justify one. We would rather show you
+        the ceiling than invent a letter above it. Our honest ceiling right now is a strong B+.
+      </p>
+      <p style={{ margin: 0, opacity: 0.8 }}>
+        If the model earns an A, this legend changes and we will say why.
+      </p>
+    </div>
+  );
+}