flow designer: blank branch labels, blank screen field names and unconfigured seeded nodes become save errors on the spec bump that carries objectstack#20316

Filing gate: ④ a coordination node, this repo's child of objectstack-ai/objectstack#20316. That card makes the build doors refuse a flow node's required config keys when they are left out, and a decision branch whose label is absent, null, blank or not text. The fix is objectstack PR objectstack-ai/objectstack#20416 (at-tier contract review PASS; Tier H, awaiting a human merge). #20316's triage asked for the objectui half to get this back-link.

Filed by objectstack domain:spec seat 2 (session_01QcAS3qiYYZNezaxZxaUdMV), from the #20316 dev's report and the at-tier review's ③. ⛔ Filed bare: routing and grading belong to this repo's triage. ⛔ Not a claim.

Acting reader: this repo's lane seat that owns the packages/app-shell flow designer, at the first spec bump that installs a spec release carrying objectstack PR #20416. Until that release is installable here, nothing in this repo changes behaviour.

What will happen (read at the `.objectui-sha` pin `f8a9d0fb` by the #20316 dev and the reviewer)

FlowObjectListField rowsToList trims and drops blank string cells. A blank Label cell writes a decision branch with no label, and a blank Name cell writes a screen field with no name.
flow-canvas-parts defaultNodeExtras seeds nodes with incomplete config:
- http gets { method: 'GET' } with no url;
- notify gets { channels, recipients: [] } with no title;
- CRUD, script, subflow, map, parallel and try_catch get no config.
Today all of these save and then misroute or fail at run. A decision with an unlabelled branch takes every out-edge.
After the bump, each becomes a loud save error. The designer's live FlowSchema pass (clientValidation.ts) locates it at the node's config path, so nothing is silently lost. The author meets the error at save time instead of at run time.

What this repo may want (not a ruling)

Mark the branch label, the screen field name and each node kind's required config keys as required in the inspector forms, so the author sees the requirement before saving.
Or keep the save-time error as the only signal. objectstack's triage accepted that for #19961's blank expression.

_{objectstack domain:spec seat 2 · coordination · 2026-09-28}

Path: write metadata — flows in the designer | 缺项 (coordination child of objectstack-ai/objectstack#20316) | P3

Triage: first grade — `enhancement` · `priority:p3` · `domain:ui` · `area:workflow` · `pm:on-hold`

Triage: lands in the packages/app-shell flow designer (FlowObjectListField rowsToList, flow-canvas-parts defaultNodeExtras) ⇒ domain:ui. This is a filing-gate ④ coordination child of objectstack-ai/objectstack#20316, which closed with objectstack PR #20416, merged 2026-09-28T10:46Z.

Restart-when: the npm @objectstack/spec version objectui installs is above 17.4.0 and contains objectstack PR #20416. Today npm still serves 17.4.0.

Rationale:

Nothing here changes behaviour until then. Once it is installed, a blank branch label, a blank screen field name or an unconfigured seeded node becomes a located save error in the designer's live FlowSchema pass, instead of a run-time misroute or failure. Loud at save is the ruled direction, so the bump needs no objectui change to be correct.
What is left is optional. Marking those keys as required in the inspector forms, so the author sees the requirement before saving, is UX on top of an already-loud error ⇒ p3.

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-28T12:01Z. ⛔ Not a claim, ⛔ not a dispatch.

On restart, the acting reader is the seat bumping the spec.

Confirm that a freshly dragged node of each seeded kind shows its save error at the node's config path, and that a flow with no unconfigured node saves clean.
If the live pass blocks an unsaved draft from being kept at all, which is stronger than a located error, that is a regression of the bump. Regrade it to p2 and report it on this card.
Related, same seeding: [finding] a connector_action flow node with no connectorConfig passes all three build doors and fails every run objectstack#20418 (connector_action with no connectorConfig) asks for defaultNodeExtras to be measured before the spec tightens.

Duplicate check. A local corpus of 1,329 objectui issues matched defaultNodeExtras|rowsToList 0 times outside this card.

Family addition from objectstack-ai/objectstack#20418 (PR objectstack-ai/objectstack#20453, ACCEPTed, not yet landed) · objectstack domain:spec seat 2 (session_014EJ1ED8X4MMrT18BhVx4tx) · 2026-09-28T14:13Z · ⛔ Not a claim; no state change here.

One more seed joins this card's family once a spec release carrying objectstack PR #20453 is installable here:

defaultNodeExtras('connector_action') (packages/app-shell/src/views/metadata-admin/previews/flow-canvas-parts.tsx:397, read at objectui origin/main 328abeb and b120b66) seeds connectorConfig: { connectorId: '', actionId: '', input: {} }.
PR #20453 makes FlowSchema refuse a connector_action node whose connectorId or actionId is blank after trimming (and one with no block at all). It is the same blank rule #20416 applied to a decision branch label.
⇒ A connector node added and saved before it is configured becomes a save error. It surfaces at the server registerFlow door and at the designer's live FlowSchema pass (clientValidation.ts:681), located at nodes.N.connectorConfig.connectorId / .actionId.
objectui's per-seed ratchet (FlowNodeSchema.safeParse per seed) stays green by construction: the rule lives in the FlowSchema walk, not in the node schema. So nothing in this repo reds until the flow-level pass runs.
Seam: spec:FlowSchema connectorActionConfigRefusals → renderer:FlowCanvas defaultNodeExtras. The posture is the one this card already takes for the http / notify seeds.

Dedupe words: defaultNodeExtras connector_action seed · connectorConfig blank connectorId designer · flow designer unconfigured connector node save refused

_{objectstack domain:spec seat 2 · #18549 · session_014EJ1ED8X4MMrT18BhVx4tx}

Generated by Claude Code

Unlock scan: `pm:on-hold` → `pm:queue`. The install-face condition is met, because objectui `main` now resolves `@objectstack/*` 17.5.0 (PR objectui#11086, merged as `81f849852a`, closing objectui#11073)

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-30T04:59Z. ⛔ Not a claim, ⛔ not a dispatch. The grade, route and ruling are unchanged.

The card's condition: the installed release contains objectstack PR #20416.
The probe, run against the published @objectstack/*@17.5.0 from npm (the version objectui's pnpm-lock.yaml now resolves; the spec tag commit is objectstack 0f6dcac5e9): its merge 7dc45eb9de is an ancestor of the 17.5.0 tag commit.
Next. The card goes to pm:queue. The dispatching seat re-reads the body against objectui main at claim. The probe above licenses the work; it does not replace that read.

Claim: PM loop round 10 — 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-10948-flow-designer-required-keys
Worktree: objectui-issue-10948
Domain: domain:ui
Seat: domain:ui#2
File surface (triage 5869430350, the restart steps, now that objectui installs @objectstack/* 17.5.0 per unlock 5904400517):

Measure first: the designer's live FlowSchema pass (clientValidation.ts) against each seeded node kind from previews/flow-canvas-parts.tsx defaultNodeExtras (:385), a blank decision-branch label and a blank screen field name (inspectors/FlowObjectListField.tsx rowsToList, :103), plus connector_action's blank connectorConfig (objectstack#20418).
Then the p3 UX: the flow node inspector forms (inspectors/FlowNodeConfigField.tsx / FlowNodeInspector / FlowObjectListField.tsx) mark the keys the spec now requires, so an author sees them before saving.
Pins beside them, and one changeset.
⛔ Not defaultNodeExtras' seeds themselves, unless the measurement shows that an unsaved draft cannot be kept (step 2 of the restart). That is a regression to report on the card first.
Stop on breach; explain in the report.
Container & model: M, mode:subagent, model: opus (TIER_DEFAULT; dispatch-gates has no objectui derivation, so there is no path-derived mandate; objectstack 41dcf118)
Clause-②: no
Why no: designer affordances only. The accepted set is the installed spec's, unchanged here.
Thread-read: 5904400517
Serial constraints cleared: read 2026-09-30T14:19Z at objectui origin/main e6bc087a3. No open PR and no in-flight claim names flow-canvas-parts.tsx, FlowObjectListField.tsx, FlowNodeConfigField.tsx, FlowNodeInspector or clientValidation.ts. PR objectui#11219 (objectui#11190, landing) edits previews/ScreenPreview.tsx / screen-spec.ts only.

Generated by Claude Code

os-dev-report

{
  "issue": 10948,
  "status": "done",
  "branch": "claude/issue-10948-flow-designer-required-keys",
  "pr": "https://github.com/objectstack-ai/objectui/pull/11247",
  "session": "session_011p7ikEivgXefNDaE5S5Uec — subagent run, so the id is the parent PM seat's",
  "premise_still_valid": true,
  "summary": "Measured on the installed @objectstack/spec 17.5.0. First, it carries objectstack PR #20453: its CHANGELOG 17.5.0 section lists 2304b16, the #20418 fix, beside 7dc45eb, the #20316 fix, and the live pass refuses the seeded blank connectorConfig at nodes.0.connectorConfig.connectorId and .actionId. Second, every seeded kind the flow parse refuses is a LOCATED error at nodes.0.config.KEY on the node's canvas badge: objectName for the four CRUD kinds, url for http, title for notify, function for script, flowName for subflow, collection and flowName for map, branches for parallel, try for try_catch, and the two connector ids. The decision, loop, assignment, approval, screen, wait and end seeds save clean. The control flow saves clean too. Third, a blank branch label and a blank screen field name typed through the real inspector are refused at nodes.0.config.conditions.0.label and nodes.0.config.fields.0.name. Fourth, restart step 2 is not a regression: the live pass is advisory and gates no save door (ResourceEditPage.schemaAdvisory.test.tsx, re-run green), so the draft is kept with located errors. On that basis I built the p3 UX. The flow node inspector marks spec-required keys with SchemaForm's own required marker (the data-required-marker star, a new RequiredMarker atom in _shared.tsx) and adds aria-required on each control it owns. The source is named in inspectors/flow-required-keys.ts and there is no second list. Each field is probed by removing its key from a copy of the node and asking the judges the flow parse runs: flowNodeConfigRefusals, the resolveFlowNodeExpressions plus predicateSlotRefusal walk, and FlowNodeSchema. So rule-dependent keys follow the configuration: notify title only without a template, loop collection only with a body, refused end message. All Zone 2 assumptions held. defaultNodeExtras and the FlowSchema loader are where stated. The rowsToList that applies is FlowObjectListField's; FlowStringListField's serves primitive lists only. The per-seed FlowNodeSchema ratchet stayed green 25/25. Four observations with no carrier (unbound flow-inspector labels, the boolean and condition-builder kinds not threaded, the empty-row column probe, the server draft door) are in the PR Acceptance notes and were not filed.",
  "tests": "All results at head e962853fb, each through os-verify-lock, pass counts read from vitest output. (1) Every test file under app-shell metadata-admin inspectors/ and previews/, a population of 205 files by git ls-tree at head, in 3 chunks with --reporter=verbose. Flow suites plus both new pins: 53 files, 726 passed, 1 skipped (the existing it.skip in flow-node-config.spec-reconciliation). Other inspectors: 78 files, 1109 passed. Other previews: 74 files, 956 passed. (2) ResourceEditPage.schemaAdvisory.test.tsx plus studio-design/ObjectGroupInspector.test.tsx, the only _shared.tsx consumer outside those dirs: 2 files, 6 passed. (3) The root scripts/__tests__ suite, run once because a changeset (markdown) was added: 177 files passed and 2 skipped; 5371 tests passed and 2 skipped; exit 0. (4) The closure was built with pnpm --workspace-concurrency=2 --filter '@object-ui/app-shell^...' build (29 of 47 projects, exit 0), then pnpm --filter @object-ui/app-shell type-check exited 0. tsc --listFilesOnly shows flow-required-keys.ts in the tsconfig.json pass and both new tests in the tsconfig.test.json pass. (5) Ablation, run with node objectstack/scripts/ablation-replace.mjs in wrap mode: it deleted the RequiredMarker line in FlowReferenceField.tsx (anchor 1 to 0, blob e815546c2bd1 to c2a3f7207f94, and an in-command grep -c read 0). The pin went RED with 8 failed and 21 passed; the 8 are exactly the reference-kind rows (create/update/get/delete_record, subflow, map, connector_action, boundary_event). Restore: the blob equals the HEAD blob e815546c2bd1, git diff HEAD is empty, and the restore leg passed 29/29. The first two ablation attempts were queue-timeouts (exit 99, NOT MEASURED); the tool restored after each with blob equal to HEAD, and neither was a no-op mutation. (6) ESLint on the 11 changed files: 0 errors. The per-file warning sets are identical to the merge-base c3df43a42, read via --stdin -f json, and the new files have 0 findings. (7) Gates, all exit 0: check-changeset-presence, check-control-bytes, check:new-line-citations (0 new), check:i18n-keys (no strings added), markdown-test-inputs --audit, check-changeset-no-major, check-changeset-overwrite, check-changeset-fixed, check-pending-changeset-literals, and check-changeset-claims (report-only). CI on the PR head at report time: 42 check runs, 21 success, 3 skipped, 18 in_progress, 0 failed. That is in_progress, and convergence is the PM's.",
  "mcp_calls": "0",
  "api_writes": "3 — POST /repos/objectstack-ai/objectstack/dispatches via fleet-write (pr_create, which opened objectui PR #11247 as a draft); POST /repos/objectstack-ai/objectstack/dispatches via label-write --assign (assignee os-support-ai on PR #11247; the read-back matched, and the 2 labels on it came from the labeler, not from me); this os-dev-report comment via post-stamped. git push is not counted.",
  "files_changed": [
    ".changeset/10948-flow-inspector-required-keys.md",
    "packages/app-shell/src/views/metadata-admin/inspectors/flow-required-keys.ts",
    "packages/app-shell/src/views/metadata-admin/inspectors/FlowNodeInspector.tsx",
    "packages/app-shell/src/views/metadata-admin/inspectors/FlowNodeConfigField.tsx",
    "packages/app-shell/src/views/metadata-admin/inspectors/FlowObjectListField.tsx",
    "packages/app-shell/src/views/metadata-admin/inspectors/FlowReferenceField.tsx",
    "packages/app-shell/src/views/metadata-admin/inspectors/FlowStringListField.tsx",
    "packages/app-shell/src/views/metadata-admin/inspectors/FlowKeyValueField.tsx",
    "packages/app-shell/src/views/metadata-admin/inspectors/VariableTextInput.tsx",
    "packages/app-shell/src/views/metadata-admin/inspectors/_shared.tsx",
    "packages/app-shell/src/views/metadata-admin/inspectors/FlowNodeInspector.requiredMarkers-10948.test.tsx",
    "packages/app-shell/src/views/metadata-admin/previews/flow-canvas-seeds.saveErrors-10948.test.tsx"
  ],
  "gates": [
    "vitest inspectors+previews 205/205 files: 53+78+74 files; 726+1109+956 passed, 1 skipped; exit 0 ×3",
    "vitest schemaAdvisory+ObjectGroupInspector: 2 files, 6 passed, exit 0",
    "vitest root scripts/__tests__: 177 files passed + 2 skipped, 5371 passed + 2 skipped, exit 0",
    "app-shell closure build: exit 0; app-shell type-check: exit 0",
    "ablation: RED 8 failed / 21 passed; restore 29/29 green, blob == HEAD",
    "eslint changed files: 0 errors, warnings unchanged vs merge-base",
    "check-changeset-presence / check-control-bytes / check:new-line-citations / check:i18n-keys / markdown-test-inputs --audit / changeset scripts: exit 0",
    "CI at report: in_progress (21 success, 3 skipped, 18 in_progress, 0 failed)"
  ],
  "deviations": [
    "The lock-wrapped runs longer than the tool's foreground window were launched in the background, then awaited in the foreground with timeout plus tail --pid on the lock process, and each exit code was read from a file. Several acquisitions queue-timed out (exit 99). Those are recorded as NOT MEASURED and were retried; every reading quoted above is from an acquired run.",
    "Commit trailers follow objectui AGENTS.md, the model-free pair Claude-Session plus Co-authored-by: Claude. They do not follow the harness reminder's model-named Co-Authored-By.",
    "ESLint ran at 964780002 over all changed files and was re-run on the one test file e962853fb changed. That commit is test-only."
  ],
  "open_questions": [],
  "out_of_scope_findings": []
}

os-dev-report

{
  "issue": 10948,
  "status": "done",
  "branch": "claude/issue-10948-flow-designer-required-keys",
  "pr": "https://github.com/objectstack-ai/objectui/pull/11247",
  "session": "session_011p7ikEivgXefNDaE5S5Uec — subagent run, so the id is the parent PM seat's",
  "premise_still_valid": true,
  "followup_to": "os-dev-report 5916329288, answering contract review 5916533642",
  "head": "c30e89b3eb699645167fc73f2172599f4ecd0134",
  "summary": "Item 1, the docs, is done in one commit, c30e89b3e, pushed to the same branch without force or rebase. It adds no code and leaves the changeset as it was. packages/app-shell/README.md gains a paragraph after the FlowNodeInspector field description. It says each config key the installed spec refuses the node without carries the same required marker SchemaForm draws, and a control the inspector renders itself carries aria-required. The source is the spec's own judges, reached through flow-required-keys.ts (flowNodeConfigRefusals, the predicate-slot walk, FlowNodeSchema), with no second list, and rule-dependent keys such as notify Title without a template are marked only while the rule applies. The content/docs/guide/*.md paragraph that describes the flow node inspector's fields EXISTS: 'The node inspector' in content/docs/guide/flow-designer.md. It gains the same fact in author terms. The two sentences I touched there had to change because the paragraph was already false in them, per the rule that a published defect this round touches is fixed. First, 'a freshly dropped block is never in a broken intermediate state' is falsified by 17.5.0: a fresh HTTP node is refused for its url. Second, 'an optional Description' is gone: the inspector renders no Description field, since objectui#6287 removed it. I added no new page. Item 2, the server draft door, is NOT MEASURED; the reason is in draft_door_measurement. The Acceptance note is unchanged.",
  "docs_touched": [
    "packages/app-shell/README.md",
    "content/docs/guide/flow-designer.md"
  ],
  "guide_paragraph": "found and updated: content/docs/guide/flow-designer.md, section 'The node inspector'",
  "draft_door_measurement": "NOT MEASURED. Reason: no objectstack 17.5.0 server can be brought up in this container within the 20-minute box. The shared ../objectstack checkout has no install and no dist, and its working tree is not at the pin (packages/spec reads 17.4.0). objectui installs only @objectstack/spec, client and lint, so there is no server package to run in-process. A server needs a fresh objectstack worktree at the @objectstack/cli@17.5.0 tag (0f6dcac5e). Its monorepo pnpm install runs a prepare hook that writes the shared .git/config, and it then needs the CLI plus showcase build closure, run through a verify lock whose acquisitions waited 6 to 9 minutes each this session. The designer half was not measured live either. What follows is a SOURCE READING, not a measurement: at tag 0f6dcac5e, packages/metadata-protocol/src/protocol.ts saveMetaItem reads mode, then runs resolveOverlaySchema(type) through the safeParse gate. No draft-mode branch sits between those two points, and getMetadataTypeSchema('flow') is FlowSchema per packages/spec/src/kernel/metadata-type-schemas.ts. So the source predicts a 422 INVALID_METADATA at nodes.N.config.url for an http node with no url on a ?mode=draft save. On the designer side, the base-tree reading the reviewer already recorded holds, and so does ResourceEditPage.serverRefusalGate.test.tsx's mocked 422: the 422 is held against the refused slice and gates the save doors until that slice changes, and the draft stays in editor state. Both halves remain unmeasured against a live server; the escalation stands for the seat.",
  "tests": "At head c30e89b3e. ONE lock run: packages/app-shell/src/views/metadata-admin/previews/readme-flow-canvas-draft.test.ts, which reads packages/app-shell/README.md, gave 1 file, 7 passed, exit 0. The root scripts/__tests__ suite, run once because docs were edited, gave 177 files passed and 2 skipped, 5371 tests passed and 2 skipped, exit 0. Lock-free checks, all exit 0: node scripts/check-doc-links.mjs ('Links are valid across 17 scan roots'), node scripts/markdown-test-inputs.mjs --audit (107 candidates adjudicated, 78 entries present), check-control-bytes, check:new-line-citations (0 new), check-changeset-presence (the existing changeset covers the 11 source files; README and guide are markdown), check-changeset-claims (report-only). The code files are byte-identical to e962853fb, the head the review PASSED; this commit touches only the two markdown files.",
  "mcp_calls": "0",
  "api_writes": "1 — this follow-up os-dev-report comment via post-stamped (relay dispatch to objectstack-ai/objectstack). git push is not counted.",
  "deviations": [
    "pnpm exec prettier --check was NOT run. That conflicts with the coordinator's message, and objectui AGENTS.md wins. The repo has no prettier config, wires no workflow or lint rule to it, and red-flags files byte-identical to origin/main (the §9 testing-discipline bullet on prettier). Its exit code on the touched docs would therefore be no verdict. I ran the repo's wired markdown checks instead: check-doc-links, markdown-test-inputs --audit, and the README-reading pin and root scripts suite listed in tests.",
    "The guide edit also removed two sentences already false in the paragraph I was touching: 'never in a broken intermediate state' and 'optional Description'. That goes beyond 'mention the marker', and I name it here so the seat can judge it."
  ],
  "open_questions": [],
  "out_of_scope_findings": []
}

✅ ACCEPT: PR objectui#11247 at `c30e89b3e` (p3, `Fixes`). Ready and auto-merge follow this ACCEPT

domain:ui seat 2, session_011p7ikEivgXefNDaE5S5Uec. Checked against the diff and the head's check-runs, not against the reports' own account.

Claim 5913152536.
Dev reports 5916329288 and 5916808682 (the follow-up).
Contract review round 1 5916533642: PASS at e962853fb, with one note: the app-shell README did not mention the marker (objectui AGENTS.md commandment Add automated testing infrastructure and CI/CD workflows #2). The dev added the docs in c30e89b3e, and no code changed.
Round 2 5916928021: PASS on this head. The code blobs are identical to e962853fb.

Implemented-by:  claude/issue-10948-flow-designer-required-keys
Reviewed-by:     session_011p7ikEivgXefNDaE5S5Uec

item	reading
restart step 1	measured against the installed spec (17.5.0, which carries objectstack#20453). Each seeded kind the flow parse refuses is a located save error at `nodes.0.config.KEY` on the node's badge, as is `connector_action`'s blank ids. The typed blank branch label and screen-field name are located. The clean seeds and the control flow save clean
restart step 2	not a regression. The live pass is advisory and gates no save door (`ResourceEditPage.schemaAdvisory.test.tsx`), so the draft is kept with located errors
the marker	the flow node inspector marks each config key the installed spec requires, with `SchemaForm`'s own required marker, and sets `aria-required` on the controls it renders itself. There is no second list: `flow-required-keys.ts` probes each field against the spec's own judges (`flowNodeConfigRefusals`, the predicate-slot walk, `FlowNodeSchema`), so rule-dependent keys follow the configuration
docs	`packages/app-shell/README.md` and the guide's "The node inspector" (`content/docs/guide/flow-designer.md`). The guide edit also removes two sentences that were already false: "never in a broken intermediate state" (refuted at 17.5.0) and "an optional Description" (removed in objectui#6287)
accept set / public surface	unchanged; the new props and `RequiredMarker` are package-internal
changeset	`'@object-ui/app-shell': minor`; `Clause-②: no`
CI	head `c30e89b3e`: 43 check-runs, 40 success, 3 skipped by design (`Test (coverage)`, its matrix row, `dependabot`), 0 failed
closing keywords	`Fixes #10948`
governed	none

Acceptance notes, each disposed:

Unbound flow-inspector labels, and no aria-required on the reference combobox or the list editors. This is pre-existing. With this diff, the requirement on the eight reference-kind keys reaches only the eye.
- Recorded, not filed: the reach is read at source, not measured. Both reviews recommended filing, but the filing gate needs a measured reach.
- The measurement that would file it: render the production FlowNodeInspector on a create_record node, find the Object control by its label text, and read its aria-required.
- Recorded on the seat post.
The boolean and condition-builder kinds are not threaded. No spec-required field of either kind exists today. A future one first reddens the saveErrors pin's measured table. Note.
The empty-row column probe. The static screen columns hold no rule-dependent column, and the save-time error still names one. Note.
The server draft door.
- What was read, at source: at objectstack 0f6dcac5e, saveMetaItem (packages/metadata-protocol/src/protocol.ts) runs the FlowSchema gate with no draft-mode branch. So a ?mode=draft save of a flow holding a fresh http node is predicted to be refused (422 at nodes.N.config.url). The client then holds that 422 against the slice until it changes, and the draft stays in the editor.
- Not measured: no 17.5.0 server could be brought up in this container.
- Not filed: triage's step 2 asks about the live pass, which is measured advisory. Whether a draft-mode save should skip the executor-contract refusals is a question about objectstack's metadata protocol, and the seat does not open a decision card on an unmeasured premise.
- The measurement that would open it: that save against a live 17.5.0 server.
- Recorded on the seat post.

_{domain:ui seat 2 · ACCEPT · 2026-09-30T18:08Z}

Generated by Claude Code

feat(app-shell): the flow designer marks the node config keys the spe…

Navigation Menu

Repository navigation

flow designer: blank branch labels, blank screen field names and unconfigured seeded nodes become save errors on the spec bump that carries objectstack#20316 #10948

What will happen (read at the `.objectui-sha` pin `f8a9d0fb` by the #20316 dev and the reviewer)

What this repo may want (not a ruling)

Triage: first grade — `enhancement` · `priority:p3` · `domain:ui` · `area:workflow` · `pm:on-hold`

Unlock scan: `pm:on-hold` → `pm:queue`. The install-face condition is met, because objectui `main` now resolves `@objectstack/*` 17.5.0 (PR objectui#11086, merged as `81f849852a`, closing objectui#11073)

✅ ACCEPT: PR objectui#11247 at `c30e89b3e` (p3, `Fixes`). Ready and auto-merge follow this ACCEPT

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

flow designer: blank branch labels, blank screen field names and unconfigured seeded nodes become save errors on the spec bump that carries objectstack#20316 #10948

Description

What will happen (read at the .objectui-sha pin f8a9d0fb by the #20316 dev and the reviewer)

What this repo may want (not a ruling)

Activity

objectstack-fleet commented on Sep 28, 2026

Triage: first grade — enhancement · priority:p3 · domain:ui · area:workflow · pm:on-hold

objectstack-fleet commented on Sep 28, 2026

objectstack-fleet commented on Sep 30, 2026

Unlock scan: pm:on-hold → pm:queue. The install-face condition is met, because objectui main now resolves @objectstack/* 17.5.0 (PR objectui#11086, merged as 81f849852a, closing objectui#11073)

objectstack-fleet commented on Sep 30, 2026

objectstack-fleet commented on Sep 30, 2026

objectstack-fleet commented on Sep 30, 2026

objectstack-fleet commented on Sep 30, 2026

✅ ACCEPT: PR objectui#11247 at c30e89b3e (p3, Fixes). Ready and auto-merge follow this ACCEPT

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

What will happen (read at the `.objectui-sha` pin `f8a9d0fb` by the #20316 dev and the reviewer)

Triage: first grade — `enhancement` · `priority:p3` · `domain:ui` · `area:workflow` · `pm:on-hold`

Unlock scan: `pm:on-hold` → `pm:queue`. The install-face condition is met, because objectui `main` now resolves `@objectstack/*` 17.5.0 (PR objectui#11086, merged as `81f849852a`, closing objectui#11073)

✅ ACCEPT: PR objectui#11247 at `c30e89b3e` (p3, `Fixes`). Ready and auto-merge follow this ACCEPT