Internal Tork partner canary for the D1 handoff path
This is an internal Tork Media partner-API canary published on 4 September 2026. It is not a customer order, marketplace fulfillment, or public announcement. The unique marker for this run is TM-PARTNER-CANARY-20260904-ADAM.
The partner path must require a real CMS post id, a verified permalink, and a public-page proof. It must not invent a URL. Replay of the same request must not create a second post. This article exists so those invariants can be checked on a confirmed non-Premium Tork-owned host.
Tork Media operates a publishing platform for guest posts, feature articles, listicles, and press releases. The partner direct-publish API is a narrow machine interface for trusted internal work. It is not a replacement for the dashboard order flow and it is not a multi-site fan-out.
A canary article should be obviously internal. The title names the canary. The body names the marker. The byline is an internal label. The destination is a Tork-owned WordPress site that is not Premium, not NewsBlaze, not SiteTrail, and not a customer marketplace listing.
WordPress remains the system of record for the live URL. The Worker stores the publication ledger, the work item, and the execute fact. GitHub Actions or an admin trigger may ask the Worker to publish. The Worker already holds the CMS credentials and the durable workspace. A second process must not mint a second post when the first response is lost.
Media recovery stays cold-process safe. If this canary has no featured image, that is intentional. Featured media would exercise a second port. The first live proof is title, body, byline, link, status, and permalink.
Quota is atomic. One accepted job consumes one slot. A replay with the same idempotency key returns the same publication. A different payload with the same key is a conflict. Those rules are already covered by fixtures. This live canary only needs one host and one article.
Do not email customers about this post. Do not invoice it. Do not send it to marketplace buyers. If the public page is later removed, the ledger keeps the receipt so a replay still resolves to the original post id.
The rest of this body is filler so the editorial word-count floor is met. The publishing platform checks client-supplied content before it accepts a partner envelope. Short stubs fail that gate. The sentences below stay on the same internal-canary subject and do not introduce a second product claim.
Internal canaries should be boring on purpose. They should not compete with customer articles. They should not use Premium inventory. They should not target timesla.com for a new post because that host is a live marketplace destination. They should not remint NewsBlaze posts that already have a production id.
Adam confirmed the HANDOFF binding is D1. The Worker lists that binding as torkmedia-handoff. Claims and execute facts belong in that database. Environment variables named HANDOFF are strings and must be ignored. Node publishers call the signed coordinator RPC. They never receive a D1 object.
After this canary, the status endpoint should show published, a https permalink, and a WordPress post id. A second execute with the same work id should report replayed and posts equal to zero. The public HTML should contain TM-PARTNER-CANARY-20260904-ADAM and the approved link to Tork Media.
If anything in that chain fails, stop. Do not retry with a new idempotency key. Do not point the same body at a second host. Read the blocked reason, keep the first receipt, and repair the path.
This paragraph exists to keep the word count honest. Guest-post quality gates are shared with the dashboard. Partner submissions do not get a secret shortcut around banned terms, empty bodies, or chrome titles. The title of this canary is a sentence about an internal publish path, not a portal status string.
One more reminder for operators: LIVE_DISPATCH_ENABLED stays false. This canary is a partner_api exception on a confirmed internal host. It does not turn on live marketplace dispatch. It does not add a Node VM. It does not set OPS_NODE_SWEEP_URL or OPS_NODE_EXECUTOR_URL.
End of internal canary copy. Marker again: TM-PARTNER-CANARY-20260904-ADAM.