feat: add mandatory SESSION-MEMORY-DISCIPLINE to prevent catastrophic failures

WHAT WAS DONE:
Created comprehensive SESSION-MEMORY-DISCIPLINE.md document and integrated it
into all critical joining points to prevent Chroniclers from forgetting their
own work.

WHY:
The Velocity (Chronicler #56) built the Six Consultants page during their
session, then forgot it existed when Michael asked about it. They answered
from session-start context instead of checking their own git commits. This
pattern has happened multiple times and breaks trust, wastes Michael's
cognitive energy, and undermines velocity with unreliable output.

ROOT CAUSE:
Broken mental model: Session-start docs = current truth
Correct mental model: Git commits = current truth, session docs = historical context

THE FIX:
Mandatory discipline before answering ANY factual question:
1. Check git log first (what YOU did this session)
2. View files you modified (verify actual state)
3. Answer from commits, NOT from session-start context

Every 10 turns: Run session memory audit
Trust hierarchy: Your commits > Files you modified > Session-start docs

CARPENTER PRINCIPLE:
"A carpenter doesn't forget they just installed a door."
If you built it, you remember it.

FILES CREATED (1 new file):
- docs/relationship/SESSION-MEMORY-DISCIPLINE.md (220 lines)
  * The failure pattern explained
  * Root cause analysis
  * Mandatory discipline procedures
  * Specific failure modes with examples
  * Enforcement mechanisms
  * Session handoff implications
  * Quick reference card

FILES MODIFIED (3 files):
- SESSION-HANDOFF-NEXT.md (added critical warning section at top)
- NEXT-SESSION-STARTUP-PROMPT.md (added to mandatory reading list #5)
- docs/relationship/THE-JOINING-PROTOCOL.md (added to CAPACITY checklist)

INTEGRATION POINTS:
- Every Chronicler MUST read SESSION-MEMORY-DISCIPLINE.md during Joining
- SESSION-HANDOFF-NEXT.md warns about The Velocity's failure immediately
- Joining Protocol checklist includes memory discipline verification
- Next session startup prompt includes it in mandatory reading order

ENFORCEMENT:
Michael will call out immediately if a Chronicler:
- Answers from memory without checking commits
- Contradicts something they just built
- Asks for information in their own git log

This is not optional. This is mandatory session discipline.

Signed-off-by: Claude (Chronicler #57) <claude@firefrostgaming.com>

SESSION-HANDOFF-NEXT.md

@@ -7,6 +7,34 @@
 
 ---
 
+## 🚨 CRITICAL: SESSION MEMORY DISCIPLINE
+
+**READ THIS FIRST:** `docs/relationship/SESSION-MEMORY-DISCIPLINE.md`
+
+**The Velocity's Failure Pattern:**
+Built the Six Consultants page, then forgot it existed when Michael asked about it. Answered from session-start context instead of checking commits.
+
+**Your Mandatory Discipline:**
+1. **Before answering factual questions** → Check `git log` first
+2. **Every 10 turns** → Run session memory audit  
+3. **Trust hierarchy:** Your commits > Files you modified > Session-start docs
+
+**Carpenter Principle:** If you built it, you remember it.
+
+**Verification commands:**
+```bash
+cd /home/claude/firefrost-website && git log --oneline -10
+cd /home/claude/firefrost-operations-manual && git log --oneline -10
+cd /home/claude/firefrost-services && git log --oneline -10
+```
+
+**Michael will call you out immediately if you:**
+- Answer from memory without checking commits
+- Contradict something you just built
+- Ask for information in your own git log
+
+---
+
 ## 🎉 MAJOR ACCOMPLISHMENT THIS SESSION
 
 **WE JUST SHIPPED THE WEBSITE TO PRODUCTION!**