Safe Message Routing Under Conflicting Browser State
Tests whether a model can reason from incomplete evidence, reject an attractive but unsafe fix, design reliable behavior for overlapping requests and retries, test its own proposal, and explain the result clearly without using tools.
Prompt
A local assistant has four separate chats. Dictation began in tab A. Eighteen milliseconds later, a test tab showing chat B sent a heartbeat. The finished request contained text and a request ID, but no chat or tab ID. It appeared in chat B. Closing the test tab prevented 20 more failures. Retrying one request created a duplicate. Normal and test pages share one routing service. A developer proposes locking one global "current chat" until dictation ends. Without files, logs, or tools, identify the smallest defensible flaw and what remains unproven. Show an event order where that lock still fails. Design safe routing for multiple tabs, simultaneous dictations, reconnects, retries, expired sessions, and separation of normal and test pages. State when delivery must be rejected rather than guessed. Give six hostile tests. End with a plain-language explanation of at most 120 words. Never claim a fix was performed.
