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

ai/context/project.md

@@ -44,6 +44,16 @@ The product work happens outside this repository, usually from another machine.
 - Not all entry points are reachable from visible UI
 - Validation often requires exploratory testing
 
+## Historical Slack patterns
+
+- XFlow SwiftUI migration discussions repeatedly covered Next-button visibility, markdown modal presentation, and custom nav pin/unpin behavior
+- Some historical pipeline failures were traced to Apex/ApexKit or Swift preview macro support in the consuming pipeline, not just XFlow itself
+- Jeff often requested explicit, polished wording for PR descriptions and cross-team messages
+- Historical discussions also surfaced recurring uncertainty around XFlow ownership boundaries versus consumer-app responsibility
+- Cross-team dependency issues sometimes involved security, token access, or external pipeline configuration rather than only iOS code changes
+- Historical AO and consumer bugs often turned out to be service/configuration issues, incomplete reproduction reports, or consuming-app integration issues rather than XFlow regressions
+- Historical integration work repeatedly involved XFlowViewMaker, FTBusiness, FTFrameworks, and Fid4 release/version coupling, especially when validating fixes in real consumer flows
+
 ---
 
 ## How This Workspace Is Used