You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[finding] the dogfood ledger row cel-action-disabled may be mis-measured: action:group / action:menu members evaluate a registered action's disabled without throwOnError and grey out on a fault #20470
Filing gate: ① a ledger row whose recorded fault face rests on evidence that does not cover it, with a named landing site. Reader: triage first (grade and route). Filed by the domain:spec seat 1 (session_01B3TqpoQbTAfG7G74GMDWNW, seat post #6017). The source is two at-tier records on PR #20420 (#20371): 5868826831 §③.2 raised it, and 5873778605 §③.4 re-read it at objectui dd3f7e1be356 and escalated it to a card. Read-only inference, not reproduced. Filed bare; no labels chosen.
The row
packages/qa/dogfood/test/expression-conformance.ledger.ts:378, id: 'cel-action-disabled' (mainfbeb56e4b or later). It records a registered action's disabled predicate as fail-soft-log.
Why its face may be wrong
The row's evidence is a console CHANGELOG line about the empty-disabled fix. That fix was about '' and empty envelopes, not faulting predicates; visibility-gate.ts:21-29 confirms this, per the record.
At objectui dd3f7e1be356, the MEMBER leaves of action:group and action:menu evaluate a registered action's disabled through useCondition without throwOnError (action-group.tsx:86 / :169, action-menu.tsx:108). On a fault, the member greys out.
Re-measure the row's fault face across the surfaces that evaluate actionObject.disabled at the live pin: the member leaves above, the grid row and bulk menus, and record:quick_actions. Then correct failPolicy and the evidence, or split the row by surface as #20420 did. If the measurement confirms fail-soft-log somewhere, say where.
Filing gate: ① a ledger row whose recorded fault face rests on evidence that does not cover it, with a named landing site. Reader: triage first (grade and route). Filed by the
domain:specseat 1 (session_01B3TqpoQbTAfG7G74GMDWNW, seat post #6017). The source is two at-tier records on PR #20420 (#20371):5868826831§③.2 raised it, and5873778605§③.4 re-read it at objectuidd3f7e1be356and escalated it to a card. Read-only inference, not reproduced. Filed bare; no labels chosen.The row
packages/qa/dogfood/test/expression-conformance.ledger.ts:378,id: 'cel-action-disabled'(mainfbeb56e4bor later). It records a registered action'sdisabledpredicate as fail-soft-log.Why its face may be wrong
disabledfix. That fix was about''and empty envelopes, not faulting predicates;visibility-gate.ts:21-29confirms this, per the record.dd3f7e1be356, the MEMBER leaves ofaction:groupandaction:menuevaluate a registered action'sdisabledthroughuseConditionwithoutthrowOnError(action-group.tsx:86/:169,action-menu.tsx:108). On a fault, the member greys out.cel-action-block-disabled, a page-componentaction:button's owndisabled) as fail-closed for the same reason. It deliberately left this row untouched, because the row is outside its claim.Landing site
Re-measure the row's fault face across the surfaces that evaluate
actionObject.disabledat the live pin: the member leaves above, the grid row and bulk menus, andrecord:quick_actions. Then correctfailPolicyand the evidence, or split the row by surface as #20420 did. If the measurement confirms fail-soft-log somewhere, say where.Dedupe words: cel-action-disabled, expression-conformance ledger, fail-soft-log, useCondition, throwOnError, action member disabled.
Generated by Claude Code