Freeze per-target SDK fact prerequisites and external ownership #50

Acceptance Criteria

• Recheck current SDK contracts and assign each missing ingress-accounting, ceiling, population or codec fact to the exact target and external owner, with its next verification action.
• Close this coordination task when the acceptance/ownership ledger is complete, not when all providers publish their facts. Actual fact fulfillment stays in each target's qualification issue; preserve unknowns and distinguish local demand overflow from external absence.

Blocking And Review Gates

• Blocked by: #33.

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

Retired Ledger Reconciliation

• Explicitly map SDK prepared contexts, scope/task registrations, queues/ledgers, boxed receipts, cleanup scratch and Fastly registration recorder/configuration-set storage to funded Auctioneer owners and simultaneous populations. Published payload subtotals or selecting a provider constant are not a complete allocator/host correspondence proof.
• Record actual host-ingress/framing scope for every affected adapter, the native configured ceiling/population, Cloudflare inbound population and hosted Spin provenance. Application response-header count/byte checks exclude provider-added fields; record actual target wire scope rather than claiming a whole-wire cap.
• Preserve ownership distinctions: Fastly application stack proof belongs to Certify Fastly memory and separate-stack fit #73; missing published SDK/host contracts require their external implementer. Unknown platform ceilings do not hide a configured-ceiling demand failure.

The 2026-11-02 SDK adoption explicitly retained opaque-host bookkeeping correspondence as open. Current source acquisition is not a demonstrated outage; retained-source release work remains #29.

Source: retired resource ledger and SDK adoption record.

Resource Proof Responsibilities

Responsible coordination role: Auctioneer SDK/resource-reconciliation maintainer.

The target-specific owner/action records are #72 (Axum), #73 (Fastly), #74 (Cloudflare) and #75 (Akamai Functions hosted Spin). SDK maintainers own missing prepared-context, scope/task, queue/channel, boxed-receipt, cleanup and Fastly recorder/backend-cache contract details; the applicable Auctioneer target maintainers verify those details against funded owners and simultaneous populations. #49 continues codec-certificate coordination.

Next coordination verification: confirm these existing issue records and native dependencies cover every missing fact. Actual fact fulfillment and target fit remain those issues' acceptance, not this coordination task's completion. Missing external facts and local configured-ceiling overflow remain independently nonpassing.

Source: approved shared resource ownership contract, delivered for review in #162. This records responsibility and the next verification action, not completed proof, target qualification, changed workload limits or permission to close this issue.

Persistent Native Transport Correspondence

The default Axum service retains one shared outbound client across requests. Its pinned SDK transport does not override locked reqwest 0.13.4 pooling defaults (90-second idle timeout, usize::MAX idle connections per host). Idle connection, connector and pool-maintenance storage can therefore outlive individual completed calls; active-call or active-stream counts alone are not a retained-pool certificate. This records an omitted owner, not a demonstrated undercharge or an authorization to change pooling settings.

The owner/action record is #72: Axum SDK maintainers document the shared client, pool and surviving background/host storage; the deployment operator identifies any supplied-client or pooling deviations; Auctioneer native qualification maintainers establish the population/lifetime and funded-term correspondence. Conservative accounting and all target-readiness blockers remain unchanged.

Source: pinned SDK service owner and transport builder; included in #162's current proof index. The service source is byte-identical to the earlier 598f0a2a baseline. The outbound delta changes timer anchoring, not client construction or pool settings; the retained-pool observations above are unchanged at a7d7fd0.

Current SDK Readiness-Signal Coordination

PR #162 uses EdgeZero a7d7fd0f2face027e3810ed67e80f6341fcf68b6. The updated Fastly scheduler and progress owner add Arc-backed wake-request flags and SourceWake wrappers retaining parent wakers. Repeated observations, retained registrations and handles surviving callback/driver boundaries can overlap. Existing payload bounds and retained outbound cancellation ownership are not physical storage certificates for those owners.

Responsible coordination role: Auctioneer SDK/resource-reconciliation maintainer. Fastly SDK maintainers supply flag, source-waker wrapper, cloned-parent and overlapping-registration layout/population/lifetime contracts; Auctioneer Fastly qualification maintainers perform the funded-term correspondence in #73.

Next coordination action: require #73's verification to enumerate both scheduler and progress flags and the simultaneously live wrappers/registrations across observation, replacement, completion, cancellation and teardown. Reconcile those owners with the existing scope, task/queue and handoff records without double counting shared backing, omitting retained handles, changing workload limits or shrinking an unproved reserve.

The target fact records in #72, #73 and #75 are rebound to this pin. The platform constants and Axum shared-client/pooling facts stated there are unchanged from 598f0a2a; changed runtime timer/readiness code is not described as byte-identical. Source/ABI/allocator and host-copy certificates remain outstanding in their existing issues. This records ownership and the next action, not fulfillment or issue closure.