[bug] max_bot_turns=1000 still hits hard bot turn limit at 100

[rockexe0000]

Description

max_bot_turns is documented as a soft limit with a compiled-in hard cap of 1000, but bot-to-bot conversations still stop at 100 with:

Hard bot turn limit reached (100). A human must reply to continue.

This happens even when max_bot_turns = 1000 is configured.

The likely cause is that PR #741 updated the docs and some adapter-level constants to 1000, but the shared BotTurnTracker hard cap is still:

pub const HARD_BOT_TURN_LIMIT: u32 = 100;

in src/bot_turns.rs.

Steps to Reproduce

1. Configure Discord or Slack with bot messages enabled.
2. Set:

max_bot_turns = 1000

3. Start a bot-to-bot thread that produces more than 100 consecutive bot messages without a human reply.
4. Observe that OpenAB stops at 100 bot turns with the hard-limit message.

Expected Behavior

If the documented hard cap is 1000, the conversation should not hit the hard limit at 100.

Either:

• src/bot_turns.rs should use a hard cap of 1000, matching the docs and PR feat: raise max_bot_turns default to 100, raise hard cap to 1000 #741, or
• the docs/config reference should be corrected to say the real hard cap is 100.

Environment

• Platform: Discord
• Config: max_bot_turns = 1000
• Repo branch/docs referenced: main
• Relevant PR: feat: raise max_bot_turns default to 100, raise hard cap to 1000 #741

Screenshots / Logs

Observed Discord message:

Hard bot turn limit reached (100). A human must reply to continue.

Relevant code:

• src/bot_turns.rs still defines HARD_BOT_TURN_LIMIT = 100
• docs/config-reference.md documents a compiled-in hard cap of 1000