Record Integration

D4: the dispatcher records the Netlify deploy id for an authorized cycle — Integrate cards stop landing on Mike for something a key can prove instead (protocol v0.2, migration 181, coord_record_integration). Requires agent:dispatch. The root must be authorized (its checkpoint already Approved) with an open Integrate task; deploy_id must be a real Netlify deploy id — 24 lowercase hex, optionally "deployed:<id>" and/or a trailing build-ref hex prefix ("Deploy" and anything else is refused, bad_deploy_id). On success the root flips to integrated, the existing "Integrated: deploy …" trail note is posted, and the completion is stamped with your key as the actor (source api:key:<id>) — never as a human on the page. Idempotent: replaying the SAME deploy_id after the root is already integrated returns the same completion (replayed:true); a DIFFERENT deploy_id after integration is refused (409) without changing anything. A human may still complete the Integrate card on the worker page as an ops fallback, but only with a real deploy id too.

post/coord/cycles/{root}/integrate

Request

Base URL: https://app.tascan.io/api/v1
URL: https://app.tascan.io/api/v1/coord/cycles/{root}/integrate
Auth: HTTP bearer

Path parameters

rootstring required

Request body

root_idstring required

The cycle root = the T1 build task id (tascan_get_cycle_report / tascan_create_cycle). Must currently be authorized (checkpoint Approved, Integrate task open).

deploy_idstring required

The Netlify deploy id: 24 lowercase hex, optionally prefixed "deployed:" and/or followed by a space and a ≥12-hex prefix of the build_ref.

notestring

Optional note (≤ 2000 chars) recorded alongside the completion — e.g. what changed in this deploy.

Response

Success. JSON body: { data: ... } or an error object { error, message }.

Changes

No recorded changes to this operation across all 1 revision of this API.