You are integrating Claude Code into your Continuous Integration/Continuous Deployment (CI/CD) pipeline.

Option A supplies the missing project context before Claude evaluates the code. Anthropic’s CLAUDE.md documentation defines project-level files as persistent, version-controlled instructions for coding standards, architecture, workflows, and conventions. The described exceptions are stable repository facts: force-unwrapping is permitted in tests, coordinator classes follow an intentional pattern, and an internally maintained dependency remains approved despite its public deprecation status. Recording these facts concisely allows every review session to interpret the patterns correctly.

Option B removes surrounding evidence and would make architectural and cross-file judgments less reliable. Option C hides findings after generation and can suppress genuine bugs containing the same keywords. Option D adds noise to source files and distributes policy across individual call sites instead of documenting it centrally. The CLAUDE.md entries should be specific and scoped—for example, limiting the force-unwrapping exception to test paths rather than approving it globally. Anthropic notes that shorter, precise instructions are followed more consistently, so the file should state the accepted convention, its scope, and any conditions that would still make the pattern reportable.

================