feat: support Premium long-form posts

[hhh2210]

Summary

Fixes #54.

Adds automatic routing to X's long-form post mutation for Premium accounts when a post exceeds the standard 280 weighted-character limit.

What changed

• Register CreateNoteTweet in GraphQL fallback query IDs.
• Add long-form related feature flags used by the write mutation.
• Route create_tweet() and quote_tweet() to CreateNoteTweet when text is over the standard weighted limit.
• Include disallowed_reply_options: null for long-form writes; without this field X can return an empty tweet_results object.
• Keep standard posts at or below the limit on the existing CreateTweet path.
• Document automatic long-form routing in README.

Why this scope

This intentionally keeps the patch narrower than #62: it does not add video upload or Article publishing. Article publishing appears to be a separate X entity flow (ArticleEntityDraftCreate / update title / update content / publish) and should be handled as a separate feature with its own payload tests.

Compared with #60, this also covers quote tweets and includes local tests for the routing and payload shape.

Validation

• uv run ruff check .
• uv run mypy twitter_cli
• uv run pytest -q
• Manual local smoke on a Premium account: posted a >280 character long-form post successfully, then deleted the test post successfully.

[hhh2210]

Article publishing note: this PR intentionally only fixes long-form posts.

X Articles use a separate entity flow (ArticleEntityDraftCreate, ArticleEntityUpdateTitle, ArticleEntityUpdateContent, ArticleEntityPublish) rather than CreateTweet / CreateNoteTweet. The repo already supports reading/exporting Articles through twitter article; publishing Articles should be a separate feature because it needs a reliable rich content-state payload builder and dedicated tests.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds long-form (“Note Tweet”) support by routing oversized tweet text to X’s CreateNoteTweet GraphQL mutation, while updating feature flags, tests, and user-facing docs.

Changes:

• Add CreateNoteTweet operation + long-form related feature flags in GraphQL config.
• Route create_tweet / quote_tweet to CreateNoteTweet when text exceeds the weighted length threshold; parse results from multiple response shapes.
• Add unit tests and README documentation for long-form routing behavior.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
twitter_cli/graphql.py	Adds CreateNoteTweet operation id and enables long-form/article-related feature flags.
twitter_cli/client.py	Implements weighted-length routing to CreateNoteTweet, shared result extraction, and improved error messages.
tests/test_client.py	Adds coverage for routing logic and asserts the chosen mutation name/variables.
README.md	Documents automatic routing for Premium long-form posts.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[hhh2210]

#60 by @rakei076 reached the same core conclusion 17 days earlier — including the disallowed_reply_options silent-failure discovery. Credit where due; I should have referenced it when opening this.

What this PR adds on top of #60:

• quote_tweet routing — feat: support long-form tweets via CreateNoteTweet #60 only routes create_tweet, so long-form quote tweets still go through the standard mutation and fail with error 186
• regression tests for both paths, including assertions that standard-length posts keep using CreateTweet so future changes can't silently flip the operation
• response parsing tolerant to all three envelopes seen from this mutation family (create_tweet / notetweet_create / create_note_tweet), in the spirit of the fix: adapt to Twitter API schema changes (April 2026) #51 schema-drift fixes
• README docs (EN + ZH sections)

Happy to either rebase this as a follow-up on top of #60, or have maintainers pick whichever — the quote path and the tests are the parts worth landing either way.

[hhh2210]

#60 is still open too, so this and that PR are both waiting on the same routing decision. Whenever you get a chance, let me know if you'd rather I rebase the quote_tweet routing on top of #60 or take this one as-is — happy to go either way.

[hhh2210]

@jackwener, I cleared the open review findings on this PR and #65.

This branch now uses twitter-text v3-style weights, 23-character URL normalization, operation-scoped NoteTweet flags, and one shared create/quote routing helper. #65 now fails closed when Article publishing returns no confirmation. Full Python 3.10 suites, Ruff, and mypy pass in both branches. Could you take a look when you have time?