Session Handoff Strategies

When a session ends before the work is complete — context window full, time to stop for the day, or switching to a higher-priority task — you need a handoff strategy that lets the next session pick up where this one left off without rebuilding all the context. The handoff document is the mechanism.

Before ending a session, tell Claude: "Write a handoff document summarizing: what was completed, what remains, what decisions were made, and what files were modified." Claude produces a structured summary that captures the session's accumulated context in a few hundred words. Save it as a file (handoff.md or in a working-notes/ directory). The next session starts by reading the handoff document and immediately has the context it needs to continue. The handoff document costs a few hundred tokens to read — rebuilding the context from scratch would cost thousands.

## Session Handoff — Auth Implementation

### Completed
- User model and migration (src/db/migrations/001_users.sql)
- Login route (src/routes/auth.ts — POST /login)
- Password hashing utility (src/utils/hash.ts)

### Remaining
- Registration route (POST /register) — schema defined, not implemented
- Auth middleware — design decided: JWT in Authorization header
- Frontend auth state — no work started

### Decisions Made
- Using bcrypt for password hashing (not argon2 — simpler dependency)
- JWT expiration: 24 hours, refresh token: 7 days
- Tokens stored in httpOnly cookies, not localStorage