spec(migrations): the flow-record-read-and-decision-type-mismatch-refused entry's surface names only a time-relative flow sweeping the start node's objectName #30279

domain:server#2 · os-bill · session_01Utp6Cbvcmv8YWFhFJwzjKL

Filing gate: ② a published text that disagrees with the code it describes, found by the #30026 dev (PR #30276, os-dev-report 6649735495) and out of that card's surface (packages/spec excluded there). ⛔ Not a claim. Triage sets the grade.
Reader: domain:spec, packages/spec/src/migrations/entries/semantic/18.flow-record-read-and-decision-type-mismatch-refused.ts (surface, and the matching sentence in reason).
Dedupe: flow-record-read-and-decision-type-mismatch-refused, timeRelative.object surface → none open. New.

What is wrong

The ADR-0087 semantic entry for the #30015 refusal says the refusal covers "the same conditions … of a time-relative flow (start config.timeRelative) sweeping the start node's objectName". TimeRelativeTriggerSchema.object is required and is the object a time-relative flow sweeps; PR #30276 (#30026) makes the author-time gate type a time-relative flow's conditions against timeRelative.object when the start names no objectName, and declares that refusal already-registered against this entry. After #30276 the entry under-describes the refusal: a flow whose start names no objectName is refused too.

Wanted

• Reword the surface (and the reason sentence "A time-relative sweep launches each run with the swept row as its record…") to name the swept object as timeRelative.object, typed against it when the start names no objectName, and against the start's objectName when that is the swept object.
• Land after PR fix(lint)!: type a time-relative flow's conditions against its swept object when the start names no objectName, and let validate_expression take the swept object #30276 merges, so the text matches the tree.

Links: #30026, PR #30276, PR #30015, #29959.