feat(decisioning): re-export SignalsFeatures + ContentStandards capability sub-models

Closes the re-export gap flagged by the code-reviewer in adcontextprotocol#484
(post-merge polish issue adcontextprotocol#485 P1). Two capability sub-models were
reachable via Pydantic nested construction but not surfaced through
:mod:`adcp.decisioning.capabilities`, forcing adopters to dig into
``generated_poc`` for deep declarations.

* ``SignalsFeatures`` — codegen name ``Features2`` (numbered because
  ``Features`` already names the media_buy features block). Surfaced
  under a stable adopter-facing name so ``Signals(features=...)``
  declarations read cleanly.
* ``ContentStandards`` — type of ``MediaBuy.content_standards``.
  Collides with ``adcp.types.ContentStandards`` (unrelated wire model
  on the content-standards protocol), so disambiguated via
  ``CapabilitiesContentStandards`` in :mod:`adcp.types.capabilities`
  and re-aliased back to the wire-spec name within
  :mod:`adcp.decisioning.capabilities`. Same pattern as ``Account`` /
  ``MediaBuy`` / ``Creative``.

One new regression test guards both re-exports against future drift.

Refs adcontextprotocol#485

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: bokelley

src/adcp/decisioning/capabilities.py

@@ -77,6 +77,7 @@ class HelloSeller(DecisioningPlatform):
     RequestSigning,
     SiCapabilities,
     Signals,
+    SignalsFeatures,
     Specialism,
     SponsoredIntelligence,
     SupportedProtocol,
@@ -90,6 +91,9 @@ class HelloSeller(DecisioningPlatform):
 from adcp.types.capabilities import (
     CapabilitiesAccount as Account,
 )
+from adcp.types.capabilities import (
+    CapabilitiesContentStandards as ContentStandards,
+)
 from adcp.types.capabilities import (
     CapabilitiesCreative as Creative,
 )
@@ -110,6 +114,7 @@ class HelloSeller(DecisioningPlatform):
     "ComplianceTesting",
     "Components",
     "CompromiseNotification",
+    "ContentStandards",
     "ConversionTracking",
     "Creative",
     "CreativeSpecs",
@@ -134,6 +139,7 @@ class HelloSeller(DecisioningPlatform):
     "RequestSigning",
     "SiCapabilities",
     "Signals",
+    "SignalsFeatures",
     "Specialism",
     "SponsoredIntelligence",
     "SupportedProtocol",

src/adcp/types/capabilities.py

@@ -97,10 +97,27 @@
 from adcp.types.generated_poc.bundled.protocol.get_adcp_capabilities_response import (
     Capabilities as SiCapabilities,
 )
+
+# ``ContentStandards`` collides with ``adcp.types.ContentStandards`` (the
+# unrelated wire model on the content-standards protocol). Same
+# disambiguation pattern as ``Account`` / ``MediaBuy`` / ``Creative`` —
+# imported here under a ``Capabilities*`` alias and re-aliased back to
+# the wire-spec name within :mod:`adcp.decisioning.capabilities`.
+from adcp.types.generated_poc.bundled.protocol.get_adcp_capabilities_response import (
+    ContentStandards as CapabilitiesContentStandards,
+)
 from adcp.types.generated_poc.bundled.protocol.get_adcp_capabilities_response import (
     Creative as CapabilitiesCreative,
 )
 
+# ``Features2`` is the codegen name for the ``Signals.features`` type
+# (numbered because ``Features`` already names the media_buy features
+# block at line 142 of the generated module). Surface under a stable
+# adopter-facing name so signals declarations read cleanly.
+from adcp.types.generated_poc.bundled.protocol.get_adcp_capabilities_response import (
+    Features2 as SignalsFeatures,
+)
+
 # ``Idempotency`` ships as a ``oneOf`` on the wire (``IdempotencySupported``
 # vs ``IdempotencyUnsupported``) — the codegen names them ``Idempotency``
 # and ``Idempotency3`` (with the numbered variant covering the
@@ -126,6 +143,7 @@
     "Avatar",
     "Brand",
     "CapabilitiesAccount",
+    "CapabilitiesContentStandards",
     "CapabilitiesCreative",
     "CapabilitiesMediaBuy",
     "Commerce",
@@ -152,8 +170,9 @@
     "NegativeKeywords",
     "Portfolio",
     "RequestSigning",
-    "Signals",
     "SiCapabilities",
+    "Signals",
+    "SignalsFeatures",
     "Specialism",
     "SponsoredIntelligence",
     "SupportedProtocol",

tests/test_decisioning_capabilities_submodule.py

@@ -134,6 +134,37 @@ def test_submodule_all_matches_imports() -> None:
         assert hasattr(caps, name), f"__all__ lists {name!r} but it is not importable"
 
 
+def test_signals_features_and_content_standards_re_exported() -> None:
+    """``SignalsFeatures`` (codegen ``Features2`` for ``Signals.features``)
+    and ``ContentStandards`` (the ``MediaBuy.content_standards`` type, which
+    collides with the unrelated wire ``adcp.types.ContentStandards``) are
+    surfaced through :mod:`adcp.decisioning.capabilities` so adopters
+    declaring deep Signals / MediaBuy blocks don't have to dig into
+    ``generated_poc``.
+    """
+    from adcp.decisioning.capabilities import (
+        ContentStandards,
+        MediaBuy,
+        Signals,
+        SignalsFeatures,
+    )
+    from adcp.types import ContentStandards as WireContentStandards
+
+    # Content-standards collision guard — same pattern as Account / MediaBuy / Creative.
+    assert ContentStandards is not WireContentStandards
+    assert ContentStandards.__name__ == "ContentStandards"
+
+    # SignalsFeatures usable on a Signals declaration.
+    sig = Signals(features=SignalsFeatures(catalog_signals=True))
+    assert sig.features is not None
+    assert sig.features.catalog_signals is True
+
+    # ContentStandards usable on a MediaBuy declaration.
+    mb = MediaBuy(content_standards=ContentStandards(supports_local_evaluation=True))
+    assert mb.content_standards is not None
+    assert mb.content_standards.supports_local_evaluation is True
+
+
 def test_decisioning_capabilities_accepts_structured_fields() -> None:
     """``DecisioningCapabilities`` carries instances of the wire-spec
     capability sub-models. Validates the dataclass widening (commit 2 of