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

ai/context/people/aylwing-olivas.md

@@ -0,0 +1,24 @@
+# Aylwing Olivas
+
+## Role
+
+Repeated Fidelity collaborator visible across multiple historical Slack channels.
+
+---
+
+## Known Context
+
+- Appears in technical discussions about XFlow, SwiftUI limitations, navigation architecture, and dependency risk
+- Surfaces cross-team constraints such as security or token access issues affecting pipeline work
+- Frequently adds architectural framing rather than only status updates
+- Often reframes implementation problems at the architecture/system-design level rather than the ticket level
+- Repeatedly advised on state machines, navigation architecture, off-screen rendering, and long-term maintainability tradeoffs
+- Common escalation point when the team needs a technical sounding board or higher-level design critique
+
+---
+
+## Guidance
+
+- Treat Aylwing as a useful source for higher-level technical framing and dependency risk context
+- Treat Aylwing as a strong reviewer for architecture direction, refactor scope, and risk framing
+- If future context clarifies the formal team or title, update this file directly

ai/context/people/bruce-meeks.md

@@ -0,0 +1,21 @@
+# Bruce Meeks
+
+## Role
+
+Repeated Fidelity collaborator in XFlow-related work.
+
+---
+
+## Known Context
+
+- Reviewed and approved XFlow work repeatedly in historical threads
+- Sometimes covered XFlow iOS issues while others were unavailable
+- Later context suggests Bruce primarily worked on Android while still remaining a useful cross-platform contact
+- Relevant in release coordination, PR review, and parity discussions between iOS and Android
+
+---
+
+## Guidance
+
+- Treat Bruce as a useful source for cross-platform context and historical PR/review state
+- If future context clarifies the formal role/team, update this file directly

ai/context/people/david-delagneau.md

@@ -0,0 +1,23 @@
+# David Delagneau
+
+## Role
+
+Repeated Fidelity collaborator in historical Slack threads.
+
+---
+
+## Known Context
+
+- Appears heavily in pipeline, Jenkins, SonarQube, test-reporting, and release-process work
+- Later historical activity also includes Sparta SDK proof-of-concept implementation and framework setup work
+- Often provides implementation updates, process notes, and operational debugging context to Jeff
+- Frequently handled CI/CD, Jenkins, reporting, and repo/setup tasks while Norman focused on SDK and consumer debugging
+- Later archive activity shows him taking lead on SpartaSDK setup, JSON decoding, and repo/bootstrap work
+
+---
+
+## Guidance
+
+- Treat David as a relevant source for CI/CD, release-process, and framework-setup context
+- Treat David as especially relevant for Jenkins, SonarQube, Pod/repo setup, and Sparta SDK bootstrapping context
+- If future context clarifies the formal role or team, update this file directly

ai/context/people/derian-cordoba.md

@@ -0,0 +1,23 @@
+# Derian Cordoba
+
+## Role
+
+Historical Fidelity collaborator in project support discussions.
+
+---
+
+## Known Context
+
+- Appears in historical pipeline, Jenkins, and documentation conversations
+- Helped document pipeline work and supported notification/credential troubleshooting
+- Collaboration signal is real but current formal role remains unclear from the archive
+- Often paired with David on CI/CD and notification-related work
+- Showed up when the team needed operational documentation, release-process notes, or pipeline triage support
+
+---
+
+## Guidance
+
+- Treat Derian as a relevant collaborator for historical pipeline/debugging context
+- Treat Derian as most relevant for historical CI/CD coordination and documentation support
+- If future context clarifies the formal role or team, update this file directly

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

ai/context/people/gurram-santosh.md

@@ -0,0 +1,25 @@
+# Gurram Santosh
+
+## Role
+
+Project-related contact involved in issue discussions.
+
+The exact formal role is not yet confirmed in workspace memory.
+
+---
+
+## Known Context
+
+- Repeatedly appears in AO-related testing, screenshot validation, and issue verification conversations
+- Often serves as a consumer-side validator or reporter when the team needs confirmation that a fix worked in their environment
+- Relevant when tracking whether an issue still reproduces, whether a release build contains a fix, or whether additional consumer validation is needed
+
+---
+
+## Guidance
+
+If future communication makes Santosh's role explicit, update this file with:
+
+- team or function
+- relationship to Fidelity work
+- whether the person is a reporter, tester, partner, or stakeholder

ai/context/people/index.md

@@ -7,10 +7,40 @@
 ## Known People
 
 - [jeff-dewitte.md](./jeff-dewitte.md)
-  Current direct manager for the active Fidelity project.
+  Current direct manager for the active Fidelity project; repeated communication gatekeeper and scope shaper in historical XFlow work.
 
-- [santosh.md](./santosh.md)
-  Project-related contact seen in issue discussions. Exact formal role should be clarified if it becomes important for repeated communication.
+- [norman-arauz.md](./norman-arauz.md)
+  Frequent XFlow collaborator in historical Slack threads; primary implementer/investigator across SwiftUI, AO/Fid4 bugs, and release work.
+
+- [david-delagneau.md](./david-delagneau.md)
+  Repeated historical collaborator on pipeline, CI/CD, and Sparta/SwiftUI proof-of-concept work, especially around Jenkins, reporting, and framework setup.
+
+- [bruce-meeks.md](./bruce-meeks.md)
+  Repeated XFlow collaborator who often reviewed PRs, covered iOS work during absences, and later shifted primarily toward Android.
+
+- [jason-mandozzi.md](./jason-mandozzi.md)
+  Repeated collaborator tied to XFlowViewMaker, FTPlanning/Fid4 integration, release support, and major architectural transitions.
+
+- [aylwing-olivas.md](./aylwing-olivas.md)
+  Repeated historical collaborator who surfaces architectural concerns, SwiftUI constraints, and cross-team dependency risks.
+
+- [erik-reynolds.md](./erik-reynolds.md)
+  Historical collaborator focused on XFlow manager behavior, integration boundaries, migration effort sizing, and framework responsibility boundaries.
+
+- [gurram-santosh.md](./gurram-santosh.md)
+  AO-related contact who often validates fixes or confirms whether issues still reproduce in consumer environments.
+
+- [raj-sundararaj.md](./raj-sundararaj.md)
+  Repeated collaborator involved in AO issue triage, release coordination, and backlog/story management around XFlow work.
+
+- [quy-mai.md](./quy-mai.md)
+  Scrum/contact point who repeatedly managed backlog state, points, and closure expectations for Fidelity work.
+
+- [tim-longfield.md](./tim-longfield.md)
+  FTPlanning-side contact relevant when issues crossed from XFlow into consumer-framework ownership.
+
+- [derian-cordoba.md](./derian-cordoba.md)
+  Historical collaborator in pipeline and documentation work, especially around CI/CD support and operational notes.
 
 ## Usage
 

ai/context/people/jason-mandozzi.md

@@ -0,0 +1,21 @@
+# Jason Mandozzi
+
+## Role
+
+Repeated Fidelity collaborator in XFlow and consumer-integration work.
+
+---
+
+## Known Context
+
+- Closely associated with XFlowViewMaker, Fid4/FTPlanning integration, and release/version work
+- Frequently authored or owned implementation branches later reviewed by others
+- Showed up repeatedly in architecture, eventing, navigation, and consumer-facing integration discussions
+- Often served as an important source of context on historical implementation choices inside XFlow and related consumer flows
+
+---
+
+## Guidance
+
+- Treat Jason as a high-signal source for XFlowViewMaker and consumer integration history
+- If future context clarifies the formal role/team, update this file directly

ai/context/people/jeff-dewitte.md

@@ -6,6 +6,15 @@ Current direct manager for the active Fidelity project.
 
 ---
 
+## Historical Collaboration Pattern
+
+- Repeatedly acted as reporting manager, reviewer, and communication gatekeeper across multi-year XFlow work
+- Frequently rewrote PR descriptions, Jira updates, and cross-team messages before they were sent
+- Regularly redirected work based on release risk, consumer pressure, or manager/stakeholder expectations
+- Often pushed for explicit distinction between framework bugs, consumer bugs, service issues, and scope creep
+
+---
+
 ## Communication Requirements
 
 - Native US English
@@ -36,3 +45,4 @@ Good updates usually clarify:
 - Story titles, points, and scope discussions with Jeff are often worth remembering
 - Jeff approvals can change what belongs in current state or work-item memory
 - Jeff feedback is often a signal to tighten wording before communicating externally
+- Jeff often asks for evidence, reproduction detail, and exact next action before approving external communication

ai/context/people/norman-arauz.md

@@ -0,0 +1,22 @@
+# Norman Arauz
+
+## Role
+
+Frequent Fidelity/XFlow engineer collaborator in historical Slack threads.
+
+---
+
+## Known Context
+
+- Repeated day-to-day implementer/investigator across XFlow SwiftUI, AO/Fid4 bugs, version bumps, analytics, and pipeline debugging
+- Often coordinated with Jeff on scope, descriptions, approvals, and manager-ready wording
+- Frequently investigated consumer-reported issues directly in Fid4 and sample-app parity checks
+- Often produced detailed technical findings first, then asked Jeff to polish or approve external wording
+- Exact formal role may need confirmation if used outside workspace memory
+
+---
+
+## Guidance
+
+- Treat Norman as a strong source for historical implementation detail, reproduction findings, and release-process context
+- If later communication clarifies the formal team/title, update this file directly

ai/context/people/quy-mai.md

@@ -0,0 +1,20 @@
+# Quy Mai
+
+## Role
+
+Scrum/contact point repeatedly involved in backlog and process management.
+
+---
+
+## Known Context
+
+- Repeatedly asked for clearer Jira/state management, points, and backlog hygiene
+- Often confirmed whether work should remain in backlog, be canceled, or be reframed as separate stories
+- Relevant for sprint structure, story cleanup, and expectation-setting around what counts as production or release-priority work
+
+---
+
+## Guidance
+
+- Treat Quy as an important source for process expectations, backlog cleanup, and story framing
+- If future context clarifies the formal title/team, update this file directly

ai/context/people/raj-sundararaj.md

@@ -0,0 +1,20 @@
+# Raj Sundararaj
+
+## Role
+
+Repeated Fidelity collaborator involved in project coordination and active issue triage.
+
+---
+
+## Known Context
+
+- Repeatedly surfaced or assigned XFlow/AO issues and asked for current status
+- Involved in release coordination, validation follow-up, and backlog movement
+- Relevant when the team needed to align issue ownership, repro state, or urgency with consumer-side expectations
+
+---
+
+## Guidance
+
+- Treat Raj as a useful contact for issue routing, AO coordination, and release follow-up
+- If future context clarifies the formal role/team, update this file directly

ai/context/people/santosh.md

@@ -1,24 +0,0 @@
-# Santosh
-
-## Role
-
-Project-related contact involved in issue discussions.
-
-The exact formal role is not yet confirmed in workspace memory.
-
----
-
-## Known Context
-
-- Mentioned in relation to AO or externally reported issue discussion
-- Relevant when tracking whether a reported issue needs more investigation or can be closed
-
----
-
-## Guidance
-
-If future communication makes Santosh's role explicit, update this file with:
-
-- team or function
-- relationship to Fidelity work
-- whether the person is a reporter, tester, partner, or stakeholder

ai/context/people/tim-longfield.md

@@ -0,0 +1,20 @@
+# Tim Longfield
+
+## Role
+
+FTPlanning-side collaborator relevant to cross-framework issue ownership.
+
+---
+
+## Known Context
+
+- Appeared when issues first thought to be XFlow bugs were traced into FTPlanning
+- Relevant contact for whether a transfer/add-money bug belonged to FTPlanning instead of XFlow
+- Useful when a consumer-side framework fix was needed before XFlow could close validation work
+
+---
+
+## Guidance
+
+- Treat Tim as a relevant contact for FTPlanning-owned fixes and cross-team validation
+- If future context clarifies the formal role/team, update this file directly

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