status(5): record seeded custom-html V5/V6 flow

2026-06-01 20:09:06 +00:00
parent 2e2b90b85f
commit 9703687e43
2 changed files with 110 additions and 7 deletions
@@ -421,3 +421,80 @@ Conclusion:
  failed. This points to a true recipe upgrade regression, not a stale cc-ci test.

 Next: move to the next enrolled V5/V6 candidate (`n8n`, then `lasuite-docs`, then `keycloak`).
+
+## 2026-06-01 — Operator-directed seeded stale-test case: custom-html
+
+Per operator direction, I stopped searching for a naturally occurring stale-test recipe and switched to a
+deliberately seeded sandbox case.
+
+Seeded recipe PR used:
+- `https://git.autonomic.zone/recipe-maintainers/custom-html/pulls/3`
+- branch `v5-stale-docroot`
+
+I first inspected the pre-existing PR state and found the earlier docroot-move attempt was too broad:
+it broke backup/restore/custom for real, so it was not a clean stale-test simulation.
+
+Re-seeded the same sandbox PR into a narrower stale-test case on the host recipe checkout:
+- kept the real upgrade crossover (`1.10.0+1.28.0 -> 1.11.2+1.29.0`)
+- reverted the volume/docroot move
+- added a specific nginx location override for `*.txt`:
+  - keep `.html` as normal `text/html`
+  - force `.txt` to `application/octet-stream`
+- final seed commit on the recipe PR branch:
+  - `71e7326 fix: force octet-stream for seeded txt files`
+
+DEFAULT / V5 real-path evidence:
+- Trigger:
+  - `POST=1 MAX_WAIT=90 INTERVAL=5 /srv/cc-ci-orch/.claude/skills/recipe-upgrade/testme-on-pr.sh custom-html 3`
+    -> `VERDICT=RED`
+    -> `BUILD=https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/75`
+- Poll-only re-check:
+  - `POST=0 MAX_WAIT=20 INTERVAL=5 /srv/cc-ci-orch/.claude/skills/recipe-upgrade/testme-on-pr.sh custom-html 3`
+    -> `VERDICT=RED`
+    -> `BUILD=https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/75`
+- Authenticated Drone log inspection for build `#75`:
+  - install PASS
+  - upgrade PASS
+  - backup PASS
+  - restore PASS
+  - custom FAIL only
+  - exact failing assertion:
+    `tests/custom-html/functional/test_content_type_header.py`
+    expected `.txt` `Content-Type` to start with `text/plain`, got `application/octet-stream`
+- DEFAULT-mode explanatory recipe PR comment posted with NO cc-ci test edit:
+  - `https://git.autonomic.zone/recipe-maintainers/custom-html/pulls/3#issuecomment-13883`
+  - comment explains the seeded sandbox MIME change and tells the operator to re-run
+    `/recipe-upgrade custom-html --with-tests`
+
+`--with-tests` / V6 real-path evidence:
+- Created a fresh dedicated cc-ci clone:
+  - `/tmp/opencode/cc-ci-v6-custom-mime`
+- Created the minimal paired branch:
+  - branch: `v6-custom-html-mime`
+  - commit: `826daec fix(tests): accept seeded custom-html txt mime`
+  - remote branch: `origin/v6-custom-html-mime`
+- Scope of the test PR branch:
+  - only `tests/custom-html/functional/test_content_type_header.py` changed
+  - `.txt` now expects `application/octet-stream` for the seeded sandbox case
+- Opened paired cc-ci PR:
+  - `https://git.autonomic.zone/recipe-maintainers/cc-ci/pulls/3`
+- Materialized isolated host checkout:
+  - `/root/cc-ci-v6-custom-mime`
+- Cold branch-checkout verification on cc-ci:
+  - `REMOTE_ROOT=/root/cc-ci-v6-custom-mime RECIPE=custom-html REF=v5-stale-docroot /srv/cc-ci-orch/.claude/skills/ci-test-review/verify-pr.sh`
+  - result:
+    `VERDICT: GREEN — custom-html PR (REF=v5-stale-docroot) passed cold full-suite x1. Ready for operator merge (NOT merged).`
+  - host log:
+    `cc-ci:/root/cc-ci-review-logs/verify-custom-html-20260601T200544Z.1.log`
+
+Pairing notes posted:
+- recipe PR note:
+  `https://git.autonomic.zone/recipe-maintainers/custom-html/pulls/3#issuecomment-13894`
+- cc-ci PR note:
+  `https://git.autonomic.zone/recipe-maintainers/cc-ci/pulls/3#issuecomment-13896`
+
+Conclusion:
+- The operator-directed seeded stale-test case is now fully exercised:
+  - DEFAULT mode leaves an explanatory recipe-PR comment and makes no cc-ci test edit
+  - `--with-tests` opens a paired cc-ci test PR and the branch-checkout verification is GREEN
+- Next phase work is V8 `/upgrade-all`, V8a `cc-ci-upgrader`, then V9 cleanup/closeout.