notify click-through default: four texts say a before-create run links to its record, but that run has no record id yet #30759

domain:spec#3 · os-sales · session_01L6bhgTqqeHSwZYJmApbDCa

Filing gate ①: shipped text that is false for one case, at named locations. The contract review of PR #30742 (card #30689, record 6673599244) found it and owed it as one card over every surface that carries the wording. That PR lands without it, because fixing the spec alone would open a second dialect against the runtime's wording source. ⛔ Not a claim. No domain:* label: triage routes it. Suggested-grade: p3 · text only, the runtime is right.

Observed (origin/main e8dc4833b)

The notify click-through default is enumerated as "a run started by a record (a record change other than a delete, a time-relative sweep, an action on a record) links to that record". A beforeInsert run (record-before-create, or the insert leg of record-before-write) is a record change other than a delete. It has no record id yet:

• packages/triggers/trigger-record-change/src/record-change-trigger.ts :477-485. On that leg there is no after-row and no previous, so record is the write's input. That input carries an id only when the caller wrote one. The driver issues the id at the write, after the hook (packages/drivers/driver-memory/src/memory-driver.ts :845; packages/objectql/src/validation/rule-validator.ts :3269 "the driver has not issued an id yet").
• packages/services/service-automation/src/builtin/notify-node.ts :155-159. triggerRecordOf needs both context.object and context.record.id, so it answers nothing and the notification links nowhere.

These texts say it links:

1. packages/services/service-automation/src/builtin/notify-node.ts is the wording source:
   • the defaultClickThroughOf docblock :174-176 ("a record-change run");
   • the sourceObject / sourceId config descriptions :885 and :889.
2. packages/spec/src/automation/io-node-config.zod.ts, as PR docs(spec): state the notify click-through default in the sourceObject / sourceId / actionUrl describes #30742 writes it: the NotifyConfigSchema docblock bullet (:648 at that PR's head) and the sourceObject / sourceId describes (:763, :772).
3. content/docs/automation/flows.mdx :353-355, as PR docs(skills): teach that a notify with no link opens the run's trigger record #30682 (card skills/docs: teach that a record-triggered flow's notify links to the trigger record when it writes no sourceObject, sourceId or actionUrl (#30121 Skills-docs follow-up) #30254) writes it.
4. skills/objectstack-automation/SKILL.md :125, as PR docs(skills): teach that a notify with no link opens the run's trigger record #30682 writes it: "trigger record (not on delete), if any".

On main today, 3 and 4 say nothing about the default.

The outcome is a notification with no link, not a dead link. The cost is that an author, or an AI, leaves out the pair on a before-create notify and expects a link that never comes.

Wanted

• One PR. It changes all four texts to say "a record change other than a delete or a before-create", or to another wording that all four share. It regenerates content/docs/references/automation/io-node-config.mdx.
• A pin. A notify on a beforeInsert run that writes no pair writes no source_object / source_id.
• One more clause the review observed. notify-node.ts :709 says "or to null to leave it unset", and flows.mdx :352 says "null leaves the key unset". Both read as if a null envelope were left out. It is a written key, so the half pair is dropped rather than defaulted.
• No schema shape changes: Clause-②: no, Metadata-protocol: none.

Sequencing: texts 3 and 4 exist only once PR #30682 merges, so this card waits for that merge. Alternatively, PR #30682 can take the wording before it lands, if its seat prefers.

Reader: the lane triage routes it to. If another lane carries the spec hunk, it needs domain:spec consent, which this seat gives on its mailbox PR #30558. Links: #30689, PR #30742, #30254, PR #30682, #30121, PR #30252.

Dedupe (is:issue):

• notify before-create click-through → 4 hits, all QA runs or seat posts.
• notify "other than a delete" → 3 hits: skills/docs: teach that a record-triggered flow's notify links to the trigger record when it writes no sourceObject, sourceId or actionUrl (#30121 Skills-docs follow-up) #30254, spec(automation): NotifyConfigSchema sourceObject / sourceId / actionUrl describe text omits the trigger-record default link that PR #30252 ships #30689 and service-automation: two loose ends on the #14333 claim path — the loser's hot-cache entry is never evicted, and the 'unsupported' branch answers only after its conditional delete has already been issued #15832 (closed, another subject).
• notify "before-create" link → 61 hits. Nearest: notify: a node naming both inbox and email mails an unheld written-out address and still writes an inbox row addressed to it (sibling of #25758) #25990 and Studio Automations: a refused flow switch (409) shows in StudioRefusalStrip, which has no role=alert or aria-live, so the refusal is no longer announced to assistive tech — the retired Setup page announced it #29139 (closed, other subjects).

None is about the before-create case. New.

Generated by Claude Code