feat: Add iOS and Swift context files and guidelines for answering programming questions

ai/context/ios/project-swift-guidance.md

@@ -0,0 +1,37 @@
+# Project Swift Guidance
+
+## Goal
+
+Apply Swift/iOS advice in a way that fits Fidelity's XFlow, Fid4, XFlowViewMaker, and FTFrameworks environment.
+
+---
+
+## Fidelity-Specific Constraints
+
+- XFlow is backend-driven; UI behavior may be service/configuration driven, not purely local Swift code.
+- Fid4 is the real consumer validation target for many issues.
+- XFlowViewMaker and FTFrameworks can affect whether a fix is visible in Fid4.
+- REST migration constraints still matter; do not assume REST is active by default.
+- Some work happens behind feature flags, especially risky consumer-impact changes.
+
+---
+
+## SwiftUI / XFlow Priorities
+
+- Treat modal presentation, dismissal sequencing, and lifecycle boundaries as high-risk areas.
+- Be careful when removing UIKit bridges such as `UIHostingController`; preserve consumer behavior and rollout safety.
+- When discussing SwiftUI architecture, include how the change affects:
+  - backend-driven flow rendering
+  - consumer app integration
+  - feature flags
+  - validation in Fid4
+  - UIKit/SwiftUI parity
+
+---
+
+## Answering Rules
+
+- If the user asks a general Swift question, answer generally but include a Fidelity/XFlow note when relevant.
+- If the user asks about a code change, separate modern best practice from what is safe for the current project.
+- If codebase constraints are unknown, say what must be confirmed: deployment target, Xcode version, module ownership, feature flag path, and consumer validation path.
+- For manager-ready explanations, connect the technical recommendation to scope, risk, and validation.