ci: run architecture check before release

.agents/skills/openclaw-release-maintainer/SKILL.md

@@ -64,6 +64,7 @@ Use this skill for release and publish-time workflow. Keep ordinary development
 Before tagging or publishing, run:
 
 ```bash
+pnpm check:architecture
 pnpm build
 pnpm ui:build
 pnpm release:check
@@ -108,6 +109,7 @@ node --import tsx scripts/openclaw-npm-postpublish-verify.ts <published-version>
 - Always validate the OpenClaw npm release path before creating the tag.
 - Default release checks:
   - `pnpm check`
+  - `pnpm check:architecture`
   - `pnpm build`
   - `pnpm ui:build`
   - `pnpm release:check`

.github/workflows/ci.yml

@@ -1289,8 +1289,7 @@ jobs:
                 run_check "ui:i18n:check" pnpm ui:i18n:check
               fi
               run_check "gateway-watch-regression" pnpm test:gateway:watch-regression
-              run_check "check:import-cycles" pnpm check:import-cycles
-              run_check "check:madge-import-cycles" pnpm check:madge-import-cycles
+              run_check "check:architecture" pnpm check:architecture
               ;;
             *)
               echo "Unsupported additional check group: $ADDITIONAL_CHECK_GROUP" >&2

.github/workflows/openclaw-npm-release.yml

@@ -110,6 +110,11 @@ jobs:
           OPENCLAW_LOCAL_CHECK: "0"
         run: pnpm check
 
+      - name: Check architecture
+        env:
+          OPENCLAW_LOCAL_CHECK: "0"
+        run: pnpm check:architecture
+
       - name: Build
         run: pnpm build
 

docs/reference/RELEASING.md

@@ -37,6 +37,8 @@ OpenClaw has three public release lanes:
 
 ## Release preflight
 
+- Run `pnpm check:architecture` before release preflight so the broader import
+  cycle and architecture boundary checks are green outside the faster local gate
 - Run `pnpm build && pnpm ui:build` before `pnpm release:check` so the expected
   `dist/*` release artifacts and Control UI bundle exist for the pack
   validation step