docs(ai-team): log feature audit session, merge 8 decisions

Session: 2026-02-23-feature-audit
Requested by: Jeffrey T. Fritz

Changes:
- Logged session to .ai-team/log/2026-02-23-feature-audit.md
- Merged 8 decisions from inbox into decisions.md
- Consolidated overlapping decisions (AccessKey/ToolTip, Chart architecture, DataBoundComponent gap)
- Propagated updates to 6 agent history files

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

Author: csharpfritz

.ai-team/agents/beast/history.md

@@ -38,4 +38,15 @@
 - **Child component docs pattern:** Chart introduces a multi-component documentation pattern (Chart, ChartSeries, ChartArea, ChartLegend, ChartTitle) with separate parameter tables for each. This nested-component doc approach should be used for any future components with required child components.
 - **Chart Type Gallery added:** Added a "Chart Type Gallery" section to `docs/DataControls/Chart.md` between "Chart Palettes" and "Web Forms Features NOT Supported". Contains 8 subsections (Column, Line, Bar, Pie, Doughnut, Area, Scatter, Stacked Column) each with a screenshot, `SeriesChartType` enum value, and 1-2 sentence usage guidance. Includes `!!! warning` admonitions on Pie and Doughnut for the Phase 1 palette limitation (single series color instead of per-segment colors).
 - **Chart image path convention:** Chart screenshots live at `docs/images/chart/chart-{type}.png` (lowercase, hyphenated). Referenced from Chart.md using relative paths: `../images/chart/chart-{type}.png`. This `docs/images/{component}/` pattern should be used for any future component screenshots.
-
+- **AccessKey and ToolTip missing across all WebControl-based components:** Neither `BaseWebFormsComponent` nor `BaseStyledComponent` defines `AccessKey` or `ToolTip` parameters. Every control inheriting from WebControl in Web Forms has these, so they are universally 🔴 Missing. Adding them to `BaseStyledComponent` would fix all styled controls in one shot.
+- **Label uses wrong base class for style support:** `Label` inherits `BaseWebFormsComponent` (no style) instead of `BaseStyledComponent`. Web Forms `Label` inherits from `WebControl` and supports all style properties (CssClass, BackColor, Font, etc.). This is the biggest gap for Label — 11 style properties are missing.
+- **ListControl-derived components share common gaps:** ListBox, RadioButtonList (and CheckBoxList, DropDownList) all have the same missing properties: `AppendDataBoundItems`, `DataTextFormatString`, `CausesValidation`, `ValidationGroup`, and `TextChanged` event. These could be fixed once in a shared base.
+- **Literal/Localize/PlaceHolder/View/MultiView are near-complete:** Controls inheriting from `Control` (not `WebControl`) have no style properties by design. The Blazor implementations are essentially feature-complete — matching all relevant properties and events.
+- **Substitution and Xml are permanently deferral candidates:** Both controls are tightly coupled to server-side ASP.NET infrastructure (output caching and XSLT transformation respectively). Neither concept maps to Blazor's component model. Recommend documenting migration alternatives rather than implementing.
+- **Style property computed but not directly settable:** Across all `BaseStyledComponent`-derived controls, the `Style` property is computed from BackColor/ForeColor/Font/etc. via `IStyle.ToStyle()`. Web Forms allowed direct `Style["property"] = "value"` assignment. This pattern difference is consistent but worth noting in migration guides.
+- **Panel is the most feature-complete styled control:** Panel implements 6 out of 7 specific Web Forms properties (only BackImageUrl missing). Combined with full BaseStyledComponent inheritance, it has the highest coverage of any editor control.
+
+
+ Team update (2026-02-23): AccessKey/ToolTip must be added to BaseStyledComponent  decided by Beast, Cyclops
+ Team update (2026-02-23): Chart implementation architecture consolidated (10 decisions)  decided by Cyclops, Forge
+ Team update (2026-02-23): DetailsView/PasswordRecovery branch (sprint3) must be merged forward  decided by Forge

.ai-team/agents/colossus/history.md

@@ -48,3 +48,6 @@
   - Chart pages use JS interop (`ChartJsInterop.cs`) — console errors are expected if Chart.js CDN/bundle isn't fully loaded; page errors are not
   - Pre-existing test suite has 97 failures on non-Chart tests due to ASP.NET structured log console errors (`[timestamp] Error:`) being caught by `Assert.Empty(consoleErrors)` — these are unrelated to Chart work
 
+
+ Team update (2026-02-23): DetailsView/PasswordRecovery branch (sprint3) must be merged forward  decided by Forge
+ Team update (2026-02-23): AccessKey/ToolTip must be added to BaseStyledComponent  decided by Beast, Cyclops

.ai-team/agents/cyclops/history.md

@@ -58,4 +58,20 @@
 - **JS interop pattern for Chart:** Uses `IJSRuntime` directly (not the shared `BlazorWebFormsJsInterop` service) because Chart.js interop is chart-specific, not page-level. `ChartJsInterop` lazily imports the ES module and exposes `CreateChartAsync`, `UpdateChartAsync`, `DestroyChartAsync`.
 - **BaseStyledComponent already has Width/Height as Unit type:** Chart adds `ChartWidth`/`ChartHeight` as string parameters for CSS dimension styling on the wrapper div, avoiding conflict with the base class Unit properties.
 - **Instance-based canvas IDs:** Uses `Guid.NewGuid()` (truncated to 8 chars) for canvas element IDs, consistent with the ImageMap pattern that avoids static counters.
+- **Feature audit — Editor Controls A–I (13 controls):** Created audit docs in `planning-docs/` comparing Web Forms API vs Blazor implementation for AdRotator, BulletedList, Button, Calendar, CheckBox, CheckBoxList, DropDownList, FileUpload, HiddenField, HyperLink, Image, ImageButton, ImageMap.
+- **Common missing property: AccessKey.** Every component that inherits WebControl in Web Forms has AccessKey. Neither `BaseStyledComponent` nor `BaseWebFormsComponent` provides it. This is the single most pervasive gap — affects all 13 audited controls.
+- **ToolTip inconsistently provided.** Some components (Button, FileUpload, Calendar, HyperLink, Image, ImageButton, ImageMap) add ToolTip directly. Others (AdRotator, BulletedList, CheckBox, CheckBoxList, DropDownList) do not. ToolTip should be on the base class.
+- **Image base class mismatch.** `Image` inherits `BaseWebFormsComponent` but Web Forms `Image` inherits `WebControl`. This means Image is missing ALL style properties (CssClass, BackColor, ForeColor, Font, Width, Height, BorderColor, BorderStyle, BorderWidth, Style). ImageMap correctly uses `BaseStyledComponent` per team decision. Image should follow the same pattern.
+- **HyperLink.NavigateUrl naming mismatch.** Web Forms uses `NavigateUrl`; Blazor uses `NavigationUrl`. This breaks migration — developers must rename the attribute.
+- **List controls missing common ListControl properties.** BulletedList, CheckBoxList, and DropDownList all lack DataTextFormatString, AppendDataBoundItems, CausesValidation, and ValidationGroup. These are inherited from ListControl in Web Forms.
+- **Calendar style sub-properties use CSS strings.** All 9 style sub-properties (DayStyle, TitleStyle, etc.) are implemented as CSS class strings instead of `TableItemStyle` objects. Functional but not API-compatible.
+- **HiddenField correctly uses BaseWebFormsComponent.** Matches Web Forms where HiddenField inherits Control (not WebControl), so no style properties needed.
 
+
+ Team update (2026-02-23): AccessKey/ToolTip must be added to BaseStyledComponent  decided by Beast, Cyclops
+ Team update (2026-02-23): Label should inherit BaseStyledComponent instead of BaseWebFormsComponent  decided by Beast
+ Team update (2026-02-23): DataBoundComponent style gap  DataBoundStyledComponent<T> recommended  decided by Forge
+ Team update (2026-02-23): Chart implementation architecture consolidated (10 decisions)  decided by Cyclops, Forge
+ Team update (2026-02-23): Validation Display property missing from all validators  migration-blocking  decided by Rogue
+ Team update (2026-02-23): ValidationSummary comma-split bug is data corruption risk  decided by Rogue
+ Team update (2026-02-23): Login controls missing outer WebControl style properties  decided by Rogue

.ai-team/agents/forge/history.md

@@ -49,6 +49,26 @@ Evaluated 4 JS libraries for Chart component. D3 rejected (zero built-in charts,
 📌 Team update (2026-02-12): Chart component feasibility confirmed — Chart.js recommended via JS interop. Effort: L. Target Milestone 4. — decided by Forge
 📌 Team update (2026-02-12): Milestone 4 planned — Chart component with Chart.js via JS interop. 8 work items, design review required before implementation. — decided by Forge + Squad
 
+### Feature Comparison Audit: Data Controls + Navigation Controls (2026-02-12)
+
+Completed full API surface audit of 12 controls (9 Data + 3 Navigation) comparing Web Forms API vs Blazor implementation. Created `planning-docs/{ControlName}.md` for each.
+
+**Key findings on control coverage:**
+
+1. **Best coverage:** Repeater (minimal Web Forms API, nearly 100% match), DataList (38 props, 8 events matching — excellent style/template support), SiteMapPath (27 props, 5 events — near-complete), DataPager (27 props, 7 events — solid paging).
+
+2. **Good but incomplete:** DetailsView (27 props, 16 events — strong CRUD events, missing style props; on sprint3 branch), TreeView (21 props, 11 events — good core + data binding + accessibility, missing node styles), Menu (16 props, 7 events — good rendering + JS interop, missing base styles and Orientation).
+
+3. **Weakest coverage:** GridView (9 props, 8 events — only basic table rendering, no paging/sorting/editing/selection), FormView (10 props, 12 events — good mode switching but missing nearly all display properties), ListView (14 props, 9 events — great templates, no CRUD events), Chart (14 props, 6 events — architectural deviation to Chart.js/canvas).
+
+**Recurring pattern — style property gap:** Controls inheriting DataBoundComponent<T> (DataGrid, GridView, FormView, DetailsView, ListView) lack WebControl-level style properties (BackColor, ForeColor, Font, BorderColor, Width, Height, etc.) because DataBoundComponent inherits BaseWebFormsComponent, not BaseStyledComponent. DataList is the exception — it implements IStyle directly with all style parameters.
+
+**Recurring pattern — missing CRUD events:** GridView, ListView, and DataGrid are all missing row/item-level CRUD events (RowDeleting/RowDeleted, ItemEditing, etc.) that are essential for inline editing scenarios. Only DetailsView and FormView have these.
+
+**Recurring pattern — no PagerSettings:** All controls that support paging (GridView, DetailsView, FormView) are missing the PagerSettings configuration object that Web Forms uses to configure pager appearance.
+
+**DetailsView branch status:** DetailsView exists on `sprint3/detailsview-passwordrecovery` but is not on the current working branch (`milestone4/chart-component`).
+
 ### Themes and Skins Migration Strategy (2026-02-12)
 
 - Evaluated 5 approaches for migrating Web Forms Themes/Skins to Blazor: CSS Custom Properties, CascadingValue ThemeProvider, Generated CSS Isolation, DI Service, and Hybrid.
@@ -59,3 +79,9 @@ Evaluated 4 JS libraries for Chart component. D3 rejected (zero built-in charts,
 - The library already uses CascadingParameters extensively (TableItemStyle, LoginControl styles) — ThemeProvider follows the same pattern.
 - Implementation is opt-in and non-breaking: no `ThemeProvider` wrapper = no behavior change.
 - Strategy is exploratory per Jeff's request — the README exclusion of themes/skins still stands until a decision to implement.
+
+ Team update (2026-02-23): AccessKey/ToolTip must be added to BaseStyledComponent  fixes all 20+ styled controls in one change  decided by Beast, Cyclops
+ Team update (2026-02-23): DataBoundComponent style gap confirmed systemic  DataBoundStyledComponent<T> recommended  decided by Forge
+ Team update (2026-02-23): GridView is highest-priority data control gap (no paging/sorting/editing)  decided by Forge
+ Team update (2026-02-23): DetailsView/PasswordRecovery branch (sprint3) must be merged forward  decided by Forge
+ Team update (2026-02-23): CascadingValue ThemeProvider recommended for Themes/Skins migration  decided by Forge

.ai-team/agents/jubilee/history.md

@@ -55,3 +55,6 @@
 - **NavMenu Chart node:** Added under Data Components with `Expanded="false"` and 8 sub-nodes for each chart type, alphabetically ordered.
 - **ComponentList updated:** Replaced placeholder `Chart(?)` with a working link.
 
+
+ Team update (2026-02-23): DetailsView/PasswordRecovery branch (sprint3) must be merged forward  decided by Forge
+ Team update (2026-02-23): AccessKey/ToolTip must be added to BaseStyledComponent  decided by Beast, Cyclops

.ai-team/agents/rogue/history.md

@@ -32,3 +32,17 @@
 
 📌 Test pattern: Chart component tests use `BunitContext` directly (not `BlazorWebFormsTestContext`) with `JSInterop.Mode = JSRuntimeMode.Loose` to handle Chart.js interop calls. ChartConfigBuilder is the most testable part — pure static class, no JS/canvas dependency. bUnit 2.x requires `Render<T>` not `RenderComponent<T>`. `GetPaletteColors` is internal, so palette behavior is tested indirectly via BuildConfig dataset colors. — Rogue
 
+📌 Feature Comparison Audit — Validation Controls + Login Controls (2026-02-12): Created 13 audit documents in `planning-docs/` comparing Web Forms API vs Blazor implementation for CompareValidator, CustomValidator, RangeValidator, RegularExpressionValidator, RequiredFieldValidator, ValidationSummary, ChangePassword, CreateUserWizard, Login, LoginName, LoginStatus, LoginView, PasswordRecovery. — Rogue
+
+📌 Validation controls common gaps: (1) `Display` property (None/Static/Dynamic) missing from all validators — affects layout behavior. (2) `SetFocusOnError` missing from all validators. (3) `ControlToValidate` uses `ForwardRef<InputBase<T>>` instead of string ID — different API shape from Web Forms. (4) `InitialValue` missing from RequiredFieldValidator. (5) `ControlToCompare` missing from CompareValidator. (6) `AccessKey` and `ToolTip` missing from all validators. (7) ValidationSummary is missing `HeaderText`, `ShowMessageBox`, `ShowSummary`, `ShowValidationErrors`, and `ValidationGroup` — significant functional gaps. (8) ValidationSummary error message parsing uses fragile comma-split (`x.Split(',')[1]`). — Rogue
+
+📌 Login control template support status: (1) ChangePassword: `ChangePasswordTemplate` and `SuccessTemplate` both supported as RenderFragment. (2) CreateUserWizard: `CreateUserStep`, `CompleteStep`, `SideBarTemplate`, `HeaderTemplate` all supported — but limited to 2 fixed wizard steps (no arbitrary WizardSteps). (3) Login: `LayoutTemplate` NOT supported (commented out in code). (4) LoginView: `AnonymousTemplate`, `LoggedInTemplate`, `RoleGroups` all supported — best template coverage of all login controls. (5) PasswordRecovery: component NOT FOUND in source tree despite Sprint 3 history references — needs investigation. — Rogue
+
+📌 Login controls inherit BaseWebFormsComponent (not BaseStyledComponent): Login, ChangePassword, CreateUserWizard, LoginView all lack outer-level WebControl style properties (BackColor, CssClass, ForeColor, Width, Height, etc.). Only LoginName and LoginStatus inherit BaseStyledComponent and have full style support. Sub-element styles are handled via CascadingParameters for the composite login controls. — Rogue
+
+
+ Team update (2026-02-23): AccessKey/ToolTip must be added to BaseStyledComponent  decided by Beast, Cyclops
+ Team update (2026-02-23): DataBoundComponent style gap  DataBoundStyledComponent<T> recommended  decided by Forge
+ Team update (2026-02-23): DetailsView/PasswordRecovery branch (sprint3) must be merged forward  decided by Forge
+ Team update (2026-02-23): Validation Display property gap confirmed migration-blocking  decided by Rogue
+ Team update (2026-02-23): ValidationSummary comma-split bug confirmed  immediate fix needed  decided by Rogue