From 9f03dfb4ab141bc18073275370cfd0b183a5738d Mon Sep 17 00:00:00 2001 From: Javier Tia Date: Thu, 19 Nov 2026 13:34:52 -0600 Subject: [PATCH] agent: Fix the CI claim in the check-provider note The README says the compile-time guard is the real enforcement point because avocado-os has no CI or pre-commit hook. That described the repository the extension used to live in. This repository has a test.yml that builds the extension through the shared workflow, so the guard does run in CI, but it has no pre-commit hook. Say what is true here: no pre-commit hook, and CI reaches the guard only through the compile. Signed-off-by: Javier Tia --- agent/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/agent/README.md b/agent/README.md index 3c40de6..c5637b7 100644 --- a/agent/README.md +++ b/agent/README.md @@ -36,7 +36,8 @@ The guard also backstops by asserting `ring` IS present: a guard that cannot see `TARGET="$RUST_TARGET" scripts/check-provider.sh` immediately before `cargo build`, resolving the same SDK triple, manifest, and `CARGO_HOME` the build uses. Under `set -e`, a non-zero exit fails the compile. This is the - real enforcement point - avocado-os has no CI or pre-commit hook. + real enforcement point - this repository has no pre-commit hook, + and CI reaches the guard only through this compile. - **Advisory run (standalone, no `TARGET`):** running `scripts/check-provider.sh` directly (e.g. from the repo root) checks the **host** triple, not the shipped cross target. Treat it as an advisory