Enforce cc_feature mutually_exclusive

[nradakovic]

Resolves #28

[nradakovic]

Already implemented. Only docs will be updated.

[Copilot]

Pull request overview

This PR moves sanitizer incompatibility enforcement (ASan+TSan, LSan+TSan) into the canonical Bazel C++ feature model by adding cc_mutually_exclusive_category constraints to the sanitizer cc_feature definitions, and updates documentation to describe feature-level enforcement as the primary mechanism (with the existing genrule retained as a secondary guard).

Changes:

• Add mutually-exclusive runtime categories in sanitizers/features/BUILD.bazel and wire them into score_asan, score_lsan, and score_tsan via mutually_exclusive.
• Update sanitizers/README.md to document feature-layer exclusivity, expected analysis-time failure mode, and the remaining role of sanitizer_combination_check.
• Update top-level README.md to describe the enforcement stack (feature level → genrule → compiler backstop).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
sanitizers/features/BUILD.bazel	Adds cc_mutually_exclusive_category targets and attaches them to sanitizer cc_features via mutually_exclusive.
sanitizers/README.md	Documents mutually-exclusive runtime categories as primary enforcement and reframes the genrule as secondary.
README.md	Updates public docs to describe enforcement at feature level first, then genrule, then compiler.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.