Context
`adcontextprotocol/adcp#3126` (merged) added typed `include_result` (request) and `result` (response) fields to `tasks/get` for AdCP 3.1.0. PR #980 makes the SDK speak the new wire shape today (sends `include_result: true`, reads typed `result`); both fields are optional and additionalProperties-allowed so it's wire-compatible against pre-3.1.0 sellers.
What's deferred until upstream 3.1.0 ships:
Action items
- Run `npm run sync-schemas` to refresh `schemas/cache/` with 3.1.0 (and `compliance/cache/` if any storyboards moved).
- Bump `ADCP_VERSION` in `src/lib/version.ts` from `'3.0.0'` → `'3.1.0'`.
- Append `'3.1.0'` to `COMPATIBLE_ADCP_VERSIONS`.
- Update generated types: `TasksGetRequest` should now include `include_result`, `TasksGetResponse` should include `result` (typed against `async-response-data.json`).
- The runtime mapping in `mapTasksGetResponseToTaskInfo` (`src/lib/core/TaskExecutor.ts:75-180`) reads `flat.result` as `unknown`; once the typed `result` lands we can narrow to the spec's `async-response-data` shape.
- Drop the changeset note about pre-3.1.0 `additionalProperties` informal passthrough — the typed and informal paths converge.
Out of scope
Related
Context
`adcontextprotocol/adcp#3126` (merged) added typed `include_result` (request) and `result` (response) fields to `tasks/get` for AdCP 3.1.0. PR #980 makes the SDK speak the new wire shape today (sends `include_result: true`, reads typed `result`); both fields are optional and additionalProperties-allowed so it's wire-compatible against pre-3.1.0 sellers.
What's deferred until upstream 3.1.0 ships:
Action items
Out of scope
Related