@adcp/sdk 9.6.0 → 9.6.2

package/dist/lib/schemas-data/3.1/bundled/protocol/get-adcp-capabilities-response.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/bundled/protocol/get-adcp-capabilities-response.json",
+  "$id": "/schemas/3.1.1/bundled/protocol/get-adcp-capabilities-response.json",
   "title": "Get AdCP Capabilities Response",
   "description": "Response payload for get_adcp_capabilities task. Protocol-level capability discovery across all AdCP protocols. Each protocol has its own capability section.",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.0/core/version-envelope.json"
+      "$id": "/schemas/3.1.1/core/version-envelope.json"
     },
     {
       "title": "Protocol Envelope",
@@ -44,7 +44,7 @@
           "description": "Per-request opaque caller-supplied correlation object echoed unchanged in the response. Used for buyer-side tracking (UI session IDs, trace IDs, custom metadata) that the agent MUST preserve byte-for-byte without parsing. Distinct from `context_id` (server-managed session identifier) — `context` is caller-owned echo, `context_id` is server-owned session scope. Both MAY appear on the same response.\n\n**Relationship to per-task body-level `context` declarations.** Many task request/response schemas (147 as of 3.1) already declare a body-level `context` field that `$ref`s `/schemas/core/context.json` at the body root. Under the flat-on-the-wire MCP serialization (see `notes` below), envelope-level `context` and body-level `context` occupy the same key on the response root — they are NOT separate fields, they MUST share the same value, and they MUST both `$ref` `core/context.json`. The envelope declaration is **authoritative** for the schema definition; per-task body declarations are mirrors retained for tooling reasons (SDK codegen completeness, per-task validation against the response schema in isolation). Future versions MAY drop body-level `context` declarations from per-task schemas; conformance does not require either declaration to be present, only that the wire value `$ref`s `core/context.json`.",
           "type": "object",
           "additionalProperties": true,
-          "$id": "/schemas/3.1.0/core/context.json"
+          "$id": "/schemas/3.1.1/core/context.json"
         },
         "task_id": {
           "type": "string",
@@ -77,7 +77,7 @@
             "auth-required": "Task requires authentication to proceed",
             "unknown": "Task is in an unknown or indeterminate state"
           },
-          "$id": "/schemas/3.1.0/enums/task-status.json"
+          "$id": "/schemas/3.1.1/enums/task-status.json"
         },
         "message": {
           "type": "string",
@@ -216,7 +216,7 @@
             "message"
           ],
           "additionalProperties": true,
-          "$id": "/schemas/3.1.0/core/error.json"
+          "$id": "/schemas/3.1.1/core/error.json"
         },
         "push_notification_config": {
           "title": "Push Notification Config",
@@ -256,7 +256,7 @@
                       "Bearer",
                       "HMAC-SHA256"
                     ],
-                    "$id": "/schemas/3.1.0/enums/auth-scheme.json"
+                    "$id": "/schemas/3.1.1/enums/auth-scheme.json"
                   },
                   "minItems": 1,
                   "maxItems": 1
@@ -277,7 +277,7 @@
           "required": [
             "url"
           ],
-          "$id": "/schemas/3.1.0/core/push-notification-config.json"
+          "$id": "/schemas/3.1.1/core/push-notification-config.json"
         },
         "governance_context": {
           "type": "string",
@@ -427,7 +427,7 @@
         "`status` is REQUIRED on the conceptual envelope across all transports. On MCP and REST it appears as a sibling field at the JSON root (or `structuredContent` root for MCP); on A2A the canonical carrier is `task.status.state`, which maps 1:1 to this `status` value — receivers MUST extract A2A's `task.status.state` into the in-memory envelope `status` per the canonical extraction algorithm. The schema-level `required: [status]` enforces the post-extraction in-memory shape; the transport-native form satisfies the requirement on each wire. `payload` remains intentionally NOT required — it is a documentary grouping construct, never a required wire field. See `mcp-guide.mdx` and `a2a-guide.mdx` for the wire-level patterns receivers MUST implement.",
         "Receivers MUST handle absence of an envelope field (e.g., `replayed` omitted) as the field's documented default — see each field's `default` clause."
       ],
-      "$id": "/schemas/3.1.0/core/protocol-envelope.json"
+      "$id": "/schemas/3.1.1/core/protocol-envelope.json"
     }
   ],
   "properties": {
@@ -596,7 +596,7 @@
               "agent": "Agent consolidates billing across brands and is invoiced by the seller",
               "advertiser": "Seller invoices the advertiser directly, even when a different operator places orders on their behalf"
             },
-            "$id": "/schemas/3.1.0/enums/billing-party.json"
+            "$id": "/schemas/3.1.1/enums/billing-party.json"
           },
           "minItems": 1
         },
@@ -653,7 +653,7 @@
               "flat_rate": "Flat Rate - fixed cost regardless of delivery volume (sponsorships, takeovers)",
               "time": "Time - cost per time unit (hour, day, week, or month) that scales with campaign duration"
             },
-            "$id": "/schemas/3.1.0/enums/pricing-model.json"
+            "$id": "/schemas/3.1.1/enums/pricing-model.json"
           },
           "minItems": 1,
           "uniqueItems": true
@@ -700,7 +700,7 @@
               "gcs",
               "azure_blob"
             ],
-            "$id": "/schemas/3.1.0/enums/cloud-storage-protocol.json"
+            "$id": "/schemas/3.1.1/enums/cloud-storage-protocol.json"
           },
           "minItems": 1,
           "uniqueItems": true
@@ -710,6 +710,11 @@
           "description": "Conformance declaration that this seller supports the full proposal lifecycle on get_products: returned proposals are actionable, draft proposals can be finalized with buying_mode: 'refine' + action: 'finalize', and committed proposals can be executed via create_media_buy with proposal_id before expires_at. Buyers SHOULD NOT use this field to decide whether a specific returned proposal is executable; proposal_status is the per-proposal source of truth. A declaration of true opts the seller into proposal-lifecycle grading. When false or absent, conformance runners skip proposal-lifecycle storyboards, but buyers should still honor any proposals the seller actually returns.",
           "default": false
         },
+        "governance_aware": {
+          "type": "boolean",
+          "description": "Conformance declaration that this seller consults a registered governance agent (via sync_governance plus an outbound check_governance call) before committing a media buy, and surfaces GOVERNANCE_DENIED when the governance agent denies. A declaration of true opts the seller into governance-denial grading (media_buy_seller/governance_denied, media_buy_seller/governance_denied_recovery). When false or absent, conformance runners skip those storyboards - a seller that does not implement outbound governance consultation is not expected to produce GOVERNANCE_DENIED. This is independent of baseline sync_governance registration, which remains gradeable on its own.",
+          "default": false
+        },
         "propagation_surfaces": {
           "type": "array",
           "description": "Where this seller surfaces dependency-resource impairments (creative suspended/rejected post-approval, audience suspended, catalog item withdrawn, event source insufficient, property depublished) to buyers. Non-exclusive: a seller mirroring impairments on both the buy snapshot AND firing webhooks declares `[\"snapshot\", \"webhook\"]` (the common case for premium guaranteed sellers). Each value names one surface where buyers can observe an impairment:\n\n- **`snapshot`** — seller propagates resource transitions into `media_buy.health` and `media_buy.impairments[]` on the next `get_media_buys` read. The `impairment.coherence` compliance assertion grades this surface; storyboards that exercise it (`media_buy_seller/dependency_impairment`, `media_buy_seller/dependency_impairment_cardinality`) require `\"snapshot\"` to be declared, else they grade `not_applicable`.\n- **`webhook`** — seller fires `notification-type: impairment` webhooks (configured via `push_notification_config`). Sellers declaring `\"webhook\"` MUST satisfy the persistent-channel webhook contract for the impairment event type. A seller declaring `[\"webhook\"]` without `\"snapshot\"` is webhook-only — buyers reconcile state from the push channel alone, and snapshot-coherence storyboards grade `not_applicable`.\n- **`out_of_band`** — seller propagates via channels outside the AdCP protocol surface entirely (email to trafficker, separate dashboard, partner-specific notification feed). Long-tail and enterprise-bundled platforms commonly use this when impairment workflows are managed in human channels. Sellers declaring only `[\"out_of_band\"]` are not graded by snapshot or webhook compliance — their bar is the offline agreement, not a protocol assertion. If a seller has impairment data in their API under a non-AdCP field name (a mapping gap, not truly out-of-band), they SHOULD document the mapping rather than declare `out_of_band` — the spec's gap, not the seller's posture, is what `out_of_band` legitimately covers.\n\nDefault: `[\"snapshot\"]` when absent (preserves the existing snapshot-coherence contract for sellers that don't declare). Empty array `[]` is invalid (`minItems: 1`) — omit the field to inherit the default rather than declaring no surfaces. Pick the surfaces that honestly describe where buyers will see impairments on this agent. Mixing is normative — `[\"snapshot\", \"webhook\"]` is the documented common case; `[\"snapshot\", \"webhook\", \"out_of_band\"]` is valid for sellers that ship all three surfaces (rare but legal). See lifecycle.mdx § Compliance for the per-surface contract.",
@@ -760,7 +765,7 @@
           "additionalProperties": {
             "type": "boolean"
           },
-          "$id": "/schemas/3.1.0/core/media-buy-features.json"
+          "$id": "/schemas/3.1.1/core/media-buy-features.json"
         },
         "execution": {
           "type": "object",
@@ -1030,7 +1035,7 @@
                           "ch_plz",
                           "at_plz"
                         ],
-                        "$id": "/schemas/3.1.0/enums/legacy-postal-system.json"
+                        "$id": "/schemas/3.1.1/enums/legacy-postal-system.json"
                       }
                     ]
                   },
@@ -1045,7 +1050,7 @@
                     "minItems": 1,
                     "uniqueItems": true
                   },
-                  "$id": "/schemas/3.1.0/core/postal-area-support.json"
+                  "$id": "/schemas/3.1.1/core/postal-area-support.json"
                 },
                 "age_restriction": {
                   "type": "object",
@@ -1069,7 +1074,7 @@
                           "credit_card",
                           "world_id"
                         ],
-                        "$id": "/schemas/3.1.0/enums/age-verification-method.json"
+                        "$id": "/schemas/3.1.1/enums/age-verification-method.json"
                       }
                     }
                   }
@@ -1147,7 +1152,7 @@
                           "driving": "Motor vehicle travel on road networks",
                           "public_transport": "Public transit including bus, rail, metro, and ferry"
                         },
-                        "$id": "/schemas/3.1.0/enums/transport-mode.json"
+                        "$id": "/schemas/3.1.1/enums/transport-mode.json"
                       },
                       "minItems": 1
                     }
@@ -1337,7 +1342,7 @@
                   "system_generated": "Event generated by an automated system",
                   "other": "Other source (specify in ext)"
                 },
-                "$id": "/schemas/3.1.0/enums/action-source.json"
+                "$id": "/schemas/3.1.1/enums/action-source.json"
               },
               "minItems": 1
             },
@@ -1380,7 +1385,7 @@
                         "unit"
                       ],
                       "additionalProperties": false,
-                      "$id": "/schemas/3.1.0/core/duration.json"
+                      "$id": "/schemas/3.1.1/core/duration.json"
                     },
                     "minItems": 1
                   },
@@ -1454,7 +1459,7 @@
                   "cookies": "Unique browser cookies.",
                   "custom": "Publisher-defined reach unit. Describe in ext."
                 },
-                "$id": "/schemas/3.1.0/enums/reach-unit.json"
+                "$id": "/schemas/3.1.1/enums/reach-unit.json"
               },
               "minItems": 1,
               "uniqueItems": true
@@ -1916,7 +1921,7 @@
             }
           },
           "additionalProperties": true,
-          "$id": "/schemas/3.1.0/sponsored-intelligence/si-capabilities.json"
+          "$id": "/schemas/3.1.1/sponsored-intelligence/si-capabilities.json"
         },
         "brand_url": {
           "type": "string",
@@ -1962,7 +1967,7 @@
               "music": "Rights to musical compositions or recordings (sync, background music)",
               "stock_media": "Rights to stock photography, video, or audio collections"
             },
-            "$id": "/schemas/3.1.0/enums/right-type.json"
+            "$id": "/schemas/3.1.1/enums/right-type.json"
           }
         },
         "available_uses": {
@@ -2002,7 +2007,7 @@
               "commercial": "Use in commercial advertising and promotional contexts",
               "ai_generated_image": "License to produce AI-generated still imagery derived from the rights holder's IP (brand assets, character designs, talent likeness). Distinct from likeness/voice by output modality — a get_rights query filtered on ai_generated_image returns rights whose pricing options cover image generation, regardless of the underlying IP category."
             },
-            "$id": "/schemas/3.1.0/enums/right-use.json"
+            "$id": "/schemas/3.1.1/enums/right-use.json"
           }
         },
         "generation_providers": {
@@ -2146,7 +2151,7 @@
                   "inventory_priority": "Rank by seller-side catalog metadata (margin, overstock, promotional priority). No buyer input.",
                   "random": "Status-quo fallback: agent samples without a ranking preference. Default when selection_strategy is omitted."
                 },
-                "$id": "/schemas/3.1.0/enums/creative-selection-strategy.json"
+                "$id": "/schemas/3.1.1/enums/creative-selection-strategy.json"
               },
               "uniqueItems": true
             }
@@ -2267,7 +2272,7 @@
                           "width"
                         ]
                       },
-                      "$id": "/schemas/3.1.0/core/format-id.json"
+                      "$id": "/schemas/3.1.1/core/format-id.json"
                     },
                     "description": "Authoritative v2 → v1 link, expressed as an array of one or more v1 `format_id` ({agent_url, id}) values. Each entry asserts that this canonical-formats declaration IS the same underlying format as the referenced v1 named format. Always an array (single-ref is `[{...}]`) so the multi-size case below has a clean wire shape — adopters surveyed in the SDK implementor review pushed for this over the lossy single-ref form.\n\nThe v2 declaration's `params` MUST narrow (be compatible with) each referenced v1 format's `requirements` — see the 'Narrows — formal definition' section in canonical-formats.mdx. SDKs comparing dual-emitted shapes (`Product.format_ids[]` ⊇ entries from `v1_format_ref` AND `Product.format_options[]` carrying this declaration) treat the link as the authoritative pairing and run the narrowing check between this declaration and EACH referenced v1 format file's `requirements`.\n\n**Multi-size fan-out (normative).** When the declaration carries `params.sizes: [{w,h}, ...]` (multi-size flexible slot), sellers SHOULD carry one `v1_format_ref[]` entry per size, each pointing at the per-size v1 named format in the AAO catalog. Example: a multi-size image declaration with `sizes: [300x250, 728x90, 970x250]` SHOULD carry `v1_format_ref: [{aao, display_300x250_image}, {aao, display_728x90_image}, {aao, display_970x250_image}]`. v1-only buyers then see the product on all three sizes via the `format_ids[]` dual-emission. When `v1_format_ref[]` count < `sizes[]` count, SDKs MUST emit `FORMAT_DECLARATION_V1_LOSSY_MULTI_SIZE` on the response `errors[]` (advisory, alongside the partial-coverage v1 emit — NOT in place of it). SDKs MAY (non-normative) fan out automatically by catalog lookup when `v1_format_ref[]` has length 1 and `sizes[]` has length N — opt-in, requires catalog access; sellers asserting refs is the source of truth.\n\nMutually exclusive with `canonical_formats_only: true` — a declaration can EITHER assert no v1 projection (`canonical_formats_only: true`) OR link to v1 named formats (`v1_format_ref[]`), never both. When neither is present, SDKs fall back to the resolution order in `v1-canonical-mapping.json` (seller's explicit `canonical` field on the v1 file → registry glob → structural match → fail-closed).\n\nThis is the v2-side authoritative replacement for the v1-side `canonical_parameters` field on `format.json` (which is deprecated for 3.1, removed at 4.0). Sellers SHOULD prefer authoring v2 declarations with `v1_format_ref[]` over mirroring the v2 shape onto v1 files via `canonical_parameters`; the directional link (v2 declaration → v1 identifiers) is the same fact without the parallel-shape drift surface.\n\n**AAO-hosted convention (normative).** For IAB-standard formats (image dimensions, VAST/DAAST tags, standard third-party tags, HTML5 banner bundles), sellers SHOULD point each `v1_format_ref[].agent_url` at the AAO-hosted canonical agent URL `https://creative.adcontextprotocol.org` and use the registry-published id (e.g., `display_300x250_image`, `video_vast_30s`, `audio_standard_30s`, `display_300x250_html`, `display_js`). This converges the v1-wire namespace: every seller's IAB MREC points at the same `{agent_url, id}` pair, so v1-only buyers' allowlists work uniformly. Without this convention, every publisher's 300x250 ships with a different `v1_format_ref` (theirs vs nytimes.example vs cnn.example vs …) and the v1 wire fragments into per-publisher namespaces — exactly what canonical-formats was designed to eliminate.\n\nFor platform-specific formats (Meta Reels, TikTok Spark, Snap Spotlight, etc.), each `v1_format_ref[].agent_url` SHOULD point at the platform's own agent_url when the platform has adopted AdCP and publishes its own `adagents.json` with `formats[]`. When the platform has NOT adopted AdCP, sellers SHOULD point at the AAO community-registry mirror — `https://creative.adcontextprotocol.org/translated/<platform>` + `id: <platform-format-name>` (e.g., `https://creative.adcontextprotocol.org/translated/meta` + `id: meta_reels`). This keeps the v1 namespace converged across all sellers selling that platform's inventory until the platform owns its own adagents.json.\n\n**Platform-adoption cutover (normative).** When a platform adopts AdCP and publishes its own adagents.json, sellers MUST update `v1_format_ref[].agent_url` to the platform's adopted agent_url in the same minor release as the AAO mirror entry's `superseded_by` field goes live (see `static/schemas/source/adagents.json#superseded_by`). The AAO mirror entry SHOULD continue serving for ≥1 minor release after `superseded_by` is set, returning an advisory 'superseded' marker so v1 buyer allowlists keyed on the mirror URL get an explicit signal rather than a silent break. **Identity-confusion note**: the mirror URL is *format-shape namespace*, NOT seller identity. Inventory authorization always flows from `authorized_agents[]` + publisher signing keys; a buyer matching `v1_format_ref[].agent_url` against an allowlist is matching format-shape provenance, not seller identity.\n\n**Mirror domain migration (3.1).** Earlier drafts used `https://mirror.adcontextprotocol.org/translated/<platform>`. As of this release, the convention is `https://creative.adcontextprotocol.org/translated/<platform>` — sibling content under the AAO catalog domain we already host. Adopters who hardcoded the earlier mirror URL MUST migrate to the new path; the canonical-formats.mdx migration section documents the move. No transitional redirect is currently published (the earlier subdomain was never provisioned).\n\nFor seller-bespoke formats (a publisher's `acme_homepage_takeover` that doesn't fit IAB conventions), each `v1_format_ref[].agent_url` is the seller's own agent_url and the id is seller-namespaced. These won't appear in `v1-canonical-mapping.json`'s registry; they're seller-asserted only."
                   },
@@ -2299,7 +2304,7 @@
                         "digest": "sha256:a3f5b7c9d8e2f1a4b6c8d0e2f4a6b8c0d2e4f6a8b0c2d4e6f8a0b2c4d6e8f0a2"
                       }
                     ],
-                    "$id": "/schemas/3.1.0/core/platform-extension-ref.json"
+                    "$id": "/schemas/3.1.1/core/platform-extension-ref.json"
                   }
                 },
                 "allOf": [
@@ -2873,7 +2878,7 @@
                                       "authorization_instructions": "Connect the creator or page that owns the source post."
                                     }
                                   ],
-                                  "$id": "/schemas/3.1.0/core/downstream-connection-requirement.json"
+                                  "$id": "/schemas/3.1.1/core/downstream-connection-requirement.json"
                                 },
                                 "description": "Downstream platform connections or grants required to use this format declaration. These are in addition to the single AdCP caller credential. Use this when a platform product requires multiple downstream grants, such as an advertiser account connection plus a publisher identity or post authorization for published-post references."
                               },
@@ -11137,7 +11142,7 @@
                   "co_view_index",
                   "incremental_lift_percent"
                 ],
-                "$id": "/schemas/3.1.0/core/vendor-metric-id.json"
+                "$id": "/schemas/3.1.1/core/vendor-metric-id.json"
               },
               "standard_reference": {
                 "type": "string",
@@ -11220,7 +11225,7 @@
                 "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
                 "type": "object",
                 "additionalProperties": true,
-                "$id": "/schemas/3.1.0/core/ext.json"
+                "$id": "/schemas/3.1.1/core/ext.json"
               }
             },
             "required": [
@@ -11314,7 +11319,7 @@
           "signed-requests": "DEPRECATED in 3.1 — reclassified to /compliance/{version}/universal/signed-requests.yaml. Advertise request_signing.supported: true in get_adcp_capabilities; this enum value is retained until 4.0 for backward compat but is no longer needed. See https://github.com/adcontextprotocol/adcp/issues/3075 (reclassification) and https://github.com/adcontextprotocol/adcp/issues/3078 (4.0 enum removal).",
           "sponsored-intelligence": "PREVIEW — agent claim for SDKs that dispatch on specialism ID (parity with `signal-marketplace`, `creative-template`, etc.). The storyboard is a placeholder pointing back to the `sponsored-intelligence` protocol baseline (`si_get_offering` → `si_initiate_session` → `si_send_message` → `si_terminate_session`). Promotes to `stable` when the SI tools graduate from `x-status: experimental`. See https://github.com/adcontextprotocol/adcp/issues/3961."
         },
-        "$id": "/schemas/3.1.0/enums/specialism.json"
+        "$id": "/schemas/3.1.1/enums/specialism.json"
       },
       "uniqueItems": true
     },
@@ -11585,7 +11590,7 @@
         "phrase": "Ads serve when the query contains the keyword phrase in order",
         "exact": "Ads serve only when the query matches the keyword exactly"
       },
-      "$id": "/schemas/3.1.0/enums/match-type.json"
+      "$id": "/schemas/3.1.1/enums/match-type.json"
     },
     "UIDType": {
       "title": "UID Type",
@@ -11617,7 +11622,7 @@
         "world_id_nullifier": "World ID nullifier — a Sybil-resistant, relying-party-scoped, unlinkable pseudonym. Carries NO personhood or age assertion on its own; trust comes only from an accompanying verified `attestation`, never from this type tag. Distinct from the `world_id` value in the age-verification-method enum, which names a method, not an identifier.",
         "other": "Other universal ID type (specify in ext)"
       },
-      "$id": "/schemas/3.1.0/enums/uid-type.json"
+      "$id": "/schemas/3.1.1/enums/uid-type.json"
     },
     "EventType": {
       "title": "Event Type",
@@ -11689,7 +11694,7 @@
         "submit_application": "User submitted an application (loan, job, etc.)",
         "custom": "Custom event type (specify in custom_event_name)"
       },
-      "$id": "/schemas/3.1.0/enums/event-type.json"
+      "$id": "/schemas/3.1.1/enums/event-type.json"
     },
     "MediaChannel": {
       "title": "Media Channel",
@@ -11739,7 +11744,7 @@
         "product_placement": "Product placement, branded content, and sponsorship integrations",
         "sponsored_intelligence": "Sponsored Intelligence — advertising within AI assistants, AI search, and generative AI experiences via the reversed data flow"
       },
-      "$id": "/schemas/3.1.0/enums/channels.json"
+      "$id": "/schemas/3.1.1/enums/channels.json"
     },
     "LogoSlot": {
       "title": "Logo Slot",
@@ -11775,11 +11780,11 @@
         "co_brand_lockup": "Co-brand, partner, sponsor, or secondary-mark lockup.",
         "marketplace_listing": "Marketplace, catalog, directory, or store listing logo."
       },
-      "$id": "/schemas/3.1.0/enums/logo-slot.json"
+      "$id": "/schemas/3.1.1/enums/logo-slot.json"
     }
   },
   "_bundled": {
-    "generatedAt": "2026-06-18T08:17:01.073Z",
+    "generatedAt": "2026-06-30T19:14:40.392Z",
     "note": "This is a bundled schema with all $ref resolved inline. For the modular version with references, use the parent directory."
   }
 }

package/dist/lib/schemas-data/3.1/bundled/protocol/get-task-status-request.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.0/bundled/protocol/get-task-status-request.json",
+  "$id": "/schemas/3.1.1/bundled/protocol/get-task-status-request.json",
   "title": "Get Task Status Request",
   "description": "Request parameters for the get_task_status AdCP tool. This is a 3.x protocol-namespace alias for the legacy AdCP tasks/get polling surface, not a transport-native MCP/A2A tasks/* method. It retrieves a specific AdCP application-layer async task by ID with optional conversation history and terminal result payload.",
   "type": "object",
@@ -28,7 +28,7 @@
           "maximum": 99
         }
       },
-      "$id": "/schemas/3.1.0/core/version-envelope.json"
+      "$id": "/schemas/3.1.1/core/version-envelope.json"
     }
   ],
   "properties": {
@@ -80,7 +80,7 @@
                     "nike",
                     "pampers"
                   ],
-                  "$id": "/schemas/3.1.0/core/brand-id.json"
+                  "$id": "/schemas/3.1.1/core/brand-id.json"
                 },
                 "industries": {
                   "type": "array",
@@ -192,7 +192,7 @@
                                 "human_edits": "Content augmented, corrected, or enhanced by humans using non-generative tools",
                                 "data_driven_media": "Assembled from structured data feeds (DCO templates, product catalogs, weather-triggered variants)"
                               },
-                              "$id": "/schemas/3.1.0/enums/digital-source-type.json"
+                              "$id": "/schemas/3.1.1/enums/digital-source-type.json"
                             },
                             "ai_tool": {
                               "type": "object",
@@ -311,7 +311,7 @@
                                       "manifest_wrapper": "A provenance manifest embedded in the file container per format-specific rules (e.g., JUMBF box in JPEG, C2PATextManifestWrapper in plaintext per C2PA Section A.7). The manifest travels with the file but is tied to the file's byte structure.",
                                       "provenance_markers": "Invisible markers embedded within the content stream that encode or reference a provenance record. Designed to survive reformatting, copy-paste, CMS ingestion, and ad-server transcoding that breaks file-level bindings."
                                     },
-                                    "$id": "/schemas/3.1.0/enums/embedded-provenance-method.json"
+                                    "$id": "/schemas/3.1.1/enums/embedded-provenance-method.json"
                                   },
                                   "standard": {
                                     "type": "string",
@@ -377,7 +377,7 @@
                                       "video": "Watermark applied to video content (e.g., per-frame image watermarking, temporal watermarking)",
                                       "text": "Watermark applied to text content (e.g., synonym substitution, structural modification)"
                                     },
-                                    "$id": "/schemas/3.1.0/enums/watermark-media-type.json"
+                                    "$id": "/schemas/3.1.1/enums/watermark-media-type.json"
                                   },
                                   "provider": {
                                     "type": "string",
@@ -415,7 +415,7 @@
                                       "c2pa.watermarked.bound": "Watermark linked to a C2PA manifest for this asset. The watermark and manifest are mutually reinforcing: the manifest references the watermark, and the watermark can be used to locate the manifest.",
                                       "c2pa.watermarked.unbound": "Watermark independent of any C2PA manifest. Applied before any provenance signing event (e.g., by the AI generator at creation time) or in pipelines where no manifest is present."
                                     },
-                                    "$id": "/schemas/3.1.0/enums/c2pa-watermark-action.json"
+                                    "$id": "/schemas/3.1.1/enums/c2pa-watermark-action.json"
                                   },
                                   "embedded_at": {
                                     "type": "string",
@@ -479,7 +479,7 @@
                                               "initial": "Disclosure must appear at the start of content for a minimum duration before it may be removed. Pair with min_duration_ms in render_guidance or creative brief to specify the required duration.",
                                               "flexible": "Disclosure presence is sufficient; placement timing and duration are at the publisher's discretion"
                                             },
-                                            "$id": "/schemas/3.1.0/enums/disclosure-persistence.json"
+                                            "$id": "/schemas/3.1.1/enums/disclosure-persistence.json"
                                           },
                                           "min_duration_ms": {
                                             "type": "integer",
@@ -503,7 +503,7 @@
                                                 "pre_roll",
                                                 "companion"
                                               ],
-                                              "$id": "/schemas/3.1.0/enums/disclosure-position.json"
+                                              "$id": "/schemas/3.1.1/enums/disclosure-position.json"
                                             },
                                             "minItems": 1,
                                             "uniqueItems": true
@@ -513,7 +513,7 @@
                                             "description": "Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.",
                                             "type": "object",
                                             "additionalProperties": true,
-                                            "$id": "/schemas/3.1.0/core/ext.json"
+                                            "$id": "/schemas/3.1.1/core/ext.json"
                                           }
                                         },
                                         "additionalProperties": true
@@ -586,7 +586,7 @@
                             }
                           },
                           "additionalProperties": true,
-                          "$id": "/schemas/3.1.0/core/provenance.json"
+                          "$id": "/schemas/3.1.1/core/provenance.json"
                         }
                       },
                       "required": [
@@ -596,7 +596,7 @@
                         "height"
                       ],
                       "additionalProperties": true,
-                      "$id": "/schemas/3.1.0/core/assets/image-asset.json"
+                      "$id": "/schemas/3.1.1/core/assets/image-asset.json"
                     },
                     "colors": {
                       "type": "object",
@@ -646,7 +646,7 @@
                   "domain": "acme-corp.com"
                 }
               ],
-              "$id": "/schemas/3.1.0/core/brand-ref.json"
+              "$id": "/schemas/3.1.1/core/brand-ref.json"
             },
             "operator": {
               "type": "string",
@@ -692,7 +692,7 @@
           "sandbox": true
         }
       ],
-      "$id": "/schemas/3.1.0/core/account-ref.json"
+      "$id": "/schemas/3.1.1/core/account-ref.json"
     },
     "include_history": {
       "type": "boolean",
@@ -709,7 +709,7 @@
       "description": "Opaque correlation data that is echoed unchanged in responses. Used for internal tracking, UI session IDs, trace IDs, and other caller-specific identifiers that don't affect protocol behavior. Context data is never parsed by AdCP agents - it's simply preserved and returned.",
       "type": "object",
       "additionalProperties": true,
-      "$id": "/schemas/3.1.0/core/context.json"
+      "$id": "/schemas/3.1.1/core/context.json"
     },
     "ext": {
       "title": "Extension Object",
@@ -752,7 +752,7 @@
     }
   ],
   "_bundled": {
-    "generatedAt": "2026-06-18T08:17:01.078Z",
+    "generatedAt": "2026-06-30T19:14:40.395Z",
     "note": "This is a bundled schema with all $ref resolved inline. For the modular version with references, use the parent directory."
   }
 }