FA-35102 / Notification interfaces / Member archive

Time-limited notification content expiry: open-action from valid · case 02

The open-action event leaves a notification in completed instead of action-pending.

Member previewVariant 2 · 3 implementations · 34 checks per implementation

Case contract

Time-limited notification content expiry is a bounded visual-notification workflow with mutable policy state {'deadline': 20, 'now': 5, 'started': None, 'completed': False}. Its default transition relation is {('valid', 'deadline-near'): 'expiring', ('expiring', 'deadline-reached'): 'expired', ('valid', 'open-action'): 'action-pending', ('action-pending', 'deadline-reached'): 'pending-at-expiry', ('pending-at-expiry', 'action-success'): 'completed', ('pending-at-expiry', 'action-failure'): 'expired-action-error', ('expired', 'deadline-extension'): 'revalidation-pending', ('revalidation-pending', 'extension-validated'): 'valid', ('revalidation-pending', 'extension-rejected'): 'expired', ('completed', 'late-expiry'): 'completed'}; domain inputs can suppress or redirect transitions and update policy fields, as specified in solve. Different-generation events are inert. Batches apply in order. Optional observe returns the selected policy field alongside the phase.

Why this case matters

Visual notification lifecycle ordering can leave an inbox or toast showing the wrong actionable state even when transport succeeds.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
valid / open-action	`"completed"`	`"action-pending"`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.