Skip to content

[Frontend][Inbox] Single and batch triage pollers can overwrite newer summary state #2301

Description

@Chris0Jeky

Found by the independent review of PR #2299 and tracked as a non-blocking MEDIUM under the bounded review policy.

The batch-triage poll replaces the whole Inbox list with a delayed list snapshot. If the separate single-item triage poll has already written a fresher terminal summary for an unrelated row, that delayed batch response can overwrite it and leave the summary stale until another refresh. Cached terminal detail remains correct and no capture/proposal write is affected.

Acceptance:

  • prevent a delayed batch-list response from regressing a newer summary written by the single-item poll or an explicit load;
  • use a shared revision/generation guard or a monotonic per-item merge rather than adding another uncoordinated timer;
  • prove the single-item-versus-batch race deterministically;
  • preserve batch completion, scope teardown, and terminal degraded-notice reconciliation.

Refs #2230 and PR #2299.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority IIIValuable but unscheduled: residuals, tech-debt, performance, depth work.bugSomething isn't workingfrontendPrimary implementation impact in Vue/TypeScript UI and client runtime.

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions