Complete Resource Qualification And Target Fit #9

Outcome

Close only with complete applicable proof and same-source boot/strict fit for all promised targets. Already implemented ownership/accounting improvements remain completed components, not work to reimplement. Sources: M7-R0 design/plan, ISSUES.md resource rows and schema qualification record. Each target advances on its own applicable facts, not completion of unrelated provider rows. Use the shared additive total and at least ceil(effective_ceiling/16) headroom; native retains its absolute 256-MiB floor.

Close only when the accepted child outcomes are complete. Native sub-issue relationships below own the implementation scope.

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.

Source Contracts

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

Resource Proof Responsibilities

Responsible technical role for the existing GVL obligation: privacy/target qualification maintainers.

Next verification action: verify distinct parsed vendor-list backing and simultaneous retained-version populations, including requests holding versions after cache eviction and release of the last shared owner. Preserve the implemented shared-backing and version-retention accounting; Arc-handle counts alone do not establish the byte bound. This supplements, rather than replaces, the epic's child acceptance criteria.

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.