Turn a generated answer into a draft ContentDocument at the same slug — the "Generate page from answer" action.

The answer is REWRITTEN first, not copied: it was written as a reply to one caller mid-conversation, so verbatim it ships "Great question!", direct address ("in your case"), and lead-capture offers into published site content. The rewrite keeps every fact and the first-person company voice while dropping the conversational register.

The customer edits/publishes the draft through the normal Company Docs flow; once published, the static pipeline (R2 + sitemap + llms.txt) serves that slug and the generated page stops being used for it.

AGENTDESK-RD(c1): the BODY of this moved to _pin_answer_page_row so POST /answer-pages/from-message reaches it too. See that helper's docstring for why it is one path rather than two — it is a money path.