review(ghost): pass fresh level-five retry
continuous-integration/drone/push Build is passing

This commit is contained in:
2026-10-20 03:22:11 +00:00
parent 2977495851
commit 13d1b33014
2 changed files with 35 additions and 2 deletions
+34 -1
View File
@@ -186,4 +186,37 @@ Builder may write `## DONE` to STATUS-ghost.md.
as required by the phase gate. The Builder must either obtain a fresh fully verified result or
add a precise operator-facing explanation of the lint blocker and its impact before M2 can pass.
## VETO Current M2 is not operator-ready: run #55 has an unintentional unverified lint stage while comment #16249 reports an unexplained plain pass.
## VETO CLEARED @2026-10-20T03:22:00Z
The prior veto applied to run #55. Fresh build #66 for the same PR head has verified lint
pass and an accurate result comment; see the fresh M1/M2 verdict below.
## Fresh gate verification — 2026-10-20T03:22:00Z
### M1: PASS @2026-10-20T03:22:00Z
- Cold Gitea inventory shows exactly one open Ghost upgrade PR: PR#8, head
`dbe40ecb7b0084050a71baf4dcf971b65aac125e` on `upgrade-ee04ca9`; PRs #1-#7 are closed.
- Gitea comments #16297 and #16298 show the fresh `!testme` and its result for build #66.
- Drone API build #66 independently reports `status=success`, `RECIPE=ghost`, `PR=8`,
`REF=dbe40ecb7b0084050a71baf4dcf971b65aac125e`, and `SRC=recipe-maintainers/ghost`.
- Host artifact `/var/lib/cc-ci-runs/66/results.json` reports `level=5`, with install,
upgrade, backup, restore, custom, and lint all `pass`; no unintentional skips are present.
- The current evidence is post-proxy and uses the current PR head. The historical failed
artifacts remain separate: builds #515/#517 failed at install and #519/#557 failed at
upgrade, while the proxy was subsequently fixed to `10.10.0.0/16`; they were not used as
evidence against the current retry.
### M2: PASS @2026-10-20T03:22:00Z
- Exactly one relevant open Ghost upgrade PR remains, PR#8; all historical PRs #1-#7 are closed.
- The operator-facing result comment #16298 links build #66 and reports the successful result.
- Artifact flags are `clean_teardown=true` and `no_secret_leak=true`; `docker stack ls`,
`docker service ls`, `docker volume ls`, and `docker network ls` probes found no
`ghos-*` or `dev-ghost` resources. The proxy subnet is `10.10.0.0/16`.
- The prior M2 veto is cleared: build #66 has a verified lint `pass`, unlike build #55's
unintentional lint `unver` result.
**Fresh verdict:** M1 and M2 PASS. The current Ghost upgrade PR is operator-ready, the
post-proxy retry is a genuine level-5 pass for the current head, historical failures remain
separate from current recipe evidence, and no Ghost resources leak.