docs: sync from backend 55321c0 — restore build procedure

11 - Testing/Smoke and Regression Procedure.md

@@ -120,13 +120,11 @@ layer. For a faster local isolation check, create a temporary Dockerfile from th
 production Dockerfile through the Yarn install `RUN` block, then append:
 
 ```dockerfile
-RUN test -d node_modules/country-flag-icons && test ! -d /root/.yarn/v6
+RUN test -d node_modules/country-flag-icons
 ```
 
 The expected install command uses a locked BuildKit Yarn cache, a Yarn mutex,
-`--frozen-lockfile`, and `--link-duplicates`; the layer must clear `/root/.yarn`
-before and after install so stale Yarn v6 cache contents do not exhaust builder
-disk while copying packages such as `country-flag-icons`.
+and `--frozen-lockfile`, matching the last known green production build shape.
 
 Scanner focus:
 
@@ -158,12 +156,12 @@ 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.
+arm64 agent and should retain the last-green simple build shape unless a scoped
+CI change is explicitly approved. Do not add Docker prune/cleanup blocks to the
+production pipelines as a first response; inspect the host and clear space
+operationally. If a killed pipeline still shows a step as `running`, queued
+builds may stay pending until the Woodpecker agent process or the stuck Docker
+process is restarted on the host.
 
 Poll latest pipelines by repo id: