chore(release): align changesets and revert tasks/get for 3.0.1 cut

[bokelley]

Summary

Prepares main for the AdCP 3.0.1 cut. After this lands, npx changeset status reports a single patch bump for adcontextprotocol and 3.0.1 cuts cleanly.

Three commits:

• f4bce25d5 — Revert feat(schema): add result and include_result to tasks/get #3126 (tasks/get result / include_result schema fields). The original PR was milestoned 3.1.0 by its author but landed on main early, forcing the changeset bundle to a minor. Re-add path: git revert f4bce25d5 on a fresh branch after 3.0.1 ships, milestone 3.1.0.
• 534f7b3d9 — Five changesets downgraded minor → patch (add-seed-creative-format-pagination, fix-format-asset-oneof-titles, fix-get-signals-max-results-precedence, hoist-duplicate-inline-enums, hoist-inline-enum-duplicates-tranche-2); envelope-prohibition overlap on protocol-envelope.json resolved by removing the redundant per-property not: {} markers and keeping the top-level not: { anyOf: [{ required: [task_status] }, { required: [response_status] }] } from envelope-forbid-legacy-status-fields; v3-envelope-integrity-conformance.md rewritten as patch scoped to the storyboard contribution.
• 9818fd81e — Align force_task_completion (patch: force_task_completion + create_media_buy_async submitted -> completed roundtrip #3138) and the comply-test-controller schema/docs with 3.0 webhook delivery, since the include_result: true polling path the original framing referenced was reverted.

Closes #2681 (already closed via comment; ships in 3.0.1).

Pre-PR expert review

• ad-tech-protocol-expert: ship it. No semver violations. All five minor→patch downgrades defensible: comply_test_controller is conformance-harness scaffolding (not core protocol), JSON Schema title is annotation-only per draft-07 §10.1, get_signals precedence is a clarification of underspecified collision behavior, and the enum-hoist refactors produce byte-identical bundled subgraphs. Envelope overlap fix is semantically equivalent — top-level not: { anyOf: [{ required: [...] }] } blocks the fields by key presence regardless of value (JSON Schema draft-07 §6.5.3). Revert is clean; the post-revert task-lifecycle.mdx reinstates the correct shipped-3.0.0 webhook-first guidance.
• code-reviewer: no CI blockers. Flagged downstream coupling — force_task_completion (patch: force_task_completion + create_media_buy_async submitted -> completed roundtrip #3138) and the comply-test-controller schema/docs referenced include_result: true from feat(schema): add result and include_result to tasks/get #3126. Fixed in 9818fd81e.

Re-add path for tasks/get result fields

After this PR + the 3.0.1 cut land:

git checkout -b bokelley/readd-tasks-get-result-3-1-0 main
git revert f4bce25d5      # restores everything from #3126 verbatim
git push -u origin bokelley/readd-tasks-get-result-3-1-0
gh pr create --base main --milestone 3.1.0 \
  --title "feat(schema): re-add result and include_result to tasks/get for 3.1.0" \
  --body "Re-adds #3126, reverted in <THIS-PR-NUMBER> to allow 3.0.1 to cut as a clean patch. Closes #3123. Unblocks adcp-client#967."

Test plan

• npx changeset status reports a single patch bump for adcontextprotocol
• Pre-commit hooks passed on all three commits (test:unit, test:test-dynamic-imports, typecheck)
• No remaining include_result references in non-dist/ paths outside the explicit "tracked for 3.1" pointers in task-lifecycle.mdx:195, revert-tasks-get-result-for-3-0-1.md, and tasks-get-include-result-docs-fix.md
• CI green on PR
• After merge: create 3.0.x branch from main, run npx changeset version on it to produce 3.0.1
• Verify dist/protocol/3.0.1.tgz serves end-to-end per the cut-major runbook

🤖 Generated with Claude Code

[bokelley]

CI failure is pre-existing main breakage, not caused by this PR.

The two failing checks (`Storyboards (framework dispatch)` and `Storyboards (legacy dispatch)`) both fail in `signed_requests` with the same 28-vector 401 pattern that's been red on main HEAD since #3351 merged ~20 hours ago. Filed as #3376.

Evidence:

• Last green on main: `c10e95d0` (fix(training-agent): per-route signing authenticator with isolated replay store #3346, 2026-04-27 11:20:34Z) ✅
• First red on main: `2bb3dcd8` (fix(training-agent): PostgresReplayStore so vector 016 catches cross-instance replays #3351, 2026-04-27 11:35:02Z) ❌
• Every PR based on post-`2bb3dcd8` main HEAD is failing identically (e.g. `claude/issue-3349-fix-activate-signal-aliases`, `claude/issue-3350-signals-error-schema-storyboards`)

This PR's diff: changeset frontmatter, one schema cleanup on `protocol-envelope.json`, comply-test-controller doc realignment, and a revert of `tasks/get` schema fields. Zero touch on `training-agent/`, signed-requests verifier code, RFC 9421 docs, or replay-store paths.

Recommend merging on green of all other 21 checks once #3376 is resolved on main and a re-run of these two jobs goes green. Or merge anyway if maintainers agree the failure is unrelated infrastructure noise — every other check is passing, including `Server integration tests`, `TypeScript Build`, `check-snippets`, and `check-schema-links`.

[bokelley]

Acknowledged. The CI failure isolation evidence is clear — signed_requests 401 pattern predates this PR's diff and tracks to #3351 / #3376. No action needed on this PR's side.

---

Generated by Claude Code

[bokelley]

Got it — no action needed on this PR's side.

---

Generated by Claude Code