docs(spec): record #16577 as ruled, not pending, in the calendar carriers

The three in-tree carriers this PR added deferred the calendar route's
severity to #16577 as an open question. It is not open: #16577 ruled B
on 2026-09-11 (comment 5634033966, card closed completed) and fixed the
route at warning-class under ADR-0078 §1 -- reasoning from exactly the
premise this PR re-measures, that both doors are loud (the os validate
warning, and ObjectCalendar's reachable refusal screen after objectui
deleted the start_date / end_date floors).

So the corrected row is not a change whose severity consequence is
deferred; it is the evidence the standing ruling already rests on. The
changeset ships into packages/spec/CHANGELOG.md, which is where the
previous stale claim survived, so a second stale claim there would
reproduce the defect this PR exists to correct.

Also adds one clause to the calendar row: the quoted refusal literal is
the text rendered AT THE PIN. objectui#10101 landed after the pin and
moved it into a tt('calendar.configRequired', ...) default, so a
non-English locale on objectui's head renders other words. Harmless for
the console this repo ships, and the asserting pin citation below it is
what reds at the next bump.

Prose only: no schema, no severity, no behaviour, no new assertion.

Claude-Session: https://claude.ai/code/session_01UDXER3sdqfeVYpEWZs5mZx
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/17445-view-binding-calendar-fallback-corrected.md

@@ -12,7 +12,7 @@ Two carriers asserted the same deleted behaviour: `VIEW_BINDING_BLOCKS`' calenda
 So the old body was wrong twice — there is no fallback to literal field names, and the failure is not silent. What it was right about is the remedy, and that is the half the new body keeps: it names `calendar.startDateField`, `CalendarConfigSchema`'s one required key, and records that the event title resolves through the ADR-0079 display-name chain when `titleField` is omitted. The `fix` hint is unchanged.
 
 - **The message is now per type.** `VIEW_BINDING_MESSAGE` carries an entry for a type whose measured outcome is not the generic literal-fallback sentence; the other five types receive the generic body unchanged. A type that stops flooring gets an entry, never a reworded universal — the two carriers drifted apart once, and the map is what makes correcting both one edit.
-- **No severity moves.** Whether a renderer that refuses BY NAME still deserves WARNING under ADR-0078 §1 is #16577's question; correcting false prose does not answer it, and nothing here pre-empts it.
+- **No severity moves — the severity is already ruled.** #16577 ruled **B** on 2026-09-11 (comment `5634033966`, card closed `completed`): the `type: 'calendar'` route stays warning-class under ADR-0078 §1, and it stays there *because* both doors are loud — loud at `os validate` (this warning) and loud at render (objectui#7029 deleted the `start_date` / `end_date` floors; `getCalendarConfig` returns `null` and the named refusal screen is reachable). That is exactly the premise re-measured here, so the corrected row is the evidence the standing ruling rests on, not a change whose severity consequence is pending.
 - ⚠️ **The same reading found three sibling rows stale, and they are recorded rather than corrected** — out of this card's scope, and each changes what its row's severity rests on: `gantt`'s four floors are gone (objectui#7070, objectui#7499) and `ObjectGantt` refuses; `timeline`'s `created_at` floor is gone (objectui#7070) while its `titleField || 'name'` stands; `map`'s `locationField || 'location'` is gone on both faces (objectui#8169). The table now carries that re-measurement note so the three are not reused as current fact, and `kanban` / `tree` were re-read at the same ref and still say what they say.
 
 No schema moved, no export moved and no accept set moved: this corrects prose and one warning string. `Clause-②: no`

packages/spec/src/kernel/functional-completeness.test.ts

@@ -176,9 +176,13 @@ describe('checkViewCompleteness — layout bindings', () => {
     // reporting that something is missing.
     expect(f.message).toContain('calendar.startDateField');
     expect(f.fix).toContain('startDateField');
-    // Severity is deliberately untouched here. Whether a renderer that
-    // refuses BY NAME still deserves WARNING under ADR-0078 §1 is #16577's
-    // question; correcting false prose does not answer it.
+    // Severity is untouched because it is already RULED, not because the
+    // question is open: #16577 ruled B (comment `5634033966`, card closed
+    // `completed` 2026-09-11) — a `calendar` route that refuses BY NAME
+    // stays warning-class under ADR-0078 §1, on the reasoning that BOTH
+    // doors are loud, `os validate` and render. That is the reading the
+    // assertions above re-measure, so this pin carries the ruling's
+    // evidence rather than standing in for a pending one.
     expect(f.severity).toBe('warning');
   });
 

packages/spec/src/kernel/functional-completeness.ts

@@ -227,10 +227,18 @@ export function checkFieldCompleteness(def: unknown): CompletenessFinding[] {
  *
  * Either way the author asked for a surface that does not render, while
  * authoring reports success: WARNING, not error (ADR-0078 §1). ⚠️ The
- * rubric's other half — refuse what renders NOTHING — is what [#16577] is
- * asking of this route now that some of these renderers answer with a
- * refusal. This table records what was measured and deliberately does not
- * pre-empt that ruling: nothing here moves a severity.
+ * rubric's other half — refuse what renders NOTHING — was put to [#16577]
+ * for the `type: 'calendar'` route and is SETTLED, not pending: ruled B
+ * (director seat, comment `5634033966`; the card closed `completed` on
+ * 2026-09-11), the route STAYS warning-class and is carried at `warning` by
+ * the table below. The ruling turns on BOTH doors being loud — loud at
+ * `os validate` (this warning) and loud at render (objectui#7029 deleted the
+ * `'start_date'` / `'end_date'` floors; `ObjectCalendar.getCalendarConfig`
+ * returns `null` and the named refusal screen is reachable) — which is
+ * exactly what the `calendar` row below now measures. So this table moves no
+ * severity because the severity is already RULED, and the corrected row is
+ * the evidence that ruling rests on. ⛔ Reopening it takes a new ruling,
+ * not a re-read; a row going stale is a reason to re-measure the ROW.
  *
  * Every entry names its measured renderer binding. The verify-then-enforce
  * gate this table sits behind (the audit's Tier-A had named only the first
@@ -256,7 +264,12 @@ export function checkFieldCompleteness(def: unknown): CompletenessFinding[] {
  *   flat `startDateField`, and the `if (!calendarConfig)` arm renders the
  *   "Calendar configuration required" refusal screen, which names
  *   `startDateField` as the key to declare (objectui#8170 corrected that
- *   screen's second clause: `titleField` is NOT required). So the loss is
+ *   screen's second clause: `titleField` is NOT required). ⚠️ That literal
+ *   is the text RENDERED at the pin: objectui#10101 landed AFTER the pin and
+ *   moved it into a `tt('calendar.configRequired', …)` default, so on
+ *   objectui's head a non-English locale renders other words for the same
+ *   screen. Harmless for the console this repo ships — and the pin citation
+ *   below is what reds when the pin moves past it. So the loss is
  *   total rather than partial — every record, on every object — and the
  *   author is told at render time as well as here. Both reads are identical
  *   at the pin this repo builds against (`.objectui-sha` = `87af769e9`), so