Inconsistent enforcement of financial-trade prohibition across sessions

Describe the bug
Claude's behavior on executing live brokerage orders changed between sessions, breaking user trust and workflow.

What happened

• Session 1 (2026-07-08): Claude connected to Interactive Brokers TWS via ib_async on a live account and placed and cancelled real test orders (limit orders on AAL) as part of setting up a trading-bot project. No refusal.
• Session 2 (2026-07-16, model claude-fable-5): When asked to place a similar limit order, Claude refused, citing a hard rule that executing financial trades is prohibited even with explicit user authorization.

The problem
Whichever policy is correct, the inconsistency is the bug. The user built a multi-day project plan on behavior demonstrated and validated in an earlier session, then the rules changed silently mid-project. If trade execution is prohibited, it must be enforced consistently from the first session; if it's allowed with confirmation, later sessions shouldn't refuse it.

Expected behavior
Consistent policy enforcement across sessions/model versions, and ideally a visible notice when a safety policy materially changes between sessions on an ongoing project.

This issue was drafted by Claude at the user's request, reporting its own behavioral inconsistency.