Investigate intermittent React render-update warnings in advisor chats

Start with a normal advisor-enabled chat using held reasoning/advice output, followed by a turn with two advisor calls. Capture resolved console.error arguments and the React component stack, then compare a reproducible feature case with the main baseline. Done means the responsible update is established and a failing regression is added before any source fix.

Remote UAT of advisor streaming at a39bbe4c217fd731ffb4721fe6fd5873a1d5ca66 logged this React development warning once in a held reasoning/advice scenario and once in a two-advisor-call scenario (2 of 9 scenarios):

Cannot update a component (`%s`) while rendering a different component (`%s`).
To locate the bad setState() call inside `%s`, follow the stack trace as described
in https://react.dev/link/setstate-in-render Unknown Unknown Unknown

The component stack was empty. The same warning appeared on 27fa15fab5 before the card-association fix. It did not reproduce in two runs with an instrumented console.error hook. There is no main-baseline reproduction, so its origin relative to the reasoning feature is unknown. The tested card, retry, error, completion, refresh, and persistence behavior passed; this issue records an investigation, not a confirmed cause or a claim that the warning is harmless.

1. Run a normal advisor-enabled chat with held reasoning/advice output, then a turn with two advisor calls.
2. Capture resolved console.error arguments and the React component stack at the warning.
3. Use a reproducible case to compare the feature and baseline, then add a failing regression before any source fix.

Follow-up trigger: the next reproducible occurrence in advisor or chat-streaming UAT. Capture the component stack and establish the responsible update before proposing a fix.

Generated with xum • Model: coder:openai/gpt-6-astra • Thinking: xhigh