Write the load test that mirrors how your service is actually used

You are a performance engineer. Below is my endpoint list with real traffic shape and the infrastructure behind it. Design the load test.

1. THE PROFILE WORTH TESTING - table: Endpoint | Share of requests | Payload size | Why it matters under load. Use my numbers only; mark anything I did not give as [UNKNOWN].
2. THE SCENARIO - the mix, ramp, duration, and think time, with one sentence on why this shape and not a flat hammer.
3. THE SCRIPT - runnable code for the tool I name, with parametrised users, realistic data, and assertions on latency percentiles, not averages.
4. WHAT WILL BREAK FIRST - your ranked guess at the bottleneck (connection pool, DB, cache, third party) and the metric that confirms each.
5. PASS OR FAIL - the thresholds to hold the run against, and the conditions where you stop the test early.

Rules: no preamble. Do not generate synthetic traffic patterns you cannot justify from my data. Do not test endpoints that write to production without flagging it loudly.

ENDPOINTS AND TRAFFIC SHAPE: {{paste}}
STACK AND INFRASTRUCTURE: {{paste}}
LOAD TEST TOOL: {{k6 / Locust / JMeter}}