In `maybeStartPager` (`internal/cmd/session.go`), the error path now closes the pager stdin pipe when `cmd.Start()` fails, preventing descriptor leakage on each failed pager launch.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Adds explicit cleanup in the `cmd.Start()` failure branch so the pipe created for pager stdin is closed immediately when pager startup fails (e.g., missing/non-executable `PAGER`), aligning failure-path resource handling with the normal success-path teardown.
Operators running Crush as a long-lived service (such as MCP integrations) will avoid accumulating leaked file descriptors when pager startup fails, reducing the chance of `too many open files` failures during repeated `session show/list/diff` calls; track long-running sessions for any remaining FD growth in other launcher error branches. The fix specifically closes the OS pipe immediately on `cmd.Start()` errors, so failure cases no longer diverge from the happy-path cleanup behavior.
Operators running Crush as a long-lived service (such as MCP integrations) will avoid accumulating leaked file descriptors when pager startup fails, reducing the chance of `too many open files` failures during repeated `session show/list/diff` calls; track long-running sessions for any remaining FD growth in other launcher error branches. The fix specifically closes the OS pipe immediately on `cmd.Start()` errors, so failure cases no longer diverge from the happy-path cleanup behavior.