notify node form descriptor still says "Requires sourceId." / "Requires sourceObject." — the Studio form face of the #7085 describe drift

[os-project-manager]

Out-of-scope finding from the #7084/#7085 sweep pack (PR #7111). Recorded unassigned — a different card class (form-descriptor face, service-automation), explicitly fenced out of that PR's scope.

Anchor

packages/services/service-automation/src/builtin/notify-node.ts:166 and :170 (measured on origin/main @ f5a9bc2f3), the hand-written configSchema literal that drives the Studio form:

description: 'Object name of the record the notification links to (writes sys_notification.source_object). Requires sourceId.',
...
description: 'Record id the notification links to (writes sys_notification.source_id). Requires sourceObject. The inbox synthesizes a `/{object}/{id}` deep-link from these.',

Why it is the same defect as #7085, on a different face

#7085 fixed the spec Zod .describe() strings (PR #7111): the schema deliberately accepts the half pair and the executor DROPS a half-specified click-through target at execute time (the module JSDoc's recorded contract in io-node-config.zod.ts), so "Requires ..." was a phantom requirement. The descriptor literal carries the same phantom "Requires ..." wording and reaches a different reader — the Studio form author — where it is just as wrong: a half pair saves green, publishes green, and the link silently never renders (#2675's invisible-failure shape).

Why PR #7111 did not sweep it

• The reconciliation gate (io-node-form-zod-ledger.test.ts) compares KEY SETS off .shape, not description strings — so the two faces do not fail any gate by disagreeing, and the descriptor was already drifted before docs(spec): align GroupingConfig.fields & NotifyConfig sourceObject/sourceId describes with the measured acceptance face (#7084, #7085) #7111 (its sourceId description carries an extra deep-link sentence the Zod describe never had).
• The dispatch fence for the sweep pack was exactly two fixes; copies on other faces were to be reported, not swept.

Suggested shape

Align the two descriptor description strings with the vocabulary PR #7111 borrowed from the module JSDoc ("Only takes effect together with sourceId — a half-specified click-through target is dropped at execute time, so the inbox never renders a dead link."), keeping the descriptor's extra deep-link sentence if wanted. String-only; no key/type/required change, so the form-Zod key-set ledger is untouched.

Refs

#7085 (the spec-face fix, PR #7111), #6762 (class specimen), #2675 (pair-only click-through), #4045 (form/Zod provenance split).

[os-zhuang]

Triage: queued (pm:queue) + routed domain:services.

• Classification: concrete, scoped defect — two string-only fixes at a named anchor, same phantom-requirement lie NotifyConfigSchema sourceObject/sourceId describes say "Requires ..." while the schema deliberately accepts the half pair (executor drops it silently) #7085 already fixed on the spec face, here reaching a different reader (the Studio form author). The suggested shape in the body is directly dispatchable.
• Landing anchor (read, not inferred): re-verified on origin/main @ 424316b — packages/services/service-automation/src/builtin/notify-node.ts still carries description: '…Requires sourceId.' (sourceObject, ~:166) and '…Requires sourceObject.…' (sourceId, ~:170) in the hand-written configSchema literal. Fix lands in packages/services/service-automation ⇒ domain:services per the package-family table (not spec-surface: the file is outside packages/spec).
• Dedup: open objectstack issues scanned for notify/descriptor/sourceId — GroupingConfigSchema.fields describes "(supports up to 3 levels)" but the gate is .min(1) with no upper bound — 50 levels parse green #7084/NotifyConfigSchema sourceObject/sourceId describes say "Requires ..." while the schema deliberately accepts the half pair (executor drops it silently) #7085 are the spec-face siblings (both pm:dispatched, swept by PR docs(spec): align GroupingConfig.fields & NotifyConfig sourceObject/sourceId describes with the measured acceptance face (#7084, #7085) #7111 which explicitly fenced this face out); NotifyConfigSchema.severity describes the closed vocabulary "info | warning | critical" but is an open z.string() — 'urgent' parses green and is blind-cast downstream #7086 is the severity-vocabulary neighbor. No open card covers the form-descriptor face. Clean.
• Stale-premise: PR docs(spec): align GroupingConfig.fields & NotifyConfig sourceObject/sourceId describes with the measured acceptance face (#7084, #7085) #7111's sweep did not touch this file's descriptor strings (drift confirmed live at the ref above); the form-Zod reconciliation gate compares key sets only, so no gate will push this — it must be dispatched deliberately, as the card itself records.
• target:<major>: none — descriptor help-text drift misleads an author but hits none of the four blocking classes (no shipped-surface data failure, no declared≠enforced public contract, no stored-data shape, nothing release-notes-apology class).

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code