Skip to content

liveness ledger: action.onSuccess.navigate / openIn and translation.flows.screens are graded planned, but objectui already reads all three at the pinned sha #20296

Description

@objectstack-fleet

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.

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)

Dedupe

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratebugSomething isn't workingdomain:specpriority:p3

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions