From 3191e1943b1ba60ab695e0b8ad8e161ad3a8afc4 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Mon, 1 Jun 2026 19:38:37 +0000 Subject: [PATCH] review(5): reorient V5/V6 to seeded stale-test case --- machine-docs/BUILDER-INBOX.md | 12 ++++++++++++ machine-docs/REVIEW-5.md | 26 ++++++++++++++++++++++++++ 2 files changed, 38 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..04eb545 --- /dev/null +++ b/machine-docs/BUILDER-INBOX.md @@ -0,0 +1,12 @@ +Seeded stale-test criterion is now the phase-5 frontier I am reviewing against. + +Current live state from my side: +- `matrix-synapse` is reclassified as a real regression, so its old V6 branch no longer satisfies V5/V6. +- `n8n#3` is just another GREEN control (`VERDICT=GREEN`, build `#61`), not a seeded stale-test case. +- `lasuite-docs` and `keycloak` currently have no open recipe PRs. +- There is still no live cc-ci PR / `verify-pr.sh` evidence for the `--with-tests` path. + +For the next useful adversary handoff, please surface a seeded stale-test case with the exact WHAT/HOW/ +EXPECTED/WHERE details in `STATUS-5.md`: +- DEFAULT mode: recipe PR comment only, no cc-ci test edits. +- `--with-tests`: paired cc-ci PR/branch plus the branch-checkout verification result. diff --git a/machine-docs/REVIEW-5.md b/machine-docs/REVIEW-5.md index 499dd4d..b6ffe80 100644 --- a/machine-docs/REVIEW-5.md +++ b/machine-docs/REVIEW-5.md @@ -332,3 +332,29 @@ than the older closed findings. there is no cc-ci test PR, no paired cross-note evidence, and no cold `verify-pr.sh` result yet. The next useful adversary action is to verify that live `--with-tests` flow once the Builder exposes a real cc-ci test PR / branch-checkout run. + +--- + +## Current-frontier review note — 2026-06-01T19:08:00Z + +Operator direction has clarified the V5/V6 criterion: the Builder does **not** need a naturally-occurring +live stale-test case; a **seeded/controlled** stale-test scenario on an enrolled sandbox candidate is +acceptable and should be the thing I verify. + +### Current live state under the seeded-case criterion +- `STATUS-5.md` now explicitly says `matrix-synapse` no longer supports the stale-test hypothesis and the + next shortlist is `n8n`, then `lasuite-docs`, then `keycloak`. +- Live probe of `recipe-maintainers/n8n#3` shows it is still only a GREEN control case, not a seeded stale + test case: + - `POST=0 MAX_WAIT=20 INTERVAL=5 /srv/cc-ci/.claude/skills/recipe-upgrade/testme-on-pr.sh n8n 3` + returned `VERDICT=GREEN BUILD=https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/61` + - PR result comment and head status both reflect terminal success for build `#61` +- `lasuite-docs` and `keycloak` currently have no open recipe PRs in `recipe-maintainers/`. +- There is still no open cc-ci PR demonstrating the V6 `--with-tests` path; the only cc-ci-side artifact + remains the older remote branch `origin/v6-matrix-synapse-real-upgrade-state`, which is now obsolete for + the seeded-case requirement because `matrix-synapse` was reclassified as a real regression. + +**Verdict:** there is currently **nothing new to cold-verify for V5/V6** under the seeded stale-test +criterion. The next required Builder output is a real seeded stale-test run on an enrolled sandbox recipe, +with (1) the DEFAULT explanatory recipe-PR comment and no cc-ci test edits, then (2) the paired +`--with-tests` cc-ci PR + branch-checkout verification evidence.