PR #22967: feat(dashboard): expose missing display and Telegram per-platform settings in config UI

• Repository: NousResearch/hermes-agent
• Author: CalmProton
• State: open | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/22967

Description (problem / solution / changelog)

Summary

Exposes 6 runtime display settings in the dashboard config page that were previously only configurable via manual config.yaml edits. These are settings the gateway reads at runtime but weren't surfaced in DEFAULT_CONFIG.

This follows up on #22772 which added display.platforms.telegram.notifications to the gateway but didn't expose it in the dashboard.

What was missing

The dashboard schema is built from DEFAULT_CONFIG, but display.platforms is {} there and several global display keys don't exist as root-level entries:

How it works

All 6 are injected as virtual fields following the existing model_context_length pattern — defined in _SCHEMA_OVERRIDES with explicit category, then appended to CONFIG_SCHEMA after the tree-walk from DEFAULT_CONFIG.

Testing

• 8/8 TestBuildSchemaFromConfig tests pass (includes category-merge and no-single-field-category invariants)
• All 640+ web server tests pass
• Verified all 6 fields appear in the schema with correct types and categories
• No single-field categories introduced (verified via Counter)

Closes #22964

Changed files

• hermes_cli/web_server.py (modified, +52/-2)