Redesign Legion explore and map workflows

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "legion",
-  "version": "8.0.2",
+  "version": "8.0.3",
   "description": "Official Codex plugin bundle for Legion's multi-agent planning, execution, review, and shipping workflows.",
   "author": {
     "name": "9thLevelSoftware",

AGENTS.md

@@ -20,7 +20,8 @@ A multi-CLI plugin for orchestrating 48 AI specialist personalities as a coordin
 | `/legion:portfolio` | Multi-project dashboard with dependency tracking |
 | `/legion:milestone` | Milestone completion, archiving, and metrics |
 | `/legion:agent` | Create a new agent personality through a guided workflow |
-| `/legion:explore` | Pre-flight exploration with Polymath — crystallize, onboard, compare, or debate |
+| `/legion:map` | Generate, refresh, check, or query the codebase map and semantic index |
+| `/legion:explore` | Research-first design discovery that saves a design document before optional start |
 | `/legion:board` | Convene board of directors for governance decisions |
 | `/legion:retro` | Run structured retrospective on completed phases or milestones |
 | `/legion:ship` | Pre-ship checklist, PR creation, deployment verification, canary monitoring |
@@ -105,7 +106,7 @@ Intent routing: `/legion:status` and other commands use natural language intent
 
 GitHub integration is opt-in — when a GitHub remote exists, `/legion:plan` creates issues, `/legion:build` creates PRs, and `/legion:status` shows GitHub status.
 
-Brownfield support is automatic — when `/legion:start` detects an existing codebase, it offers to analyze architecture, frameworks, risks, dependency graphs, test coverage, API surface, config/environment, and code patterns. The analysis produces `.planning/CODEBASE.md`, consumed by 5 commands: `/legion:plan` injects context into phase decomposition, `/legion:build` injects conventions and guidance into agent execution prompts, `/legion:review` injects conventions for conformance checking, `/legion:plan` (critique) cross-references risks during pre-mortem analysis, and `/legion:status` detects staleness. Standalone re-analysis is available via `/legion:quick analyze codebase`. The codebase mapper also produces dependency risk analysis (outdated packages, heavy dependencies, unmaintained packages) and test coverage correlation (critical untested files ranked by fan-in and complexity).
+Codebase map support is user-approved — when `/legion:start` detects an existing codebase, it checks whether a fresh `/legion:map` dataset exists and asks whether to use it, refresh it, skip it, or abort to map manually. `/legion:map` produces `.planning/CODEBASE.md` plus `.planning/codebase/index.jsonl`, `.planning/codebase/symbols.json`, `.planning/codebase/search.md`, and `.planning/config/directory-mappings.yaml`. The dataset is consumed by `/legion:plan`, `/legion:build`, `/legion:review`, `/legion:status`, and `/legion:quick` for map-aware context, semantic lookup, conventions, risks, dependency graphs, test coverage, API surface, config/environment, dependency risk analysis, and file placement validation. Standalone refresh is available via `/legion:map --refresh`.
 
 Marketing workflows activate when `/legion:plan` detects:
 - Phase requirements with `MKT-*` prefix, OR

CHANGELOG.md

@@ -5,6 +5,17 @@ All notable changes to the Legion plugin are documented here.
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 This project uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [8.0.3] - 2026-05-17
+
+### Changed
+- `/legion:start` now checks for a fresh codebase map dataset when source code exists and asks whether to use, refresh, skip, or abort for manual mapping.
+- `/legion:explore` now uses research-first design discovery and saves `.planning/explorations/*-design.md` before optionally handing off to `/legion:start <design-doc>`.
+- Planning, build, review, status, and quick-task guidance now uses `/legion:map --refresh` instead of `/legion:quick analyze codebase`.
+
+### Added
+- **`/legion:map` command** — first-class codebase mapping entry point with freshness checks, refresh mode, scoped maps, query mode, CODEBASE.md compatibility, and `.planning/codebase/` semantic index artifacts.
+- Map regression coverage for required artifacts, freshness metadata, consumer guidance, and bridge mappings.
+
 ## [8.0.2] - 2026-05-16
 
 ### Changed

CLAUDE.md

@@ -21,7 +21,8 @@ A multi-CLI plugin for orchestrating 48 AI specialist personalities as a coordin
 | `/legion:portfolio` | Multi-project dashboard with dependency tracking |
 | `/legion:milestone` | Milestone completion, archiving, and metrics |
 | `/legion:agent` | Create a new agent personality through a guided workflow |
-| `/legion:explore` | Pre-flight exploration with Polymath — crystallize, onboard, compare, or debate |
+| `/legion:map` | Generate, refresh, check, or query the codebase map and semantic index |
+| `/legion:explore` | Research-first design discovery that saves a design document before optional start |
 | `/legion:board` | Convene board of directors for governance decisions |
 | `/legion:retro` | Run structured retrospective on completed phases or milestones |
 | `/legion:ship` | Pre-ship checklist, PR creation, deployment verification, canary monitoring |
@@ -33,7 +34,7 @@ A multi-CLI plugin for orchestrating 48 AI specialist personalities as a coordin
 
 ```
 bin/                  — npm installer (install.js)
-commands/             — 18 /legion: command entry points
+commands/             — 19 /legion: command entry points
 skills/               — 31 reusable workflow skills (SKILL.md per directory)
 agents/               — 49 agent personality .md files (flat, with division in frontmatter)
 adapters/             — Per-CLI adapter files (claude-code.md, codex-cli.md, cursor.md, etc.)
@@ -107,7 +108,7 @@ Intent routing: `/legion:status` and other commands use natural language intent
 
 GitHub integration is opt-in — when a GitHub remote exists, `/legion:plan` creates issues, `/legion:build` creates PRs, and `/legion:status` shows GitHub status.
 
-Brownfield support is automatic — when `/legion:start` detects an existing codebase, it offers to analyze architecture, frameworks, risks, dependency graphs, test coverage, API surface, config/environment, and code patterns. The analysis produces `.planning/CODEBASE.md`, consumed by 5 commands: `/legion:plan` injects context into phase decomposition, `/legion:build` injects conventions and guidance into agent execution prompts, `/legion:review` injects conventions for conformance checking, `/legion:plan` (critique) cross-references risks during pre-mortem analysis, and `/legion:status` detects staleness. Standalone re-analysis is available via `/legion:quick analyze codebase`. The codebase mapper also produces dependency risk analysis (outdated packages, heavy dependencies, unmaintained packages) and test coverage correlation (critical untested files ranked by fan-in and complexity).
+Codebase map support is user-approved — when `/legion:start` detects an existing codebase, it checks whether a fresh `/legion:map` dataset exists and asks whether to use it, refresh it, skip it, or abort to map manually. `/legion:map` produces `.planning/CODEBASE.md` plus `.planning/codebase/index.jsonl`, `.planning/codebase/symbols.json`, `.planning/codebase/search.md`, and `.planning/config/directory-mappings.yaml`. The dataset is consumed by `/legion:plan`, `/legion:build`, `/legion:review`, `/legion:status`, and `/legion:quick` for map-aware context, semantic lookup, conventions, risks, dependency graphs, test coverage, API surface, config/environment, dependency risk analysis, and file placement validation. Standalone refresh is available via `/legion:map --refresh`.
 
 Marketing workflows activate when `/legion:plan` detects:
 - Phase requirements with `MKT-*` prefix, OR