style(ghost): name "answering unasked questions" as a tell in both passes

ghost/skills/draft-post/SKILL.md

@@ -239,6 +239,7 @@ The greps in Phase 5 catch fixed strings. The tells that make writing read as AI
 - **Negative-first.** Lead with the reason, not the absence.
   - _Before:_ "Pages don't get their own tools." → _After:_ "Because a page is the same object as a post, the tools take a `type` argument."
 - **Slip-narration.** Present the working config, not a blow-by-blow of what broke and how it got fixed.
+- **Answering unasked questions.** Pre-emptive explanation of mechanisms, alternatives, dead ends, or edge cases the reader didn't need. A paragraph justifying why some other approach wouldn't work — when the reader never asked about that approach — is a cut. One clause of warning is the ceiling for a dead end, and only when the reader would plausibly hit it. If a sentence exists to head off a hypothetical objection, delete it.
 
 Fix these in the file. Only then continue to the hand-off.
 

ghost/skills/revise-post/SKILL.md

@@ -174,6 +174,7 @@ If the style guide is available, also check:
 - **Retcon** — a fix dressed up as intentional design; describe what the thing does and why, not a story of having meant it all along.
 - **Overselling** — "I set one rule at the start", "the part I lean on"; understate.
 - **Negative-first** — lead with the reason, not the absence ("Because a page is the same object as a post…," not "Pages don't get their own tools").
+- **Answering unasked questions** — pre-emptive explanation of mechanisms, alternatives, dead ends, or edge cases the reader didn't need. One clause of warning is the ceiling for a dead end, and only when the reader would plausibly hit it. If a sentence exists to head off a hypothetical objection, delete it.
 
 #### Axis 3 — Content and accuracy