Certify Cloudflare total-memory and ingress fit #74

Acceptance Criteria

• Reconcile guest and provider/JS-owned ingress/storage with the actual memory scope and enforced inbound population, not the outbound connection allowance.
• Prove same-source fit/headroom and target observations; retain explicit pending/unsupported results where the required host facts or meter cannot be established.

Blocking And Review Gates

• Blocked by: #46, #47, #48, #50.
• External blockers: Applicable Cloudflare SDK/decoder, provider/JS memory-scope and inbound-population facts, as enumerated by #50.

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.

Approved Integration Contract

PR #152 merged the specification and delivery plan at 9b83deaa680ad8e867169db3b4ebb195b8a1b33c. Their shared requirements apply: whole-catalog reports with verified skipped: not_implemented rows, positive qualification of every implemented identity/alias on all four adapters, existing build discovery and the qualified common native_only retirement. The first Trusted Server host remains Fastly display; Trusted Server #1505 coordinates host-owned work. The planning merge is not implementation or qualification evidence and changes no workload limit, resource ceiling or configuration mechanism.

Discovered Catalog Acceptance

• Bind actual Cloudflare Worker execution, SDK/features/configuration, ingress population and provider/JS memory facts to every discovered implemented identity/alias. Native or WASI publication checks do not establish Worker execution.
• Reconcile complete-catalog reports with explicit unimplemented skips and exact positive implemented serving coverage across bounded batches, including privacy, invalid input, original deadlines, cancellation and overload boundaries. Keep missing execution/provider facts nonpassing.

Source Contracts

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

Resource Proof Responsibilities

Responsible roles: Cloudflare SDK/provider maintainers supply enforced inbound-population and provider/JS/guest memory-scope facts; Auctioneer Cloudflare qualification maintainers own actual Worker artifact and application correspondence verification.

Next verification action: reconcile request ingress/framing, JS/host allocations, SDK tasks/queues/scopes and response handoff against the published 128,000,000-byte instance-scoped allowance and actual enforced inbound population. Preserve unknowns; neither the outbound connection allowance nor the application's charged six slots proves inbound enforcement. Native or WASI execution cannot certify this Worker.

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.