Session Handoff
Good handoff keeps the next agent from rediscovering the same state.
August 24, 2026 update
The backend handoff documentation now covers Supabase, authentication, Event Manager, ticketing, Stripe, media, email and SMS, analytics, environments, deployment rules, and high-risk areas.
What To Record
User request and final outcome.
Files changed.
Commands run and verification result.
Production systems touched.
Migration versions applied.
Browser/dashboard actions taken.
Commits and branches pushed.
Remaining manual checks.
Where To Record It
CURRENT_STATE.md
Compact current operating state and active verification context.
PROGRESS.md
Dated detailed work log.
feature_manifest.json
Feature verification state, only when relevant.
Git commit
Permanent code/docs change record.
Handoff Quality Bar
A future agent should be able to answer:
What is the current branch and latest relevant commit?
Was the change pushed, and to which branch?
Did production data or dashboard config change?
Which checks passed?
Which checks are still pending?
Is the work ready to rely on, or just staged?
GitBook-Specific Handoff
When docs change for GitBook, mention whether they were pushed to main. GitBook currently syncs from main, so a docs commit on dev alone will not update the visible GitBook space. Also mention whether .gitbook.yaml and SUMMARY.md were link-checked.
Screenshot And Video Handoff
When a task creates docs visuals, record:
source route or source recording flow
final asset path under
web/public/public URL and content type
GitBook page URL
live screenshot path or verification note
whether the docs manifest entry is passing or still pending
Last updated