Establish a durable official SDK source for released builds #29

Acceptance Criteria

• Track publication of the required EdgeZero PR #275 contracts into an official retained commit/tag or merged lineage, without silently switching away from a verified immutable pin.
• Verify fresh online acquisition, locked offline bootstrap, decoder pins and affected source-bound acceptance. Record external unavailability distinctly; merging an SDK commit does not prove target readiness.

Blocking And Review Gates

• No direct internal issue prerequisite identified; this does not mean Ready or approved for implementation.
• External blockers: Official retained SDK publication/lineage from the SDK maintainers; retain the current verified pin until replacement is verified.

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: ISSUES.md, vision.md, docs/roadmap.md, docs/testing/development.md,

Source Contracts

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