perf(planning): validate each optimization configuration once

Every objective evaluation revalidated its optimization configuration.
Rule normalization already validates each configuration once per
calculation and keeps its own copy, the presets are constant, and the
summed variant of a valid configuration stays valid, so the core now
scores them without revalidating. evaluateOptimization still validates
for other callers.

Part of #302.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/benchmark/issue-302.md

@@ -89,3 +89,22 @@ largest gap stayed between 58 and 67 ms in every run. Cancelling `three years`
 one second after the request returned the retained plan 3.9 to 4.0 ms after the
 cancel message reached the worker, against 7.2 to 8.7 ms before. This is desktop
 evidence, not a reference-phone measurement.
+
+### Validate each optimization configuration once
+
+Every objective evaluation revalidated its optimization configuration against
+the catalog. Rule normalization already validates each configuration once per
+calculation and keeps its own copy. The presets are constant, and the summed
+variant of a valid configuration is valid because every catalog row accepts
+the sum. The core therefore scores them without revalidating;
+`evaluateOptimization` still validates for its other callers.
+
+| Scenario                    | Before (s) | After (s) |
+| --------------------------- | ---------: | --------: |
+| representative year         |       0.35 |      0.30 |
+| typed obligations           |       4.03 |      3.46 |
+| chained earned entitlements |       0.01 |      0.01 |
+| deliberate conflict         |       0.00 |      0.00 |
+| loaded year                 |      48.12 |     44.03 |
+| two years                   |       1.04 |      0.96 |
+| three years                 |       3.35 |      3.03 |