claim(bsky): M1 — root cause proven (:0.4 republished w/ 0.5.1/index.ts vs entrypoint index.js), mirror PR#2 re-pin 0.4.219 green at head via drone run 427 (level 5, upgrade=declared intentional skip, negative control run 423), screenshot verified real+credential-free
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
This commit is contained in:
@ -72,3 +72,15 @@ path (UPGRADE_BASE_VERSION="0.3.0+v0.4.219" once published). 6 new unit tests
|
||||
Verified: 253 unit tests pass on cc-ci (was 247), repo lint PASS. Pushed e9745c8.
|
||||
|
||||
Re-triggered !testme (comment 14342) → build/run 427. Monitor armed.
|
||||
|
||||
## 2026-06-11T12:05Z — run 427 GREEN: level 5 at PR head; M1 claimed (B5, B6, B7)
|
||||
|
||||
Run 427 (drone build 427, comment 14342): level 5 — install/backup_restore/functional/
|
||||
lint PASS, upgrade = declared intentional skip (reason verbatim in skips.intentional),
|
||||
clean_teardown + no_secret_leak true, ref f7b6c8dfb81c. Per-run recipe checkout at PR
|
||||
head f7b6c8d with image 0.4.219 (the fix WAS what deployed). Bridge reflected success →
|
||||
PR comment 14343 ✅. Screenshot Read and verified: genuine PDS landing page (ASCII
|
||||
butterfly, "This is an AT Protocol Personal Data Server", /xrpc/ pointer) — exactly the
|
||||
default capture the phase plan predicted would work once deploy works; no hook needed.
|
||||
Card (summary.png): 5/5, upgrade shown INTENTIONAL SKIP with reason; badge "level 5"
|
||||
green. M1 claimed in STATUS-bsky.md.
|
||||
|
||||
Reference in New Issue
Block a user