110 -Add a queued-follow-up test proving input arriving during an active run applies to the next `agent_start`, not the active run.
110 +Add a queued-follow-up test proving interactive input arriving during an active lifecycle makes that lifecycle eligible and does not leak into the next run.
136 -- add minimal active/pending eligibility bookkeeping driven by `input`, `agent_start`, and `agent_end`
136 +- add minimal active/pending eligibility bookkeeping driven by `input`, `agent_start`, and `agent_end`; steering and follow-ups stay within the active lifecycle
33 33 The extension records input origin in extension-instance memory because `agent_end` does not expose it.
34 -It tracks the active run separately from queued follow-up origins so later input cannot reclassify an active run.
34 +It tracks pending pre-start input separately from the active agent lifecycle.
35 +Pi drains steering and queued follow-ups inside that active lifecycle, so direct interactive input received while active makes that lifecycle eligible without leaking into the next run.
35 36 Pi dispatches extension events serially, so this is event-order bookkeeping rather than cross-thread synchronization.
36 37 State is cleared on completion and session shutdown.
37 38 Nothing is written to disk or session history.