The proven factThe summarization stream received an aborted options signal. The exact upstream lifecycle owner still requires evidence.

Follow the signal, not the error text.

Clientcommand invokeexplicit cancel or lifecycle
→
GatewayRemote tokeninstall or disposal
→
Agentmaintenanceidle owner signal
→
AdapterABORTEDcaller signal is live evidence

Capture the first abort reason.

command signalUI or API caller

Join explicit actions and component lifetime.

Remote tokenGateway lifecycle

Record install generation, invoke, dispose, and reinstall.

maintenanceAgent lifetime

Capture cancel cause, wakeups, and Session boundary.

Host signalProcess lifetime

Correlate PID, profile reload, HMR, and shutdown.

Test one hypothesis at a time.

Stable Web pathOne tab, no HMR, no profile editsRecord Remote generation and every source signal.
versus
Non-Web pathSame Session, route, and contextOne attempt only. Compare the first owner to abort.

Keep the Session. Move the work.

PreserveExport the untouched Session and transaction IDs.
HandoffCarry goals, confirmed state, risks, and artifact paths.
ContinueStart a fresh Session without hidden full-history input.

Twelve repair gates.

  1. Long summary survives rerender.
  2. Event reconnect is harmless.
  3. User cancel stays prompt.
  4. Abort reason stays specific.
  5. Host shutdown closes durably.
  6. Reload cannot kill silently.
  7. Token generation is logged.
  8. One command, one LLM call.
  9. No summary lands on failure.
  10. End flushes before release.
  11. Owners remain distinct.
  12. Success points to summary.

Primary evidence.

Keep the complete incident runbook.

The canonical guide includes signal instrumentation, a controlled A/B matrix, safe continuity, unsafe shortcuts, and a complete incident bundle.

Read and star on GitHub