feat: Enhance documentation on build inspection sources, clarifying the role of iosinstaller and app-store debugging paths

vault/03-context/workstreams/consumer-integration.md

@@ -89,6 +89,7 @@ Capture the durable release and validation path between XFlow changes and real c
 - The fastest reliable signals are:
   - fixed version references in the Podfile when present
   - archived pipeline artifacts such as `xcarchive` outputs and captured `Podfile.lock` files
+- Useful Fidelity-specific sources include `iosinstaller`, which exposes App Store/internal builds plus their `Podfile.lock`, and the Flagship app pipeline artifact `appstore/DistributionSummary.plist`, which records the framework versions included in a shipped build.
 - Even those checks are not perfect guarantees because the podspec repo can be edited after publication.
 - When a consumer build must be reproduced exactly from an older dependency snapshot, `Podfile.lock` alone may still be insufficient if the private podspec repo changed afterward; the stronger reproduction path is to align the podspec repo revision too.
 - A newly published XFlowViewMaker version can still be blocked in Fid4 if downstream podspec constraints in `FTAccountOpen` or `FTTransfer` do not yet accept the new adapter version.