[ty] Clarify writing guidance for human readers (#27912)
Sometimes Codex will write prose that assumes familiarity with the
current session, a specific PR change, or the issue that triggered it.
Add general guidance for writing mdtests, code comments, documentation,
PR descriptions, and GitHub issues for their eventual readers, grounded
in the final code and verified evidence.
Keep mdtest-specific advice to explain behavior and its rationale
directly, including a preference for "We reject this assignment" over
"We must reject this assignment." Clarify that common behavior comes
before specialized regressions, and that coherent subsections can be
long when they contain short examples interspersed with prose.
## Test plan
Guidance-only change; no runtime behavior or mdtest scenarios were
added. File-scoped documentation hooks pass.