feat: Update CocoaPods dependency management guidance and index for improved clarity on versioning and release propagation

vault/03-context/ios/project-swift-guidance.md

@@ -2,7 +2,7 @@
 type: guidance
 project: fidelity
 status: active
-updated: 2026-04-16
+updated: 2026-04-17
 tags:
   - ios
   - fidelity
@@ -20,6 +20,7 @@ Apply Swift/iOS advice in a way that fits Fidelity's XFlow, Fid4, XFlowViewMaker
 - 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.
+- CocoaPods and private podspec-repo behavior are part of the real integration surface, not just build tooling details.
 - REST migration constraints still matter; do not assume REST is active by default.
 - Some work happens behind feature flags, especially risky consumer-impact changes.
 
@@ -43,4 +44,5 @@ Apply Swift/iOS advice in a way that fits Fidelity's XFlow, Fid4, XFlowViewMaker
 - 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.
+- If the work touches dependency propagation, published specs, or consumer upgrade behavior, explicitly include CocoaPods and podspec-repo reasoning instead of treating them as secondary operational noise.
 - For manager-ready explanations, connect the technical recommendation to scope, risk, and validation.