Allow Threads text-only posts.publish - #25
Conversation
The reviewed create path is configure_text_post_app_feed. Attachment was required only because the captured fixture included an image. Keep PNG image posts on the same contract and snapshot 1.4.0 as the image-required predecessor. Co-authored-by: ben <0thernet@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Adding the text-only publish writer identity increases the durable inventory from 283 to 284 rows. Snapshot the new hashes so every NODE_ENV mode still pins the exact predecessor writer identities. Co-authored-by: ben <0thernet@users.noreply.github.com>
The current adapter is 1.5.0. Recovery and bundled upgrades still need the image-required 1.4.0 snapshot next to the other historical Threads manifests. Co-authored-by: ben <0thernet@users.noreply.github.com>
|
Closing as superseded by #42 after recovering the still-valid behavior onto the current release stack. The successor preserves the active Threads media.publish@1 video path, archives the prior v1.6.0 adapter exactly, and advances the active adapter to v1.7.0 with posts.publish@5 text-only support. Exact successor head 860a32e was independently audited with no P0/P1/P2 findings. Its local full gate exited 0 with 2,766 pass, 1 skip, 0 fail in the main suite, 18/18 serial omni tests, and the standalone package smoke complete. All exact-head hosted PR checks passed. #42 squash-merged as fca412b. Exact postmerge run 32622325676 completed successfully on that SHA, including Linux check, macOS, package smoke, and Required. This original PR is stale against the current adapter and release history and cannot merge safely as written, so it is closed unmerged. Its source branch remains retained at exact original head 2f8ba64 for provenance. |
2 participants
The installed
threads-web1.4.0 contract markedposts.publishattachmentrequired because the reviewed live fixture was an image post. Threads itself accepts text-only posts, and the official create-container path documentsmedia_type=TEXT. Preview therefore rejected ordinary text withinput.attachment is required, which is why recent cross-posts skipped Threads rather than invent a dummy PNG.This keeps the installed
threads-webcookie-session transport.posts.publish@5now requiresbodyand treats the existing PNGattachmentas optional. Image posts still use the reviewed rupload plusconfigure_text_post_app_feedpath. Text-only posts skip rupload and use that same create form, then bind a locator-only target and verify permalink actor/text with no image.Behavior
posts.publish@4image recovery still works. New text-only recovery uses the locator-only target.Docs
skills/wrenchrouting and platform notes no longer say Threads always needs a PNG.Verification
bun test src/providers/meta-web.test.ts src/providers/meta-web-runtime.internal.test.ts src/plugins/meta-web/plugin.test.ts src/scripts/sync-bundled-adapters.test.tsbun run check