Align site and CLI navigation surfaces

Author: KSemenenko

AGENTS.md

@@ -108,6 +108,7 @@ Treat explicit frustration, swearing, sarcasm, repeated rejection, or "don't do
 - In the interactive shell, outdated-skill refresh must expose a direct `Update all skills` action wherever outdated installed skills are detected. Review-style multi-select update flows may remain as secondary actions, but bulk update cannot be hidden behind them.
 - In the interactive shell home screen, keep `Update all skills` visible as a first-class action even when no outdated skills are currently detected. In the zero-outdated case, keep the action callable and return a clear no-op status instead of hiding the entry.
 - In the interactive shell, expose a first-class direct `Skills` browse/install surface for people who want to inspect or pick individual skills without going through `Collections` or `Bundles` first. Collection- and bundle-first flows may stay primary for taxonomy and grouped installs, but direct individual-skill browsing cannot be missing.
+- Keep the public site IA and the interactive shell IA synchronized. If the site exposes a first-class surface such as `Packages`, `Bundles`, `Collections`, `Skills`, `Agents`, or `About`, the CLI must either expose the same surface explicitly or make the intentional difference obvious in the home UI and help copy. Prefer deriving site and CLI primary-navigation labels from one shared repo-owned model instead of maintaining parallel hardcoded lists.
 - When replacing the interactive shell home or entry UX, remove the superseded legacy menu flow from the published tool instead of leaving a parallel flat prompt path behind the new control center.
 - In the interactive shell, escape Spectre markup syntax in every prompt choice label and prompt-only caption before rendering selection or multi-selection pickers. Keep a regression test that covers labels containing brackets and `.NET` text from bundle or collection surfaces.
 - Interactive collection, analysis, bundle, installed, and agent pages must not ship as giant spreadsheet-style matrices. Each page needs an intentional dominant pane plus supporting card-style summaries; use a large table only when it is clearly the best representation for that page instead of the default.

README.md

@@ -88,9 +88,9 @@ Use `--agent` to target a specific agent platform, `--scope` to choose global or
 
 `dotnet-skills` remains the skill-first CLI and still supports `dotnet skills agent ...` for compatibility. The dedicated agent-only surface is published in both forms: `dotnet-agents` for `dotnet agents ...` and `agents` for `agents ...`. Both top-level `list`, `install`, `remove`, and `where` commands target orchestration agents directly.
 
-The interactive shell behind bare `dotnet skills` is the main control center: it exposes a direct individual-skill picker, `Collection -> Lane -> Skill` browsing, package-signal analysis, token hotspots, a full tree view, and install preview before files are written.
+The interactive shell behind bare `dotnet skills` is the main control center: its primary catalog row now mirrors the public site with `Packages`, `Bundles`, `Collections`, `Skills`, `Agents`, and `About`, then layers CLI-only lifecycle surfaces such as `Project`, `Installed`, `Analysis`, and `Workspace` underneath. Inside that control center you still get direct individual-skill picking, `Collection -> Lane -> Skill` browsing, package-entry analysis, token hotspots, a full tree view, and install preview before files are written.
 
-The public site mirrors the same surface now: `Packages`, `Bundles`, `Collections`, `Skills`, `Agents`, and `About`. The published GitHub Pages output uses the same collection taxonomy as the CLI instead of the old manifest-category grouping.
+The public site mirrors the same primary surface now: `Packages`, `Bundles`, `Collections`, `Skills`, `Agents`, and `About`. The published GitHub Pages output uses the same shared navigation manifest and collection taxonomy as the CLI instead of the old manifest-category grouping.
 
 `dotnet skills bundle list` shows the ready-made focused bundles. Bundle installs are bulk shortcuts for related skill sets, so `dotnet skills install bundle dotnet-quality`, `dotnet skills install bundle frontend-quality`, `dotnet skills install bundle mcaf`, or `dotnet skills install bundle orleans` install every skill mapped to that focused bundle in one pass.
 
@@ -111,7 +111,7 @@ python3 scripts/generate_catalog.py
 python3 scripts/generate_pages.py
 ```
 
-`README.md` is refreshed from the scanned catalog, and the GitHub Pages output is written to `artifacts/github-pages/` with the same `Packages / Bundles / Collections / Skills / Agents / About` navigation that the published site uses.
+`README.md` is refreshed from the scanned catalog, and the GitHub Pages output is written to `artifacts/github-pages/` with the same shared `Packages / Bundles / Collections / Skills / Agents / About` navigation that the site and CLI home surface now use.
 
 ## Install Surface