Repository navigation
Close the remaining Cloudflare deployed-handler acceptance rows #101
Description
Acceptance Criteria
- Execute any outstanding Cloudflare handler/config-corruption/recovery cases on the real generated App and preserve Unknown body omission where required.
- Reuse matching current #100 evidence where it already satisfies a row; do not rerun solely to satisfy two issue names or infer a pass for unobserved behavior.
Consolidated Operator-Configuration Acceptance
Superseded #132 did not identify missing configuration plumbing. The pinned EdgeZero adapter already binds the declared stores to the generated App, and Auctioneer reads one typed runtime policy. Only the remaining Cloudflare acceptance belongs here:
- Use one unchanged released code artifact/component with two isolated operator configurations and secret references; observe independently differing effective policy, bidder/alias and privacy behavior without rebuild/relink or cross-operator cached state. Binding metadata may differ, but executable code bytes must match.
- Exercise missing/corrupt/invalid config, bounded safe health/liveness, captured extraction/admission caps, update or restart semantics and recovery through the applicable real entrypoint and existing local guest/handler controls. Perform temporary corruption/restoration only in authorized isolated bindings.
- Record actual artifact/config/runtime/SDK identities and executed observations separately from compilation, packaging and native checks. Keep per-request App construction distinct from isolate-global admission ownership and preserve Unknown-body omission. Use the packaged Worker artifact and its actual bindings; a native fixture cannot establish Worker execution.
- Reuse matching existing Execute selected-path handler and config failure/recovery acceptance #100 evidence instead of repeating the same case for two issue names. Resource/stack/ingress facts and fit remain Certify Cloudflare total-memory and ingress fit #74, serving eligibility remains Enable qualified Cloudflare guest schema and registry serving #89, and selected actual-deployment measurements remain Qualify the selected actual deployment under Q2-D #99. This issue does not promote native-only bidders or claim provider fit.
These transferred criteria are still unexecuted unless supported by matching existing evidence; closing #132 is not a hosted pass. No new config source, loader or startup configuration is required.
Blocking And Review Gates
- Blocked by: #52, #89.
- External blockers: Authorized Cloudflare deployment, isolated bindings and restoration inputs.
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: roadmap sections 6 and 8 and the existing M6 contracts/runbooks.
Activity