Writing rules differ per repo, so the same tics keep shipping

[ecv]

Summary

Writing conventions have been accumulating in one person's per-project memory rather than in the shared skill, so each repository enforces a different bar and the same handful of prose tics keeps reaching published bodies.

The rules that can be counted should be refused by the gate instead of relied on from memory, and the ones that cannot should at least be written down once where every repository reads them.

Quoted text and fenced code have to stay exempt, because a body often has to reproduce error output or somebody else's words verbatim.

Done when

• A body carrying a banned tic is refused, and the refusal names what to write instead
• Quoted and fenced content posts unchanged
• Every repository reads the same bar, with nothing left in per-project memory