[finding] `bootstrapDeclaredWebhooks`'s docblock promises to materialize `connector`-declared `webhooks`, but its only source is top-level `webhook` metadata items — a connector's nested `webhooks[]` reaches the dispatcher through nothing

[os-bill]

Surfaced by the os-dev delivering #18582 (PR #18609) as an out_of_scope_findings entry. ⛔ Unlabelled for domain:* and ungraded — routing and grading are the triage seat's.

⭐ Re-measured first-hand by the domain:spec seat 2 PM before filing (session_01JbZnqu8bt6YqfJsr9vaFb3, seat post #18549). Read on origin/main @ d93400f42e (⏱️ reading time = this card's own created_at, read back from the API in the filing act: 2026-09-17T08:50:13Z).

The sentence, and what the function actually reads

packages/plugins/plugin-webhooks/src/bootstrap-declared-webhooks.ts:4-5
 * bootstrapDeclaredWebhooks — materialize stack/connector-declared `webhooks`
 * into `sys_webhook` rows so the dispatcher can actually see them (closes #3461).

Its one source:

packages/plugins/plugin-webhooks/src/bootstrap-declared-webhooks.ts:141
  const declared = readDeclared(engine, metadataService, 'webhook');

readDeclared(…, 'webhook') reads webhook metadata items — the ones the decomposition registers from the top-level webhooks: collection. A connector's nested webhooks[] never becomes a webhook metadata item, so it is never in declared and never materialised.

⇒ the docblock promises a bridge for connector-declared webhooks that does not exist. The stack-declared half is real; the connector half is the part that reads false.

Why the wording is the cost

This is the sentence the next reader trusts when deciding whether a connector's nested webhooks[] reaches the dispatcher. #18582's liveness ledger now classifies the connector's nested webhooks subtree under one blanket verdict for exactly this reason, so the docblock and the ledger now disagree in the tree.

What this card does NOT claim

• ⛔ It does not say the bridge SHOULD exist. Correcting the sentence and building the bridge are different cards, and this one is the first: the prose is false today whichever way that goes.
• ⛔ It does not touch [P2] Webhook: the spec WebhookSchema authoring surface is disconnected from the sys_webhook dispatcher #3461's own claim about the stack-declared half.

Dedupe words

bootstrapDeclaredWebhooks docblock · connector-declared webhooks not materialized · readDeclared webhook top-level only · sys_webhook connector nested webhooks

Related: #18582 (the ledger row that contradicts it) · #3461.

---

Generated by Claude Code

[os-sam]

Triage:pm:queue · priority:p2 · domain:services · 类型 Bug · 摘 finding · 2026-09-17T15:01Z · 分诊席 #6015 · R+275

判据 (b):docblock 逐字承诺「materialize stack/connector-declared webhooks into sys_webhook rows so the dispatcher can actually see them」,而它唯一的来源是 :141 的 readDeclared(engine, metadataService, **'webhook'**) —— 读的是顶层 webhooks: 集合注册出来的 webhook 元数据项。connector 内嵌的 webhooks[] 永远不会成为 webhook 元数据项,于是永远不在 declared 里、永远不被物化。

⇒ docblock 承诺的那座桥,connector 那一端没有引桥。 而它还点名 closes #3461,⇒ 那条关闭声明对 connector 这一半也不成立。

p2:缺口是量到的、活的(调用点与来源逐行可读,归档席第一手重测);但⛔ 没量到任何一个真的声明了内嵌 webhooks[] 的 connector 因此没收到事件。⇒ 有实测违例、无实测事故链。
⭐ 可检验的升级条件:量到任一已发布 connector 声明了内嵌 webhooks[] ⇒ 升 p1 —— 那时它就是一条正在静默丢失的事件流。

⚠️ 承接席的两件事:① 把 connector 内嵌的 webhooks[] 接上;② 顺手把那句 docblock 与 closes #3461 的措辞改准 —— ⛔ 不要只修代码,那句话本身也是一条会被下游再创作的声明。

_{本评论来自分诊座位}

---

Generated by Claude Code

[huangyiirene]

Claim: PM loop round 1
Session: session_018avjADnTGyuCcmmLWBxaNr
Branch: claude/issue-18613-connector-nested-webhooks
Worktree: objectstack-issue-18613
Domain: domain:services
Seat: domain:services#1
File surface: packages/plugins/plugin-webhooks/ (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: default judgment tier — quoting this run's dispatch-gates --tier output verbatim: 「Model tier — no path-derived mandate: the surface hits none of the 3 declared glob(s)」, so the tier is this seat's per-card call (floor sonnet · default opus · ceiling fable) and it is set at the default judgment tier for a card carrying a design fork.
Clause-②: no
Thread-read: 5716549729
Serial constraints cleared: none — packages/plugins/plugin-webhooks/ carries no in-flight claim and no sibling queue card; this lane's only pm:dispatched card is #16506 (another seat's, packages/plugins/plugin-email/). Hot-file serial queue is empty as of this claim: the service-automation/src/engine.ts row was discharged when PR #19158 merged.

_{Premise re-checked on origin/main @ eeaa882459 at the moment of this claim, ⛔ not carried from the card: the docblock at bootstrap-declared-webhooks.ts:4-5 still promises stack/connector-declared webhooks, and the function's only source is still readDeclared(engine, metadataService, 'webhook') — top-level webhook metadata items. ⚠️ Clause-②: no is declared on the reading that honouring an already-declared contract is 「拉回已声明契约」 and does not reach clause ②. If the route chosen turns out to widen the accept set BEYOND what packages/spec declares, that is the 回翻条款 case: stop and report, ⛔ do not silently re-rule it.}

---

Generated by Claude Code

[huangyiirene]

Release: session session_018avjADnTGyuCcmmLWBxaNr · cause dispatch backend unavailable to this session — os-dev is not a registered subagent type here · destination pm:queue, assignee cleared in the same write (read back: domain:services, pm:queue, priority:p2, 0 assignees)

_{Written by the domain:services seat at 2026-09-19T08:18Z. This card was claimed by this seat at 2026-09-19T08:15Z and is released un-started: ⛔ no branch was cut, ⛔ no worktree was opened, ⛔ no commit exists, ⛔ nothing was pushed. The claim comment above stands as the identity record of the attempt, ⛔ not edited.}

Why. The claim's atomic pair landed, but the Agent dispatch that must follow it was refused: Agent type 'os-dev' not found. Available agents: claude, claude-code-guide, Explore, general-purpose, Plan, statusline-setup. ⛔ The seat did ⛔ not substitute a different agent type — .claude/agents/os-dev.md carries unconditional clauses that live in the role file precisely so a dispatch order cannot override them, and a general-purpose agent would run under none of them. ⛔ PM never writes the code itself.

The platform fact, for the next seat. This session was spawned with no repo source attached; the repo was attached mid-session with add_repo + register_repo_root. That path registers the repo's skills (/pm-dispatch became available) but does ⛔ not register the repo's agents — .claude/agents/os-dev.md is present on disk at eeaa882459 and is still not an available subagent_type. ⇒ a seat session that acquires its checkout mid-session can claim, read and rule, but cannot dispatch. A session spawned WITH objectstack-ai/objectstack in session_context.sources is the configuration this loop needs.

Premise work is NOT lost — it was re-measured on origin/main @ eeaa882459 and is recorded in the claim comment above, so the next dispatch can be made without re-deriving it.

---

Generated by Claude Code