akita-finish: finishing touches for an article

This is the third pass of the article pipeline, applied to the file on disk:

Draft the article from the brief and the sources.
fact-check: adversarial verification of every claim, number and attribution against the sources. Run the fact-check skill's checker prompt (references/checker-prompt.md) inside isolated general-purpose agents in this session: one agent for claims verifiable against local source files, one or more for web claims. Do not use the external CLI harnesses (grok/zcode/codex) unless Akita asks. Apply the corrections.
humanizer: remove AI-writing tells.
akita-finish (this skill): structure, rhythm, emphasis, numbers and voice bans.

Run it as an explicit pass over the finished text. Do not rely on having "kept the rules in mind" while composing; count and grep.

Pass 1: structure

Paragraph ceiling: 4 sentences. Count sentences in every prose paragraph (skip tables, lists, blockquotes, headings). Split anything with 5 or more at the beat boundary. Short paragraph after long paragraph is part of the voice.
List-shaped prose becomes a list. A paragraph that enumerates 4+ parallel items (use cases, tasks, conditions, metrics, options, steps) becomes a bulleted or numbered list. Keep one short intro sentence before it.
Blockquotes for takeaways. Put the key conclusion of a section, the TL;DR, warnings and "what this means for you" in a > blockquote. Also use one to break any stretch of 6 to 8 consecutive plain paragraphs with no visual break.
### subsections to scope any ## section longer than roughly 6 to 8 paragraphs. Headings in sentence case, no Title Case.
Narrative flow per section: the point first, then the evidence, then what it means for the reader.