hermes - 💡(How to fix) Fix feat: extend runtime_footer with provider, tokens, cost, and tool count fields

Description

The runtime footer currently supports only 3 fields: model, context_pct, and cwd. For Discord gateway users, this is insufficient — operators need real-time visibility into token consumption, provider status, and per-turn cost without relying on /usage or digging through gateway logs.

Proposed New Fields

Motivation

When using Hermes via Discord (gateway mode), there is no status bar like the CLI has. The runtime footer is the only place where operators can see model + context info without running /usage. Adding these fields gives:

• Cost awareness — know immediately if a turn cost $0.001 or $0.05
• Provider diagnostics — see which provider answered (useful when routing through OpenRouter or custom providers)
• Performance visibility — duration and token count help identify latency vs. cost tradeoffs
• Operational transparency — tool count reveals turn complexity at a glance

Current Footer

mimo-v2.5 · 85% · ~/.hermes/hermes-agent

Proposed Footer

mimo-v2.5 · opencode-go · 12.4K/2.1K · $0.003 · 3 tools · 8s · ~/.hermes/hermes-agent

Implementation Notes

• agent_result in gateway/run.py:7824 already passes model, last_prompt_tokens, context_length, and cwd to build_footer_line(). The new fields (provider, completion_tokens, tool count, duration) are available in the same result dict or can be computed from existing data.
• format_runtime_footer() in runtime_footer.py already supports dynamic field iteration — adding new field names with their render logic should be straightforward.
• Cost lookup requires provider pricing data — could use a simple lookup table or the existing cost estimation logic if available.
• Fields should remain configurable via display.runtime_footer.fields so operators can choose what to show.
• Backward compatible — default fields remain [model, context_pct, cwd].

Use Case Context

Discord gateway operators who manage Hermes as a multi-user service need per-turn telemetry visible in the chat itself. The current footer is a good foundation but缺少 the operational fields that make it truly useful for production monitoring.