recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

claim(M2): samever proven in real CI — step-back base<head, version-bump unaffected, discourse #4 + hedgedoc spot-check
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source 
5 real cc-ci runs (samever-deploy @ cc-ci main): Run B nightly steady-state step-back
custom-html 1.11.0+1.29.0→1.13.0+1.31.1 (base<head real delta, 5 tiers green); Run C
version-bump UNAFFECTED (last-green path); Run D PR-form step-back (ref set); discourse #4
kind=ref main-tip unaffected (migration 0.8.1→1.0.0 green); hedgedoc spot-check step-back
3.0.9→3.0.10 green. WHAT/HOW/EXPECTED/WHERE in STATUS-samever.md; logs /root/samever-*.log,
artifacts /var/lib/cc-ci-runs/samever-*/ on cc-ci.
This commit is contained in:
autonomic-bot
2026-06-17 04:58:48 +00:00
parent 8e8985b96f
commit 96c4ad9ef3
3 changed files with 97 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
machine-docs/JOURNAL-samever.md
View File

@ -79,3 +79,22 @@ Two-run authentic nightly simulation on cc-ci (/root/samever-deploy @ cc-ci main
Artifacts preserved on cc-ci: /root/samever-run{A,B,C}.log, /root/samever-disc4.log; run B/C results
copied to /var/lib/cc-ci-runs/samever-run{B,C}/ (Adversary-readable).
## 2026-06-17T04:55Z — M2 complete (PR form + spot-check), claiming
- **Run D (PR form):** ran custom-html with REF=2b82ebab PR=999 (a PR head whose compose version is
still 1.13.0 == canonical). Resolver stepped back to 1.11.0+1.29.0 even with the ref present —
confirming the step-back is ref-independent (the canonical branch precedes the main-tip/ref path).
Upgrade 1.11.0→1.13.0 green.
- **Spot-check (hedgedoc):** only custom-html is WARM_CANONICAL-enrolled, so to exercise the resolver on
a SECOND recipe + different tag ordering I hand-seeded hedgedoc's canonical record to its latest
(3.0.10+1.10.8) — the resolver reads canonical.read_registry regardless of enrollment, so this is the
same production code path. cold-on-latest → step-back to 3.0.9+1.10.7, upgrade green. Removed the
seeded record afterward (`rm -rf /var/lib/ci-warm/hedgedoc`) to leave clean state; hedgedoc is not
enrolled and would be pruned anyway.
- **State hygiene:** custom-html canonical left at the legitimately-promoted 1.13.0+1.31.1 (its real
enrolled steady state). No leftover run stacks (clean teardown verified). Pre-existing warm-keycloak
orphan untouched.
Design B (canonical history) is already recorded out-of-scope in cc-ci-plan/IDEAS.md (per plan §5) —
verify before DONE.