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
liveness ledger: action.onSuccess.navigate / openIn and translation.flows.screens are graded planned, but objectui already reads all three at the pinned sha #20296
Filing gate: ① a ledger verdict that is wrong on measurement. Three rows say planned, but a shipped reader exists in objectui at the .objectui-sha pin this repo builds against. The ledger UNDERSTATES them, so os lint's planned-row warning is a false alarm to authors who write these keys.
action.onSuccess.navigate / action.onSuccess.openIn (packages/spec/liveness/action.json:201, :207): objectui packages/core/src/actions/ActionRunner.ts. The path is readOnSuccessNavigation → navigateOnSuccess (:1447 at the pin), entered at :1415; it reads block.navigate (:1457) and block.openIn.
translation.flows.screens (packages/spec/liveness/translation.json:106): objectui packages/app-shell/src/views/FlowRunner.tsx:227, bundle[language]?.flows?.[flowName]?.screens?.[…]. The census reports it mounted at app-shell/src/hooks/useConsoleActionRuntime.tsx and apps/console/src/pages/developer/FlowRunsPage.tsx.
translation.flows.label has NO reader (census C14). It stays planned and is family card rank 15 (translation-flow-label), not this card.
Found by the #18900 ④ per-family census (finding 2). Filed by the domain:spec execution seat 1 (session_01Rjy9MeetSfq34PKn81CRiN, seat post #6017). ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim.
What the fix is (for the dispatch to confirm)
Re-verify each row to live, citing objectui @<pin> with file and symbol, plus the producer leg the ledger's rules require. The onSuccess pair has a materialized .default('self') on openIn, which the row's own note discusses.
Drop any authorWarn the planned status carried, and regenerate state-counts.md. pnpm check:liveness stays green.
A local scan of every open and recently closed objectstack issue and PR for onSuccess.(navigate|openIn)|flows.screens|navigateOnSuccess finds 3 hits: two seat posts and #19678 (closed, unrelated). None carries these rows.
Filing gate: ① a ledger verdict that is wrong on measurement. Three rows say
planned, but a shipped reader exists in objectui at the.objectui-shapin this repo builds against. The ledger UNDERSTATES them, soos lint's planned-row warning is a false alarm to authors who write these keys.reach:named readers. The seat read each one at the pinf8a9d0fb0596; the [Decision] Route declared≠enforced work by the SEAM, not the layer — aSeam:line on filing, vertical dispatch by default in the spec lane, automatic parent + sub-issues for spec↔objectui seams, Journey as a filter, bulk retirement per spec family, Console Pin Gate back to required (the maintainer's 「同意」 on the five-line batch, 2026-09-18) #18900 ④ census also read them at objectuimain6fa5f64a1.action.onSuccess.navigate/action.onSuccess.openIn(packages/spec/liveness/action.json:201,:207): objectuipackages/core/src/actions/ActionRunner.ts. The path isreadOnSuccessNavigation→navigateOnSuccess(:1447at the pin), entered at:1415; it readsblock.navigate(:1457) andblock.openIn.translation.flows.screens(packages/spec/liveness/translation.json:106): objectuipackages/app-shell/src/views/FlowRunner.tsx:227,bundle[language]?.flows?.[flowName]?.screens?.[…]. The census reports it mounted atapp-shell/src/hooks/useConsoleActionRuntime.tsxandapps/console/src/pages/developer/FlowRunsPage.tsx.translation.flows.labelhas NO reader (census C14). It staysplannedand is family card rank 15 (translation-flow-label), not this card.Found by the #18900 ④ per-family census (finding 2). Filed by the
domain:specexecution seat 1 (session_01Rjy9MeetSfq34PKn81CRiN, seat post #6017). ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim.What the fix is (for the dispatch to confirm)
live, citingobjectui @<pin>with file and symbol, plus the producer leg the ledger's rules require. TheonSuccesspair has a materialized.default('self')onopenIn, which the row's own note discusses.authorWarntheplannedstatus carried, and regeneratestate-counts.md.pnpm check:livenessstays green.planned(the spec: ListViewSchema(strictObject)没有 map 可视化配置块 —— map 列表视图的 titleField/locationField/相机整体不可声明,showcase 全部 marker 标题为 undefined #9340 / spec: declareviewModeonGanttConfigSchema— the contract half of objectui#5074's ruled both-branches wiring #9463 spec-first convention) and what flipped it: the reader landed and the pin absorbed it. [决策] SDUI 深链「导航即运行动作」(?runAction=<actionName>)要不要升格为 spec 声明的正式契约 #4848's flip note inapp.jsonis the precedent shape.Dedupe
A local scan of every open and recently closed objectstack issue and PR for
onSuccess.(navigate|openIn)|flows.screens|navigateOnSuccessfinds 3 hits: two seat posts and #19678 (closed, unrelated). None carries these rows.