analyze: bump max_tokens 2000 → 4000 for portfolio analysis

Logs (analyze.lang_resolved → portfolio_analysis.reviewer_rejected
chain on 2026-05-29) showed the lang directive was working — the
model was producing Italian — but the reviewer was rejecting every
response as truncated mid-word ("supera i mass", "INRG +8"). The
analyze endpoint then returns 502 and the frontend keeps showing
whatever stale English row was last cached in localStorage, so from
the user's POV the analysis "is still in English".

Same shape as the strategic-log translation cap we fixed earlier:
the prompt targets ~350 English words, IT runs ~25-35% longer in
tokens, and DeepSeek-V4-flash bills internal reasoning against the
same budget. At 2000 we ran out of room mid-sentence. 4000 is well
above the longest realistic Italian output; cost is bounded by
tokens actually emitted, not the cap.

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

app/services/portfolio_analysis.py

@@ -344,7 +344,17 @@ async def analyse(
                     {"role": "system", "content": system},
                     {"role": "user", "content": user},
                 ],
-                max_tokens=2000,
+                # 4000 not 2000. Italian / Spanish / French / German
+                # output runs ~25-35% longer in tokens than English; on
+                # top of that DeepSeek-V4-flash bills its internal
+                # reasoning against the same budget. At 2000 we
+                # repeatedly hit finish_reason=length mid-sentence,
+                # which the reviewer agent then correctly flags as
+                # truncated and rejects — the user ends up looking at
+                # whatever stale row was last cached. 4000 leaves
+                # ample headroom; we only pay for tokens actually
+                # emitted, not the cap itself.
+                max_tokens=4000,
             )
             status = "ok"
             error_msg = None