Guides

Session continuity

A new session starts from nothing. The handoff note below is what it reads first, whichever tool opens the repository. To step away in the middle of a session instead, ab-pause-checkpoint saves a snapshot and keeps the execution state in docs/context/STATE.md current through ab-session-continuity. What a session reads when it starts, and in which order, is on How it works.

The Session Continuity section of docs/context/STATUS.md is the handoff note between sessions, and between tools:

## Session Continuity

**Last session:** 2026-03-04

**What was done:**
- Implemented JWT refresh token rotation
- Added rate limiting middleware
- Fixed Safari redirect loop (root cause: SameSite cookie attribute)

**What's remaining:**
- Integration tests for token refresh edge cases
- Load testing the rate limiter

**Start here:** Run the failing integration tests in tests/auth/refresh.test.ts

**Current state of the code:**
- Build: passing
- Tests: 2 failing (expected: the ones we need to write)
- Uncommitted changes: none

ab-session-wrap rewrites it at the end of each session from git history and the file system, never from an earlier summary, and ab-resume-session reads it first.