fix(rectification): bump scoring identity to scoring-10 for functional profile v2; dated contract by generation (BUG-1181)

Functional roles feed the *_functional_*_auxiliary rules, so 57782aea changes
candidate scores for identical input (memoization fixture 12:00: 8.6274 ->
8.4977). Per the "scoring semantics change => bump ALGORITHM_VERSION"
precedent (scoring-7 -> 8 -> 9), the identity moves to scoring-10; policy v3,
input contract v5 and Skill versions are unchanged, history is not relabeled.

Five frontend sites and one SQL guard tested `=== "...scoring-9"` for the
dated candidate-window contract; they now use isDatedScoringAlgorithmVersion /
a generation regex (>= 9). Migration 20261002010000 only recreates
validate_dated_rectification_candidate (one-line guard change).

Memoization golden v2 written by the test's own write_golden; v1 (scoring-8)
frozen by sha256. Real-engine scoring-10 cross-midnight golden added. Research
records re-frozen per ERR-110 (label functional_v2_2026_10_02) and
scripts/functional_benefics.py added to the frozen production identity
(ERR-114: 57782aea changed scores without tripping it).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N4f2nya58RoRu4yEmJgRGE

tests/test_rectification_relative_support.py

@@ -20,7 +20,8 @@ class RelativeSupportScaleTest(unittest.TestCase):
     def test_holdout_gate_keeps_proportional_default(self) -> None:
         self.assertEqual(POLICY_VERSION, "rectification-candidate-policy-v3")
         # Explicit date windows: scoring identity -8 -> -9, not a prior/policy change.
-        self.assertEqual(ALGORITHM_VERSION, "rectification-v5-matrix-scoring-9")
+        # 原值: -9；新值: -10；原因: 功能吉凶 v2 改变打分（BUG-1181），策略 v3 与相对支持口径不变。
+        self.assertEqual(ALGORITHM_VERSION, "rectification-v5-matrix-scoring-10")
         self.assertEqual(RELATIVE_SUPPORT_MODE, "proportional")
 
     def test_offset_top_two_lead_is_at_least_proportional(self) -> None: