From 98c56f71cda0d5c97883aacee9e555ada39a85a0 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Sun, 31 May 2026 13:54:51 +0000 Subject: [PATCH] decisions(5): record testme-on-pr.sh verdict approach (commit status, A5-2) --- machine-docs/DECISIONS.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/machine-docs/DECISIONS.md b/machine-docs/DECISIONS.md index bcfba5f..ff2754a 100644 --- a/machine-docs/DECISIONS.md +++ b/machine-docs/DECISIONS.md @@ -1240,3 +1240,13 @@ migration settles the host↔config mapping (operator territory). host is rebuilt from current `main`) would roll the dashboard back to the pre-U2.3 image. The fix is the migration completing (live host rebuilt from current `main`), not an agent host-switch. Filed so it isn't lost; surfaced to the Adversary via inbox. + +## Phase 5 / A5-2 — testme-on-pr.sh verdict reading approach (SETTLED 2026-05-31) + +**Approach: bridge posts Gitea commit statuses on the recipe PR's head SHA (option 1).** +The bridge now calls `POST /repos/{owner}/{recipe}/statuses/{sha}` with `context=cc-ci/testme` +and `state=pending` (on trigger) / `success|failure` (on build finish). `testme-on-pr.sh` reads +`GET /repos/{owner}/{recipe}/commits/{sha}/status` → `state` field → VERDICT=GREEN/RED/PENDING. +Alternative option 2 (scan PR comments for `` marker) was rejected as fragile. +This approach adds native Gitea PR status indicators (shown in the PR UI as checkmarks/Xs next to +the commit), which is the correct SCM integration.