{"version":"2.1.271","anchor":"ios-project-evidence-detection-reworked-to-track-evidence-so","canonical_anchor":"ios-project-evidence-detection-reworked-to-track-evidence-so","heading":"iOS-project evidence detection reworked to track evidence source","tier":"internal","area":"Dev Intent","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/ios-project-evidence-detection-reworked-to-track-evidence-so","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### iOS-project evidence detection reworked to track evidence source\n\niOS-project detection now records which signal triggered it instead of just yes\/no\n\n**What**\n\nClaude Code has a heuristic for deciding whether an edit relates to an iOS project. Previously this produced a plain true\/false `iosEvidence` flag; now it records the actual source of the evidence: a content match, an `ios_command`, or an `xcode_project` tool result.\n\n**Why**\n\nTracking the specific source rather than a single flag allows more precise or differentiated handling of iOS-related edits depending on how the evidence was found.\n\n- Area: Dev Intent\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}