chore: lean AI-native UI quality deliverables

Drop alwaysApply Cursor rule and in-tree plan doc; revert non-core
api/refactor/README instruction churn. Keep theme.config, verify:ui,
frontend instructions, and AGENTS validation.

Co-authored-by: zuiidea <zuiiidea@gmail.com>

apps/basic/.github/instructions/README.md

@@ -4,13 +4,11 @@ This directory contains scoped instruction files used by AI coding agents.
 
 ## Files
 
-- `frontend.instructions.md`: UI/routes/components/style changes (includes golden paths and `verify:ui`)
+- `frontend.instructions.md`: UI/routes/components/style changes
 - `testing.instructions.md`: Playwright/MSW/test changes
 - `api.instructions.md`: API client/schema/handler changes
 - `refactor.instructions.md`: behavior-preserving cleanup and deduplication
 
-UI golden paths and Ant Design/token rules live in `frontend.instructions.md`.
-
 ## Authoring Rules
 
 - Keep each file focused on one domain.

apps/basic/.github/instructions/api.instructions.md

@@ -13,7 +13,6 @@ Maintain strict API contracts and consistent server/client mock behavior.
 ## Do
 
 - Keep request/response shapes schema-driven and type-safe.
-- New endpoints and client mutations/queries must use Zod schemas at the boundary.
 - Reuse endpoint constants and shared response helpers.
 - Keep handler response envelope consistent (`code`, `data`, `message`).
 - Ensure mock handlers reflect real API behavior and error semantics.

apps/basic/.github/instructions/refactor.instructions.md

@@ -14,7 +14,6 @@ Reduce duplication while preserving behavior and public contracts.
 
 - Keep refactors incremental and scoped to one concern per change.
 - Prefer extracting shared utilities/hooks/components over large rewrites.
-- Do not extract a shared module without at least three call sites.
 - Preserve existing external behavior and route/store contracts.
 - Keep diffs reviewable with minimal unrelated formatting churn.
 - Add or update lightweight comments only when logic is non-obvious.