docs(workspace): require comments stay on one line when possible

AGENTS.md

@@ -137,6 +137,7 @@ The game is **multithreaded by design** — single-threaded would not meet the p
 - **Focus:** Describe the code's behavior, the system's state, or technical invariants. 
 - **Struct Documentation:** Every field in a public or internal struct must have a doc comment (`///`) explaining its purpose and any invariants.
 - **Stability:** Treat the documentation as a technical specification for the engine.
+- **Line breaks:** Do not insert line returns inside a comment unless necessary. A comment that fits on a single line stays on a single line — do not pre-wrap at ~80 chars for aesthetics. Only break across lines when the comment is genuinely long (multi-sentence prose, enumerated invariants) or when a hard break carries meaning (separating an intro line from a bullet list, for instance).
 
 ## Target platforms
 

CLAUDE.md

@@ -137,6 +137,7 @@ The game is **multithreaded by design** — single-threaded would not meet the p
 - **Focus:** Describe the code's behavior, the system's state, or technical invariants. 
 - **Struct Documentation:** Every field in a public or internal struct must have a doc comment (`///`) explaining its purpose and any invariants.
 - **Stability:** Treat the documentation as a technical specification for the engine.
+- **Line breaks:** Do not insert line returns inside a comment unless necessary. A comment that fits on a single line stays on a single line — do not pre-wrap at ~80 chars for aesthetics. Only break across lines when the comment is genuinely long (multi-sentence prose, enumerated invariants) or when a hard break carries meaning (separating an intro line from a bullet list, for instance).
 
 ## Target platforms