Article exported as a thread of images plus the author's replies #41

Impact

"Create AI link" on an X Article can publish a capsule with no article text: the article's images, laid out as a thread of posts, followed by the author's own replies. Two owner-reported capsules (899e7abb…, b81752ef…, 2026-10-05) look like this.

When the Article path does run, it has two smaller defects:

• The capsule title is the first h1 in the body (e.g. "Intro to Crypto") instead of the article title ("The Sunk Cost Cage").
• The cover image is missing.

Cause

1. On an Article status page, X can mount the article's tweet before the rich-text reader. At that instant detectPageType() returns post, so ensurePerPostControls puts a per-post control on the article tweet. Once the reader mounts, ensureArticleHeaderControl bails because a post control already exists in the column. Clicking it calls runExport('share', { targetTweetEl }), which forces type = 'post' and runs buildModelForPost with thread scope. That path reads tweetText only (articles have none), collects the article's images, and appends same-author replies as "Post n of N".
2. X dropped the twitterArticleReadView wrapper. The current root is twitterArticleRichTextView, and twitter-article-title plus the cover tweetPhoto now sit outside it. buildModelForArticle searched for both only inside the root.

Environment

Brave, MV3 extension v1.6.4 (main 61cbb77), live X DOM on 2026-10-05.

Next action

Route any export whose target is the focused Article tweet to the Article model. Let the Article header control replace a post control on that tweet. Read the title and cover from the article tweet. Add jsdom regression tests with the current DOM shape.