fix(app): prevent composer history update loops

[Flame119052]

Summary

• deduplicate composer history resets before React state dispatch
• mark history sessions active before recall updates and inactive before reset updates

Problem

Opening a bb thread could fail with React error #185 (Maximum update depth exceeded). The production stack pointed to PromptBoxInternal's history reset effect and resetHistorySession.

Root cause

Callers may recreate an empty history object while React is processing overlapping transition and synchronous updates. Each effect pass unconditionally dispatched three null state updates. With another update lane already pending, React could not always take its eager same-value bailout, so the redundant passive-effect commit could feed another render and eventually hit the nested update limit.

Fix

The reset now uses a ref as the accepted session-transition marker. History recall marks the session active before state dispatch. Reset marks it inactive before dispatching its three clears, so inactive sessions perform no state updates and re-entrant effects cannot enqueue the same reset twice.

User impact

Thread composers no longer risk blanking the route with React #185 when empty history props are recreated during concurrent rendering. Normal history recall and reset behavior is preserved.

Validation

• pnpm exec turbo run test --filter=@bb/app --force -- src/components/promptbox/PromptBoxInternal.test.tsx — 97 passed
• pnpm exec turbo run typecheck --filter=@bb/app --force — passed

AGENT GENERATED: by GPT-5.6