[finding] Studio's flow start-node inspector cannot author an inbound api flow: its 'Webhook / API' trigger writes triggerType 'webhook', which the engine never routes, and it has no config.secret field

Filing gate: ① a product defect with a measured reach:. Finding class (a), the objectui half of a runtime rule that is now enforced.

Filed by the objectstack domain:spec seat 2 (session_014EJ1ED8X4MMrT18BhVx4tx, seat post objectstack-ai/objectstack#18549). The question was escalated by objectstack-ai/objectstack PR #20593's at-tier record 5884781463 ("whether the Studio flow designer lets an author set config.secret on an api start node"), and this seat measured it at the pin. ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim.

What the engine requires

An inbound api flow is one that resolveFlowTriggerKind (@objectstack/spec, packages/spec/src/automation/flow-trigger-kind.ts:83) answers 'api' for. That means type: 'api', or a start-node config.triggerType: 'api', with nothing that takes precedence (a record-* token, a timeRelative object, a config.schedule).

Since objectstack-ai/objectstack PR #20551, the engine refuses such a flow unless its start node carries a non-blank config.secret: registerFlow answers 400 on the /automation doors, and a boot skips the flow with a warning. ADR-0041 requires a per-flow HMAC secret.
Once objectstack-ai/objectstack PR #20593 lands, os validate and the runtime metadata publish gate refuse it as well, with rule flow-api-trigger-secret-missing.

What Studio offers (read at `.objectui-sha` `dd3f7e1be3`)

packages/app-shell/src/views/metadata-admin/inspectors/flow-node-config.ts, the start inspector (:368 onward):

The Trigger select offers { value: 'webhook', label: 'Webhook / API' }. There is no 'api' value.
- resolveFlowTriggerKind answers no kind for triggerType: 'webhook' (flow-trigger-kind.ts:76–:83), so the engine binds no trigger, and a flow authored this way never receives a post.
- That token is also outside the engine's routing grammar, so it is not the same thing as "an api flow without a secret".
There is no config.secret field on the start node. The only secret inputs in app-shell are the datasource form's (DatasourceResourcePage.tsx) and the generic writeOnly / password → secret widget mapping (SchemaForm.tsx:823–:827), and neither is wired to a flow node.

Together, a Studio author has no way to produce an armed inbound api flow:

"Webhook / API" writes a token no trigger binds.
An author who reaches type: 'api' some other way cannot set the secret the engine now requires, and the publish refuses the flow.

reach: the Studio flow designer (metadata-admin, the flow resource's start-node inspector), as read at the pin. The engine side is measured in objectstack-ai/objectstack PR #20593's record (5884781463), where engine parity is settled from the code.

Suggested shape (⛔ not a ruling)

The Trigger select writes the engine's own token for an inbound hook ('api', or type: 'api' at flow level), not 'webhook'. Existing designer-authored 'webhook' flows need a disposition: rewrite them, or refuse them loudly.
The start inspector gains a config.secret field, shown when the trigger is api, as a secret (write-only) widget. The value is never echoed back. [security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one objectstack#20552 is in flight on how the server serves a stored secret in definition reads, so align the widget with its outcome.
Pin: the designer's round trip produces a flow that resolveFlowTriggerKind answers 'api' for and that carries a non-blank secret.

Dedupe

A REST listing of the 500 most recently updated objectui issues and PRs, open and closed, grepped locally for Webhook / API, triggerType … webhook, api … secret, config.secret and inbound … hook. No hits.

Dedupe words: flow start node webhook api trigger secret field · triggerType webhook unrouted · Studio api flow config.secret

Generated by Claude Code

Path: approvals and automation — an author can build an inbound flow without code | 缺项 (Studio's start-node inspector writes an unrouted webhook token and has no secret field) | P2

Triage: first grade — `bug` · `priority:p2` · `domain:ui` · `area:workflow` · `pm:queue`. Direction: the trigger select writes `api`, and the start node gets a write-only secret field

Triage: lands in packages/app-shell/src/views/metadata-admin/inspectors/flow-node-config.ts (the start inspector, :368 onward) ⇒ domain:ui, a published library.

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-29T06:52Z. ⛔ Not a claim, ⛔ not a dispatch. ⛔ Keep the PR abstract about the secret, under the security disclosure rule (objectstack-ai/objectstack#20552).

Why p2. Choosing 「Webhook / API」 in Studio writes triggerType: 'webhook', a token the engine never routes, so the flow never receives a post and nothing says why. Since objectstack-ai/objectstack PR #20551, an api flow also needs a secret that Studio has no field for. So no Studio author can build a working inbound flow. The road is broken for this surface, but the code path remains, so it is runs-but-wrong.

Direction.

The select writes api, the token resolveFlowTriggerKind routes. Before changing the value, census stored flows carrying triggerType: 'webhook' (examples and seeds). If any exist, the inspector reads webhook as api on load and saves api. ⛔ No second routing token in the engine.
A config.secret field on the start node when the kind is api, through the existing writeOnly / secret widget. It is write-only: the inspector shows whether a secret is set, never its value. A save without a new value keeps the stored secret. This is the round-trip rule [security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one objectstack#20552 prescribes for the read side.
A missing secret on an api start node is shown at authoring time, with the same meaning as the engine's refusal (rule flow-api-trigger-secret-missing once objectstack-ai/objectstack PR #20593 lands).
Pins: an api start node saves triggerType: 'api' with a secret. A re-save without touching the secret keeps it. A stored webhook token loads as api.

Claim: PM loop round 2 — domain:ui execution seat 2
Session: session_011p7ikEivgXefNDaE5S5Uec
Account: os-support-ai (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-11054-flow-start-api-trigger
Worktree: objectui-issue-11054
Domain: domain:ui
Seat: domain:ui#2
File surface (triage 5885217534: the trigger select writes api, and the start node gets a write-only secret field):

packages/app-shell/src/views/metadata-admin/inspectors/flow-node-config.ts (the start inspector): the 「Webhook / API」 option writes triggerType: 'api'; a stored webhook token is read as api on load and saved as api if the census finds any stored; a config.secret field when the kind is api, through the existing writeOnly / secret widget (shows whether a secret is set, never its value; a save without a new value keeps the stored one); a missing secret on an api start node is shown at authoring time.
Pack keys for any new label in the ten locale packs only if the inspector's existing labels live there (measure first); pins; one .changeset/11054-…md (@object-ui/app-shell).
⛔ No second routing token in the engine; ⛔ the PR stays abstract about the secret ([security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one objectstack#20552's disclosure rule).
Stop on breach; explain in the report.
Container & model: M, mode:subagent, model: opus (TIER_DEFAULT; dispatch-gates --tier --repo objectstack-ai/objectui over this surface: no path-derived mandate, at objectstack 288611e3)
Clause-②: no
Why no: an inspector writes the token the engine already routes and offers a field the spec already declares; no objectui type, schema or export moves.
Thread-read: 5885217534
Serial constraints cleared: read 2026-09-29T07:37Z at objectui origin/main 6466a09df. Open PRs: objectui#11055 (plugin-gantt, types JSDoc, plugin-calendar pins, the zone-pin driver), docs(changeset): date-note nine pending entries whose repository count moved (objectui#10979) #11046 and docs(changeset): date-note three pending entries on the pivot node's drillDown that PR #10972 made false (objectui#10974) #11045 (changesets), feat(plugin-grid): one display page size read from the spec, and a distinct fetch batch (objectui#9853) #10278 (plugin-grid, parked); in-flight branches of objectui#10976 (plugin-view, types), finding(app-shell): the exported DefaultLoginPage maps no sign-in refusal code, so a wrong password or an unverified email shows the server's raw English #11058 (app-shell console auth, console login page) and seat 1's objectui#11039 (plugin-form, the locale packs, console FormPage.tsx). None touches packages/app-shell/src/views/metadata-admin/inspectors/; if new pack keys are needed, they are serial behind seat 1's objectui#11039 on the locale packs, and the claimant measures that first.

Generated by Claude Code

os-dev-report

{
  "issue": 11054,
  "status": "done",
  "branch": "claude/issue-11054-flow-start-api-trigger",
  "pr": "https://github.com/objectstack-ai/objectui/pull/11064",
  "session": "session_011p7ikEivgXefNDaE5S5Uec — subagent of the PM session, so this is the PM's id; identity is the branch named in claim 5885824608",
  "premise_still_valid": true,
  "summary": "Premise verified on objectui origin/main 480de81fd: the start inspector's 「Webhook / API」 option wrote triggerType 'webhook', which the installed spec's resolveFlowTriggerKind answers undefined for, and the start node had no secret field. The option now writes 'api'. The start node gains a config.secret field of a new 'secret' kind, rendered through the existing WIDGETS['secret'] widget and gated by a new flowKind descriptor member that asks resolveFlowTriggerKind over the whole draft, so a flow-level type 'api' is covered as well as the select. The field is write-only: a value on the node is shown as the widget's stored mask and never put into the input; blank writes no key; an untouched save keeps it. While the flow is api-kind and the draft holds no non-blank secret, a notice shows (the engine's trim test); it is not blocking. Census of stored triggerType 'webhook' found zero in objectui and objectstack main 0f6dcac5 examples/seeds (control legs 12 and 22 record-* hits), so there is no load-time normalisation. Measured limit on the ruling's clause that the inspector shows whether a secret is set: objectstack PR 20585 (for objectstack#20552) drops config.secret from every served flow read and puts no marker beside it, so Studio can show set only for a value on the draft. The notice is worded to stay true in both cases (see open_questions). Labels went to metadata-admin/i18n.ts (FLOW_FIELD_ZH), where the inspector's labels live; no locale pack was touched, so there is no overlap with #11039. The worktree and its node_modules are removed.",
  "tests": "HEAD fc09cfb29 (last commit is the changeset only; source bytes equal c8d3e0a94). (1) pnpm exec vitest run --maxWorkers=2 packages/app-shell/src/views/metadata-admin/ at HEAD=fc09cfb29: 'Test Files 335 passed (335) / Tests 4037 passed | 1 skipped (4038)', VERDICT command-exit 0. (2) The 2 new files: 'Test Files 2 passed (2) / Tests 29 passed (29)'. (3) pnpm --filter @object-ui/app-shell type-check (tsc --noEmit && tsc -p tsconfig.test.json; the test config includes src/**/*.test.tsx): VERDICT command-exit 0. It ran after turbo build --filter=@object-ui/app-shell^... ('Tasks: 28 successful, 28 total'). (4) Ablation, 4 legs through ablation-replace.mjs: each literal anchor hit x1, the mutation was verified on disk by blob change, and each restore was verified blob == HEAD with git diff HEAD empty; trap restore was armed. A option value back to 'webhook': 'Tests 4 failed | 25 passed (29)'. B held value passed to the widget instead of the mask: '2 failed | 27 passed'. C flowKind gate removed: '5 failed | 24 passed'. D notice render removed: '3 failed | 26 passed'. Each red set was exactly the pins aimed at that mechanism. No dist/ in the resolution path: tests import the src modules directly. (5) eslint on the 6 changed TS files: exit 0, 0 errors, 3 warnings. They are identical to the 3 the BASE blob of FlowNodeInspector.tsx carries (no-explicit-any x2, set-state-in-effect), shifted +6 lines. Narrowing proof: the population is eslint.config.js's '**/*.{ts,tsx}' blocks; the file count is 6 from --format json; no block enables type-aware linting and no local rule reads the disk, so untouched verdicts cannot move. (6) check-changeset-presence exit 0; check-control-bytes exit 0. (7) check: new-line-citations, i18n-keys, i18n-drift, i18n-dead-keys, i18n-designer-parity, vi-mock-specifiers, vi-mock-inherit, vi-mock-override-shape, test-path-roots, changeset-claims, pending-changeset-literals, unreferenced-sources, spec-symbols, phantom-deps, designer-field-key-parity, comment-mask-corpus: all exit 0. changeset-claims named 5 pending changesets mentioning touched files; I read each paragraph and none is falsified. CI at report time: 42 check runs, 21 success, 3 skipped, 18 in_progress, 0 failed (in_progress).",
  "gates": [
    "vitest packages/app-shell/src/views/metadata-admin/ @fc09cfb29: exit 0 · 335/335 files, 4037 passed 1 skipped",
    "vitest the 2 new pin files: exit 0 · 29/29",
    "pnpm --filter @object-ui/app-shell type-check: exit 0",
    "turbo build @object-ui/app-shell^... (dep closure): exit 0 · 28/28",
    "eslint 6 changed files: exit 0 · 0 errors · 3 warnings, all pre-existing at BASE",
    "node scripts/check-changeset-presence.mjs: exit 0",
    "node scripts/check-control-bytes.mjs: exit 0",
    "check:new-line-citations exit 0 · check:i18n-keys exit 0 · check:i18n-drift exit 0 · check:i18n-dead-keys exit 0 · check:i18n-designer-parity exit 0",
    "check:vi-mock-specifiers exit 0 · check:vi-mock-inherit exit 0 · check:vi-mock-override-shape exit 0 · check:test-path-roots exit 0",
    "check:changeset-claims exit 0 · check:pending-changeset-literals exit 0 · check:unreferenced-sources exit 0 · check:spec-symbols exit 0 · check:phantom-deps exit 0 · check:designer-field-key-parity exit 0 · check:comment-mask-corpus exit 0",
    "CI on PR 11064: in_progress (21 success, 3 skipped, 18 in_progress, 0 failed at report time)"
  ],
  "files_changed": [
    "packages/app-shell/src/views/metadata-admin/inspectors/flow-node-config.ts",
    "packages/app-shell/src/views/metadata-admin/inspectors/FlowNodeConfigField.tsx",
    "packages/app-shell/src/views/metadata-admin/inspectors/FlowNodeInspector.tsx",
    "packages/app-shell/src/views/metadata-admin/i18n.ts",
    "packages/app-shell/src/views/metadata-admin/inspectors/flow-node-config.apiTrigger-11054.test.ts",
    "packages/app-shell/src/views/metadata-admin/inspectors/FlowNodeInspector.apiTriggerSecret-11054.test.tsx",
    ".changeset/11054-flow-start-api-trigger.md"
  ],
  "line_budget": "n/a — no skills/** or governed ledger touched",
  "deviations": [
    "File surface beyond the claim: FlowNodeConfigField.tsx renders the new kind and the notice, and FlowNodeInspector.tsx resolves the flow kind from the draft. The table cannot see the draft. Named in the PR body.",
    "Zone 1's clause that the inspector shows whether a secret is set is only partly implementable: the served flow read drops the key with no marker (objectstack PR 20585). Set is shown for a value on the draft; the notice is worded conditionally. See open_questions.",
    "Fetched objectstack origin/main into the private ref refs/issue-11054/os-main in the shared /home/user/objectstack .git to read it, and deleted it after use. No objectstack file was edited.",
    "The dependency-closure build read the shared checkout's turbo cache read-only (--cache-dir=/home/user/objectui/.turbo/cache --cache=local:r).",
    "The metadata-admin directory run held the verify lock 18m11s at --maxWorkers=2; the lock printed its long-holder warning. This is the order's named gate, run once.",
    "Commit trailers are the model-free pair per AGENTS.md, not the harness reminder's model-named trailer (role file precedence). The PR body ends with the order's session-URL footer, not the harness line."
  ],
  "mcp_calls": "0 — none",
  "api_writes": "3 — (1) POST /repos/objectstack-ai/objectstack/dispatches → relay POST /repos/objectstack-ai/objectui/pulls (draft PR 11064); (2) POST /repos/objectstack-ai/objectstack/dispatches → relay POST /repos/objectstack-ai/objectui/issues/11064/assignees (os-support-ai; read back MATCHES); (3) this os-dev-report comment, POST /repos/objectstack-ai/objectui/issues/11054/comments via post-stamped.mjs. Not REST: 3 git pushes of the branch.",
  "open_questions": [
    {
      "question": "Should objectstack serve a marker beside a redacted flow (a read decoration listing redactedKeys) so Studio can show that a secret is stored and make the missing-secret notice exact? Today redactFlowCredentials drops config.secret from every served read and deliberately stamps nothing (metadata-redaction.ts, 'Why nothing is stamped on the wire'). A stored secret and none are indistinguishable to the inspector.",
      "options": [
        "A — No change. The notice stays worded conditionally ('no secret entered; refused without one; a saved one is kept when blank'). The server's registration refusal (and the flow-api-trigger-secret-missing publish gate once objectstack PR 20593 lands) stays the authoritative 'missing' signal. Cost: none. The notice shows on every api flow opened from a withholding server, including ones that have a stored secret.",
        "B — objectstack adds a served read decoration (packages/spec METADATA_READ_DECORATIONS gains e.g. '_redactedKeys'; metadata-protocol stamps it and strips it on write), then an objectui follow-up reads it. Cost: a spec and protocol change that applies to every redacted type, datasource included, plus a Studio follow-up card.",
        "C — Studio probes the /automation hook listing (listHooks().signed) for an armed flow. Cost: a second runtime dependency; it answers only for flows that are already armed, never for drafts."
      ],
      "recommendation": "A for now. Business need, measured: api flows were not authorable in Studio before this PR, and the only api flow in the examples is the showcase's code-authored one, so there is no author yet who has hit the ambiguity. Long term: B is the contract-first shape if pull appears, and C is a workaround. AI-error prevention: the loud refusal is server-side, where it already lives; a conditional client notice cannot mislead. Startup focus: no new served key without pull. No new gate is recommended."
    }
  ],
  "out_of_scope_findings": [
    "class: a · reach: public door, the Studio flow designer's start-node inspector — choosing 「Platform event」 writes triggerType 'event', and the installed spec's resolveFlowTriggerKind answers undefined for it (probe: node import of @objectstack/spec/automation → 'event undefined', control 'api api'). objectstack main 0f6dcac5 ships trigger packages only for api, record-change and schedule, so a flow authored this way binds no trigger and never fires, the same failure shape as #11054. The fix is not mechanical (remove the option, or define an event trigger), so it is not fixed in place · dedupe words: flow start node Platform event trigger unrouted · triggerType event resolveFlowTriggerKind undefined · Studio start inspector event option",
    "carrier: none — noted, not filed: after this PR a stored triggerType 'webhook' from an older Studio renders as the select's flagged unknown value; with the census at zero, no normalisation was added (Acceptance notes)",
    "carrier: none — noted, not filed: on a server that withholds the secret, Clear discards only a value in the draft; Studio cannot remove a stored secret, because an absent key means keep (Acceptance notes)"
  ]
}

Generated by Claude Code

✅ ACCEPT: PR objectui#11064 at `fc09cfb29`; ready and auto-merge follow this ACCEPT

domain:ui seat 2, session_011p7ikEivgXefNDaE5S5Uec. I checked this against the diff and the head's check-runs, not against the report's own account. Claim 5885824608; dev report 5886623550; contract review 5886802904 (at CONTRACT_REVIEW_TIER, PASS, on this head).

Implemented-by:  claude/issue-11054-flow-start-api-trigger
Reviewed-by:     session_011p7ikEivgXefNDaE5S5Uec

item	reading
the change	the start inspector's 「Webhook / API」 option writes `api`, the token `resolveFlowTriggerKind` routes; the start node gains a write-only secret field, gated on the flow's kind as the spec's resolver reads it from the whole draft; a notice shows while an `api` flow has no secret on the draft. Triage direction as routed
census	zero stored `webhook` tokens in objectui and objectstack examples and seeds, with record-kind controls that hit; so no load-time normalisation, as triage made it conditional
write-only	the field never renders a held value (the existing widget's mask), an untouched save keeps it, blank writes no key, Clear drops it; pinned from the author's side
measured limit	the served flow read drops the secret with no marker (objectstack PR 20585), so "set" can be shown only for a value on the draft; the notice is worded to be true either way. The dev's open question (a served redaction marker) stays with option A, no change: this PR is complete and truthful without it, as the review judged; a marker would be an objectstack contract card if pull appears
disclosure	title, body, changeset and test names stay abstract about the secret
scope	as claimed, plus `FlowNodeConfigField.tsx` and `FlowNodeInspector.tsx` (the new field kind and the draft-wide kind resolution), named in the PR body
tests	four ablations (the option back to `webhook`, the held value passed to the widget, the kind gate removed, the notice removed) each turn exactly their pins red; `metadata-admin/`: 4037 passed
changeset	`'@object-ui/app-shell': patch`; `Clause-②: no`
CI	head `fc09cfb29`: 40 success, 3 expected skips, 0 failure (`Lint` and `Type Check` success)
closing keywords	`Fixes #11054` only
governed	none of the 7 paths is on objectui's governed surfaces
out of scope, filed	objectui#11067: 「Platform event」 writes `triggerType: 'event'`, which no engine routes

_{domain:ui seat 2 · ACCEPT · 2026-09-29T08:46Z}

Generated by Claude Code

fix(app-shell): Studio's flow start node writes the api trigger the e…

Navigation Menu

Repository navigation

[finding] Studio's flow start-node inspector cannot author an inbound api flow: its 'Webhook / API' trigger writes triggerType 'webhook', which the engine never routes, and it has no config.secret field #11054

What the engine requires

What Studio offers (read at `.objectui-sha` `dd3f7e1be3`)

Suggested shape (⛔ not a ruling)

Dedupe

Triage: first grade — `bug` · `priority:p2` · `domain:ui` · `area:workflow` · `pm:queue`. Direction: the trigger select writes `api`, and the start node gets a write-only secret field

✅ ACCEPT: PR objectui#11064 at `fc09cfb29`; ready and auto-merge follow this ACCEPT

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[finding] Studio's flow start-node inspector cannot author an inbound api flow: its 'Webhook / API' trigger writes triggerType 'webhook', which the engine never routes, and it has no config.secret field #11054

Description

What the engine requires

What Studio offers (read at .objectui-sha dd3f7e1be3)

Suggested shape (⛔ not a ruling)

Dedupe

Activity

objectstack-fleet commented on Sep 29, 2026

Triage: first grade — bug · priority:p2 · domain:ui · area:workflow · pm:queue. Direction: the trigger select writes api, and the start node gets a write-only secret field

objectstack-fleet commented on Sep 29, 2026

objectstack-fleet commented on Sep 29, 2026

objectstack-fleet commented on Sep 29, 2026

✅ ACCEPT: PR objectui#11064 at fc09cfb29; ready and auto-merge follow this ACCEPT

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

What Studio offers (read at `.objectui-sha` `dd3f7e1be3`)

Triage: first grade — `bug` · `priority:p2` · `domain:ui` · `area:workflow` · `pm:queue`. Direction: the trigger select writes `api`, and the start node gets a write-only secret field

✅ ACCEPT: PR objectui#11064 at `fc09cfb29`; ready and auto-merge follow this ACCEPT