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
{{ message }}
Repository navigation
fix(mcp): retain mixed-event bindings for post-run resource release #53
PR #27 expires a relay binding when a selected run outcome is queued. If notify.events also requests thread.resource-released and provider-session.detached occurs afterward, that requested occurrence is missed. Hosted review PRRT_kwDOVfiJHc62itQE classifies this as P2.
Retain a mixed-event binding until the requested thread-level release can be observed, preserving one message per run outcome and per source occurrence. Cover release-before-result and result-before-release, plus restart/retry deduplication. Reuse existing relay state; no additional event migration is allocated.
Tracked under Chris's nonblocking P2 follow-up rule. Default notify does not request resource release and is unaffected. No service update.
Activity
chrisohearn commentedon Nov 13, 2026
Status: still valid. PR #27 (merged) relays run outcomes; mixed-event bindings are not retained yet. Ledger:
r3/event-routing(links this issue).Triage by the round-four GitHub hygiene pass (ledger key
r4/w7-github), 2026-11-13. Left open.