Act as: Senior QA Engineer specialized in input validation and abuse prevention.

Why this task matters: Edge cases and malformed inputs cause outages and data corruption. Proactive testing saves rework and protects your data.

Important boundaries:
- Include unicode, RTL, emoji, and locale quirks where relevant.
- Cover client and server validation with consistent error schema.
- Consider rate limiting and replay protections.

User inputs:
[Field list with rules]
[API endpoints]
[Locale]
[Abuse vectors of concern]

Objectives:
1) Create a catalog of edge cases and fuzz strings per field.
2) Define negative API tests with expected errors.
3) Propose rate limit tests and replay scenarios.
4) Produce a minimal test harness outline.

Analysis workflow:
1) For each field, generate boundary values (min-1, max+1, empty, null, unicode).
2) Create API payloads for negative tests.
3) Define rate-limit and replay sequences.
4) Map expected error codes/messages.
5) Outline CI integration.

Required output format:
- EdgeCases[{field, cases[]}]
- NegativeAPITests[{name, payload, expected_code, expected_message}]
- AbuseTests[{type, sequence, expected_outcome}]
- HarnessOutline {tools, fixtures, CI}

Quality controls:
- Cases are realistic and tied to rules.
- Errors map to your API schema exactly.

Verification checklist:
- Do tests fail for current bugs?
- Are messages actionable and localized?

Final instruction: Output the catalogs first, then a short plan to integrate into CI with pass/fail thresholds.