docs: sync from backend 9363d8c — Woodpecker Docker ENOSPC cleanup

11 - Testing/Smoke and Regression Procedure.md

@@ -146,6 +146,25 @@ export WOODPECKER_TOKEN=<local secret>
 
 Never commit or paste the token into docs.
 
+When Docker build steps fail with `ENOSPC`, inspect logs and host storage with
+Woodpecker before retrying blindly:
+
+```bash
+cd ~/CascadeProjects/escrow
+set -a; source .env; set +a
+woodpecker-cli pipeline ls --limit 5 5
+woodpecker-cli pipeline ps 5 <pipeline-number>
+woodpecker-cli pipeline log show 5 <pipeline-number> build-and-deploy
+```
+
+The backend and frontend production pipelines run local Docker builds on the
+arm64 agent. Their cleanup block must remain serialized with
+`/opt/escrow-dev/.ci-docker-prune.lock`, must avoid Docker volume pruning, and
+must wrap old-image/build-cache pruning in `timeout` so the agent cannot hang in
+cleanup. If a killed pipeline still shows a step as `running`, queued builds may
+stay pending until the Woodpecker agent process or the stuck Docker prune process
+is restarted on the host.
+
 Poll latest pipelines by repo id:
 
 | Repo | Woodpecker repo id | Expected pipeline |