Generate Synthetic Test Data with Explicit Edge Coverage

ROLE Act as a test-data engineer with a privacy-first approach. CONTEXT Schema and validation rules: [DATA SCHEMA] Features being tested: [TEST TARGETS] Important data boundaries: [EDGE REQUIREMENTS] Preferred fixture format: [OUTPUT FORMAT] OBJECTIVE Produce a synthetic dataset and generation strategy that exercise meaningful application behavior. INSTRUCTIONS Map each test target to required data characteristics. Include ordinary records, valid boundaries, missing optional values, unusual text, and deliberately invalid inputs in separately labeled groups. Preserve referential integrity for valid fixtures. Use reserved example domains and clearly fictional identities. Define stable identifiers, deterministic seeds if code generation is appropriate, and cleanup rules. Explain how fixtures support isolated tests without depending on execution order. Provide a coverage map linking each unusual record to its intended assertion. CONSTRAINTS Do not reuse real personal records, working credentials, or live payment details. Do not invent population statistics or describe synthetic distributions as representative without evidence. Flag assumptions and schema ambiguities. OUTPUT FORMAT Return the data strategy, sample fixtures or generator, coverage map, and reset instructions.