Expert and integration roles on claude-haiku-5-5

claude-haiku-4-5 is being replaced by claude-haiku-5-5 in LiteLLM: the
integration tests' roles and the example config's expert move to it.
Its profile keeps the predecessor's benchmark figures, marked as such
until it's measured. The plan's models-by-role line also gains the
local classifier (M3.2). Results measured on 4.5 stay as they were.

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

nisse-dev.example.yaml

@@ -48,7 +48,7 @@ roles:                                # L9: role -> LiteLLM model alias
   # Each work item pins the mapping when it opens.
   driver: claude-opus-5-5       # drives the loop: talks, restates, works
   helper: claude-opus-5-5       # takes over what the driver got stuck on
-  expert: claude-haiku-4-5      # one question at a time, no tools: cheap is enough
+  expert: claude-haiku-5-5      # one question at a time, no tools: cheap is enough
   # Reads go-aheads and judges actions the fast path doesn't know (L4); unset,
   # the expert's. It never sees the transcript, so the driver's model is fine.
   classifier: qwen3.8-27b
@@ -61,10 +61,11 @@ profiles:
     tools: reliable (37/40 on the executor benchmark, PR #55)
     strengths: careful multi-step edits that follow a clear brief
     weaknesses: speed (minutes per hard task) and open-ended design
-  claude-haiku-4-5:
+  claude-haiku-5-5:
     tools: reliable
     strengths: quick, well-scoped changes and short answers
-    weaknesses: long multi-file work (15/20 on the harder benchmark tasks)
+    # Measured on its predecessor, claude-haiku-4-5; not benchmarked yet.
+    weaknesses: long multi-file work (15/20 on the harder benchmark tasks, as 4.5)
   claude-opus-5-5:
     tools: reliable
     strengths: design, debugging, and work other models got stuck on