The guidance in https://developer.apple.com/forums/thread/739774 explains the context search list, the kSecMatchSearchList override and continued use of deprecated file-based APIs where that keychain model is required.
For a SecItemCopyMatching query using kSecClassCertificate and an explicitly supplied file-based test keychain, what is the supported way to refuse authentication UI rather than allow a prompt? I am considering macOS 26.6.1 with the macOS 27.0 SDK; please clarify applicability to that combination and any relevant application-context restrictions.
In particular, which refusal mechanism applies to the file-based path given the deprecation of earlier authentication-UI options? If access would require keychain unlock or authentication UI, is an error guaranteed, or can the query omit items and return success? A public documentation reference and any version limitations would be helpful.
This is a contract question for a prospective test; I have not run it or reproduced a problem.