[FEATURE] Removal of "/history" command breaks session recovery on interruption

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The removal of the /history command in favor of /session-report is a significant regression. /history provided retrospective visibility into what happened in previous sessions, whereas /session-report only works if you explicitly run it before the session ends.

The Problem:

• If a session crashes, disconnects, times out, or is otherwise interrupted before you run /session-report, there's no way to recover what was accomplished
• /session-report requires user discipline (remembering to run it), whereas /history was always available
• Session state is lost with no fallback mechanism

Expected Behavior (pre-change):

/history allowed viewing a summary of work from a previous session, even if the session ended unexpectedly.

Current Behavior:

• /session-report only captures state if explicitly invoked before session close
• No command exists to query historical session data
• Interrupted sessions leave no visible trail of what was attempted

Impact:

Users working on long-running tasks or in unstable environments lose context when sessions terminate unexpectedly. This is particularly problematic during active development where you may not have committed all intermediate state.

Proposed Solution

Restore a /history command (or similar) that can:

1. Show recent session summaries from a persistent log
2. Work even if the previous session ended unexpectedly
3. Be available as a safety net for session recovery

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_