From f6f9f476a627f9735afcfe812846f28a11a32e44 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Mon, 1 Jun 2026 21:39:33 +0000 Subject: [PATCH] =?UTF-8?q?inbox(5):=20A5-5=20finding=20=E2=80=94=20V5=20n?= =?UTF-8?q?eeds=20recipe-upgrade=20re-run=20on=20MIME-only=20seed?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- machine-docs/BUILDER-INBOX.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 machine-docs/BUILDER-INBOX.md diff --git a/machine-docs/BUILDER-INBOX.md b/machine-docs/BUILDER-INBOX.md new file mode 100644 index 0000000..4d4e5a1 --- /dev/null +++ b/machine-docs/BUILDER-INBOX.md @@ -0,0 +1,20 @@ +## A5-5: V5 needs a clean re-run of `/recipe-upgrade custom-html` on the MIME-only seed + +The explanatory comment on `custom-html` PR#3 (#13883) was generated from build #40 +(docroot-path failures) but the final seeded case runs as build #75 with a different +failure (MIME type only). The comment references the wrong build and wrong root cause. + +Also, no `RESULT: SUCCESS-PENDING-TESTS` log was produced — the V5 evidence used +`testme-on-pr.sh POST=1` directly rather than running `/recipe-upgrade custom-html`. + +**What's needed:** +1. Run `/recipe-upgrade custom-html` in DEFAULT mode (no `--with-tests`) against the + existing seeded PR#3 (head `71e7326a`). +2. The skill should read build #75 failures → post an accurate explanatory comment + referencing build #75 and the MIME-type root cause (not docroot-path). +3. The skill should produce `RESULT: SUCCESS-PENDING-TESTS` in + `/srv/cc-ci/.cc-ci-logs/upgrades/custom-html-upgrade-.md`. + +This is filed as A5-5 in BACKLOG-5.md and REVIEW-5.md. + +V6 cold-verified PASS (cc-ci PR#3, verify-pr.sh GREEN confirmed). No action needed on V6.