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

ai/AGENTS.md

@@ -63,6 +63,7 @@ When drafting messages for a manager or stakeholder:
 - Treat workspace files as persistent memory, not just reference notes
 - Before answering prompts about current work, verify `ai/state/current.md` and the latest relevant log in `ai/logs/`
 - Before answering architecture, process, or historical questions, check the relevant file under `ai/context/systems/`, `ai/context/workstreams/`, or `ai/context/process/`
+- Before answering Swift, SwiftUI, iOS architecture, testing, or debugging questions, check `ai/context/ios/` and use the project-local iOS skills when available
 - If `ai/inbox/mattermost-latest.md` exists, check it before answering prompts about current status, standups, or supervisor communication
 - Treat all meaningful user prompts as potential memory updates, not only explicit sync commands
 - If a Mattermost sync or other context-ingestion step fails, do not update `ai/logs/`, `ai/state/`, or stable context files based on that failure
@@ -78,6 +79,7 @@ When drafting messages for a manager or stakeholder:
 - Update existing memory when the new information is a correction, clarification, or refinement of something already stored
 - Prefer updating stable project context over appending generic operational summaries
 - Do not create daily log entries for tooling activity, sync status, or generic chat noise
+- For Swift/iOS best-practice answers, distinguish current Apple guidance from project-safe recommendations when Fidelity constraints may change the answer
 - Do not ask the user what should be promoted after a successful sync unless multiple conflicting interpretations are equally plausible
 - When the user shares relevant new information, update today's log if the information belongs to the daily record
 - When the user corrects or changes stable context, update the canonical file directly: