build-status: record pipeline shakeout state for the next session

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/build-status.md

@@ -152,6 +152,16 @@ Archived as `…-build2.json` in `echolot-prober/reports/`. The findings:
 - `ip_monitor` returned no events this run even with the provoked gateway ping (gateway was
   already REACHABLE, so no NEIGH transition happened). Evidence-dependent, not a bug.
 
+## Pipeline shakeout — 2026-07-30, partially done
+Repo pushed to git.rambossek.at/EchoLot/echolot (ssh :2222). Actions runner works:
+`server-test` green on push. `server-v0.1.0` tag → release **created but empty** — asset upload
+failed (likely Gitea's default `[attachment] ALLOWED_TYPES` rejecting extension-less binaries;
+job logs need a token/UI to confirm). Image job fails separately (runner probably lacks docker).
+To finish: (1) check the failed `server-release` job log in the Gitea UI; if it's the attachment
+type limit, either set `[attachment] ALLOWED_TYPES = */*` in app.ini or switch the workflow to
+.tar.gz assets (then teach server/internal/selfupdate to unpack); (2) decide whether the runner
+gets docker (image job) or images wait. Delete + re-push the tag to re-run.
+
 ## Next steps
 1. Build locally, run on several physical devices (varied Android versions/vendors), collect the
    JSON reports — especially the real per-device Shizuku dump formats.