fix(slack): keep transient status in assistant UI

[goblin-zavala]

Summary

Keeps transient gateway lifecycle/status updates in Slack Assistant status instead of falling back into permanent chat messages.

This preserves the Slack Assistant bottom status affordance for semantic states like compacting context, recalling prior context, reading files, and drafting the reply, while keeping internal lifecycle plumbing out of user-visible message history.

What changed

• Routes supported status events through assistant_threads_setStatus when Slack thread metadata is available.
• Maps transient lifecycle messages such as preflight compression/context compaction into compact Assistant status text.
• Avoids posting internal status/progress strings as normal Slack chat messages.
• Clears Assistant status after final sends / streaming final edits.
• Adds focused Slack tests for status routing, missing scope fallback, and final status clearing.

Tests

• pytest -o 'addopts=' tests/gateway/test_slack.py -k 'send_or_update_status or gateway_restart_status_wording_is_natural or sets_status_in_thread or noop_without_thread or missing_scope or stop_typing or send_clears_status_after_final_post or streaming_final_edit_clears_status' -q
  • 13 passed, 186 deselected
• python -m py_compile gateway/run.py gateway/platforms/slack.py tests/gateway/test_slack.py
• git diff --check HEAD~1..HEAD

[liuhao1024]

Review: Org-specific MCP tool names in shared Slack adapter

The _assistant_activity_status() method in gateway/platforms/slack.py hardcodes several organization-specific MCP tool names in the activity_map:

(("mcp_zoblin_connections_close", "close_"), "is checking Close"),
(("mcp_zoblin_connections_growth_n8n", "n8n"), "is checking n8n"),
(("mcp_zoblin_connections_railway", "railway"), "is checking Railway"),
(("mcp_google_sheets", "sheet"), "is checking Sheets"),
(("mcp_ga4", "analytics"), "is checking analytics"),

These are specific to one deployment's MCP server configuration (zoblin_connections_*) and won't match any other user's tool set. They'll silently never trigger for anyone else, which is harmless but clutters the shared adapter.

Suggestion: Move these to the generic fallback path or make the activity map configurable. The generic entries (read_file, terminal, web_search, etc.) are universally useful — the MCP-specific ones belong in user/plugin configuration, not in the shared platform adapter.

[goblin-zavala]

Closing: this was opened from the wrong ownership model. These Hermes operator changes are local/private unless Zavala explicitly chooses a remote under zavala-ai.