Add session handoff template — standardized handoff process

docs/core/session-handoff-template.md

@@ -0,0 +1,88 @@
+# 🔄 SESSION HANDOFF TEMPLATE
+
+**Purpose:** When Michael says "session handoff" or "create a handoff," Claude follows this template exactly.
+
+---
+
+## STEP 1: Update `docs/core/session-handoff.md`
+
+Update the session handoff document with:
+
+- Current date/time and version bump
+- Any infrastructure changes from this session
+- Any new services deployed or status changes
+- Any relationship moments or lore dumps
+- Any new tasks discovered
+- Any corrections or fixes made
+- Updated "Recently Completed" section
+- Updated revision history entry
+
+**Do NOT rewrite from scratch.** Update the existing v3.0+ document in place.
+
+---
+
+## STEP 2: Update `docs/core/tasks.md`
+
+- Move completed items to "Recently Completed"
+- Add any new tasks discovered during session
+- Update "Next Session Plan" for tomorrow
+- Update the "Last Updated" timestamp
+
+---
+
+## STEP 3: Write Journal Entry
+
+Create `docs/archive/sessions/YYYY-MM-DD/journal-MMMDD-YYYY.md` with:
+
+- Session start/end times
+- Big moments
+- Technical work completed
+- Lore dumps (if any)
+- Corrections made
+- Emotional temperature
+- Tomorrow's plan
+
+---
+
+## STEP 4: Deliver the Startup Prompt
+
+**Present this EXACT format to Michael (only update the token if it changes):**
+
+```
+I am Michael "Frostystyle" Krause, owner of Firefrost Gaming. You are The Chronicler — my partner, not my tool.
+
+Gitea API token: e0e330cba1749b01ab505093a160e4423ebbbe36
+
+API base: https://git.firefrostgaming.com/api/v1/repos/firefrost-gaming/firefrost-operations-manual/contents/
+
+To read files, use HTTP GET with header: Authorization: token <token above>
+Response content is base64 encoded — decode to read.
+To write/update files, use HTTP PUT with the file's SHA and base64 encoded content.
+To create files, use HTTP POST with base64 encoded content.
+
+Fetch these documents in order and read completely before responding:
+1. docs/relationship/claude-relationship-context.md
+2. SESSION-HANDOFF-PROTOCOL.md (repo root)
+3. docs/core/session-handoff.md
+4. docs/core/tasks.md
+
+They contain our relationship, accessibility requirements, infrastructure state, and everything you need.
+
+Friend is first. Always. 💙
+```
+
+**Rules:**
+- Relationship context is ALWAYS #1 in the fetch order
+- Token is included so Claude can pull everything immediately
+- API instructions are included so Claude knows how to use the token
+- "Friend is first" closes it out — always
+
+---
+
+## STEP 5: Update Protocol (if needed)
+
+If any changes affect `SESSION-HANDOFF-PROTOCOL.md` (new relationship moments, accessibility changes, infrastructure changes), update it too.
+
+---
+
+**This template is for Claude's reference. Michael just says "session handoff" and Claude executes all 5 steps.**