fix: make Slack platform capability note tool-aware

[tgasgarth-coatue]

What changed

• replace the absolute Slack API denial with capability-aware guidance
• tell agents to inspect loaded tools, plugins, and bounded helpers before claiming read access is unavailable
• preserve the guard against unsupported write/admin actions

Why

Profiles can provide bounded read-only Slack helpers even when Hermes has no native Slack tool. The previous absolute note caused an agent to incorrectly refuse a channel-history summary despite a working helper.

Verification

• direct build_session_context_prompt runtime assertion passed
• py_compile passed for changed Python files
• git diff --check passed
• canonical pytest runner unavailable in this air-gapped workspace because no test venv/pytest cache is installed

[alt-glitch]

This was generated by AI during triage.

Duplicate of #6538 — the earliest open PR making the Slack platform note in build_session_context_prompt capability-aware for the same bug (#6533). #6545 is a second open sibling with the same approach. Marking this as a duplicate of the earliest open PR; a maintainer can pick whichever is cleanest to merge.

[tonydwb]

Code Review Summary

Looks good! No obvious issues found.

---

Reviewed by Hermes Agent

[teknium1]

Thanks for targeting the real Slack prompt/runtime mismatch.

Problems

• The replacement at gateway/session.py:499 is selected unconditionally. build_session_context_prompt() currently has no loaded-tool argument (gateway/session.py:380-384), and the gateway supplies only context and redact_pii (gateway/run.py:10866). As a result, a Slack session without scoped tools gets the same relaxed note as a session with Slack MCP tools. That misses #6533's required split: retain the conservative note when no scoped tool is available, and emit a capability-aware note only when one is.

Suggested changes

• Thread a stable, session-selected Slack capability signal into the prompt builder, analogous to the existing Discord capability gate at gateway/session.py:343-365, and cover both tool-present and tool-absent paths in tests/gateway/test_session.py.

Automated hermes-sweeper review.

[teknium1]

This note is emitted for every Slack session, regardless of whether a scoped Slack tool is actually exposed. Please select it from an explicit, stable loaded-tool capability signal so no-tool sessions retain the conservative disclaimer required by #6533.

[teknium1]

This test covers only the single generic note. Add separate tool-present and tool-absent cases so the regression contract verifies that no-tool sessions remain conservative while scoped Slack-tool sessions are acknowledged.

[teknium1]

Closing as superseded by #70194 (merged): covered by the derivation approach landed via #70194.

Thanks for the work — it's credited in #70194's summary.