Add hero graphic and move multi-event note below the fold

- Add Build-CLI.png hero graphic at top of README
- Move the Ignite/past events note down to just above Scope and Limitations
- Keep Build 2026 front and center

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: mikekinsman

Build-CLI.png

@@ -1,9 +1,8 @@
 # Microsoft Build CLI
 
-A [GitHub Copilot CLI](https://github.com/features/copilot/cli/) skill that connects your local project to the Microsoft Build session catalog. It reads your dependencies, finds relevant sessions, and helps you act on what you learn — all from your terminal.
+![Build CLI](Build-CLI.png)
 
-> [!NOTE]
-> Build-CLI targets **Build 2026** and also indexes past events (Build 2025, Ignite 2025). It supports any future event that follows the same catalog endpoint pattern. It is not a replacement for the event app or session browser — it's a developer-first complement to them.
+A [GitHub Copilot CLI](https://github.com/features/copilot/cli/) skill that connects your local project to the Microsoft Build session catalog. It reads your dependencies, finds relevant sessions, and helps you act on what you learn — all from your terminal.
 
 ## Quick Start
 
@@ -57,6 +56,9 @@ The skill is a thin layer over the **live Build 2026 catalog API** — no stale
 
 Session results are a starting point. For broad topics, ask the agent to refine (*"show me more Foundry sessions about observability"*) or browse the full catalog at [build.microsoft.com/sessions](https://build.microsoft.com/sessions).
 
+> [!NOTE]
+> Build-CLI targets **Build 2026** and also indexes past events (Build 2025, Ignite 2025). It supports any future event that follows the same catalog endpoint pattern. It is not a replacement for the event app or session browser — it's a developer-first complement to them.
+
 ## Scope and Limitations
 
 - **Event-scoped:** Targets Build 2026, with Build 2025 and Ignite 2025 also available. The architecture supports any event that uses the same catalog endpoints.