From 654ec96e3b1a1c8605565ed5e17266af24967e37 Mon Sep 17 00:00:00 2001 From: Mikkeli Date: Tue, 13 Oct 2026 20:01:14 +0900 Subject: [PATCH] CI-RUNNER: contracts' rust-consumers workflow Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01DDwfd6Ki8UfG4hK6W5YpJz --- docs/impl/reports/CI-RUNNER.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/impl/reports/CI-RUNNER.md b/docs/impl/reports/CI-RUNNER.md index e240f47..65a9a31 100644 --- a/docs/impl/reports/CI-RUNNER.md +++ b/docs/impl/reports/CI-RUNNER.md @@ -41,8 +41,12 @@ script needs `node` (JavaScript actions in host mode), `objdump` (check-glibc), `.gitea/workflows/rust.yml` in svc-core, svc-gw and svc-nav (identical): clone the pushed commit with contracts beside it, then clippy with `-D warnings`, tests, a release build, and `scripts/check-glibc.sh` on every binary. Plain git, no JavaScript -actions. It runs on changes to `src/`, `Cargo.*`, the glibc script or itself, not on -contracts changes. +actions. It runs on changes to `src/`, `Cargo.*`, the glibc script or itself. + +contracts' `.gitea/workflows/rust-consumers.yml` covers the other direction: on a change +under `schema/` (what services compile in), it finds every yukart Rust repo whose source +refers to `../contracts/` and runs the same checks on each, at its master, against the +pushed contracts. README, docs and checklists do not trigger it. ⚠ **Upgrade both Orins or neither.** This runner proves glibc parity only while its L4T/Ubuntu release matches the car's (R36.4.7 here, R36.4.4 on the car, both glibc 2.35