fix web ui smoke and brand assets

tests/README.md

@@ -0,0 +1,30 @@
+# Automated Test Workspace
+
+This directory holds executable test assets derived from `docs/TEST_PLAN_AND_CASES.md`.
+
+- `api/`: API and full `AppModule` E2E suites.
+- `web/`: Browser automation suites.
+- `smoke/`: Environment smoke checks and optional call-flow probes.
+- `fixtures/`: Shared static fixtures used by tests.
+- `reports/`: Generated test result files.
+
+Current runnable entry points:
+
+- `pnpm test:baseline`
+- `pnpm test:api`
+- `pnpm test:smoke`
+- `pnpm test:remote-smoke`
+- `pnpm test:remote-auth`
+- `pnpm test:remote-customers`
+- `pnpm test:remote-gateways`
+- `pnpm test:remote-vendors`
+- `pnpm test:remote-calls`
+- `pnpm test:remote-recordings`
+- `pnpm test:remote-dashboard`
+- `pnpm test:remote-perf-security`
+- `pnpm test:remote-web-ui`
+- `pnpm db:seed:test`
+
+`pnpm lint` now includes `apps/web/src/**`, so undefined frontend identifiers such as missing page normalizers fail before build.
+
+Use `pnpm test:remote-web-ui` after Web releases. It logs in with `LISGLOSIPS_AUTH_USERNAME` / `LISGLOSIPS_AUTH_PASSWORD`, clicks every non-pending core menu, and fails on blank pages, `API 数据不可用`, `pageerror`, or console errors.