docs: add Roslyn analyzer documentation, samples, and examples

- Create docs/Migration/Analyzers.md with full reference for all 8 BWFC analyzers (BWFC001-005, BWFC010-012) including before/after code, code fix descriptions, installation guide, and .editorconfig configuration
- Add analyzer sample page to AfterBlazorServerSide under MigrationTools/Analyzers with inline code examples
- Create standalone BeforeFix/AfterFix example files showing full analyzer pass on realistic migrated code
- Update mkdocs.yml nav and Migration readme with analyzer cross-references
- Add Migration Tools nav category to sample app ComponentList

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

Author: csharpfritz

.squad/agents/beast/history.md

@@ -497,3 +497,50 @@ Updated `.squad/skills/migration-standards/SKILL.md` to add new section at end:
 - Created docs/ValidationControls/BaseValidator.md 
 - Created docs/ValidationControls/BaseCompareValidator.md
 - Updated mkdocs.yml (Validation Controls section)
+
+### Roslyn Analyzer Suite Documentation (Current Session)
+
+**Delivered:** Comprehensive MkDocs page documenting all 8 BWFC Roslyn analyzers with code fixes.
+
+**File created:** `docs/Migration/Analyzers.md` (~17.7 KB)
+
+**Content structure:**
+1. **Overview** — What the analyzer package is, how to install it, when to use it (post-migration)
+2. **Summary table** — All 8 rules with ID, severity, name, and brief description
+3. **Per-analyzer sections** (8 total, each with):
+   - Rule ID, severity, category
+   - What it detects (the problematic pattern from source code analysis)
+   - Why it matters (migration context for Web Forms devs)
+   - Before/after code examples (realistic, not toy)
+   - Code fix description (what the automatic fix produces)
+4. **Configuration/suppression** — `.editorconfig`, `#pragma warning`, `[SuppressMessage]`, bulk suppression strategy
+5. **Recommended workflow** — 6-step checklist tying analyzers into the migration pipeline
+
+**Analyzer coverage:**
+- BWFC001: Missing [Parameter] attribute on WebControl properties
+- BWFC002: ViewState["key"] usage patterns → component state
+- BWFC003: IsPostBack checks → Blazor lifecycle methods
+- BWFC004: Response.Redirect() → NavigationManager.NavigateTo()
+- BWFC005: Session["key"] and HttpContext.Current → scoped services/ProtectedSessionStorage
+- BWFC010: Required attributes missing on BWFC components (GridView.DataSource, etc.)
+- BWFC011: Web Forms event handler signature (object, EventArgs) → EventCallback
+- BWFC012: Leftover runat="server" in string literals
+
+**Additional updates:**
+- `mkdocs.yml` — added "Roslyn Analyzers: Migration/Analyzers.md" after "Automated Migration Guide"
+- `docs/Migration/readme.md` — added "Clean Up with Roslyn Analyzers" section with install command and link
+
+**Key decisions:**
+- Placed after Automated Migration Guide in nav — developers run automation first, then use analyzers to clean up code-behind
+- Code fix examples show the literal output (TODO comments, commented-out code) so developers know what to expect
+- Tabbed before/after examples using `=== "Before"` / `=== "After"` pattern matching DeprecationGuidance.md style
+- Lifecycle mapping table in BWFC003 section shows IsPostBack → OnInitialized equivalence
+- Bulk suppression strategy section helps large codebases adopt analyzers incrementally
+- Cross-references to existing BWFC docs (ViewState utility, Response.Redirect utility) where relevant
+
+**Learnings:**
+- Analyzer code fixes fall into two categories: (1) additive (BWFC001 adds [Parameter]), (2) commenting-out with TODO (BWFC002-005, BWFC011). The commenting pattern is intentional — these require human judgment for the replacement.
+- BWFC010 (RequiredAttributeAnalyzer) tracks a small set of components (GridView, HyperLink, Image) — extensible in future
+- BWFC012 (RunatServerAnalyzer) targets string literals, not markup — catches dynamically-built HTML, not .razor files
+- Source reading revealed team decision (2026-03-21): BWFC001 skips static properties — documented this in the analyzer description
+- MkDocs strict build passes with analyzer docs included (59.43s build time)

.squad/agents/jubilee/history.md

@@ -205,3 +205,13 @@
 - **Build verified:** 0 errors.
 
 
+
+### Analyzer Sample Content (2026-03-20)
+
+- **Created Razor sample page** at `samples/AfterBlazorServerSide/Components/Pages/MigrationTools/Analyzers/Index.razor`  informational/reference page covering all 8 BWFC analyzers (BWFC001-005, BWFC010-012) with installation instructions, summary table, and before/after code examples for each rule.
+- **Created before/after example files** at `samples/AnalyzerExamples/BeforeFix.cs.example` and `AfterFix.cs.example`  realistic ProductManager code-behind showing every analyzer pattern in context.
+- **Added 'Migration Tools' nav category** to `ComponentList.razor` with link to Roslyn Analyzers page.
+- **Route pattern:** `/MigrationTools/Analyzers`  new top-level route alongside `/ControlSamples/` and `/UtilityFeatures/` since analyzers are not controls or utility features.
+- **Convention for non-compilable examples:** Used `.cs.example` extension per task requirements to signal these are reference files, not build artifacts.
+- **Lesson:** Analyzer sample pages are educational/reference-style (like Theming) rather than interactive demo pages. No `@code` block needed since there's no interactive state.
+- **Build verified:** 0 errors.

.squad/decisions/inbox/beast-analyzer-docs.md

@@ -0,0 +1,25 @@
+# Decision: Roslyn Analyzer Documentation Placement and Structure
+
+**Author:** Beast (Technical Writer)  
+**Date:** 2026-03-XX  
+**Status:** Delivered
+
+## Context
+
+The BWFC project has 8 Roslyn analyzers with code fixes in `BlazorWebFormsComponents.Analyzers`. These needed comprehensive documentation for developers using the analyzer package post-migration.
+
+## Decision
+
+1. **Placement:** `docs/Migration/Analyzers.md` under the Migration section, positioned after "Automated Migration Guide" and before "Deprecation Guidance". Rationale: analyzers are a post-migration tool — developers run automation first, then use analyzers to clean up code-behind patterns the script couldn't address.
+
+2. **Structure:** Each analyzer gets a dedicated section with: what it detects, why it matters, before/after code, and code fix description. This matches the pattern established in DeprecationGuidance.md.
+
+3. **Cross-references:** Links to existing utility docs (ViewState, Response.Redirect) where the analyzer topic overlaps with a BWFC compatibility shim.
+
+4. **Migration readme update:** Added "Clean Up with Roslyn Analyzers" section to `docs/Migration/readme.md` as a follow-up step in the migration journey.
+
+## Impact
+
+- New file: `docs/Migration/Analyzers.md` (~17.7 KB)
+- Updated: `mkdocs.yml` (nav entry), `docs/Migration/readme.md` (new section)
+- MkDocs strict build passes

.squad/decisions/inbox/jubilee-analyzer-samples.md

@@ -0,0 +1,17 @@
+# Decision: Analyzer Samples Use /MigrationTools/ Route
+
+**Author:** Jubilee
+**Date:** 2026-03-20
+**Status:** Implemented
+
+## Context
+Needed a sample page for the BWFC Roslyn analyzer suite. Analyzers are IDE tools, not UI components, so they don't fit under `/ControlSamples/` or `/UtilityFeatures/`.
+
+## Decision
+Created a new `/MigrationTools/` route category with its own nav section in ComponentList.razor. The page at `/MigrationTools/Analyzers` is an informational/reference page (no interactive demos) following the educational style of the Theming page.
+
+Standalone before/after example files use `.cs.example` extension in `samples/AnalyzerExamples/` to distinguish reference examples from compilable code.
+
+## Impact
+- New nav category 'Migration Tools' in ComponentList.razor
+- Establishes pattern for future migration tooling pages (e.g., migration scripts, config helpers)