Scope guard verification

Requirements: REQ-PRODUCT-SCOPE-GUARDS, with partial links to REQ-US-COPPA-SCOPE, REQ-US-VA-RIGHTS, REQ-CA-OBA, REQ-CH-PROFILING and REQ-AU-PIXELS.

The automated tests cover every present/unknown fact, inherited restrictions, safe siblings and combined services, blocked granular grants, mixed available-choice delivery, no fabricated refusal when everything is blocked, stored grants and material assessment revisions, continued rejection/withdrawal, independent CF archive verification, historical receipts, malformed/hidden overrides, private-note isolation, default disabled controls, ordinary terms/collection rendering, and setup conflicts and private-report migration.

The mechanism does not determine legal applicability, verify parenthood, collect sensitive information, adjudicate appeals, cover every sector, stop unregistered/server processing, or establish a legally supported jurisdiction pack. Those boundaries are explicit in the guide and catalog.

Results

Verified on 2026-10-18:

• npm run check: 261 package tests and 36 website tests pass; all workspace builds, 65 requirement scenarios and the local Worker dry run pass.
• The 14 dedicated scope tests include mixed delivery, archived-policy rejection, Italian withholding-floor interaction, all-false granular evidence wording and bounded Unicode revision generation. React snapshot and consumer TypeScript tests cover the public integration.
• The local Workers HTTP check passes against persisted SQLite Durable Objects, including protected history, consent, processing choices, lifecycle review and the new light/dark laboratory and runtime modules.
• Chrome manual checks confirm one available service starts while the specialized and combined samples stay off; guarded preferences are disabled; a child-data context disables all grants; changing to ordinary scope requires fresh permission; withdrawal stops services and a revised assessment preserves refusal.
• Desktop light and midnight themes were visually inspected. Mobile layouts were checked at 390px and 320px, with no horizontal overflow; visible notice controls meet the 44px target. Preferences open deliberately into the bottom drawer.

Browser checks are manual evidence for these scenarios, not a comprehensive device, assistive-technology or jurisdiction review. Specialized legal workflows remain unimplemented and the broader scope-guards feature remains partial.

Desktop capture · Midnight capture · Mobile notice · Mobile preferences