ci: drop the backend e2e step from the dev image pipeline

.woodpecker/dev-image.yml

@@ -102,17 +102,3 @@ steps:
     depends_on:
       - build-amd64-agent
       - build-arm64-agent-musl
-
-  - name: backend-e2e-tests
-    image: bash
-    when:
-      - evaluate: 'not (CI_COMMIT_MESSAGE contains "[SKIP TESTS]")'
-    environment:
-      NUGET_PACKAGES: /home/justme/woodpecker/cache/nuget/packages
-    commands:
-      - python3 ci/guard-step.py backend-e2e-tests 1500 bash ci/verify-backend.sh slow
-    depends_on:
-      - publish-agent-images
-      - build-linux-amd64-backend
-      - build-amd64-agent
-      - build-arm64-agent

.woodpecker/e2e.yml

@@ -8,7 +8,7 @@ clone:
     settings:
       lfs: false
 
-# 带 [CI] 的推送会出镜像，慢测试放在 dev-image 里、等镜像构建完再跑（不和 AOT 编译抢内存）；这个 workflow 管其余的：PR 和没带 [CI] 的推送
+# 带 [CI] 的推送只出镜像，不跑慢测试；这个 workflow 管其余的：PR 和没带 [CI] 的推送
 when:
   - event: pull_request
   - event: push

AGENTS.md

@@ -80,7 +80,7 @@ First run of the Backend prints a claim code in its log; the admin UI asks for i
 Triggers, tags and image paths are defined in `.woodpecker/*.yml` and [`docs/ops/deployment.md`](docs/ops/deployment.md). Verify them there before changing or describing them. The rules below are the stable contract.
 
 - Every push to `main` runs the fast Backend tests and the web build. Both must pass before images are published.
-- A commit message containing `[CI]` builds and pushes development images. `[CI SKIP]` skips the pipeline; `[SKIP TESTS]` skips only the Backend tests. Slow end-to-end tests run after image publication and do not block it.
+- A commit message containing `[CI]` builds and pushes development images. `[CI SKIP]` skips the pipeline; `[SKIP TESTS]` skips only the Backend tests. Slow end-to-end tests run only for pushes without `[CI]` and for pull requests.
 - A tag `vMAJOR.MINOR.PATCH` runs the full cross-platform release pipeline. No version-bump commit is needed.
 - Versions are produced by `ci/version.sh`. The `<Version>` in `backend/Directory.Build.props` and the `version` in `web` `package.json` files are placeholders (`0.0.0-dev`) and must not be edited.
 - Linux Agent builds use `ci/build-linux-agent.sh` for glibc on amd64/arm64 and musl on arm64 in both dev and tag workflows. OCI and OpenWrt installers reuse these native outputs; Windows runners build only Windows/macOS.