# Specialist pack verification

Requirement: `REQ-PRODUCT-SPECIALIST-PACKS`; underlying requirements remain `REQ-QC-PROFILING`, `REQ-UK-EXCEPTIONS`, `REQ-PRODUCT-STORAGE-EXCEPTIONS` and `REQ-GOOGLE-MODE` with their existing partial/review boundaries.

The pack suite tests distinct prerequisites, focused questions, missing declarations, technology inventory conflicts, storage condition paths, English-only native storage controls, independent consent/exception enrollment, and Google declarations among unrelated services. Several Google entries prompt ownership review without assuming they run on the same page. Saved reports preserve old pins, mappings, entries and restrictions, leave new facts unknown and regenerate input reviews rather than trusting saved status. Private justifications do not enter the agent brief.

UI/CLI draft and resume tests compare the same regenerated reviews and connection tasks while forbidding setup network/storage effects. Shared connection tests exercise every pack. The target assessment checks at least one populated Google declaration, while normal configuration validation still checks the exact signal shape, ownership, product mappings and enrollment. Site tests check all twenty packs and direct example/guide links.

Existing technology, storage-exception and Google adapter suites test the component behavior: exact release/scope binding and supplemental retention limits; atomic journal/presentation gates, objections and revision-bound resume; defaults, loaders, independent restrictions, receipts, pending cancellation and terminal reload. Passing setup tests does not replace those integrations or establish actual profile eligibility, presentation, vendor behavior, downstream handling or legal approval.