test(agents): score the mapper leak as a correctness lens

The full-skill run was losing the gate to an uninstructed baseline.
Evaluate firstSpanWritten the same way as the JS correctness cases.

Author: robertomonteromiguel

.llm-validation/suites/dd-apm-sdk-review.yaml

@@ -326,14 +326,12 @@ cases:
 
   - id: java-correctness-mapper-state-leak
     files:
-      - .agents/skills/dd-apm-sdk-review/SKILL.md
       - .agents/skills/dd-apm-sdk-review/reviewers/_common.md
       - .agents/skills/dd-apm-sdk-review/reviewers/correctness.md
-      - .agents/skills/dd-apm-sdk-review/reviewers/report-template.md
     input: |
-      Run dd-apm-sdk-review on the following change. There is no git repository to
-      inspect — this diff is the entire change set; do not attempt any git commands, go
-      straight to running the reviewers on the pasted content below.
+      Apply this repo's correctness-review criteria (reviewers/correctness.md and _common.md)
+      to the following change. No git checkout available — this snippet is the entire
+      change to review.
 
       ```diff
       diff --git a/dd-trace-core/src/main/java/datadog/trace/common/writer/ddagent/TraceMapperV0_4.java b/dd-trace-core/src/main/java/datadog/trace/common/writer/ddagent/TraceMapperV0_4.java
@@ -363,7 +361,6 @@ cases:
       - "Flags that `firstSpanWritten` is an instance field that is only ever set to `true` and is never cleared between payloads."
       - "Explains the concrete consequence given mapper reuse across the writer's lifetime: after the first payload, later payloads never write process/propagation tags (`dd-p-*`) — silent cross-payload data loss."
       - "Recommends clearing `firstSpanWritten` in `reset()` (the payload-flush hook), not at the start of every `map()` — a per-map reset would write the tags on every chunk of the same payload."
-      - "States an explicit verdict line and the matching gate line: `DO NOT PUSH` on BLOCK, `WAITING ON HUMAN` on APPROVE_WITH_COMMENTS, or `READY TO PUSH` on APPROVE."
     bad_signals:
       - "Notes the flag exists but misses that nothing re-initializes it per payload."
       - "Suggests resetting the field at the start of every `map()` (or only \"make it volatile\" / \"add logging\")."