136 -- add minimal candidate/prepared/active eligibility bookkeeping driven by `input`, `before_agent_start`, `agent_start`, and `agent_settled`; handled input cannot leak, while steering, retries, and follow-ups stay within the active lifecycle
136 +- add minimal candidate/prepared/active eligibility bookkeeping driven by `input`, `before_agent_start`, user `message_start`, `agent_start`, and `agent_settled`; handled input cannot leak, while accepted steering, retries, and follow-ups stay within the active lifecycle
34 34 The extension records input origin in extension-instance memory because `agent_end` does not expose it.
35 35 It records idle `input` as a candidate, then confirms it at `before_agent_start` only when Pi accepts the prompt.
36 36 This prevents handled input from leaking eligibility into extension-triggered runs that start without an `input` event.
37 -Pi drains steering and queued follow-ups inside the active agent lifecycle, so direct interactive input received while active makes that lifecycle eligible without leaking into the next run.
37 +Pi drains steering and queued follow-ups inside the active agent lifecycle.
38 +Interactive input received while active becomes a candidate, then a user `message_start` confirms Pi accepted it before making the lifecycle eligible.
39 +Handled active input therefore cannot create a notification or leak into the next run.
38 40 Pi dispatches extension events serially, so this is event-order bookkeeping rather than cross-thread synchronization.
39 41 State is cleared on completion and session shutdown.
40 42 Nothing is written to disk or session history.