Python SDK: wholesale feed mirror helper for products/signals

[bokelley]

Context

This is the Python follow-up for the current 3.1 wholesale-feed model, replacing the stale CatalogSync shape tracked in adcp#4789. The protocol no longer has separate /catalog/events or /catalog/subscriptions endpoints.

Current surface:

• bootstrap via get_products with buying_mode: "wholesale" and get_signals with discovery_mode: "wholesale"
• persist wholesale_feed_version and cache_scope per connected agent/account
• refresh with if_wholesale_feed_version; unchanged feeds return unchanged: true
• register receivers through account-level sync_accounts.accounts[].notification_configs[]
• process product.*, signal.*, and wholesale_feed.bulk_change notifications

Request

After the TypeScript API shape stabilizes in adcp-client#2094, port an idiomatic Python helper for maintaining a local mirror of wholesale product/signal feeds.

Suggested scope:

• Async bootstrap and refresh API for product and signal wholesale feeds.
• In-memory indexes keyed by agent URL/account plus product or signal id.
• Version/cache-scope tracking with conditional refresh support.
• Optional persistence hooks for stored versions/index state.
• Event/callback hooks for wholesale-feed webhook notifications.
• Re-bootstrap the affected feed on wholesale_feed.bulk_change, using affected_entity_type to choose product vs signal.
• Helper for registering notification_configs[] through sync_accounts.
• Docs or example showing receiver plus mirror usage.

Tests

• Unit coverage for conditional refresh, unchanged responses, re-bootstrap on bulk change, and product/signal notification routing.
• Integration coverage against the training-agent storyboards from adcp#5056 where practical.

Related

• adcp#4789 — stale umbrella issue, superseded by repo-specific SDK trackers
• adcp-client#2094 — TypeScript source-of-truth tracker
• Promote 6.1.0 beta catalog webhook support to a stable release #840 — stable release tracker for existing 3.1 catalog/wholesale webhook support

[bokelley]

Triage

Classification: Feature request
Bucket(s): client, handlers (neither label confirmed in repo — gap flagged in run summary)
Status: deferred
Milestone: omitted

What the experts said:

• Pre-classification exit: issue body explicitly gates work on adcp-client#2094 stabilizing; child-of-open-parent path taken, expert panel skipped per routing rule.

My take: Starting the Python port now risks significant rework if the TypeScript API shape in adcp-client#2094 shifts before it stabilizes. The scope (async bootstrap/refresh cycle, in-memory indexes keyed by agent URL/account+id, version/cache-scope tracking, persistence hooks, notification routing, bulk_change re-bootstrap) is well-specified and will be ready for a Ready-to-implement brief as soon as the TS shape is locked — re-triage then or remove claude-triaged to trigger a new pass.

Blocked-on: adcp-client#2094 — resurfaces on merge

---

Triaged by Claude Code. Session: https://claude.ai/code/cse_01Ngp6MHS1twaRv97qeiZd1J

---

Generated by Claude Code