When Hermes runs on an interactive coding surface (CLI, TUI, desktop app,
ACP) inside a git repo, it now shifts into a coding posture:
- Tool restriction: the toolset collapses to a new `coding` set (files,
terminal, search, web docs, skills, todo, delegate, vision, browser) plus
the user's enabled MCP servers. Messaging / TTS / image-gen / smart-home /
music / cron / computer-use fall away.
- Operating brief: a Cursor-style system block (gather context before
editing, focused diffs, verify, never fabricate, git is the user's).
- Live workspace snapshot: git root, branch + upstream (ahead/behind),
worktree, dirty/staged counts, recent commits — built once per session
(cache-safe; never re-probed per turn).
Activation via `agent.coding_context` (auto|on|off, default auto). `auto`
fires only on interactive surfaces in a git repo; messaging platforms are
never affected. A `--toolsets` flag or `HERMES_TUI_TOOLSETS` pin always wins.
