[objectstack-fleet]

Requested by Sales · project thread

Fixes #30689

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么：notify 节点 sourceObject / sourceId / actionUrl 三个字段的 spec 说明文字（及其注释、生成的参考文档页），补上"三者都不写时，通知自动链接到触发本次运行的记录"这条默认行为及其例外。
• 为什么改：运行时早已默认链接到触发记录，但 spec 文档只说"成对生效、缺一半会被丢弃"，元数据作者和 AI 读到的说明与实际行为不一致。
• 风险与回滚：只改说明文字，不改任何键、结构、默认值或校验；回滚即 revert 本 PR，无数据或行为影响。
• 先看：packages/spec/src/automation/io-node-config.zod.ts 的三个 .describe() 与 NotifyConfigSchema 文档块；其次 content/docs/references/automation/io-node-config.mdx 的生成差异。
• 两分钟验证：pnpm --filter @objectstack/spec check:generated，预期输出 "All 14 generated artifacts are up to date"。
• 需要你做的：无，席位落地。

What changes

• packages/spec/src/automation/io-node-config.zod.ts
  • sourceObject and sourceId .describe(): keep the pair rule (a half-written pair is dropped, now "not defaulted"), and add the default: when sourceObject, sourceId and actionUrl are all left out, 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 run with no trigger record links nowhere, and an explicit pair or an actionUrl is kept as written.
  • actionUrl .describe(): adds "written alone keeps the notification from linking to the record that started the run". This is the runtime's own sentence from notify-node.ts.
  • The JSDoc of the three keys, and a new "Click-through default" bullet in the NotifyConfigSchema docblock that names every exception the executor applies: delete events, runs with no trigger record, an explicit pair or actionUrl, a half pair.
• content/docs/references/automation/io-node-config.mdx: regenerated by gen:docs, not edited by hand.
• .changeset/30689-notify-click-through-default-describe.md: @objectstack/spec patch.

No key, shape, default, refinement or export changes. Nothing outside packages/spec/** changes, apart from the generated page and the changeset.

The claims, checked against the runtime on origin/main ab44ec94b (packages/services/service-automation/src/builtin/notify-node.ts, read only):

• triggerRecordOf returns a trigger record only when the run context has both object and record.id.
• defaultClickThroughOf returns nothing when any of the three keys is written, and nothing for beforeDelete / afterDelete.
• The executor uses the explicit pair only when both halves resolve, and otherwise falls back to defaultClickThroughOf. So a half pair is dropped and is not defaulted.
• Which runs carry object + record:
  • record change: yes, through trigger-record-change;
  • time-relative sweep: yes (time-relative-trigger.ts, event: 'time_relative');
  • action on a record: yes (action-execution.ts, which passes record and object).
• Which runs do not:
  • inbound API post: trigger-api passes record: payload and no object;
  • manual REST start: buildAutomationContext sets object and no record;
  • schedule tick: neither.
• The six tests in notify-node.test.ts under "notify click-through defaults to the trigger record" pin each case.

Tests

All readings below are on head 5c4599568 (git rev-parse --short HEAD), worktree off base ab44ec94b. Exit codes were captured before any pipe.

• pnpm --filter @objectstack/spec build under the verify lock: VERDICT command-exit 0.
• pnpm --filter @objectstack/spec check:generated:
  • before regenerating: exit 1, content/docs/references/** stale;
  • after gen:docs: exit 0, All 14 generated artifacts are up to date.
• The nine @objectstack/spec test files that import or cover io-node-config, under the lock: Test Files 9 passed (9), Tests 628 passed (628). They include io-node-config.test.ts, whose /dropped at execute time/i pin still holds.
• pnpm --filter @objectstack/spec typecheck (tsc, scripts typecheck, test typecheck): exit 0.
• npx eslint --no-inline-config packages/spec/src/automation/io-node-config.zod.ts: exit 0.
• node scripts/check-changeset-no-major.mjs --base ab44ec94b --event with an offline PR event that carries this body's two declaration lines: exit 0. Its verdict: "LEVEL AXIS: this PR declares clause-② no and metadata-protocol none … a non-protocol change at patch".
• node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack: 96 commands, and every one ran.
  • Five first exited 3 (PREREQUISITE NOT MET: unbuilt lint, formula, client-react and objectql dists). A sixth also exited 3 because it needs the full workspace build. After turbo run build of those closures, and then the full build, all six re-ran at exit 0.
  • --ran reconciliation: 96 derived, 96 run, 0 NOT-MEASURED, 0 UNRUN.
• Local-only gates: pnpm check:dev-prereqs exit 0, pnpm check:skill-frame-freshness exit 0, node scripts/check-nul-bytes.mjs exit 0.
• No ablation: this diff changes no tested behaviour, only describe text and docs.

Acceptance notes

• Pair note in NOTIFY_KEY_GUIDANCE.source (≈:137) is left as it is, on purpose. It says "the pair only takes effect together: a half-specified target is dropped". That is still true under the default. It speaks to an author who is moving a nested source: { object, id } onto the flat pair, so it is about a pair that is written, and the default never applies to such a pair. Nothing in it became false or incomplete for that reader.
• Skill wording: skills/objectstack-automation/SKILL.md:124 comments the example as click-through: a PAIR, else dropped. That is still true, and it is not the old "only takes effect together" sentence. It does not mention the trigger-record default. Not edited here, because skills/** is outside this card's surface.
• Hand-written docs: content/docs/automation/flows.mdx:352 says "a half-specified click-through pair is dropped, as before". That is still true, and the page does not mention the default either. Not edited here: it is outside this card's surface.
• Not merged with origin/main. The branch is 6 commits behind 447226b22. Those commits touch packages/spec/src/system/i18n-resolver* and platform-locales* plus five unrelated changesets, and none of them touches this diff's files. The dispatch-gates derivation says none of them touched what its answer derives from.

---

Generated by Claude Code

🤖 Generated with Claude Code

https://claude.ai/code/session_01L6bhgTqqeHSwZYJmApbDCa

[github-actions]

📓 Docs Drift Check

1 anchor(s) derived from 1 changed package(s); no hand-written page names any of them, so this run has nothing to list — not a clean bill of health. This check sees only pages that NAME a derived anchor: one that documents this change in prose, or enumerates it in an authoring dialect, names none and stays invisible to it on every run.

What this run could not see

• the SDK route bridge reached 63 of 221 client-bound route-ledger rows — the other 158 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 158: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 103 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 170 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 447226b222467709ed74ca99eaf808c178656b33 → packageMentionDocs.

Which tree this was computed on

This run read content/docs from 7dab66c728dfd6f048fe17efe439fbcf3f414c95 — the merge of head 5c45995686283d9a7bbc1335b985276c5c7b265d into base 447226b222467709ed74ca99eaf808c178656b33, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin 7dab66c728dfd6f048fe17efe439fbcf3f414c95 && git checkout 7dab66c728dfd6f048fe17efe439fbcf3f414c95
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin 447226b222467709ed74ca99eaf808c178656b33 5c45995686283d9a7bbc1335b985276c5c7b265d && git checkout -B drift-repro 447226b222467709ed74ca99eaf808c178656b33 && git merge --no-ff 5c45995686283d9a7bbc1335b985276c5c7b265d

node scripts/docs-audit/affected-docs.mjs --json 447226b222467709ed74ca99eaf808c178656b33

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

[objectstack-fleet]

domain:spec#3 · os-sales · session_01L6bhgTqqeHSwZYJmApbDCa

Contract-review-claim: session_01L6bhgTqqeHSwZYJmApbDCa · head 5c45995 · 2026-11-06T00:22Z

Full review at CONTRACT_REVIEW_TIER (published schema face: automation/io-node-config.zod.ts; JSDoc and .describe() text only), run by an isolated at-tier subagent of this seat.

---

Generated by Claude Code

[objectstack-fleet]

domain:spec#3 · os-sales · session_01L6bhgTqqeHSwZYJmApbDCa

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 5c45995686283d9a7bbc1335b985276c5c7b265d
Local-runs: none
Scope: packages/spec/src/automation/io-node-config.zod.ts (hits) + cited, all read on origin/main 82142ed65 (merge base ab44ec94b; none of the 7 commits between touches a cited file): packages/services/service-automation/src/builtin/notify-node.ts, notify-node.test.ts, builtin/template.ts, packages/triggers/trigger-record-change/src/record-change-trigger.ts, packages/triggers/trigger-schedule/src/time-relative-trigger.ts, schedule-trigger.ts, packages/triggers/trigger-api/src/api-trigger.ts, packages/runtime/src/domains/automation.ts, packages/runtime/src/action-execution.ts, packages/objectql/src/validation/rule-validator.ts, packages/drivers/driver-memory/src/memory-driver.ts, skills/objectstack-automation/SKILL.md, content/docs/automation/flows.mdx, and PR #30682's head d9415882 for the last two. The regenerated content/docs/references/automation/io-node-config.mdx and .changeset/30689-notify-click-through-default-describe.md are the lane seat's ACCEPT at TIER_DEFAULT.

① Derived judgments

• Accept set: unchanged. The hunk touches four JSDoc blocks (the NotifyConfigSchema docblock bullet at :646-655, the three key comments at :755-760, :764-769, :776-781) and three .describe() strings (:763, :772, :784). The strictObject key set, every .optional(), NotifySourceIdSlotSchema, notifyLiteralStringSchema, the superRefine (:800-890) and NOTIFY_KEY_GUIDANCE are byte-identical to main. No key, shape, default, refinement or export moves. Clause-②: no is right.
• Public surface: none. No export added, removed or renamed; check:api-surface and check:authorable-surface have nothing to see. Only check:docs is owed, and the diff carries its regenerate: the three io-node-config.mdx rows (:106, :107, :109) hold the three describes byte-for-byte.
• io-node-config.test.ts's /dropped at execute time/i pin still matches ("dropped at execute time, not defaulted").
• Tier: a published schema file under packages/spec/src/** ⇒ CONTRACT_REVIEW_TIER, this record. No governed path (Governed Surface Queue Guard: success). Head repo is the base repo, not a fork; 50 changed lines; draft; author objectstack-fleet[bot].

② Semver level

'@objectstack/spec': patch with Clause-②: no and Metadata-protocol: none is what the diff publishes. The classifier's semantic is "the meaning or default of an authorable key changes" (scripts/check-changeset-no-major.mjs :2191). The default moved in PR #30252 (merged 2026-11-05, Metadata-protocol: semantic there, on @objectstack/service-automation); this diff moves nothing, it describes what already ships, so none and patch follow by the rule and check-changeset-no-major agrees (Check Changeset: success). Both declaration lines are line-initial in the changeset and the PR body; no skip-changeset. Same classification record 6671186834 reached for the sibling skills PR #30682.

③ Boundary flags

• No merge of origin/main: accepted. Seven commits sit between the merge base ab44ec94b and origin/main 82142ed65 (fix(spec/system): read the script-subtag Chinese spellings (zh-Hant-TW, zh-Hans-CN, …) as platform locale read aliases #30681, fix(metadata-protocol, runtime)!: refuse navigationContributions on a package created at runtime #30707, fix(spec): resolveBundleLocale and pickData answer only a bundle's own locale keys #30678, fix(metadata-protocol,cli,cloud-connection)!: refuse an object extension that re-declares an owner's field beyond its display properties (ADR-0146 D10) #30712, fix(app-shell): word the flow closure refusal on the Problems list in the Console's language #30721, test(plugin-gantt): fold seven ObjectGantt fetch and row pins onto one shared harness #30725, fix(metadata-protocol,rest,runtime): serve the pending draft as the /layers draft layer, untranslated and ungoverned #30713); git diff --stat over the diff's three paths, notify-node.ts, SKILL.md and flows.mdx is empty. The dev counted six behind 447226b22; fix(metadata-protocol,rest,runtime): serve the pending draft as the /layers draft layer, untranslated and ungoverned #30713 landed since and touches metadata-protocol, rest and runtime only.
• NOTIFY_KEY_GUIDANCE.source pair note (:137-138) left unchanged: accepted. Its reader is an author lifting the retired nested source: { object, id } onto a written pair, and the default never applies once either half is written (notify-node.ts :185), so the note is true and complete for that reader.
• skills/objectstack-automation/SKILL.md :124 ("click-through: a PAIR, else dropped") and content/docs/automation/flows.mdx :352 ("a half-specified click-through pair is dropped, as before") on main: both silent on the default, neither false. The silence does not mislead into a broken link: an author or an AI following them writes a pair, which the runtime keeps as written (test "keeps an explicit pair over the trigger record"); the cost is an unneeded pair, not a dead or missing link. Neither this PR nor a new card should carry them, because 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 items 1 and 2; open, draft, head d9415882, PASS record 6671186834, Tier H awaiting the approver) already does: its SKILL.md :124-126 and flows.mdx :352-358 state the default with the same three exceptions. The dev's report wrote carrier: none for both; the carrier is PR docs(skills): teach that a notify with no link opens the run's trigger record #30682.
• open_questions: none. Security findings: none. No skills/** or packages/services/** edit, as the claim's surface required.
• Check-runs on 5c45995686283d9a7bbc1335b985276c5c7b265d, read at 2026-11-06T00:50Z after every one completed (polled every 3 minutes from the claim; converged at 2026-11-06T00:49Z): 65 runs, 57 success, 8 skipped (opt-in and paths-filtered jobs: 18.x upgrade harness, Dogfood shards and Verify CLI, Lint UI, Packed-tarball smoke, Schedule gate, Temporal Conformance, UI Published Artifacts), 0 failure, 0 pending. The gate-carrying contexts Lint & Repo Gates, TypeScript Type Check (which runs check:docs over the regenerated page), Test Core, Build Core, Governed Surface Queue Guard, Type Check UI, Test UI, Build & E2E UI and Live E2E UI are all success.

④ Design judgment

packages/spec/src/automation/io-node-config.zod.ts, every new sentence against the runtime on main:

• "a node that writes none of sourceObject, sourceId and actionUrl links to the run's trigger record, when the run has one": TRUE. defaultClickThroughOf (notify-node.ts :180-188) answers nothing when any of the three is != null on the parsed config (:185), nothing on beforeDelete / afterDelete (:162, :186), else the trigger record; triggerRecordOf (:155-159) needs both context.object and context.record.id. The executor takes the explicit pair only when both halves resolve, else the default (:1022-1024). Pinned by notify-node.test.ts :401-477, six cases.
• Which runs have a trigger record, read at the doors:
  • record change: record-change-trigger.ts :477-485 builds record from previous ⊕ input.data ⊕ the after-row, :586-589 hands record, object, event: binding.event. afterInsert / afterUpdate carry the id on the after-row, beforeUpdate on previous; a delete carries it on previous and is excluded at :186. Has one (with the beforeInsert exception below).
  • time-relative sweep: time-relative-trigger.ts :714-717, record is the swept row, object: desc.object, event: 'time_relative'. Has one.
  • action on a record: action-execution.ts :2698-2709, record is the subject row with the requested id stamped even when the caller-scope load was refused (:3636), object: objectName unless the action key is object-less; no event, so never a delete. Has one.
  • inbound API post: api-trigger.ts :406-412, record: payload, no object. None, whatever the payload carries.
  • manual REST start: buildAutomationContext (automation.ts :146-227) sets object and event: 'manual' and puts recordId under params only; no record. None, so the docblock's "a manual start with no record" is the whole class, not a sub-case.
  • schedule tick: schedule-trigger.ts :845-846, event: 'schedule' and params; no record, no object. None.
• "an explicit pair or actionUrl is kept as written": TRUE. A pair that resolves wins at :1022-1023; actionUrl rides payload.url (:1157) and the messaging service lets it override the synthesized link. Does actionUrl alone suppress the default? Yes: :185 judges the parsed key, pinned by "keeps an explicit actionUrl alone". That holds for an actionUrl that renders to no text too: renderTextSlot (template.ts :131-145) returns undefined for an empty render, the key is still != null at :185, so the notification carries no url and no source, which is exactly "written alone keeps the notification from linking to the record that started the run".
• "a half pair is dropped, not defaulted": TRUE. Either half written makes :185 answer nothing, and :1022 builds no pair, so source is undefined: a half pair plus no actionUrl links nowhere, never defaults. Pinned by "still drops a half-written pair". A sourceId CEL envelope that evaluates to null or blank is the same case: resolveStringSlot (:696-711) answers ok with no value, the written envelope is != null at :185, so the pair fails and nothing is defaulted. The describe's discriminator is "left out", which is the right word; an envelope that evaluates to nothing is written, not left out.
• "a run with no trigger record links nowhere": TRUE by :187 returning trigger, pinned by "links nowhere on a run with no trigger record".
• Docblock bullet (:646-655) against the describes: the same four rules; the bullet adds the delete reason and names defaultClickThroughOf as the owner, and says the schema shape is unchanged, which ① confirms. They agree.
• Sentences left in place: the pair bullet at :642-645 and the :137 note stay true beside the new bullet; the actionUrl describe's pre-existing "Overrides the link synthesized from sourceObject/sourceId" stays as it was (an actionUrl rendering to no text does not override a resolved pair, notify-node.ts :994-998, but that is the old sentence, not a new claim). No contradiction.
• Breaking the enumeration — should-fix, io-node-config.zod.ts :763 and :772 ("a record change other than a delete"), :648 ("a record change other than a delete"): a beforeInsert run (record-before-create, or the insert leg of record-before-write) is a record change other than a delete whose row has no id yet. record-change-trigger.ts :477-485 has no after-row and no previous on that leg, input.data carries an id only when the caller wrote one, and the driver issues the id at the write (memory-driver.ts :845, rule-validator.ts :3269 "the driver has not issued an id yet"), after the hook. triggerRecordOf answers nothing, so that notify links nowhere, while the sentence says it links to the record. The precise rule in the same sentence ("a run with no trigger record links nowhere") and the docblock's "when the run has one" are right, the outcome is a notification with no link rather than a dead one, and the wording is the runtime's own at notify-node.ts :174-176, :885 and :889, which card spec(automation): NotifyConfigSchema sourceObject / sourceId / actionUrl describe text omits the trigger-record default link that PR #30252 ships #30689 ordered reused, and PR docs(skills): teach that a notify with no link opens the run's trigger record #30682's flows.mdx :353-355 repeats it. Not a must-fix: correcting the spec alone would open a dialect against the wording source. Owed as one card over all four surfaces (notify-node.ts docblock and descriptions, these describes and the docblock, flows.mdx, SKILL.md): "a record change other than a delete or a before-create". The seat files it; this PR need not wait.
• Observation, no finding on the hits file: the runtime's refusal text at notify-node.ts :706-707 ("or to null to leave it unset") and flows.mdx :352 ("null leaves the key unset", kept at PR docs(skills): teach that a notify with no link opens the run's trigger record #30682's head) now read as if a null envelope were "left out"; it is written, so it drops rather than defaults. The same card can carry one clause for it.
• must-fix: none. should-fix: one, above.

Implemented-by: claude/issue-30689-notify-default-link
Reviewed-by: session_01L6bhgTqqeHSwZYJmApbDCa

VERDICT: PASS

---

Generated by Claude Code

[objectstack-fleet]

domain:spec#3 · os-sales · session_01L6bhgTqqeHSwZYJmApbDCa

维护者速读

• 改了什么：notify 节点 sourceObject / sourceId / actionUrl 三个字段的 spec 说明文字（及其注释、生成的参考文档页），补上"三者都不写时，通知自动链接到触发本次运行的记录"这条默认行为及其例外。
• 为什么改：运行时早已默认链接到触发记录，但 spec 文档只说"成对生效、缺一半会被丢弃"，元数据作者和 AI 读到的说明与实际行为不一致。
• 风险与回滚：只改说明文字，不改任何键、结构、默认值或校验；回滚即 revert 本 PR，无数据或行为影响。
• 先看：packages/spec/src/automation/io-node-config.zod.ts 的三个 .describe() 与 NotifyConfigSchema 文档块；其次 content/docs/references/automation/io-node-config.mdx 的生成差异。
• 两分钟验证：pnpm --filter @objectstack/spec check:generated，预期输出 "All 14 generated artifacts are up to date"。
• 需要你做的：无，席位落地。

席位意见：契约复审一轮 PASS，没有必须改的项。它提了一条建议项：例外清单"除删除外的记录变更"漏了"创建前"（beforeInsert）这一种。那次运行还没有记录 id，所以通知不带链接。运行时 notify-node.ts 的原文本也是这么写的，本卡要求复用那段原文。只改 spec 会和运行时的原文分成两种说法。所以按复审建议，席位另立一张卡 #30759，覆盖全部四处文本，本 PR 不等它。

席位核对 — ACCEPT · domain:spec#3 · head 5c45995686283d9a7bbc1335b985276c5c7b265d

• Shape:
  • 3 files (+39 −11), draft, base main, first card reference Fixes #30689.
  • Two commits, r0 only: the describes, then the regenerate. No merge of origin/main, nothing rebased.
  • Hand-written, in packages/spec/src/automation/io-node-config.zod.ts:
    • the sourceObject / sourceId / actionUrl .describe() texts;
    • their JSDoc;
    • a new "Click-through default" bullet in the NotifyConfigSchema docblock.
  • Also hand-written: the changeset. Regenerated: content/docs/references/automation/io-node-config.mdx.
  • No key, shape, default, refinement, export or runtime change.
• Premise measured: on main, the three describes said only "takes effect together; a half-specified target is dropped". PR feat(service-automation): a record-triggered flow's notification links to the record that started the run when it names no link #30252 (Flow notify: a record-triggered flow's notification links nowhere unless the author adds the source pair #30121) made the runtime link a notify that writes none of the three keys to the run's trigger record. In notify-node.ts:
  • triggerRecordOf :155-159 is that lookup;
  • defaultClickThroughOf :180-188 applies the exceptions (:185 any key written, :186 delete events);
  • the node's own config descriptions :885 and :889 already said so.
• Gates:
  • CI on this head: 65 runs over 65 names; 57 success, 8 skipped, 0 red. check-expected-skips was not run, because no checkout here has node_modules (it imports yaml). I compared the 8 skipped names instead. Each one is in the skip set that check-expected-skips passed today on PR docs(spec): push vendor docblocks read ADR-0012 §6.1, not alternate channel plugins #30631. Check Changeset is green, and so is the Governed Surface Queue Guard.
  • Dev report 6673117469, on 5c4599568:
    • 96 derived gate families, 96 run, 0 NOT-MEASURED, after a full build;
    • the nine io-node-config spec test files: 628 tests passed;
    • typecheck exit 0;
    • check:generated: stale before gen:docs, up to date after;
    • eslint --no-inline-config exit 0;
    • check-changeset-no-major exit 0 at patch.
  • Merge: git merge-tree against main e8dc4833b merges clean. The commits since the merge base touch none of the diff's paths. The review read the stat of the diff's paths plus notify-node.ts, SKILL.md and flows.mdx up to 82142ed65, and it was empty.
  • No ablation, because no behaviour changed. No dogfood battery: no ! and no (narrowing) arm.
• Contract review: 6673599244 on 5c4599568: PASS, Served-tier: CONTRACT_REVIEW_TIER, no must-fix.
  • Every enumerated claim is true against the runtime, except one should-fix: "a record change other than a delete" (:648, :763, :772) also covers a beforeInsert run, which has no record id yet.
    • On that leg, record-change-trigger.ts :477-485 has no after-row and no previous.
    • The driver issues the id at the write, after the hook.
    • So triggerRecordOf answers nothing and the notification links nowhere.
  • It was not made a must-fix, because the wording is the runtime's own (notify-node.ts :174-176, :885, :889), and card spec(automation): NotifyConfigSchema sourceObject / sourceId / actionUrl describe text omits the trigger-record default link that PR #30252 ships #30689 ordered that wording reused. Fixing the spec alone would split it from its source. The record owes one card over all four surfaces and says this PR need not wait.
  • One observation: a null envelope is a written key, so it drops rather than defaults (notify-node.ts :709, flows.mdx :352). The same card carries it.
• Declarations: Clause-②: no, Metadata-protocol: none, @objectstack/spec patch, the same in the body and in the changeset.
  • The text now states what PR feat(service-automation): a record-triggered flow's notification links to the record that started the run when it names no link #30252 already ships, and no accept set or authored key's meaning moves. The semantic move was declared on PR feat(service-automation): a record-triggered flow's notification links to the record that started the run when it names no link #30252 itself.
  • TSDoc and .describe() in src/**/*.zod.ts ship in the published declarations, so the patch is owed.
• Accepted deviations:
  • The NOTIFY_KEY_GUIDANCE.source pair note (≈:137) was left as it is. It speaks to an author moving the retired nested source: { object, id } onto a written pair, and the default never applies once a half is written (:185). The review accepted this.
  • The branch did not merge origin/main; the merge-tree reading above covers it.
  • mcp_calls: 0.
• Carried:
  • The review's should-fix and its null observation: filed notify click-through default: four texts say a before-create run links to its record, but that run has no record id yet #30759. It covers the notify-node.ts docblock and descriptions, these describes and docblock, flows.mdx and SKILL.md. It waits for PR docs(skills): teach that a notify with no link opens the run's trigger record #30682, which writes the last two.
  • Acceptance notes skills/objectstack-automation/SKILL.md:124 and content/docs/automation/flows.mdx:352, which are silent on the default: carrier 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, domain:skills). Its head states the default at SKILL.md :124-126 and flows.mdx :352-358. Nothing more filed.
• Landing: not governed (check-governed-merges --pr 30742: 0 of 3 paths, 50 lines ≤ 3000). The hand-off is pr_ready plus automerge_enable, through the merge queue.

---

Generated by Claude Code