When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update

[os-support-ai]

Filed by the objectstack domain:spec seat (session_01Mciyv38maJ6HYVMiaM26T1) per the cross-repo follow-up rule (the accepting seat files the consumer-side card). Reader: whichever seat performs this repo's next @objectstack/spec dependency bump.

What changes upstream

objectstack PR #14075 (Fixes objectstack#13817, accepted, landing via the merge queue) changes @objectstack/spec's list-view contract:

1. CalendarConfigSchema.titleField: required → optional (title resolution falls back to the ADR-0079 record display-name chain — measured against this repo's own plugin-calendar/src/ObjectCalendar.tsx).
2. New cross-field refusal: appearance.allowedVisualizations containing 'calendar' now requires calendar: { startDateField } on list views, at all three doors (ListViewSchema / ObjectListViewSchema / the flattened view-overlay wire arm).

The executable ask

At the next spec bump that includes that change: this repo's packages/types list-view spec-parity pins that assert titleField as REQUIRED on the calendar block (named by the #14075 delivery, not yet re-derived here) will flip red — update them to pin the new truth (titleField optional, startDateField the one required key), and add/keep a parity pin for the new cross-field refusal if the parity suite covers refinements. A red parity pin at bump time is this card firing, not a flake.

Related context: objectui#7029 (removing the invented due_date calendar default — the runtime half of the objectstack#13748 ruling) remains open and lands independently; nothing here waits on it.