fix(tools): fix discord tool schema type mismatch for Gemini

[dirty-bun-ops]

What does this PR do?

Resolves an issue where the discord_server tool causes Google Gemini API requests to fail with HTTP 400 INVALID_ARGUMENT.

Problem:
The Google Gemini API strictly requires all enum parameter values in tool function declarations to be strings (or it rejects the schema). The auto_archive_duration parameter in the discord_server schema was using an integer enum ([60, 1440, ...]). Because Gemini validates the entire toolset upon initialization, this single typo would cause the entire tool payload to be rejected, instantly breaking agent sessions and any scheduled Cron jobs that rely on these global toolsets.

Solution:
Changed the auto_archive_duration schema type to "string" and converted its enums to string representations (["60", "1440", ...]). To preserve compatibility with Discord's REST API (which expects an integer payload), a simple int() cast was added inside the tool's runtime implementation.

Related Issue

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• tools/discord_tool.py:
  • Updated auto_archive_duration parameter schema type to "string".
  • Updated enum list to strictly use strings: ["60", "1440", "4320", "10080"].
  • Added an int() cast to auto_archive_duration when constructing the JSON body in _create_thread.

How to Test

1. Configure an agent session using a Gemini model (google/gemma-4-31b via AI Studio).
2. Start the Hermes Agent or run a Cron Job that injects the full global toolset (including discord_server).
3. Before, the connection immediately crashes on startup with 400 Bad Request regarding schema validation.
4. After, the toolset is successfully parsed, and Discord features work as intended.

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: Windows/Production Environment

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

Screenshots / Logs

Tested on production with google/gemma-4-31b where all previously failing Cron jobs utilizing the same toolset were successfully restored.