Consume a complete SDK decoder allocation contract #49

Acceptance Criteria

• Obtain a source/ABI/scope-bound contract covering decoder buffers, wrappers and allocator terms while preserving supported coding, framing, errors, cancellation and window limits.
• Coordinate common integration and record separate backend/target certificate rows. Each target owns its applicable missing row in #72 through #75; this aggregate item is not an all-provider prerequisite for a selected pilot. Never lower a fixed allowance from a payload-only measurement or replace the codec to bypass the gate.

Blocking And Review Gates

• Blocked by: #33.
• External blockers: SDK compression maintainers' source/ABI/scope-bound decoder allocation contracts; fulfillment is tracked separately per affected target.

Use native blocked-by/blocking links for unconditional issue relationships. Conditional target gates are not universal blockers; link only the selected applicable path after its contract is frozen.

Shared Acceptance Requirements

Every implementation issue ships its own unit/conformance, failure, resource and privacy tests. A later integration issue does not postpone those checks. New untrusted decoders include generated hostile-input controls; changed hot paths include repeatable measurements. Use the existing engine, host services, validated config/push path and EdgeZero handler registration. Preserve privacy, authorization, cookie integrity, HTTPS/SSRF protections, deadlines, exact sent coverage, authoritative bidder/alias attribution and bounded work/storage. Standalone and embedded behavior share policy rather than fork implementations.

No issue may claim a missing capability from metadata import, compilation, observed allocations, a signed cookie, or a different artifact's old evidence. New public/configuration behavior requires its reviewed design before execution. No workload reduction, raised ceiling or replacement budget equation is implied. Bodies and evidence must not publish credentials, identifiers, raw consent, private provider addresses or customer configuration.

Technical Ownership

Sources: M7-R0 design/plan, ISSUES.md resource rows and schema qualification record.

Source Contracts

• Approved roadmap
• Product vision
• Issue ledger and qualification limitations
• Schema qualification record

Resource Proof Responsibilities

Responsible coordination role: Auctioneer codec/resource-integration maintainer. EdgeZero compression maintainers own the missing decoder/wrapper/allocator contracts; each affected Auctioneer adapter maintainer verifies its source/ABI/scope correspondence under #72-#75.

Next verification action: enumerate the pinned SDK's supported decoding/framing paths and their overlapping buffers, wrappers, cleanup and cancellation lifetimes. Obtain the applicable source/ABI/scope-bound decoder allocation contract, map its byte/population/lifetime terms to existing funded owners, and execute the selected adapter's codec/error/cancellation controls against the actual artifact. Record independently which backend/target rows are fulfilled or still externally blocked; a payload-only allocation measurement is not a complete certificate.

The missing SDK allocation contracts remain external prerequisites. Coordinate the separate target rows in #72-#75 without making every provider a prerequisite for one selected pilot, changing the codec, reducing workload or lowering conservative allowances.

Source: the approved shared resource ownership contract, reconciled in #162. This records ownership and a next verification action, not delivered proof or permission to close this issue.