Repo File Sync: Add AI Policy and check-no-default-features task (#83)

synced local file(s) with
[OpenDevicePartnership/patina-devops](https://github.com/OpenDevicePartnership/patina-devops).

🤖: View the [Repo File Sync Configuration
File](https://github.com/OpenDevicePartnership/patina-devops/blob/main/.sync/Files.yml)
to see how files are synced.

---

This PR was created automatically by the
[repo-file-sync-action](https://github.com/BetaHuhn/repo-file-sync-action)
workflow run
[#23235303320](https://github.com/OpenDevicePartnership/patina-devops/actions/runs/23235303320)

Signed-off-by: Patina Automation Bot <patina@microsoft.com>
Co-authored-by: patina-automation[bot] <196234736+patina-automation[bot]@users.noreply.github.com>

Author: patina-automation[bot]

CONTRIBUTING.md

@@ -20,6 +20,30 @@ indicate that clearly in your pull request so that the project team can discuss
 * Format the code with `cargo make all`.
 * Use meaningful commit messages. See [this blogpost](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
 
+## AI Policy
+
+Patina does not accept contributions directly from AI tools (e.g. GitHub Copilot). If you use an AI tool to assist in
+the development of a Patina contribution, ensure that:
+
+1. You have the legal right to submit the code generated by an AI tool under Patina's contribution and licensing
+   guidelines.
+2. You fully understand the changes being made to the codebase and can explain the changes to other contributors.
+3. You have thoroughly reviewed the code to ensure it meets Patina contribution guidelines.
+4. You have thoroughly tested the code. Firmware changes must be tested on QEMU and a physical platform.
+
+If you do not fully understand the changes being made to the codebase, please ask for help from the Patina
+community before submitting a pull request. You can start a GitHub discussion to get more background on a topic or
+submit a GitHub issue to report a bug or request.
+
+At a minimum, contributors submitting firmware changes should have a working understanding of the Rust programming
+language and UEFI firmware development. If you are new to either topic, the Patina community is happy to help you
+and there are many existing resources available for both subjects on the Internet.
+
+Patina maintainers reserve the right to reject or close a pull request at any time if it is determined to violate this
+policy, including cases where AI‑assisted contributions lack sufficient human understanding, review, testing, or legal
+clarity. If a user repeatedly violates this policy, they may be temporarily or permanently banned from contributing to
+the Patina project.
+
 ## PR Etiquette
 
 * Make sure that GitHub status checks ("PR gates") pass in your PR.

Makefile.toml

@@ -97,6 +97,23 @@ description = "Checks rust code for errors. Example `cargo make check`"
 clear = true
 run_task = [{ name = ["check_no_std", "check_std", "check_tests"], parallel = true }]
 
+[tasks.check-no-default-features-code]
+description = "Checks rust code compiles without default features."
+private = true
+command = "cargo"
+args = ["check", "--no-default-features", "@@split(CARGO_MAKE_TASK_ARGS, )"]
+
+[tasks.check-no-default-features-tests]
+description = "Checks rust test code compiles without default features."
+private = true
+command = "cargo"
+args = ["test", "--no-run", "--no-default-features", "@@split(CARGO_MAKE_TASK_ARGS, )"]
+
+[tasks.check-no-default-features]
+description = "Checks rust code and tests compile without default features to catch feature-gate regressions."
+clear = true
+run_task = [{ name = ["check-no-default-features-code", "check-no-default-features-tests"], parallel = true }]
+
 [tasks.llvm-cov-clean]
 description = "Clean coverage data"
 private = true
@@ -237,6 +254,7 @@ dependencies = [
     "deny",
     "clippy",
     "cspell",
+    "check-no-default-features",
     "build",
     "build-x64",
     "build-aarch64",