docs: keep gate cadence guidance agent-only

docs/development.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write
-development.md: 509888b3d74bd22de658c5176355bb34d95e4cfd
-development.zh.md: 5260eeefccac99cd8080f0bef8c9b4f3fd04fca9
+development.md: f032764fff29baaca007211db8b69d9a5129078f
+development.zh.md: 3a650d03ce7cafd0e34290ae918e5a303c2ad8a9

docs/development.md

@@ -84,8 +84,6 @@ The GitHub workflow runs these gates on each pull request:
 
 `pnpm run hygiene` is the local shorthand for `pnpm run knip && pnpm run publint && pnpm run constraints && pnpm run verify-node-next-types`; CI also runs `pnpm run constraints` as an earlier fail-fast step, then runs the full hygiene script after `pnpm run build`.
 
-During implementation, prefer the narrowest gate that can fail for the change you just made: filtered tests for touched packages/specs, `pnpm run typecheck` after type or API changes, `pnpm run lint` after code edits, and the specific doc/generator check only when that surface changed. Run the full CI-gate sequence from `AGENTS.md` once the change is complete and before marking a PR ready; repeat it only after later edits could invalidate the result.
-
 ## Daily commands
 
 Use these from the repo root:

docs/development.zh.md

@@ -84,8 +84,6 @@ GitHub 工作流在每个 pull request 上运行这些门禁：
 
 `pnpm run hygiene` 是 `pnpm run knip && pnpm run publint && pnpm run constraints && pnpm run verify-node-next-types` 的本地简写；CI 还会把 `pnpm run constraints` 作为更早的快速失败步骤单独跑一次，然后在 `pnpm run build` 之后跑完整的 hygiene 脚本。
 
-开发过程中，优先运行刚才那次改动可能打红的最窄门禁：针对受影响 package/spec 的过滤测试；类型或 API 变动后跑 `pnpm run typecheck`；代码改动后跑 `pnpm run lint`；只在触及文档或生成面时跑对应的 doc/generator 检查。改动完成、准备把 PR 标为 ready 前，再按 `AGENTS.md` 中的完整 CI 门禁跑一遍；只有后续改动可能让结果失效时才重复全量。
-
 ## 日常命令
 
 在仓库根目录使用：