fix(deps): relax dev setuptools pin to 81.0.0 (torch caps setuptools<82)

[benegessarit]

What does this PR do?

Relaxes the dev extra's setuptools pin from 82.0.1 to 81.0.0. torch (>= 2.11) publishes Requires-Dist: setuptools<82, so any environment that resolves the dev extra together with torch is unsatisfiable — e.g. developing hermes-agent in an env that also carries a local embedding/reranker stack. 81.0.0 is the latest release under torch's cap and stays inside the build-system support window already declared in pyproject.toml (requires = ["setuptools>=77.0,<83"]).

Related Issue

Fixes #44692

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)

Changes Made

• pyproject.toml: dev extra setuptools==82.0.1 → setuptools==81.0.0, with a comment noting the torch cap (keeps the exact-pin style of the extra)
• uv.lock: regenerated via uv lock; the diff is scoped to the setuptools entry only (specifier, version, sdist, wheel — 8 lines)

How to Test

1. On main, reproduce the conflict:

   $ uv pip install --dry-run ".[dev]" "torch==2.12.0"
     × No solution found when resolving dependencies:
     ╰─▶ ... torch==2.12.0 and all versions of hermes-agent[dev] are incompatible.

2. On this branch, the same command resolves cleanly.
3. uv sync --locked --python 3.11 --extra all --extra dev succeeds (the same invocation CI uses), confirming manifest/lock consistency.

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 — ran the full suite via scripts/run_tests.sh (~17k tests): 39 failures across 12 files on my dev box, all environment-dependent (a live Hermes gateway runs on the same machine) and identical with the old setuptools==82.0.1 pin re-installed in the same venv (A/B-verified) — i.e. unrelated to this change
• I've added tests for my changes — N/A: dependency-metadata-only change; the regression gate is CI's uv sync --locked, which fails if pin and lock drift
• I've tested on my platform: macOS 26.4 (arm64), Python 3.11, uv 0.9.29

Documentation & Housekeeping

• I've updated relevant documentation — N/A (no behavior change)
• I've updated cli-config.yaml.example if I added/changed config keys — N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — N/A
• I've considered cross-platform impact — dependency-metadata change, platform-independent
• I've updated tool descriptions/schemas if I changed tool behavior — N/A

[austinpickett]

Merged into main via #46744 (commit 0bbff1f). Your fix was cherry-picked onto current main — the dev setuptools pin is relaxed to 81.0.0 so it stays compatible with torch >=2.11 (which caps setuptools<82). The pyproject hunk was reconciled against current main and uv.lock regenerated. Thanks @benegessarit! 🙏