Why

Gateway shutdown/restart is an operationally sensitive boundary where lifecycle observability is important for uptime tooling. This PR emits explicit shutdown lifecycle events so monitoring and guardrail hooks can react consistently.

Detailed Changes

• Added internal gateway lifecycle events in close flow:
  • gateway:shutdown
  • gateway:pre-restart (when restart is expected)
• Hook execution is best-effort and does not block shutdown path
• Added focused tests covering gateway lifecycle event emission

Related Links and Issues

• Existing source PR (split from): feat(hooks): fixed and adding various agent, messaging, system and compaction hooks #9761
• Closes Feature request: gateway:shutdown and gateway:pre-restart hook events #6711

Greptile Overview

Greptile Summary

This PR adds two new internal hook emissions to the gateway shutdown flow (gateway:shutdown and conditional gateway:pre-restart) and updates the hooks documentation accordingly. It also introduces a focused unit test that mocks internal hook dispatch and asserts the emitted event contexts during a restart-oriented shutdown.

The changes plug into the existing internal hook registry (src/hooks/internal-hooks.ts) by constructing InternalHookEvents and calling triggerInternalHook(...) early in createGatewayCloseHandler, before the rest of the shutdown teardown proceeds.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk.
• The change is narrowly scoped to emitting new internal hook events and updating docs/tests. The previously-raised issues (sessionKey misuse, shutdown hook await semantics, timer cleanup, docs wording) are already addressed in the current head SHA, and no new definite correctness regressions were identified in the modified code paths.
• No files require special attention