[UX] /context: token stats require scrolling past 100+ MCP tool entries to be visible

Summary

The /context command currently outputs sections in this order:

1. Context usage (token breakdown) ✅
2. MCP tools — a list that can exceed 100 entries ⚠️
3. Memory files
4. Skills

The MCP tools section dominates the output and forces scrolling past it to reach Memory files and Skills, which are typically what you want to check alongside the token usage.

Expected behavior

Reverse the output order so that MCP tools appear first (scrolled past if needed) and the most useful information — token stats, memory files, skills — is visible at the bottom without scrolling.

MCP tools could also be collapsed by default (e.g. just showing the count) with a flag like --mcp to expand them.

Context

This is noticeable when many MCP servers are connected — in my case ~100 tools across Figma, Linear, Notion, Slack, etc. The MCP list takes up the entire visible terminal area, making the command nearly useless for a quick context check.