Skip to content

Postmortem: recurring local dispatch quarantine and unshipped repair - #3683

Queued
brianduff wants to merge 1 commit into
mainfrom
boss/exec_18e8fe21ec502d60_85
Queued

brianduff wants to merge 1 commit into
mainfrom
boss/exec_18e8fe21ec502d60_85

Conversation

@brianduff

Copy link
Copy Markdown
Contributor

Summary

Document the recurring local dispatch quarantine, the repair that never started, and the missing escalation from a stalled execution to an acknowledged delivery obligation. Separate confirmed behavior from unavailable historical admission and abandonment evidence, and identify a two-second inconsistency in the supplied timestamps.

Incident 009 already exists, so this report is incident 010. This PR adds one Markdown document and changes no runtime behavior.

Evidence

  • Compared source and history from incident 008 PR Add postmortem: local dispatch quarantined by an app update mid-spawn #3403 to main at c3c7282: update lifecycle and engine process controller have no diff; quarantine storage was extracted while relevant hold semantics remain.
  • Inspected dispatch admission, abandonment, retry, attention, and shutdown code, plus public PRs Close recovery quarantine gaps found in post-merge review of #3478 #3485 and Remint never-started executions abandoned by deferral #3586. Historical main ca283c0 also does not clear automatic start in ghost-active healing.
  • Converted epoch 1794963106 using America/Chicago: 18:51:46 CST, two seconds after the supplied bundle replacement time. The document discloses this limit.
  • checkleft run: exit 0, 23 checks, no findings after formatting and correcting a source link.
  • Fresh local-rebase against main completed; branch contains one new document and no conflicted commits.
  • No runtime tests were run for this documentation-only change. Production state was not accessed; historical admission flags and the abandonment audit basis remain unavailable.

@brianduff
brianduff added this pull request to the merge queue Nov 18, 2026
Any commits made after this event will not be merged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant