feat(gateway): show provider and effort in runtime footer

[intelege-ma]

Summary

Extends the existing runtime metadata footer from #17026 to include provider and reasoning effort when those values are available.

This does not introduce the footer mechanism itself. The opt-in footer, gateway/runtime_footer.py, build_footer_line(), /footer on|off, and the off-by-default display.runtime_footer.enabled config already exist on main from #17026.

This PR adds two missing runtime fields to that existing footer:

• provider
• effort

Example when enabled with these fields:

codex · gpt-5.5 · xhigh · 25%

Motivation

The existing footer shows model/context/cwd, but model alone is not enough to explain the actual runtime path in Hermes deployments where the same or similar model can be served through different providers/transports.

Provider and reasoning effort are useful for spotting:

• provider fallback or routing surprises
• reasoning-effort changes from config or runtime commands
• different behavior caused by transport/provider rather than model name alone

Scope

This is intentionally a small extension of the existing footer:

• no new command
• no new config namespace
• no change to the opt-in/off-by-default privacy posture
• no model prompt/context change
• no footer rendering on tool-progress messages

Implementation

• Adds provider shortening aliases in gateway/runtime_footer.py.
• Adds an effort field rendered from resolved reasoning effort.
• Passes provider and reasoning_effort through the existing agent_result footer path in gateway/run.py.
• Resolves reasoning effort from live agent.reasoning_config first, then falls back to config.

Privacy and compatibility

The footer remains off by default.

Existing users who do not enable the footer see no behavior change. Users who enable it can still configure fields and omit provider, effort, or cwd if they do not want those shown.

No API keys, tokens, or secret values are included.

Tests

Clean branch from current origin/main, one commit.

Targeted footer tests:

python3 -m pytest tests/gateway/test_runtime_footer.py -q
30 passed in 0.78s

Gateway-adjacent smoke suite:

python3 -m pytest tests/gateway/test_runtime_footer.py tests/gateway/test_slack.py tests/gateway/test_discord_clarify_buttons.py tests/gateway/test_slash_access_dispatch.py -q
264 passed, 34 warnings in 16.95s

Warnings are existing Slack AsyncMock coroutine warnings, not footer failures.

Manual render smoke:

codex · gpt-5.5 · xhigh · 25%
manual_footer_render=PASS
manual_disabled_default=PASS

Static checks:

git diff --check origin/main...HEAD
python3 -m compileall -q gateway/runtime_footer.py gateway/run.py

Added-lines security scan found no hardcoded secrets or shell/eval/deserialization/SQL-injection patterns.

[alt-glitch]

Duplicate of #17026 — the opt-in runtime-metadata footer (gateway/runtime_footer.py + build_footer_line, /footer on, off-by-default display.runtime_footer.enabled) was already merged on 2026-04-28 and is present on main with the same files and mechanism this PR re-implements.