Allow Threads text-only posts.publish

package.json

@@ -111,6 +111,7 @@
     "src/assets/adapters/threads/wrench-web-adapter.v1.1.0.json",
     "src/assets/adapters/threads/wrench-web-adapter.v1.2.0.json",
     "src/assets/adapters/threads/wrench-web-adapter.v1.3.0.json",
+    "src/assets/adapters/threads/wrench-web-adapter.v1.4.0.json",
     "src/assets/adapters/tiktok/wrench-web-adapter.json",
     "src/assets/adapters/whatsapp/wrench-web-adapter.json",
     "src/assets/adapters/whatsapp/wrench-web-adapter.v1.0.0.json",

skills/wrench/references/platform-patterns.md

@@ -82,7 +82,7 @@ template.
 - Treat Instagram, Threads, Facebook Page, Facebook Group, and Facebook Marketplace as separate surfaces and auth/account bindings even when Meta shares infrastructure.
 - Live-proven direct R1 coverage currently includes Instagram feed/post/media/comment/inbox summaries, the Threads feed, Facebook's bounded initial personal home-feed bootstrap, one exact Group's bounded first feed page, the Marketplace browse feed with cursor continuation, and one exact Marketplace listing. Every result is exact-current-user bound; Group and Marketplace reads additionally bind their exact numeric targets.
 - The personal Facebook home result makes no completion or pagination claim. The Group reader assembles only the complete first streamed page and never exposes its provider cursor because the matching continuation query is not yet reviewed. Marketplace reads use a direct inert HTML bootstrap, resolve the current registered Relay revision from bounded canonical first-party bundles without executing them, and assemble each complete streamed page before returning a locally authenticated, account/descriptor/target/chain-bound cursor envelope. A locally truncated projection returns no cursor so it cannot skip unreturned listings. Exact listing reads use the inert bootstrap so the browser-only item-seen mutation is never executed.
-- Threads `posts.publish@4` is the one observed Meta write: it requires exactly one plan-bound PNG, binds the exact minimal created locator plus the completed upload dimensions into durable target evidence, and verifies the exact permalink actor, text, and image before success. Facebook personal Messenger listing is capture-required: the current route and folder queries, paging and completeness, and acknowledgement/presence behavior are not proven. Every other Meta write, all message reads/sends, every Facebook Page operation, and all Group operations except the exact first-page feed read remain capture-required. Marketplace messaging and mutations remain capture-required; its observed feed/listing reads do not confer publishing, seller, conversation, or purchase authority.
+- Threads `posts.publish@5` is the one observed Meta write: it publishes exact text with an optional plan-bound PNG, binds the exact minimal created locator plus completed-upload dimensions when an image is supplied, and verifies the exact permalink actor, text, and optional image before success. Facebook personal Messenger listing is capture-required: the current route and folder queries, paging and completeness, and acknowledgement/presence behavior are not proven. Every other Meta write, all message reads/sends, every Facebook Page operation, and all Group operations except the exact first-page feed read remain capture-required. Marketplace messaging and mutations remain capture-required; its observed feed/listing reads do not confer publishing, seller, conversation, or purchase authority.
 - Capture each surface's exact first-party GraphQL/REST exchange and dynamic token source. Do not copy an operation name, revision, feature set, or actor binding across surfaces.
 - DMs, comments, replies, posts, stories, reels, shares, Page messages, Group posts, and Marketplace listing publication are R3. Reversible likes, reactions, follows, and saves may be R2.
 - For Facebook, bind Page/profile/group/Marketplace actor and target independently. Keep roles, ads, business settings, member moderation, purchases, payments, shipping commitments, and deletion R4.

skills/wrench/references/social-platform-routing.md

@@ -10,7 +10,7 @@ Use this as routing guidance only. Always inspect `wrench capabilities <adapter>
 | LinkedIn | `linkedin` | Official OAuth | Inspect installed schema | Documented API post |
 | Bluesky | `bluesky-web` | Profile-backed Bluesky web session | `body`, optional image, media type, and alt text | AT Protocol feed post |
 | Substack | `substack-web` | Browser cookies/profile | `body`, optional Note media | Public Substack Note, not an article/newsletter |
-| Threads | `threads-web` | Browser cookies/profile | `body`, explicit audience when required, one required PNG attachment in the current reviewed schema | Threads post |
+| Threads | `threads-web` | Browser cookies/profile | `body`, explicit audience when required, optional PNG attachment | Threads post |
 
 Cleanup is capability-driven too. At this reference revision, `bluesky-web`
 exposes observed `content.delete@1` only for one current-account post URI plus
@@ -55,5 +55,5 @@ Do not place credentials in the input file. Delete task input files after planni
 - If the ordered image set exceeds one platform's bound, request a smaller shared set or an explicit per-platform set. Do not manufacture a collage.
 - If LinkedIn requires visibility and the user requested a public cross-post, use `public`; otherwise obtain the user's audience choice.
 - If Threads requires `audience` and the user requested ordinary posting, use the installed schema's ordinary/default audience only when that meaning is explicit in the capability description.
-- At this reference revision, the reviewed Threads contract requires exactly one PNG. Treat text-only Threads publication as unavailable unless the installed schema says otherwise.
+- At this reference revision, the reviewed Threads contract publishes text-only posts and optional PNG image posts. When the package is text-only, publish it as text. A dummy PNG, collage, or composer click-path changes the package and is not an installed fallback. JPEG and other image types remain unavailable unless the installed schema independently lists them.
 - If image alt text is supported on only some targets, preserve the same factual description on every target that accepts it; unsupported alt text is not a reason to alter the visible post.

src/assets/adapters/threads/wrench-web-adapter.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 4,
   "id": "threads-web",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "displayName": "Threads (Authenticated Internal API)",
   "surfaceId": "threads",
   "origins": [
@@ -367,9 +367,9 @@
       }
     },
     "posts.publish": {
-      "description": "Observed contract: publish one confirmed Threads post with one reviewed PNG after exact viewer binding, synchronous upload completion, exact minimal created-locator binding, durable upload-dimension target retention, and independent exact permalink actor/text/image readback.",
+      "description": "Observed contract: publish one confirmed Threads post with optional reviewed PNG after exact viewer binding, optional synchronous upload completion, exact minimal created-locator binding, durable response-bound post identity plus completed-upload dimensions when an image is supplied, and independent exact permalink actor/text and optional image readback.",
       "risk": "R3",
-      "sideEffect": "Publishes one externally visible Threads post with the exact confirmed text and one reviewed PNG.",
+      "sideEffect": "Publishes one externally visible Threads post with the exact confirmed text and optional reviewed PNG.",
       "idempotency": "local-at-most-once",
       "dedupeWindowMs": 86400000,
       "input": {
@@ -382,7 +382,7 @@
           },
           "attachment": {
             "type": "file",
-            "description": "One exact reviewed PNG attachment",
+            "description": "Optional exact reviewed PNG attachment",
             "maxBytes": 20971520,
             "mediaTypes": [
               "image/png"
@@ -397,14 +397,13 @@
           }
         },
         "required": [
-          "attachment",
           "body"
         ]
       },
       "webSession": {
         "site": "threads",
         "action": "posts.publish",
-        "contractVersion": 4,
+        "contractVersion": 5,
         "timeoutMs": 60000,
         "maxOutputBytes": 8388608
       }