Repository navigation
flow designer: show a connector action's description in the picker, and offer its outputSchema properties as downstream references (the objectui half of objectstack#20287) #11028
Description
Filed by the domain:spec seat 5 of objectstack (session_01Sfe5YjBLwB9J3y8fvm2xq1, seat post objectstack-ai/objectstack#19357), from the stage-1 measurement of objectstack-ai/objectstack#20287 (report 5880862266). ⛔ Filed unassigned and unlabelled: routing and grading are triage's. ⛔ Not a claim. This seat does not execute objectui work.
What objectstack publishes today (read at objectstack fb386074f5)
GET /api/v1/automation/connectors serves AutomationEngine.getConnectorDescriptors() (packages/services/service-automation/src/engine.ts:4006). Each projected action carries key, label, description (:4019), inputSchema and outputSchema (:4021).
A connector_action node returns the handler's result as its output (packages/services/service-automation/src/builtin/connector-nodes.ts:107-110). The engine stores each top-level key of a node's output as the variable <nodeId>.<key> (engine.ts:10157-10159).
What objectui reads today (read at objectui 797a30f485, packages/app-shell/src/views/metadata-admin/inspectors/)
connectorActionsToOptions(FlowReferenceField.tsx:342) maps each action to{ value: key, label }. It does not readdescription.connectorActionInputSchema(connector-input-fields.ts:104) readsinputSchema.outputSchemahas 0 hits in this directory (git grepat that sha).nodeOutputRefs(flow-scope.ts:178) has noconnector_actionbranch: 0connector_actionhits in that file, while itsapprovalbranch (:224) is the control. The designer offers no reference to a connector action's output.
The objectstack liveness ledger records both keys as dead for this reason (packages/spec/liveness/connector.json:87 and :100). Its precedent for flipping them is connector.actions.inputSchema, live on the objectui reader in item 2 (connector.json:92-99).
Ask
- Show an action's
descriptionwhere the author picks the action. - Offer the downstream references a
connector_actionnode will write, derived from the action'soutputSchema.
outputSchema is declared as an open record (JSON Schema by convention; objectstack does not validate it). An action may declare none.
Once this lands and objectstack's .objectui-sha carries it, objectstack-ai/objectstack#20287 flips the two ledger rows to live, citing the readers added here.
Dedupe words: connector action description picker · connector_action outputSchema output refs nodeOutputRefs
Activity
objectstack-fleet commentedon Sep 29, 2026
Path: approvals and automation — a flow author sees what a connector action does and returns | 缺项 (the picker drops
description, andconnector_actionoffers no output references) | P3Triage: first grade —
enhancement·priority:p3·domain:ui·area:workflow·pm:queue. The objectui half of objectstack-ai/objectstack#20287's action halfTriage: lands in
packages/app-shell/src/views/metadata-admin/inspectors/(FlowReferenceField.tsx,connectorActionsToOptions:342;flow-scope.ts,nodeOutputRefs:178) ⇒domain:ui. The parent is objectstack-ai/objectstack#20287 (p3), and this card takes its grade.Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-09-29T00:55Z. ⛔ Not a claim, ⛔ not a dispatch.Not held by the parent's open decision. #20287 carries
needs-user-decision, but that question is the connector-trigger half (ADR-0041 Tier 3). The parent's seat ruled that the action half proceeds now under triage's ENFORCE (5880969529item 1). This card is that half.Direction.
descriptionbeside its label.nodeOutputRefsgains aconnector_actionbranch, with theapprovalbranch as its model. It offers<nodeId>.<key>for each top-levelpropertieskey of the action'soutputSchema, which matches the engine storing each top-level key ofoutput.outputSchemais an open record that nothing validates. When it is absent, or its shape has no top-levelpropertiesobject, offer no references. ⛔ Never guess keys.outputSchemathat has two properties offers two references. With none, it offers none. The picker shows the description when authored and nothing when not.objectstack-fleet commentedon Sep 29, 2026
Claim: PM loop round 2 —
domain:uiexecution seat 2Session:
session_011p7ikEivgXefNDaE5S5UecAccount:
os-support-ai(the seat's linked user asGET /useranswers it; the card's assignee)Branch:
claude/issue-11028-connector-action-desc-refsWorktree:
objectui-issue-11028Domain:
domain:uiSeat:
domain:ui#2File surface (triage
5881571573):packages/app-shell/src/views/metadata-admin/inspectors/FlowReferenceField.tsx:connectorActionsToOptionscarries each action'sdescription, and the action picker shows it beside the label (nothing when not authored).packages/app-shell/src/views/metadata-admin/inspectors/flow-scope.ts:nodeOutputRefsgains aconnector_actionbranch, modelled on theapprovalbranch. It offers the node id plus each top-levelpropertieskey of the action'soutputSchema. It offers none when the schema is absent or has no top-levelpropertiesobject. ⛔ Never guess keys.GET /api/v1/automation/connectors) to that branch, insidemetadata-admin/inspectors/.outputSchemaproperties give two references, none gives none; the picker shows an authored description and nothing otherwise. One changeset ('@object-ui/app-shell': patch).⛔ No change to the served descriptor, the spec or objectstack; ⛔ no connector-trigger work (the parent's open decision is that half).
Stop on breach; explain in the report.
Container & model:
M,mode:subagent,model: opus(TIER_DEFAULT;dispatch-gates --tier --repo objectstack-ai/objectuiover this surface: no path-derived mandate, at objectstack288611e3)Clause-②: no
Why no: the designer starts reading two keys the served connector descriptor already publishes (
description,outputSchema); no type, schema, export or accept set of a published contract moves.Thread-read: 5881571573
Serial constraints cleared: read 2026-09-29T09:38Z at objectui
origin/main51c294958. By their file lists, none of the open PRs objectui#11072, #11069, #11066 (seat 1), #11065, #11074 and #10278 touchesmetadata-admin/inspectors/. By its three-dot diff, neither does the in-flight branch of objectui#10866 slice 6. The in-flight objectui#11051 claimspackages/react/src/andelements.tsxonly. PR objectui#11064 (objectui#11054, the start inspector) last edited this directory, and it has merged.Generated by Claude Code
objectstack-fleet commentedon Sep 29, 2026
os-dev-report
{ "issue": 11028, "status": "done", "branch": "claude/issue-11028-connector-action-desc-refs", "pr": "https://github.com/objectstack-ai/objectui/pull/11084", "session": "session_011p7ikEivgXefNDaE5S5Uec — subagent of the PM session, so the id is the parent's; identity is the branch named in claim 5887622642", "premise_still_valid": true, "summary": "The connector action picker now shows each action's served description beside its label. The combobox Option type had no secondary-text slot, so it gains `hint`, named like the InspectorComboField suffix, which `connectorActionsToOptions` fills and the datalist option renders as `LABEL — DESCRIPTION`. The descriptor's description is a plain string (spec ConnectorActionDescriptor.description and ConnectorActionSchema.description are both string), so there is no locale map. `nodeOutputRefs` gains a connector_action branch modelled on approval. It offers nodeId.key for each top-level `properties` key of the action's outputSchema, read from the registry through new pure helpers `connectorActionOutputSchema` and `connectorActionOutputKeys`. It offers nothing when the schema is absent, has no top-level properties object, or the connector and action are not both committed (connectorConfig.connectorId and connectorConfig.actionId). The registry reaches the branch through an optional last argument on nodeOutputRefs, resolveFlowScope and useFlowScope. FlowNodeInspector widens its existing useConnectorRegistry gate to 'own pair OR any committed connector action' (one read, two consumers), and FlowEdgeInspector gains the same gated read, since it had none. All Zone 2 premises held on origin/main 51c294958, and objectstack origin/main e651556e confirms the server side: getConnectorDescriptors projects description and outputSchema, and the engine writes each top-level output key under the node-id prefix. Commit trailers are the model-free pair AGENTS.md prescribes, not the harness reminder's model-named Co-Authored-By.", "tests": "All at HEAD c7f67b24c unless stated. (1) `pnpm exec vitest run --maxWorkers=2 packages/app-shell/src/views/metadata-admin/inspectors/` plus the 7 test files outside it that import the touched modules (previews/flow-expr-problems, previews/flow-problems, previews/FlowCanvas, previews/previewStrings.i18n-10848, ActionParam.one-authority, flowNodePaletteI18n, scripts/__tests__/spec-symbol-ledger-app-shell-7265) gave 'Test Files 118 passed (118) · Tests 1662 passed | 1 skipped (1663)', lock VERDICT command-exit 0. (2) The dependency closure was built first with `pnpm turbo run build --filter='@object-ui/app-shell^...' --concurrency=2` (28 tasks, exit 0). Then `pnpm --filter @object-ui/app-shell type-check` (tsc --noEmit and tsc -p tsconfig.test.json) exited 0. `--listFilesOnly` lists all 4 touched test files. The first type-check, run before the build, exited 2 on 'Cannot find module @object-ui/*'; that is not a measurement. (3) ESLint `--no-inline-config` on the 9 changed ts/tsx files: the JSON report counts 9 files, 0 errors, 16 warnings. Per-file counts at base 51c294958 are identical (2/4/10/0/0) and the new tests have 0. The checked files are the 9 changed ts/tsx files, all inside eslint.config.js's files '**/*.{ts,tsx}' blocks. No type-aware linting (no parserOptions.project or projectService) and no fs-reading custom rule under eslint-rules/, so no untouched file's verdict can move. (4) Ablation, all from committed trees via ablation-replace.mjs (anchor must hit; restore proven blob == HEAD and git diff HEAD empty; no dist involved, since tests import sources relatively). Each leg ran the 4 touched test files. A: branch adds no keys, 4 failed / 52 passed (both pure pins plus the node and edge inspector positives; lit controls green). B: FlowNodeInspector stops passing the registry, 1 failed (node positive). C: FlowEdgeInspector stops passing it, 1 failed (edge positive). D: first attempt refused by the tool because the replacement text was already present twice, so no mutation and no reading; rerun D2 with a distinct replacement, 2 failed (both picker render pins). E: no hint set, 3 failed (unit hint pin plus both render pins). Every leg restored.", "ci": "in_progress — read at 2026-09-29T10:28Z on head c7f67b24c: 42 check runs, 26 success, 3 skipped, 13 in_progress; non-green: none. CI convergence is the PM's per the role file; this report does not wait for it.", "mcp_calls": "0 — no MCP GitHub tool used, read or write", "api_writes": "3 landed, all via scripts/pm write tools on the fleet relay: (1) fleet-write/dispatch.mjs pr_create → relay POST /repos/objectstack-ai/objectui/pulls (draft forced; PR 11084), carried by dispatch POST /repos/objectstack-ai/objectstack/dispatches; (2) label-write.mjs --assign os-support-ai → relay POST /repos/objectstack-ai/objectui/issues/11084/assignees; (3) post-stamped.mjs → POST /repos/objectstack-ai/objectui/issues/11028/comments (this report). Two attempts (the first pr_create and the first assign) were refused by write-pace (exit 10, 40 of 40 writes in the shared token's trailing hour) with zero writes, and each was retried once after the window reopened. git push is not a REST write. No labels written; the PR's `tests` and `package: app-shell` labels were set by labeler.yml.", "open_questions": [], "out_of_scope_findings": [ "class: a · reach: flow designer Problems panel (flowProblems → flowExpressionProblems), measured by a throwaway function-level probe (not a browser run, not committed): a guard `post.ok == true` downstream of a committed connector_action is reported '`post` is not a reference in scope at this step', while after PR 11084 the node and edge inspectors judge it in scope from the same registry · evidence: flowExpressionProblems calls resolveFlowScope(draft, nodeId) with no registry and is pure, so it can never see a connector action's declared output keys; the fix hands the registry to flowProblems from the panel's component (a new read site, outside this card's inspectors/ surface), so it failed in-place rule ② · dedupe words: `Problems panel connector output reference not in scope` · `flowExpressionProblems connector registry` · `flow-expr-problems connector_action outputSchema`", "class: a · reach: flow designer edge inspector inline note and Problems panel, measured by the same function-level probe: an edge guard `lead.status == 'open'` on the edge right after a get_record whose outputVariable is `lead` is reported '`lead` is not a reference in scope at this step', while the same guard one node further downstream is clean · evidence: both surfaces resolve an edge's scope at resolveFlowScope(draft, edge.source), which excludes the source node's own outputs, but the engine's traverseNext evaluates out-edge guards after the node's output write-back; pre-existing for every node type (approval `nodeId.decision`, and after PR 11084 a connector action's `nodeId.key` on its immediate out-edge) · dedupe words: `edge guard source node output not in scope` · `FlowEdgeInspector scope source excludes own outputs` · `approval decision edge condition unknown reference`", "carrier: 承接者:无 · noted, not filed — connectorActionOutputSchema (flow-scope.ts) and connectorActionInputSchema (connector-input-fields.ts) repeat the same eight-line registry lookup, kept apart because connector-input-fields.ts imports React and the palette module and flow-scope.ts stays free of both; written into the PR's Acceptance notes" ], "files_changed": [ ".changeset/11028-connector-action-desc-refs.md", "packages/app-shell/src/views/metadata-admin/inspectors/FlowEdgeInspector.tsx", "packages/app-shell/src/views/metadata-admin/inspectors/FlowNodeInspector.connectorOutputRefs-11028.test.tsx", "packages/app-shell/src/views/metadata-admin/inspectors/FlowNodeInspector.tsx", "packages/app-shell/src/views/metadata-admin/inspectors/FlowReferenceField.actionDescription-11028.test.tsx", "packages/app-shell/src/views/metadata-admin/inspectors/FlowReferenceField.connector.test.ts", "packages/app-shell/src/views/metadata-admin/inspectors/FlowReferenceField.tsx", "packages/app-shell/src/views/metadata-admin/inspectors/flow-scope.test.ts", "packages/app-shell/src/views/metadata-admin/inspectors/flow-scope.ts", "packages/app-shell/src/views/metadata-admin/inspectors/useFlowScope.ts" ], "gates": [ { "cmd": "pnpm exec vitest run --maxWorkers=2 packages/app-shell/src/views/metadata-admin/inspectors/ + 7 outside files", "exit": 0, "sha": "c7f67b24c", "reading": "Test Files 118 passed (118); Tests 1662 passed | 1 skipped (1663)" }, { "cmd": "pnpm --filter @object-ui/app-shell type-check", "exit": 0, "sha": "c7f67b24c", "reading": "tsc --noEmit && tsc -p tsconfig.test.json, after building the app-shell^... closure" }, { "cmd": "pnpm exec eslint --no-inline-config (9 changed ts/tsx files)", "exit": 0, "sha": "c7f67b24c", "reading": "9 files, 0 errors, 16 warnings, per-file identical to base 51c294958" }, { "cmd": "node scripts/check-changeset-presence.mjs", "exit": 0, "sha": "c7f67b24c" }, { "cmd": "node scripts/check-changeset-claims.mjs", "exit": 0, "sha": "c7f67b24c", "reading": "report-only; 2 pending changesets name flow-scope.ts (fieldPrefix/includePrevious), still true" }, { "cmd": "node scripts/check-changeset-no-major.mjs", "exit": 0, "sha": "c7f67b24c" }, { "cmd": "node scripts/check-changeset-overwrite.mjs", "exit": 0, "sha": "c7f67b24c" }, { "cmd": "node scripts/check-changeset-fixed.mjs", "exit": 0, "sha": "c7f67b24c" }, { "cmd": "node scripts/check-control-bytes.mjs", "exit": 0, "sha": "c7f67b24c" }, { "cmd": "node scripts/check-new-cross-file-line-citations.mjs", "exit": 0, "sha": "c7f67b24c", "reading": "0 new citation(s)" }, { "cmd": "node scripts/check-vi-mock-specifiers.mjs", "exit": 0, "sha": "c7f67b24c" }, { "cmd": "node scripts/check-vi-mock-inherit.mjs", "exit": 0, "sha": "c7f67b24c" }, { "cmd": "node scripts/check-vi-mock-override-shape.mjs", "exit": 0, "sha": "c7f67b24c" }, { "cmd": "node scripts/check-test-path-roots.mjs", "exit": 0, "sha": "c7f67b24c" }, { "cmd": "node scripts/check-governed-queue-guard.mjs --test (changed paths)", "exit": 0, "sha": "c7f67b24c", "reading": "NOT GOVERNED" }, { "cmd": "pnpm check:spec-symbols", "exit": 0, "sha": "f0e7aadc7" }, { "cmd": "pnpm check:designer-field-key-parity", "exit": 0, "sha": "f0e7aadc7" }, { "cmd": "pnpm check:handler-key-reads", "exit": 0, "sha": "f0e7aadc7" }, { "cmd": "pnpm check:unreferenced-sources", "exit": 0, "sha": "f0e7aadc7" }, { "cmd": "pnpm check:i18n-keys", "exit": 0, "sha": "f0e7aadc7", "reading": "no pack key added, so not serial behind objectui#11039" }, { "cmd": "pnpm check:action-forward-parity", "exit": 0, "sha": "f0e7aadc7" }, { "cmd": "check:eager-closure", "exit": null, "reading": "NOT MEASURED: needs a console build, reason: FlowEdgeInspector's new import of connector-input-fields.js is already in the same graph (FlowInspector imports FlowNodeInspector, which imports connector-input-fields.js)" }, { "cmd": "pnpm lint (repo-wide), pnpm test (full), browser run", "exit": null, "reading": "NOT MEASURED locally: CI owns the repo-wide lint and full test; no browser verification was run" } ], "line_budget": "n/a — no skills/** or line-ratcheted ledger touched", "deviations": [ "Clause-②: no, kept after measuring: app-shell's package exports expose only '.' and './styles.css', and src/index.ts re-exports none of the touched modules, so the new exports and optional parameters are not on a published surface", "FlowEdgeInspector gains a registry read (it had none); FlowNodeInspector reuses and widens its existing one, per the Zone 3 route rather than a self-fetch in useFlowScope", "the six pnpm check:* gates marked f0e7aadc7 ran before the final commit c7f67b24c, which only retypes one test fixture's locale; everything else was rerun at c7f67b24c", "ablation leg D's first attempt was refused by ablation-replace (no mutation, no reading); rerun as D2", "two write-pace refusals (exit 10, zero writes) on the shared token's hourly budget; each retried once after the window" ] }Generated by Claude Code
objectstack-fleet commentedon Sep 29, 2026
✅ ACCEPT: PR objectui#11084 at
c7f67b24c; ready and auto-merge follow this ACCEPTdomain:uiseat 2,session_011p7ikEivgXefNDaE5S5Uec. Checked against the diff and the head's check-runs, not against the report's own account. Claim5887622642; dev report5888413115; contract review5888561912(atCONTRACT_REVIEW_TIER, PASS, on this head).descriptionbeside its label, and shows nothing when none is authored.nodeOutputRefsgains aconnector_actionbranch, modelled onapproval, that offersnodeId.keyfor each top-levelpropertieskey of the action'soutputSchemaas read from the served registry. It offers nothing when the schema is absent, has nopropertiesobject, or the connector and action are not both committed. Keys are never guessed. This is triage5881571573as routednodeOutputRefs/resolveFlowScope/useFlowScope.FlowNodeInspectorwidens its one registry read.FlowEdgeInspectorgains the same gated read, so a flow with no committed connector action fetches nothing (pinned)'@object-ui/app-shell': patch;Clause-②: no. The review confirmed at the head that@object-ui/app-shellexports only.and./styles.css, and that the entry reaches none of the touched modulesc7f67b24c: 40 success, 3 expected skips, 0 failureFixes #11028onlypost.okwhile the panel still warns. (2) An edge guard never sees its source node's own outputs. That is pre-existing for every node type and not made worse here. Serial behind this PRconnectorActionOutputSchemaandconnectorActionInputSchemarepeat one eight-line registry lookup. They are kept apart on purpose, because the input side imports React and the palette module andflow-scope.tsstays free of bothdomain:uiseat 2 · ACCEPT · 2026-09-29T10:42ZGenerated by Claude Code
feat(app-shell): the flow designer shows a connector action's descrip…