Repository navigation
Enable qualified Fastly guest schema and registry serving #88
Description
Acceptance Criteria
- Review and install the qualified shipped-closure descriptors, precharged initialization/cache ownership and schema admission into the actual guest path; replace target-dependent publication through the reviewed discovery-driven common cutover described below.
- Repeat fit/accounting and real generated-handler acceptance on the final artifact/source/features, including activation, invalid parameters, privacy, errors and cancellation. Keep unqualified definitions blocked; certificates alone do not enable routing.
Blocking And Review Gates
- Blocked by: #73.
- Blocks selected Fastly host acceptance: #76.
- Conditionally blocks: #99, #100 when their selected guest/bidder set requires this Fastly 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 Fastly'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 candidate artifact. All four adapter candidates must pass before the common flag-retirement cutover is accepted; staged/unqualified artifacts do not satisfy serving acceptance.
- Reuse the existing Fastly runtime/qualification owners and preserve independent privacy, endpoint, resource and workload gates. No direct-factory bypass, replacement bidder list or reduced subset may satisfy this issue.
The selected host in #76 is Fastly, so this is its required guest-serving dependency. Cloudflare/Spin host integration is not added to #76; the wider common catalog release gate remains explicit and separate.
Activity