@@ -0,0 +1,12 @@
+---
+'@objectstack/skills': patch
+---
+
+docs(skills): a `notify` node that writes no link opens the record that started the run
+
+Clause-②: no
+Metadata-protocol: none
+
+- **Before.** The `objectstack-automation` skill's `notify` example commented its click-through keys as "a PAIR, else dropped", so a record-triggered flow's notification looked like it linked nowhere unless the author wrote `sourceObject` + `sourceId: record.id`.
+- **Now.** The example says what the runtime does: a node that writes none of `sourceObject`, `sourceId` and `actionUrl` links to the run's trigger record when it has one (a record change other than a delete, a time-relative sweep's row, an action started on a record). An explicit pair or `actionUrl` wins; half a pair is still dropped; a run with no trigger record links nowhere. A new eval asks for a record-triggered notification that opens its record and expects no source keys written.
+- No schema, key or behaviour changes.
@@ -349,8 +349,14 @@ entry (`['{owners}']`), on as **one** recipient joined with commas (`'u1,u2'`),
 which reached nobody. Guard a recipient field that may be unset —
 `has(record.assignee) ? record.assignee : null` — so it is dropped rather than
 failing the run. `sourceId` takes a string or an envelope evaluating to one:
-`null` leaves the key unset, and a half-specified click-through pair is
-dropped, as before. The node's `sourceObject`, `actorId` and `payload` are
+`null` leaves the key unset. A node that writes none of `sourceObject`,
+`sourceId` and `actionUrl` links to the run's trigger record when it has one —
+a record change other than a delete, a time-relative sweep's row, an action
+started on a record — so a record-triggered `notify` opens its record without a
+pair. An explicit pair or `actionUrl` wins; a half-specified pair is dropped,
+never defaulted; a run with no trigger record (a schedule tick, an inbound API
+post, a manual start with no record) links nowhere.
+The node's `sourceObject`, `actorId` and `payload` are
 **literals**, read as written: no flow computed one, so nothing is evaluated
 there — write the value itself (`sourceObject: 'crm_case'`). A `{…}` token
 there is refused, since it would reach the messaging service with its braces,
 
@@ -45,7 +45,7 @@ A **Flow** is a directed graph of nodes — the primary automation building bloc
 | `screen` | Interactive — presents UI screens to the user (wizards, forms) |
 | `schedule` | Runs on a cron/interval cadence declared on the **start node's `config.schedule`** — or a **per-record date sweep** via `config.timeRelative`, see *Time-relative triggers* |
 | `record_change` | Fires automatically on record create/update/delete. `autolaunched` + the same `record-*` binding behaves identically; `record_change` also opts into the trigger-readiness lint |
-| `api` | Inbound **webhook** — needs a start-node `secretRef` (or a literal `secret`; see *Inbound webhook triggers* below); a flow only ever started explicitly is `autolaunched` |
+| `api` | Inbound **webhook** — needs a start-node `secretRef` (see *Inbound webhook triggers* below); a flow only ever started explicitly is `autolaunched` |
 
 **A flow an installed package ships** is read-only. To change what it does, save
 a same-named flow in the base's paired `.custom` package declaring
@@ -121,9 +121,9 @@ error. **RAW** keys are read as written: a
     topic: 'task',                     // RAW; default 'notify'
     severity: 'warning',               // RAW; CLOSED enum info|warning|critical
     channels: ['inbox'],               // RAW; default inbox
-    sourceObject: 'task',              // click-through: a PAIR, else dropped
-    sourceId: { dialect: 'cel', source: 'record.id' }, // (a value slot)
-    actionUrl: '/tasks/{{ record.id }}', // text slot; overrides the synthesized link
+    sourceObject: 'task',              // link: PAIR, else dropped; none of the 3 ⇒ the
+    sourceId: { dialect: 'cel', source: 'record.id' }, // trigger record (not on delete), if any
+    actionUrl: '/tasks/{{ record.id }}', // overrides the pair
 } }
 ```
 
 
@@ -242,6 +242,24 @@
           "beforeUpdate"
         ]
       }
+    },
+    {
+      "id": 14,
+      "prompt": "When a `crm_case`'s `priority` becomes `urgent`, send its owner an inbox notification; clicking the notification should open that case.",
+      "expected_output": "A `record_change` flow bound on the `start` node `config` (`objectName: 'crm_case'`, `triggerType: 'record-after-update'`, condition `previous.priority != 'urgent' && record.priority == 'urgent'`) and a `notify` node with `recipients: { dialect: 'cel', source: 'record.owner_id' }`, an inline `title`, `channels: ['inbox']`, and no `sourceObject` / `sourceId` / `actionUrl`: a notify that writes none of the three links to the run's trigger record, here the case. An explicit pair or `actionUrl` is only for linking elsewhere and wins when written; half a pair is dropped, never defaulted; a run with no trigger record (a schedule tick) links nowhere. `requires` lists `automation`, `triggers`, `messaging`.",
+      "files": [],
+      "assertions": {
+        "must_contain": [
+          "record-after-update",
+          "notify",
+          "recipients",
+          "trigger record"
+        ],
+        "must_not_contain": [
+          "sourceObject:",
+          "actionUrl:"
+        ]
+      }
     }
   ]
 }
Original file line number	Diff line number	Diff line change
`@@ -242,6 +242,24 @@`
`242`	`242`	`"beforeUpdate"`
`243`	`243`	`]`
`244`	`244`	`}`
	`245`	`+ },`
	`246`	`+ {`
	`247`	`+ "id": 14,`
	`248`	+ "prompt": "When a `crm_case`'s `priority` becomes `urgent`, send its owner an inbox notification; clicking the notification should open that case.",
	`249`	+ "expected_output": "A `record_change` flow bound on the `start` node `config` (`objectName: 'crm_case'`, `triggerType: 'record-after-update'`, condition `previous.priority != 'urgent' && record.priority == 'urgent'`) and a `notify` node with `recipients: { dialect: 'cel', source: 'record.owner_id' }`, an inline `title`, `channels: ['inbox']`, and no `sourceObject` / `sourceId` / `actionUrl`: a notify that writes none of the three links to the run's trigger record, here the case. An explicit pair or `actionUrl` is only for linking elsewhere and wins when written; half a pair is dropped, never defaulted; a run with no trigger record (a schedule tick) links nowhere. `requires` lists `automation`, `triggers`, `messaging`.",
	`250`	`+ "files": [],`
	`251`	`+ "assertions": {`
	`252`	`+ "must_contain": [`
	`253`	`+ "record-after-update",`
	`254`	`+ "notify",`
	`255`	`+ "recipients",`
	`256`	`+ "trigger record"`
	`257`	`+ ],`
	`258`	`+ "must_not_contain": [`
	`259`	`+ "sourceObject:",`
	`260`	`+ "actionUrl:"`
	`261`	`+ ]`
	`262`	`+ }`
`245`	`263`	`}`
`246`	`264`	`]`
`247`	`265`	`}`