docs: clarify technical issue requirements (#2226)

Author: thymikee

AGENTS.md

@@ -15,7 +15,7 @@ task procedures only when needed:
 | Adding or changing a CLI flag | `docs/agents/cli-flags.md` |
 | Opening or reviewing a PR | `docs/agents/pull-requests.md` |
 | Running against a real device | `docs/agents/device-verification.md` |
-| Issues, PRDs, and triage labels | `docs/agents/issue-tracker.md`, `docs/agents/triage-labels.md` |
+| Writing issues or PRDs, and triage labels | `docs/agents/issue-tracker.md`, `docs/agents/triage-labels.md` |
 | Web backend setup or diagnostics | `docs/agents/web-backend.md` |
 
 Versioned CLI help is the source of truth for command behavior. Start workflow planning with

docs/agents/issue-tracker.md

@@ -10,6 +10,11 @@ External PRs are not part of the triage request queue. Use `gh pr` commands only
 
 ## Conventions
 
+Write issues as concise implementation contracts. Start with the purpose. Include a concrete API,
+data shape, or CLI example when the issue changes a boundary. State required behavior, observable
+completion conditions, and dependencies. Use plain, direct sentences. Remove persuasion, repeated
+context, and filler, but never remove a normative requirement to make the issue shorter.
+
 `gh` authentication may only be available through the user's login shell. In sandboxed agent environments, run GitHub operations through the login shell and request escalation for network/auth access, for example:
 
 ```sh