False positive: safeguard flagged a routine iOS build-config commit message, forced switch to Opus 5

Bug Description
Title: False positive: safeguard flagged a routine iOS build-config commit message, forced switch to Opus 5 Description: Context: a long Claude Code session doing an iOS CocoaPods to Swift Package Manager migration in a Flutter monorepo (Bitbucket, Jira MCP). Model: Fable 5. What was flagged: an assistant message that summarized four small build-configuration fixes and proposed a git commit message. Content was entirely mundane: a Crashlytics dSYM upload script path in project.pbxproj, an iOS platform floor in a Package.swift, an Xcode scheme pre-action, and an analyzer exclude entry. No security, credential, or dual-use topic anywhere in the message or the surrounding work. Possible triggers (guessing, since the flag reason is not visible): shell-ish fragments in the discussion of a build script (test -x, exit 1, path variables), the word "crash" via Crashlytics, or the fact that flutter build ipa output quoted an "xcrun altool --upload-app" line in the transcript shortly before. Impact: the session auto-switched to Opus 5 mid-task. Work continued, but the assistant could not see the switch notice, so when I asked why it had switched, it confidently denied switching at all. That mismatch is worth noting on its own: the model has no visibility into an event the user is shown, which produces a contradiction the user has to resolve. Expected: routine build-tooling and CI configuration discussion should not trip the safeguard.

Environment Info

• Platform: darwin
• Terminal: Apple_Terminal
• Version: 2.1.221
• Feedback ID: b2ee4add-8671-4690-85fb-b0eefcb3e39c

Errors

[]