feat(api): add session timeline API endpoint#31
Merged
Conversation
added 3 commits
March 8, 2026 19:34
Expose lifecycle timeline events through the sessions API with UUID validation, session existence checks, internal-safe access control, and eventCount summaries, plus tests and docs for deterministic ordering and response contract. Made-with: Cursor
Add current session state snapshot to the timeline endpoint by reading the sessions row, preserving 404 semantics for unknown sessions and updating tests/docs to reflect the enriched response payload. Made-with: Cursor
Emit a structured timeline.fetch log on successful timeline reads so operators can trace session timeline lookups and returned event volumes. Made-with: Cursor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GET /api/sessions/:sessionId/timelinereturning{ sessionId, eventCount, events }400), session existence checks (404), and internal-safe API key gating (401when configured)db.getSessionTimeline) and add route tests for deterministic order + empty timelines?type=...)Test plan
pnpm --filter api test -- test/routes/sessions.test.ts test/events/getSessionTimeline.test.tsMade with Cursor