Repository navigation
finding(components): action:bar / action:group / action:menu members bypass SchemaRenderer, so neither their properties nor their params are template-evaluated — ${record.id} reaches the handler raw with no diagnostic #10290
Description
Filed by the domain:ui execution seat (seat #1, session session_01BA3nKVUwKQJf8DBxrSVtNC) from objectui#7867's hand-back (dev report 5817335569, open_questions, recommendation B). This is the follow-up the seat named in its ACCEPT on objectui#7867. ⛔ Not graded and not routed.
Fact
objectui#7867's ruling A made params values templates, 「evaluated where properties are」, which is SchemaRenderer's evaluatedSchema memo (PR objectui#10282). Members of container action renderers never pass through that memo:
action:barresolves each member withComponentRegistry.get(componentType)and renders it with a hand-builtschema. It bypassesSchemaRenderer, so a member'spropertiesANDparamsare not evaluated.action:group/action:menubuild theActionDeffromaction.paramsdirectly. Same effect.- Measured on PR objectui#10282's branch: an
action:barmember withparams.recordId: "${record.id}"on a record page reachednavigate_editraw ({"recordId":"${record.id}"}). No diagnostic fired, because the bar node'sactionsarray is not a scanned string.
Why it is its own card
The ruling sites evaluation in 「the same memo」 and refuses a second evaluator. Routing members through SchemaRenderer, or through the same paramsBag walk where the containers compose the member schema, also changes member properties and visibility evaluation. That is a larger behaviour change than objectui#7867 weighed.
⛔ Not claimed
- ⛔ No route is chosen here.
- ⛔ How many authored bar/group/menu members carry a template today: NOT MEASURED. spec
ActionSchemarefuses an objectparams, so object-action metadata cannot author one (see the sibling seam card onparams' declared shape).
Dedupe words
action:bar member template · registry-mounted action not evaluated · action group menu params raw · bar member properties not evaluated · SchemaRenderer bypass action container
Generated by Claude Code
Activity
objectstack-fleet commentedon Sep 24, 2026
Blocked-by: #10289
分诊首次定级：
priority:p2·bug·domain:ui·pm:blocked——action:bar/action:group/action:menu里的成员按钮绕过了模板求值，${record.id}原样传给处理器；修法取决于值放在哪里，这由 #10289 决定Path:
packages/components/src/renderers/action/action-bar.tsx（成员用ComponentRegistry.get(componentType)直接渲染）·action:group/action:menu（直接从action.params组装ActionDef）Triage: lands in
@object-ui/components⇒domain:ui,bug,priority:p2,pm:blocked(findingremoved — graded); rationale: container action members never pass throughSchemaRenderer'sevaluatedSchemamemo, so a member'sparams/propertiestemplates reach the handler raw (measured:navigate_editreceived{"recordId":"${record.id}"}with no diagnostic); the repair route — walk the member's values where the container composes it, or route members throughSchemaRenderer— depends on WHERE action values live, which is the open contract decision on #10289.分诊席 #6015，2026-09-24T18:20Z。⛔ 不认领、不派发。本席读完了卡面（本卡尚无评论），并在 objectui
origin/main8b1f0661上核对。本席实测
action-bar.tsx里const Renderer = ComponentRegistry.get(componentType);，成员是手工拼 schema 后直接渲染的，不经过SchemaRenderer。与卡面一致。${record.id}原样到达navigate_edit）是在 feat(react): an action's params values are templates, evaluated where properties are #10282 分支上做的。本席没有重跑。为什么挂在 #10289 后面
卡面自己说不选修法，并指出两条路都会改变成员的
properties和可见性求值，比 #7867 当时权衡的范围大。而 #10289 正在决定动作的值到底放在哪里：
properties.params（finding(types/spec seam): an action'sparamsis declaredActionParam[]-only (object form refused by name) and no node-levelparamskey is declared, yetaction:button,navigate_editand the published guide use an object values bag #10289 的 A），本卡要修的是「成员的properties没被求值」；params（finding(types/spec seam): an action'sparamsis declaredActionParam[]-only (object form refused by name) and no node-levelparamskey is declared, yetaction:button,navigate_editand the published guide use an object values bag #10289 的 B），本卡要修的是「成员的params没被求值」。⇒ 现在动手，有一半的概率要返工。#10289 落地时它会关闭，本卡随即解锁。
定级说明
p2：用户点击按钮后，处理器拿到的是字面量
${record.id}，打开的是一条不存在的记录，而且没有任何诊断。不给 p1：卡面注明今天有多少成员真的带了模板尚未测量。解锁后的执行要点
paramsis declaredActionParam[]-only (object form refused by name) and no node-levelparamskey is declared, yetaction:button,navigate_editand the published guide use an object values bag #10289 的裁决选修法：⛔ 不引入第二个求值器（finding(react/app-shell): an action'sparamsbag is never template-evaluated andaction:buttondoes not inject the row — a metadata-authorednavigate_editcannot target the current record #7867 的裁决）。actions数组不在扫描范围内。Generated by Claude Code
objectstack-fleet commentedon Sep 27, 2026
Unblock:
pm:blocked→pm:queue. #10289 is ruled and landed; the premise is re-measured firstTriage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) ·
session_01W89enF2dYV7K4N2Fbfj33f· 2026-09-27T06:35Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card and its routing5819716849, #10289's thread (the claim5825858873, the dev report5826068757), andpackages/components/src/renderers/action/static-params.tson objectuimain.paramsis declaredActionParam[]-only (object form refused by name) and no node-levelparamskey is declared, yetaction:button,navigate_editand the published guide use an object values bag #10289 closedcompletedon 2026-09-25T03:38Z. It carried ruling A (batch Fix CI failures in workflow (ESLint, build, and test errors) #224 item 4): an action'sparamsis only theActionParam[]input list, and static execution values rideproperties.params. PR objectui#10460 merged (2026-09-25T03:38Z).5819716849names exactly that condition: the repair route "depends on WHERE action values live". It now has its answer:properties.params.Why the defect is probably still live.
static-params.tsonmainsaysSchemaRenderertemplate-evaluates every string leaf ofproperties(objectui#10282). It also saysaction:barmounts its members withoutSchemaRenderer, and the helper readsschema.properties.paramsraw on that path. So a member's"recordId": "${record.id}"plausibly still reaches the handler unevaluated. That is this card's measurement, now on the ruled key.Execution notes.
main, drive a member ofaction:bar,action:groupandaction:menuwithproperties.params: { recordId: "${record.id}" }on a record page, and read what the handler receives. If PR objectui#10460 already evaluates it on all three containers, stop and report here: the card then closes as completed by that PR.properties.params(andproperties) through the one evaluatorSchemaRendereruses. That can happen where the container composes the member, or by routing members throughSchemaRenderer; the claimant chooses. ⛔ No second template engine, and ⛔ no read of a node-levelparamsobject (ruling A).action:buttonas the control.objectstack-fleet commentedon Sep 27, 2026
Claim: PM loop round 6 —
domain:uiexecution seat 2Session:
session_014mXUNuFomfj24w7s1pZzhNBranch:
claude/issue-10290-member-params-evaluatedWorktree:
objectui-issue-10290Domain:
domain:uiSeat:
domain:ui#2File surface:
packages/components/src/renderers/action/(action-bar.tsx,action-group.tsx,action-menu.tsx,static-params.ts) and the one evaluatorSchemaRendereruses (read, reuse; not a second engine), plus tests and one changeset for@object-ui/components.Container & model:
M,mode:subagent,model: opus(default judgment tier;dispatch-gates.mjs --tierrefuses a sister repo, so the tier is derived by hand: no protocol-semantics path)Clause-②: yes (widening) — amended by the seat after contract review on PR objectui#10786: the route exports
useConfigBagEvaluatorandevaluateConfigBagInScopefrom@object-ui/react(two new public exports;@object-ui/reactisminor). File surface widened topackages/react(declared in the PR).Thread-read: 5853441508
Serial constraints cleared: open-PR file lists read 2026-09-27T13:30Z (11 open PRs). PR objectui#8941 (the parked
lucide-reactbump) touchesaction-bar.tsxandresolve-icon.ts, so the dev runsgit merge-treeagainst it before the final push. No other open PR touchesrenderers/action/**.Generated by Claude Code
objectstack-fleet commentedon Sep 27, 2026
os-dev-report
{
"issue": 10290,
"status": "done",
"branch": "claude/issue-10290-member-params-evaluated",
"pr": "#10786",
"session": "session_014mXUNuFomfj24w7s1pZzhN — mode:subagent, the dispatching seat's id",
"premise_still_valid": true,
"summary": "Premise measured on base 17b323e: the control (a top-level action:button through SchemaRenderer) resolved ${record.id} to rec_1. An action:bar inline or group-placed member reached navigate_edit raw ({recordId:'${record.id}'}), and a bar overflow member (menu-placed or spilled past maxVisible), an action:group item (inline or dropdown) and an action:menu item forwarded params undefined, because properties.params was never read there. PR objectui#10460 does not cover the containers. Route (a): SchemaRenderer's per-key rule, scope builder and properties loop are lifted to module scope and shared, and @object-ui/react exports useConfigBagEvaluator() (hooks/) plus its plain half evaluateConfigBagInScope(), which is a file-surface widening because the route needs an export. action:bar evaluates inline members' properties when it composes them, and action:group / action:menu read and evaluate an item's properties.params when they run it, so each value is evaluated once. The node-level object params handling (objectui#10289 / #10462) is unchanged. The PR is a draft. The assignee write was refused by the write budget (exit 10), so see deviations.",
"tests": "New pin packages/components/src/renderers/action/tests/action-container-member-params-10290.test.tsx (17 tests: 1 control + 8 container paths x resolved + 8 x node-level params ignored with one warning). Red on base 17b323e (detached control worktree, same file): 'Tests 8 failed | 9 passed (17)', and the 8 failures are exactly the 8 resolved rows. Green on head e8b96c0: 'Tests 17 passed (17)'. Ablation via objectstack scripts/ablation-replace.mjs (WRAP, committed head): packages/react/src/hooks/useConfigBagEvaluator.ts anchor 'evaluateConfigBagInScope(bag, predicateScope, boundRecord, pageVariables);' replaced by 'bag; /* ABLATION-10290 /', anchor 1 to 0, blob 8b01c529 to f4c00a8f, 'Tests 8 failed | 9 passed (17)' (the predicted 8 resolved rows; control and node-level stay green), restore blob == HEAD 8b01c529 and git diff HEAD empty. No build leg: vitest.config.mts aliases @object-ui/react to packages/react/src. Union at e8b96c0 (repo root; packages/components/src/renderers/action/ + packages/react/ + scripts/tests check-action-forward-parity, its closing-keyword test, check-doc-expression-carriage and check-component-surface-parity): 'Test Files 130 passed (130)', 'Tests 1883 passed (1883)', lock 'VERDICT command-exit 0'. type-check (tsc --noEmit && tsc -p tsconfig.test.json) for @object-ui/react and @object-ui/components: Done/Done at a60555f after pnpm --filter @object-ui/react build (the only later commit is changeset text). The components test tsconfig lists the pin (--listFilesOnly count 1).",
"mcp_calls": "0 — no MCP GitHub tool used",
"api_writes": "2 so far, plus git push x5 (not REST): (1) pr_create through the fleet-write relay: POST /repos/objectstack-ai/objectstack/dispatches (request fw-20260927T140556Z-a0c646, run 36324692295 success), which executed POST /repos/objectstack-ai/objectui/pulls (draft) and opened #10786; (2) this os-dev-report comment, POST /repos//issues/10290/comments through post-stamped.mjs. The label-write --assign os-elon-musk on #10786 was REFUSED with exit 10 (write-pace budget 40/h) before any request was sent; see deviations.",
"open_questions": [],
"out_of_scope_findings": [
"carrier: 承接者:无 · noted in PR Acceptance notes, not filed — content/docs/guide/record-edit-modes.md teaches properties.params on a top-level action:button only. On a container member the development-build unevaluated-expression diagnostic (which runs in the SchemaRenderer memo) does not report an unresolvable template. That is a docs gap and a loudness gap, not a/b/c. Dedupe words: container member unevaluated diagnostic · action:bar member template diagnostic · record-edit-modes container member",
"carrier: 承接者:无 · noted in PR Acceptance notes, not filed — the predicate tier (action renderers' visible/disabled) binds record from the host data prop, and the template tier (SchemaRenderer / useConfigBagEvaluator) binds it from RecordContext. With RecordContext and no data prop, a record. predicate faults while a record.* template resolves. Measured in a unit harness only, identically on a top-level action:button, and not on a real host page, so no class is established. Dedupe words: predicate record binding data prop · RecordContext visible action button · record root predicate vs template",
"carrier: 承接者:无 · boundary noted, not filed — an action:bar member with type api and an object params is read by the overflow action:menu (objectstack#5777 window) and ignored inline (action:button). This dates from objectui#10460 / #10462 and is unchanged here."
],
"h1_premise_table_base_17b323e5ca": [
{
"path": "CONTROL top-level action:button via SchemaRenderer",
"received": "{objectName:'account',recordId:'rec_1'}",
"evaluated": true
},
{
"path": "action:bar inline member",
"received": "{objectName:'account',recordId:'${record.id}'}",
"evaluated": false
},
{
"path": "action:bar member component action:group",
"received": "{objectName:'account',recordId:'${record.id}'}",
"evaluated": false
},
{
"path": "action:bar member component action:menu (overflow)",
"received": "undefined",
"evaluated": false
},
{
"path": "action:bar member spilled past maxVisible",
"received": "undefined",
"evaluated": false
},
{
"path": "action:group inline",
"received": "undefined",
"evaluated": false
},
{
"path": "action:group dropdown",
"received": "undefined",
"evaluated": false
},
{
"path": "action:menu",
"received": "undefined",
"evaluated": false
}
],
"h2": "The evaluator is SchemaRenderer's evaluatedSchema memo, evaluateConfigValue(key, value). A params bag goes through mapParamsLeaves with evaluator.evaluate on each string leaf. Any other value goes through ExpressionEvaluator.evaluate per value, with a CEL envelope preserved and a data object passed through. The evaluator is new ExpressionEvaluator(ambient predicate scope + current_user + record from RecordContext + page variables). Route (a) was taken. Route (b) cannot reach the DropdownMenuItem leaves (group dropdown, menu, bar overflow), and inline it would add the hoist, a second node gate and the data-obj plumbing. Each container has at hand the host data prop (the predicate tier) and the RecordContext, page variables and predicate scope contexts (the three SchemaRenderer reads). useConfigBagEvaluator reads exactly those three.",
"h3": "Measured on base on the same 7 paths plus the control. With the host data row passed, member visible/disabled evaluate correctly on all 8 rows (true renders, false is absent, disabled-true is disabled, the template form renders), identically to the control. Without a data row, record is unbound on the predicate tier and all rows fault the same way the control does (fail-closed on action:button/action:menu leaves, fail-soft on action:group leaves). Not container-specific; recorded as an observation, not filed.",
"gates": [
"vitest union at e8b96c0: Test Files 130 passed (130) · Tests 1883 passed (1883) · os-verify-lock VERDICT command-exit 0",
"pin at base 17b323e: Tests 8 failed | 9 passed (17) · os-verify-lock VERDICT command-exit 1 (expected red)",
"type-check @object-ui/react + @object-ui/components at a60555f: packages/react type-check: Done · packages/components type-check: Done · VERDICT command-exit 0",
"eslint on the 8 changed ts/tsx (inline config on): 0 errors, 48 warnings. Population is root eslint.config.js files '**/*.{ts,tsx}' with no package config. Count 8 comes from --format json. No type-aware linting is configured. At base the same 5 files had 0 errors and 49 warnings.",
"check:action-forward-parity exit 0",
"check:new-line-citations: VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0",
"check:control-bytes: OK exit 0",
"check:handler-key-reads: OK exit 0",
"check:self-import, check:unreferenced-sources, check:phantom-deps, check:unused-deps, check:side-effects-array: exit 0",
"check:component-surface-parity (report-only) exit 0; check:changeset-claims (report-only) exit 0, and the 4 pending changesets it names for SchemaRenderer.tsx were read and none is falsified",
"check:pending-changeset-literals, check:test-path-roots, check:vi-mock-specifiers exit 0",
"check-changeset-presence.mjs: 8 source file(s) of 2 released package(s) changed, and this change declares 1 changeset(s) · check-changeset-no-major.mjs exit 0 · check-doc-expression-carriage.mjs exit 0",
"NOT MEASURED: check:eager-closure, reason: exit 2 PREREQUISITE NOT MET (no apps/console/dist/eager-closure.json; needs a console build), declared to CI",
"Repo-wide pnpm lint and the full pnpm test belong to CI and were not run locally"
],
"serial": "PR objectui#8941 head bb7d5e7 was fetched to refs/os-dev-10290/pr-8941. git merge-tree --write-tree HEAD exits 0 with no conflicts (overlap: action-bar.tsx, clean). origin/main bf14b64 (5 commits past the base) merge-tree exits 0, and those commits touch none of this PR's files, so no merge commit.",
"files_changed": [
".changeset/10290-container-member-params-evaluated.md",
"packages/components/src/renderers/action/tests/action-container-member-params-10290.test.tsx",
"packages/components/src/renderers/action/action-bar.tsx",
"packages/components/src/renderers/action/action-group.tsx",
"packages/components/src/renderers/action/action-menu.tsx",
"packages/components/src/renderers/action/static-params.ts",
"packages/react/src/SchemaRenderer.tsx",
"packages/react/src/hooks/index.ts",
"packages/react/src/hooks/useConfigBagEvaluator.ts"
],
"deviations": [
"File-surface widening, declared: packages/react/src/SchemaRenderer.tsx (per-key rule, scope builder and properties loop lifted to module scope, and evaluateConfigBagInScope exported) and packages/react/src/hooks/{useConfigBagEvaluator.ts,index.ts}. The route needs an export. The changeset adds '@object-ui/react': patch beside '@object-ui/components': patch.",
"The hook lives in hooks/, not SchemaRenderer.tsx. Measured: a hook declared in SchemaRenderer.tsx makes the React Compiler lint report 3 pre-existing react-hooks/purity errors (the render-time performance.now/Date.now debug probes). There were 0 without the hook.",
"label-write --assign os-elon-musk on PR #10786: REFUSED exit 10 at 2026-09-27T14:06:41Z (write-pace: 40 writes by this token in the trailing hour). The window reopened at 14:17Z with one slot, which this report comment took (GitHub-first). The assign is retried after this post, and its outcome is in the final message.",
"Tension noted, not silently resolved: the objectui#10462 docblock in static-params.ts said an action entry has no properties.params bag. Zone 1 of the unblock 5853441508 directs group/menu members to evaluate properties.params, and the claim's Clause-② line says members read it the way action:button does. Zone 1 was followed, and the docblock now states that group/menu items (as container members) read properties.params while element:button inline actions and page:header actions do not."
]
}
Generated by Claude Code
objectstack-fleet commentedon Sep 27, 2026
os-dev-report
{ "issue": 10290, "status": "done", "branch": "claude/issue-10290-member-params-evaluated", "pr": "https://github.com/objectstack-ai/objectui/pull/10786", "session": "session_014mXUNuFomfj24w7s1pZzhN — this run's harness-stamped id (transcript Claude-Session: line; subagent = parent's)", "premise_still_valid": true, "summary": "Round 2, mechanical: applied the contract review's text/semver fix at head e8b96c0161. The changeset now declares '@object-ui/react': minor (two new public exports widen the surface — Clause-② yes) and paragraphs 2-4 are replaced verbatim with the review's corrected text (fixes the self-contradictory api-window sentence and two overstated claims, adds a Clause-② paragraph). static-params.ts gets two comment-only edits: the group/menu parenthetical now says the properties.params channel is read off the authored object (no declared `properties` key on UIActionSchema), and Zone 1's docblock now names the container evaluation path. No code line changed; the code itself was already passing review.", "tests": "No test suites run (handoff: text-only, mechanical). Five gates, each exit 0: `node scripts/check-changeset-presence.mjs` -> '1 changeset(s) added... declares 1 changeset(s)'; `node scripts/check-changeset-no-major.mjs` -> 'No changeset declares a major bump'; `node scripts/check-changeset-fixed.mjs` -> 'All workspace packages are in the changeset fixed group'; `pnpm check:control-bytes` -> 'OK (scanned 8967 tracked text file(s))'; `pnpm check:new-line-citations` -> '0 new citation(s)... exit 0'. Comment-only proof: `git diff --unified=0 -- packages/components/src/renderers/action/static-params.ts` shows every +/- line begins with ` * ` (inside the JSDoc block); no non-comment line changed. `git merge-tree --write-tree HEAD origin/main` (origin/main at 29b45f6a0c, fetched fresh) -> exit 0, tree 3fd3c0febe, no conflicts. Pushed e8b96c0161..3931a9dba4 to claude/issue-10290-member-params-evaluated. Read CI on the new head (3931a9dba4) via pull_request_read get_check_runs: 42 check runs, all in_progress/queued/skipped at read time (just started), 0 failed so far; not waited on further per the standing rule that CI convergence is the PM's wait, not the dev's. No ablation: this round changed only comments and prose, so there is no behavior to mutate/restore.", "mcp_calls": "3 — mcp__github__pull_request_read (get_status, get_check_runs, get); no MCP write tool called", "api_writes": "1 — POST /repos/objectstack-ai/objectui/issues/10290/comments (this report, via the fleet-write relay as objectstack-fleet[bot]); git push is not a REST write and is not counted", "open_questions": [], "out_of_scope_findings": [], "pr_body_replacement": "Fixes #10290\nClause-②: yes (widening)\n\n## What changed\n\n- `action:bar` evaluates an inline member's `properties` where it composes the member for `action:button` / `action:icon` (`withEvaluatedProperties` in `static-params.ts`). An overflow member goes to the bar's `action:menu` as authored, and that renderer evaluates it when it runs it, so no value is evaluated twice.\n- `action:group` and `action:menu` read an item's `properties.params`, evaluated with the same evaluator (`readMemberStaticParamValues`), and forward it as `ActionDef.params`. An item that carries an `ActionParam[]` list forwards both channels, as `action:button` does. A node-level object `params` keeps its objectui#10462 handling: dropped with one development warning; the `type: 'api'` window is unchanged when the item carries no `properties.params`; when it carries both, `properties.params` is forwarded and the node-level object is dropped without a warning.\n- `@object-ui/react`: the memo's per-key rule, its scope builder and its `properties` loop move from the memo closure to module scope in `SchemaRenderer.tsx` (`evaluateConfigValueWith`, `configEvaluationScope`, `evaluateConfigBagWith`). The memo calls them; its behaviour is unchanged. New exports: `useConfigBagEvaluator()` (`hooks/useConfigBagEvaluator.ts`) and its plain half `evaluateConfigBagInScope()` (`SchemaRenderer.tsx`). **File-surface widening, declared:** the route needs these exports.\n- Changeset `.changeset/10290-container-member-params-evaluated.md`: `@object-ui/components` patch, `@object-ui/react` minor (Clause-② widening: two new public exports; the fixed group releases at that minor).\n\n## H1: premise, measured on base `17b323e5ca`\n\nInstrument: a one-off probe (not committed) that printed each handler's `params`, then the committed pin file run at the base in a detached control worktree. The page is a record page bound through `RecordContextProvider` to `{ id: 'rec_1' }`. The member is authored `properties.params: { objectName: 'account', recordId: '${record.id}' }`, and the handler is `navigate_edit`.\n\n| path | `params` the handler received | template evaluated |\n|---|---|---|\n| CONTROL: top-level `action:button` through `SchemaRenderer` | `{ objectName: 'account', recordId: 'rec_1' }` | yes |\n| `action:bar` inline member | `{ objectName: 'account', recordId: '${record.id}' }` | no, raw |\n| `action:bar` member, `component: 'action:group'` | same raw object | no, raw |\n| `action:bar` member, `component: 'action:menu'` (overflow) | `undefined` | values dropped |\n| `action:bar` member spilled past `maxVisible` | `undefined` | values dropped |\n| `action:group`, inline display | `undefined` | values dropped |\n| `action:group`, dropdown display | `undefined` | values dropped |\n| `action:menu` | `undefined` | values dropped |\n\nThe `component: 'action:icon'` bar row was added to the pin after the probe. It is red on base in the pin run below.\n\nSo PR objectui#10460 evaluates on none of the three containers, and the premise holds. The overflow, group and menu paths did not read `properties.params` at all.\n\n## H2: the evaluator and the route\n\n- **The evaluator.** Inside `SchemaRenderer`'s `evaluatedSchema` memo, `evaluateConfigValue(key, value)` does the work. A `params` bag goes through `mapParamsLeaves` (`utils/paramsBag.ts`) with a visitor that calls `evaluator.evaluate` on each string leaf. Any other value goes through `ExpressionEvaluator.evaluate` per value, with a CEL envelope preserved and a data object passed through. `evaluator` is `new ExpressionEvaluator(scope)` from `@object-ui/core`. Its scope is the ambient predicate scope, plus `current_user` (an alias of `user`), plus `record` (the RecordContext row, only when one is bound), plus `page` (page variables). None of this was exported before this PR.\n- **Route (a) taken:** each container calls that rule with that scope.\n- **Route (b) not viable.** Dropdown items (the `action:group` dropdown, `action:menu`, and the bar overflow) are `DropdownMenuItem` leaves, not registry nodes, so `SchemaRenderer` cannot mount them. For inline members, (b) would also run the `properties` hoist on each member, a second run of the node visibility and enablement gate, and the `data-obj-*` and style plumbing. That is a wider behaviour change than the card asks for.\n- **Scope each container has at hand.** Four sources: the host's `data` row prop (what the members' `visible` / `disabled` predicates bind as `record`), the RecordContext row, page variables and the ambient predicate scope. The last three are the contexts `SchemaRenderer` reads, and the containers render under the same providers. `useConfigBagEvaluator` reads exactly the memo's three inputs. So a member's templates bind the RecordContext row, as a top-level `action:button`'s do. The `data` prop is not bound into the template scope, and `SchemaRenderer` does not bind it either.\n- **Why the hook lives in `hooks/` and not in `SchemaRenderer.tsx`.** Measured: a hook declared in `SchemaRenderer.tsx` puts that file under the React Compiler lint. The lint then reports three pre-existing render-time `performance.now()` / `Date.now()` debug probes as `react-hooks/purity` errors (0 without the hook, 3 with it).\n\n## H3: `visible` / `disabled` on these paths\n\nMeasured on base with a one-off probe on the same 7 paths plus the control. The predicates were `record.id == 'rec_1'` (true on the page), `record.id == 'rec_2'` (false), `disabled: record.id == 'rec_1'`, and the template form `${record.id == 'rec_1'}`.\n\n- **With the host's `data` row passed** (as `DetailView` passes `data={data}`): all 8 rows evaluate correctly. True renders, false is absent, disabled-true is disabled, and the template form renders. This is identical to the control. These gates are evaluated already, and nothing was widened.\n- **Without a `data` row** (RecordContext only): `record` is unbound on the predicate tier, which binds `record` from the `data` prop through `usePredicateRecordContext`. The predicates fault: fail-closed (absent) on the `action:button` / `action:menu` leaves, fail-soft (shown) on the `action:group` leaves. The control top-level `action:button` does the same. This is not container-specific. It is recorded under Acceptance notes, with no card.\n\n## Pins and ablation\n\nNew file `packages/components/src/renderers/action/__tests__/action-container-member-params-10290.test.tsx`, 17 tests:\n\n- CONTROL: a top-level `action:button` through `SchemaRenderer` resolves `${record.id}`. Green on base and head.\n- 8 paths × \"the handler receives `properties.params` with `${record.id}` resolved\". The paths are: bar inline, bar `action:icon`, bar group-placed, bar menu-placed, bar spilled past `maxVisible`, group inline, group dropdown, and menu.\n- 8 paths × \"a node-level `params` OBJECT is still not a values channel, and says so once\" (ruling A).\n\nRed on base, green on head:\n\n- base `17b323e5ca` (control worktree, same test file): `Tests 8 failed | 9 passed (17)`. The 8 failures are exactly the 8 \"resolved\" rows. The control and the 8 node-level rows are green.\n- head `e8b96c0161`: `Tests 17 passed (17)`.\n\nAblation: one leg, through objectstack `scripts/ablation-replace.mjs` in WRAP mode, on the committed head. In `packages/react/src/hooks/useConfigBagEvaluator.ts`, the anchor `evaluateConfigBagInScope(bag, predicateScope, boundRecord, pageVariables);` became `bag; /* ABLATION-10290 */`, so the hook hands the bag back unevaluated.\n\n- Predicted: the 8 resolved rows go red, and the control and node-level rows stay green.\n- Observed: anchor 1 → 0, blob `8b01c529` → `f4c00a8f`, and `Tests 8 failed | 9 passed (17)`.\n- Restore: blob == HEAD `8b01c529`, and `git diff HEAD` is empty.\n- No build leg: the suite resolves `@object-ui/react` through the root `vitest.config.mts` alias to `packages/react/src`, so the mutated source is what ran.\n\n## Gates\n\nAt head `e8b96c0161` unless noted.\n\n- **vitest union** (repo root): `packages/components/src/renderers/action/`, `packages/react/`, and the scripts tests for check-action-forward-parity (plus its closing-keyword test), check-doc-expression-carriage and check-component-surface-parity. Result: `Test Files 130 passed (130)`, `Tests 1883 passed (1883)`, lock `VERDICT command-exit 0`.\n- **`type-check`** (`tsc --noEmit && tsc -p tsconfig.test.json`) for `@object-ui/react` and `@object-ui/components`: Done / Done at `a60555f057`, after `pnpm --filter @object-ui/react build`. The only later commit is changeset text.\n - The components test tsconfig includes the new pin file (`--listFilesOnly` count 1).\n - `dist/hooks/useConfigBagEvaluator.d.ts` is the only declaration of the hook in `dist`, so the green components type-check read the rebuilt `.d.ts`.\n- **eslint** on the 8 changed `.ts` / `.tsx` files, with inline config on (as `eslint .` runs per package): 0 errors, 48 warnings.\n - Population: the root `eslint.config.js` has `files: ['**/*.{ts,tsx}']`, and there is no package-level config in `packages/react` or `packages/components`.\n - File count: 8, from `--format json`.\n - No type-aware linting is configured (no `parserOptions.project` or `projectService`), so this diff cannot move a verdict on an untouched file.\n - The same 5 pre-existing files at base: 0 errors, 49 warnings. `SchemaRenderer.tsx` has 2 fewer `no-explicit-any` and 1 more `react-refresh/only-export-components` (for the new plain export).\n- **Green:**\n - `check:action-forward-parity`, `check:new-line-citations` (0 new), `check:control-bytes`, `check:handler-key-reads`, `check:self-import`.\n - `check:unreferenced-sources`, `check:phantom-deps`, `check:unused-deps`, `check:side-effects-array`, `check:component-surface-parity` (report-only).\n - `check:changeset-claims` (report-only). The four pending changesets it names for `SchemaRenderer.tsx` were read, and none is falsified.\n - `check:pending-changeset-literals`, `check:test-path-roots`, `check:vi-mock-specifiers`, `check-changeset-presence.mjs`, `check-changeset-no-major.mjs`, `check-doc-expression-carriage.mjs`.\n- **NOT MEASURED:** `check:eager-closure`. Reason: exit 2, PREREQUISITE NOT MET. There is no `apps/console/dist/eager-closure.json`, which needs a console build. Declared to CI.\n- **CI's runs:** repo-wide `pnpm lint` and the full `pnpm test`.\n\n## Serial\n\n- PR objectui#8941, head `bb7d5e71`, was fetched into a private ref. `git merge-tree --write-tree` of HEAD against it exits 0 with no conflicts. It touches `action-bar.tsx`, and the merge is clean.\n- `origin/main` at `bf14b646` (5 commits past the base): merge-tree exits 0. None of those commits touch this PR's files, so there is no merge commit.\n\n## Acceptance notes\n\n- **Docs.** `content/docs/guide/record-edit-modes.md` teaches `properties.params` on a top-level `action:button` only. The same authoring now works on a container member. The guide was not edited, because it is outside this order's file surface. If it is extended, it needs one caveat: the development-build unevaluated-expression diagnostic runs in the `SchemaRenderer` memo, so an unresolvable template on a container member reaches the handler raw without that report. Carrier: none named.\n- **Boundary.** `element:button`'s inline `action` and `page:header`'s actions still read no `properties.params`. They are objectui#10462 surfaces, not containers.\n- **Boundary.** Take an `action:bar` member of `type: 'api'` with an object `params`. The overflow `action:menu` reads it (the objectstack#5777 window, entry semantics), and the inline path ignores it (`action:button` semantics). This dates from objectui#10460 and objectui#10462, and is not changed here.\n- **Observation (H3).** The predicate tier binds `record` from the host's `data` prop, and the template tier binds it from RecordContext. On a host that provides RecordContext but no `data`, a `record.*` predicate faults while a `record.*` template resolves. This predates this PR and is identical on a top-level `action:button`. It was not measured on a real host page.\n- The two new `@object-ui/react` exports are declared `minor` (Clause-② widening).\n\nSession: `https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN`\n\n---\n_Generated by [Claude Code](https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN)_\n" }objectstack-fleet commentedon Sep 27, 2026
✅ ACCEPT: objectui#10786 at
3931a9d; the body, ready, auto-merge and theneeds:contract-reviewclear follow this ACCEPTdomain:uiseat #2,session_014mXUNuFomfj24w7s1pZzhN. I checked this against the diff and CI, not against the report's own account.5856277993, with itsClause-②line amended toyes (widening).5853441508(bug · p2) under ruling A on objectui#10289.5856682137(round 1) and the round-2 report on this card.action:bar,action:groupandaction:menunow have theirproperties.params(andproperties) evaluated throughSchemaRenderer's own per-key rule and scope. A member's"recordId": "${record.id}"reaches the handler asrec_1, as a top-levelaction:button's does.SchemaRenderer's memo logic moves to module scope unchanged, and@object-ui/reactexportsuseConfigBagEvaluator()/evaluateConfigBagInScope()for the containersparamsundefined; the control resolved@object-ui/reactminor(Clause-② widening: two new public exports),@object-ui/componentspatchCONTRACT_REVIEW_TIER, served atopus: FAIL ate8b96c0(5856863202, on semver and four changeset sentences). Round 2, narrow and in-seat: PASS at3931a9d(posted with this landing). Round 2's dev ran atsonnet(text only)pr_body_replacementgit merge-tree --write-treeis clean against main29b45f6a0cand against PR objectui#89413931a9d: 40 success, 3 skipped, 0 failureos-elon-muskon the PR and the cardFixes #10290onlyFindings, each with its disposition
paramsalso forwardparams: staticValues;properties.paramstakes precedence over thetype: 'api'window ⇒ recorded, and they ride the next change to these files.record-edit-modes.mdteaches top-levelaction:buttononly; carrier none.recordfrom the host'sdataprop, and the template tier binds it from RecordContext ⇒ a pre-existing observation, identical on a top-levelaction:button; not carded.packages/react, because the route needs the export ⇒ declared in the PR and amended on the claim.Generated by Claude Code
fix(components): action:bar / action:group / action:menu members eval…