Repository navigation
Enable qualified Cloudflare guest schema and registry serving #89
Description
Acceptance Criteria
- Integrate target-qualified descriptors, funded validation/init/cache lifetimes and explicit publication/dispatch for the complete discovered implemented set; remove native-only publication only through the reviewed common cutover, without bypassing qualification.
- Accept the final Cloudflare artifact's generated handler and updated fit/resource identity with real branch/safety controls, not just a metadata or compiler inspection.
Blocking And Review Gates
- Blocked by: #74.
- Conditionally blocks: #99, #100 when their selected guest/bidder set requires this Cloudflare cutover.
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.
Uniform Catalog Cutover
- Replace Cloudflare's architecture-based publication and native-only schema admission with qualified discovery-driven descriptors/initialization. Retire the manifest/model/codegen/storage/registry flag through the common accepted cutover; reject the retired field instead of accepting a legacy alias.
- Require exact complete-catalog report membership, only verified unimplemented skips, and positive execution of every implemented identity/alias across bounded fixture batches on the actual Worker candidate. All four adapter candidates must pass before the common flag-retirement cutover is accepted; native/WASI checks are not Worker execution.
- Reuse existing runtime/qualification owners, freeze the exact executed-runtime controls in this issue's reviewed package, and preserve privacy, endpoint safety, resource gates and current workload limits. No replacement bidder list or direct-factory bypass.
Activity