Regression: onSessionEnd hook behaviour changed

[QuinnBast]

Describe the bug

After the most recent update to Copilot CLI (1.0.25), the onSessionEnd hooks have introduced a regression.

Previously, the onSessionEnd hooks would be fired any time the copilot agent had sent a response message back to the user's input request and would be marked as a "completed". However, after the update, these copilot hooks are no longer firing whenever the copilot agent sends a response.

Now, the onSessionEnd is only firing when the user terminates their session entirely instead of also firing whenever the agent sent a response.

Affected version

1.0.25

Steps to reproduce the behavior

1. Type a fake input command like "Hello"
2. See a session start hook
3. Wait for a response
4. No session end hook is fired

The session end hook used to trigger in the previous version ^

Expected behavior

The session end hook should fire. If this was not intended, then a new hook should be created once the assistant sends it's final reply

Additional context

No response

[examon]

This was an intentional change in v1.0.25 (fix for #991): sessionEnd now fires once per session as documented. For per-turn completion notifications, use the agentStop hook, which fires when the agent naturally stops after each response. If you'd like us to revisit, please comment with details.