fix: Return empty events for resume with missing/cursorless session

[evansenter]

Summary

• Fix get_events(resume=True) to return empty events when session doesn't exist or has no saved cursor
• Prevents flooding users with stale events from the beginning of time
• Add debug logging for production visibility when resume is skipped

Problem

When --resume was used with a session that either:

1. Doesn't exist in the database, OR
2. Exists but has no saved last_cursor

The code would fall through to the default behavior, returning ALL events from the beginning (event #1 from December 2025). This broke the prompt-events.sh hook which relies on --resume for incremental polling.

Solution

Add an early return when resume=True but no cursor is available, returning empty events with a valid next_cursor for future polling. This treats the session as "caught up".

Test plan

• Added test_resume_with_nonexistent_session_returns_empty
• Added test_resume_with_session_without_cursor_returns_empty
• All 265 existing tests pass
• Manual verification with non-existent session ID

Fixes #99

🤖 Generated with Claude Code

[claude]

Prompt: evansenter/dotfiles/.../claude-review.md

Code Review

Summary

This PR fixes a bug where get_events(resume=True) would return all events from the beginning of time when a session doesn't exist or has no saved cursor. The fix adds an early return that returns empty events with a valid next_cursor for future polling, treating the session as "caught up".

Issues Found

Critical

None

Important

None

Suggestions

None

Verdict

APPROVE - Code looks good, no issues found. The fix is minimal and targeted, correctly addressing the bug described in #99. The two new tests provide good coverage for both failure scenarios (nonexistent session and session without cursor). The debug logging is properly guarded since session_id is verified truthy before the slicing operation.

---

Automated review by Claude Code

[claude]

Prompt: evansenter/dotfiles/.../claude-review.md

Code Review

Summary

This PR fixes a bug where get_events(resume=True) would flood users with stale events from the beginning of time when a session doesn't exist or has no saved cursor. The fix adds an early return that treats the session as "caught up", returning empty events with a valid next_cursor for future polling.

Issues Found

Critical

None

Important

None

Suggestions

None

Verdict

APPROVE - The fix is minimal and correctly addresses the issue described in #99. Key observations:

1. Correct behavior: Returning empty events with a valid next_cursor allows future polling to work properly - the session will start receiving only new events from that point forward.

2. Good test coverage: Two new tests cover both failure scenarios (nonexistent session and session without cursor), and verify both the empty events and valid next_cursor behavior.

3. Safe string slicing: The session_id[:8] in the logging is safe because the condition if resume and session_id and cursor is None ensures session_id is truthy before the else branch executes.

4. Consistent with existing patterns: The return structure matches the normal return at line 456-458, maintaining API consistency.

---

Automated review by Claude Code