feat: Add historical context files for team members and update project documentation with Slack archive import details

ai/context/people/erik-reynolds.md

@@ -0,0 +1,24 @@
+# Erik Reynolds
+
+## Role
+
+Historical Fidelity collaborator in XFlow-related discussions.
+
+---
+
+## Known Context
+
+- Appears in discussions about XFlow manager behavior, consumer-vs-framework boundaries, and migration constraints
+- Raises implementation and sizing concerns in architecture-heavy conversations
+- Often comments on where responsibility lies between XFlow and consuming teams
+- Deep archive signal suggests strong familiarity with XFlow and Apex internals, especially ownership boundaries and migration tradeoffs
+- Often challenged weak assumptions about architecture, sizing, and framework responsibilities
+- Useful source when deciding whether a problem belongs in XFlow, Apex, or the consumer app
+
+---
+
+## Guidance
+
+- Treat Erik as a relevant source when historical context touches XFlow ownership boundaries or migration difficulty
+- Treat Erik as a high-signal source for framework architecture and responsibility boundaries
+- If future context clarifies the formal role or team, update this file directly