amacgregor / amgr_phx / 5fe7517471324ac16966b98fae6c6b03de62a64c-PR-74

33%

main: 33%

Pull #74

github

Post the article link as an X reply instead of in the post body

X drafts now ship as a two-post thread: the copy leads, the URL follows as a
reply. LinkedIn, Threads and Mastodon are unchanged and keep the link inline.

The reasoning is a hypothesis, not a finding. @allanmacgregor averaged 89
impressions per post over 32 posts against 2,763 followers, and link-in-body
suppression is the cheapest candidate cause to eliminate — but nobody outside X
can observe its ranker, and two other causes are equally live: everything
tracked shipped through the Typefully API rather than natively, and the account
does almost no outbound engagement. This change is worth making because it is
cheap and reversible, not because the diagnosis is proven.

Scoped to X on purpose. Moving the link off platforms that aren't suspected of
demoting it would cost click-through to buy nothing, so the behaviour is a
one-entry @link_in_reply list rather than a rewrite of build_content.

Two details that would quietly undo the point if got wrong: the card stays on
the lead post, which is the one being ranked, and the reply keeps the x-tagged
UTM, without which the change would trade reach for blind analytics — and the
tagging is what the ticket's own success measure depends on.

Verified against the Typefully v2 OpenAPI spec: every platform's `posts` array
takes up to 50 items, so a thread is the documented shape rather than a trick.

Four existing tests assumed one post per platform and would have kept passing
while asserting against the wrong post. Rewrote those and added coverage for
the reply shape, UTM survival, media placement, and the URL appearing exactly
once per platform.

VEN-46

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

8 of 8 new or added lines in 1 file covered. (100.0%)

528 of 1602 relevant lines covered (32.96%)

332.64 hits per line