AGENTS.md: platform gaps wait for the platform — no app-side workaround, no temporary fixture

[zhuangjianguo]

What changed

One row of AGENTS.md's delivery-process table, Platform gaps:

• Before: "Report, never patch. … The app may carry an env-gated temporary fixture that names the platform issue."
• After: "Report, then wait — never patch, never work around." The app does not reshape its own metadata to dodge a platform defect (splitting a screen, moving a gate, duplicating a page or a check), and carries no temporary fixture for one. The card that needs the fix carries Blocked-by: on the platform issue and waits for it.

Why

These are maintainer rulings from 2026-10-10, quoted verbatim. Both came during the #87 browser pass, after the agent had suggested splitting the intake screen to work around the console's single-column dialog:

• 「平台的问题就等平台，这个应该写入 agents.md」
• 「fixture 例外删掉，推送并开 PR」

Notes for the reviewer

• AGENTS.md is a governed surface, so the maintainer merges this PR.
• AGENTS.md:62 still says "This is not hypothetical — see the fixture in pnpm-workspace.yaml." That sentence describes an existing artifact under the boot-warnings rule and does not grant an exception, so it is left as is. Say if it should go too.
• PR The two surfaces that merely restate the gate set should name pnpm verify instead of enumerating it — a restatement of a definition cannot be allowed to drift #81 also edits AGENTS.md but does not touch this row; the two should merge without a content conflict.

Gates

pnpm verify → exit 0 on b5be4f6:

  ✓ Validation passed (1432ms)
✓ i18n gate
  COVERAGE : 0 missing keys across 2 locale(s)

lint and typecheck are part of the same pnpm verify run. Only the existing author-time warnings appear (approval-approvers-may-resolve-empty × 6, unchanged by this docs-only diff).

🤖 Generated with Claude Code

https://claude.ai/code/session_012BtouqNfFazqX5akwoC8Jk

---

Generated by Claude Code