Context

Health checks, agent summaries, security audits, gateway init, and TUI use the default agent for ordering and as a display anchor. Post-gut, display order should follow agents.list order — first configured is first displayed, no special "default" marker.

Depends on #1575 (schema field removal).

What

1. Replace default-agent-first ordering with list-order semantics across all display sites
2. Remove any "default" badges/markers from health, status, TUI output
3. Empty agent list → show "no agents configured" instead of phantom default

Acceptance Criteria

• Agents display in agents.list order (first in config = first displayed)
• No "default" badge or marker appears in any display output
• Empty agent list → "no agents configured" shown
• All display/enumeration call sites migrated (no resolveDefaultAgentId references)
• Tests updated; CI passes

Files

• src/commands/health.ts, src/commands/agents.config.ts
• src/security/fix.ts, src/security/audit-extra.async.ts
• src/gateway/server.impl.ts, src/gateway/server/health-state.ts
• src/gateway/hooks.ts, src/gateway/assistant-identity.ts
• src/tui/tui.ts
• src/commands/agents.commands.identity.ts, src/commands/agents.commands.bind.ts
• src/telegram/bot.ts, src/telegram/bot-handlers.ts
• src/commands/agents.commands.list.ts — formats the (default) tag (lines 23, 102–103, 107)
• src/commands/agents.providers.ts — has summaryIsDefault (lines 147, 179)
• src/commands/channels/add.ts:143 — uses isDefault for display label