Skip to content

epic: Python SDK parity with JS @adcp/sdk@6.7 framework primitives #452

Closed

Description

@bokelley

Context

Building the v3 reference seller (PR #447) confirmed adopters hand-roll patterns that JS now ships as helpers. The JS 6.7 migration guide at docs/migration-6.6-to-6.7.md (in adcp-client-js) documents 15 recipes.

Goal

Ship the high-leverage 11 helpers as Python SDK primitives so adopters (Prebid salesagent, GAM-shaped publishers, etc.) get the same DX as JS.

Sequence

Batch 1 (parallel, no deps)

Batch 2 (depends on #456)

Batch 3 (DX polish)

Validation point

Refactor v3 reference seller to USE the new helpers (concrete demo).

Reference

JS changesets in adcp-client-js/.changeset/ (6.7 release).

Activity

  1. added
    enhancementNew feature or request
    claude-triagingTriage routine is actively working on this issue (1-3 min)
    on May 3, 2026
  2. bokelley commented on May 3, 2026

    @bokelley
    ContributorAuthor

    Triage

    Classification: Feature request (epic — multi-batch, cross-cutting)
    Bucket(s): handlers, client, validation (labels not present in repo — gap noted below)
    Status: ready-for-human
    Milestone: (omitted — no target version specified)

    Assessment: Epic is well-structured. Batch 1 (4 parallel items) feeds Batch 2's dependency on AccountStore.upsert/list/sync_governance(ctx) from item #4; Batch 3 is independent DX polish. PR #447 (v3 reference seller motivating this) merged this morning. The Batch 1 item #4 (Account v3 wire fields + AccountStore) is the critical-path gate — Batch 2 cannot start until it lands.

    My take: Keeping this as a tracking epic is correct. When child issues are filed, triage will process each one individually — Batch 1 items are non-breaking additions and Execute-eligible; Batch 2/3 items will be evaluated as each child lands. No auto-PR from this issue.

    Label gap: handlers, client, and validation bucket labels do not exist in this repo. Adding them would enable label-based filtering across epic children.


    Triaged by Claude Code. Session: https://claude.ai/code/${CLAUDE_CODE_REMOTE_SESSION_ID}


    Generated by Claude Code

  3. added and removed
    claude-triagingTriage routine is actively working on this issue (1-3 min)
    on May 3, 2026
  4. bokelley commented on May 14, 2026

    @bokelley
    ContributorAuthor

    Status check — 9 of 11 children shipped

    Bringing the checkboxes up-to-date based on a cross-check against merged PRs:

    Batch 1 (parallel, no deps)

    Batch 2 (depends on #456) — complete

    Batch 3 (DX polish)

    Remaining work: #453 and #462 — both need design decisions before they can draft. Leaving this epic open until both close.

    Validation: v3 reference seller has been refactored to use most of these helpers in subsequent PRs.

  5. bokelley commented on May 23, 2026

    @bokelley
    ContributorAuthor

    Closing the tracking epic: the two remaining children called out in the last status update (#453 and #462) are now closed as completed. Any new parity gaps should be filed as focused follow-up issues rather than keeping this stale epic open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions