docs(ai-team): propagate cross-agent decision updates

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

Author: csharpfritz

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

@@ -49,12 +49,11 @@ Audited 13 controls. Found: AccessKey/ToolTip missing from base class (universal
 📌 Team update (2026-02-23): Milestone 6 Work Plan ratified — 54 WIs across P0/P1/P2 tiers targeting ~345 feature gaps — decided by Forge
 📌 Team update (2026-02-23): UI overhaul requested — ComponentCatalog (UI-2) and search (UI-8) assigned to Cyclops — decided by Jeffrey T. Fritz
 
-### Milestone 8 Release-Readiness Bug Fixes (2026-02-24)
+<!-- ⚠ Summarized 2026-02-25 by Scribe — M8 details condensed -->
 
-- **Menu JS interop crash (Bug 1):** `Menu.js` `Sys.WebForms.Menu` constructor crashes when `getElement()` returns null (e.g., headless Chrome timing). Fixed by adding null guard after `getElement()` (early return if element missing) and wrapping entire constructor body in try/catch to prevent unhandled exceptions from killing the Blazor circuit. File: `src/BlazorWebFormsComponents/wwwroot/Menu/Menu.js`.
-- **Calendar attribute rendering (Bug 2):** `Calendar.razor` line 64 used raw Razor expression injection to conditionally add `scope="col"` to `<th>` tags. This caused `@(UseAccessibleHeader` to appear literally in server logs due to Razor parsing issues. Fixed by replacing with proper conditional attribute: `scope="@(UseAccessibleHeader ? "col" : null)"` -- Blazor omits the attribute entirely when value is null. File: `src/BlazorWebFormsComponents/Calendar.razor`.
-- **Menu auto-ID generation (Bug 3):** Menu JS interop requires a DOM element ID, but when no `ID` parameter is provided, it passes an empty string causing null element lookup. Fixed by adding `OnParametersSet` override in `Menu.razor.cs` that auto-generates `menu_{GetHashCode():x}` when ID is null/empty. File: `src/BlazorWebFormsComponents/Menu.razor.cs`.
-- **Shared PagerSettings sub-component:** Created `PagerSettings` class (plain C# POCO, not a Blazor component) with all 12 Web Forms PagerSettings properties (Mode, PageButtonCount, First/Last/Next/PreviousPageText, image URLs, Position, Visible). Created `PagerPosition` enum in `Enums/` (PagerButtons already existed). Created `IPagerSettingsContainer` interface in `Interfaces/`. Created `UiPagerSettings` abstract base component following the `UiTableItemStyle` CascadingParameter pattern but for settings instead of styles. Created 3 concrete sub-component pairs: `GridViewPagerSettings`, `FormViewPagerSettings`, `DetailsViewPagerSettings` — each inherits `UiPagerSettings` and uses `[CascadingParameter(Name = "ParentXxx")]` to set properties on the parent's `PagerSettings` instance. Wired into GridView, FormView, DetailsView: added `IPagerSettingsContainer` to each control's interface list, added `PagerSettings` property + `PagerSettingsContent` RenderFragment parameter, rendered `@PagerSettingsContent` inside existing `<CascadingValue>` block. Key files: `Enums/PagerPosition.cs`, `PagerSettings.cs`, `Interfaces/IPagerSettingsContainer.cs`, `UiPagerSettings.cs`, `GridViewPagerSettings.razor(.cs)`, `FormViewPagerSettings.razor(.cs)`, `DetailsViewPagerSettings.razor(.cs)`.
+### Summary: Milestone 8 Release-Readiness (2026-02-24)
+
+Fixed 3 bugs: Menu.js null guard + try/catch (Bug 1), Calendar `scope="col"` conditional attribute (Bug 2), Menu auto-ID generation via `OnParametersSet` (Bug 3). Created shared PagerSettings sub-component system: `PagerSettings` POCO (12 properties), `PagerPosition` enum, `IPagerSettingsContainer` interface, `UiPagerSettings` abstract base (CascadingParameter pattern), 3 concrete sub-components for GridView/FormView/DetailsView.
  Team update (2026-02-24): Substitution/Xml formally deferred  no implementation needed  decided by Beast
  Team update (2026-02-24): M8 scope excludes version bump to 1.0 and release  decided by Jeffrey T. Fritz
 

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

@@ -75,23 +75,11 @@ Planned M7: "Control Depth & Navigation Overhaul" — 51 WIs targeting ~138 gap
  Team update (2026-02-24): M8 scope excludes version bump to 1.0 and release  decided by Jeffrey T. Fritz
  Team update (2026-02-24): PagerSettings shared sub-component created for GridView/FormView/DetailsView  decided by Cyclops
 
-### Summary: v0.14 Deployment Pipeline Fixes (2026-02-25)
-
-Fixed three deployment pipeline issues on `fix/deployment-workflows` branch:
-
-- **Docker version computation:** `.dockerignore` excludes `.git`, so nbgv can't run inside the Docker build. Solution: compute version with `nbgv get-version` in the workflow BEFORE Docker build, pass as `ARG VERSION` into the Dockerfile, use `-p:Version=$VERSION -p:InformationalVersion=$VERSION` in both `dotnet build` and `dotnet publish`. This pattern (compute outside, inject via build-arg) is the standard approach when `.git` isn't available inside the build context.
-- **Azure App Service webhook:** Added a `curl -sf -X POST` step gated on `AZURE_WEBAPP_WEBHOOK_URL` secret. Uses `|| echo "::warning::..."` fallback so the workflow doesn't fail if the webhook is unavailable. The webhook URL comes from Azure Portal → App Service → Deployment Center.
-- **nuget.org publishing:** Added a second push step after the existing GitHub Packages push, gated on `NUGET_API_KEY` secret. Both pushes use `--skip-duplicate` for idempotency.
+<!-- ⚠ Summarized 2026-02-25 by Scribe — deployment pipeline details condensed -->
 
-**Key file paths:**
-- `.github/workflows/deploy-server-side.yml` — Docker build + push + Azure webhook
-- `.github/workflows/nuget.yml` — NuGet pack + push (GitHub Packages + nuget.org)
-- `samples/AfterBlazorServerSide/Dockerfile` — server-side demo container
+### Summary: v0.14 Deployment Pipeline Fixes (2026-02-25)
 
-**Patterns established:**
-- Secret-gated workflow steps use `if: ${{ secrets.SECRET_NAME != '' }}` for graceful fallback when secrets aren't configured
-- Docker images are tagged with version number (from nbgv), `latest`, and commit SHA
-- Version is computed once via nbgv and shared via GitHub Actions step outputs (`steps.nbgv.outputs.version`)
+Fixed 3 pipeline issues: Docker version computation (nbgv outside build, inject via ARG), Azure App Service webhook (secret-gated curl), nuget.org dual publishing (secret-gated, --skip-duplicate). Key pattern: secret-gated steps with graceful fallback, Docker tags = version + latest + SHA, version via nbgv step outputs. Files: `.github/workflows/deploy-server-side.yml`, `.github/workflows/nuget.yml`, `samples/AfterBlazorServerSide/Dockerfile`.
 
  Team update (2026-02-25): Deployment pipeline patterns established  compute Docker version with nbgv before build, gate on secrets, dual NuGet publishing  decided by Forge
 
@@ -107,52 +95,21 @@ Planned M9: "Migration Fidelity & Hardening" — 12 work items, ~30 gap closures
  Team update (2026-02-25): Nav audit found 4 missing components + 15 missing SubPages  decided by Jubilee
  Team update (2026-02-25): Test audit found 5 missing smoke tests  decided by Colossus
 
-### Summary: Milestone 12 Planning — Migration Analysis Tool PoC (2026-02-25)
-
-Planned M12: "Migration Analysis Tool (PoC)" — 13 work items. A CLI tool (`bwfc-migrate`) that analyzes existing Web Forms applications and produces migration reports showing control coverage, gaps, code-behind pattern detection, and complexity scoring.
+<!-- ⚠ Summarized 2026-02-25 by Scribe — M12 planning details condensed -->
 
-**Architecture decisions:**
-- Same repo, new project: `src/BlazorWebFormsComponents.MigrationAnalysis/` — mapping table must stay in sync with component library
-- CLI tool via `System.CommandLine`, packaged as `dotnet tool` for easy distribution
-- Regex-based parsing for PoC (not Roslyn) — hard scope boundary to prevent scope creep
-- Control mapping registry derived from `status.md`: 51 supported, 2 deferred, ~15 explicitly unsupported with migration guidance
-- Complexity scoring: Green/Yellow/Red based on control gaps + code-behind pattern density
-- Two output formats: Markdown (human-readable) + JSON (machine-readable)
-- Three-phase roadmap: Phase 1 (M12) = analysis engine + CLI, Phase 2 = Roslyn + scaffolding, Phase 3 = Copilot agent integration
+### Summary: Milestone 12 Planning — Migration Analysis Tool PoC (2026-02-25)
 
-**Key insight:** At 51/53 components, the highest-value work is no longer building components — it's reducing the friction of using the ones we have. A migration analysis tool turns a week of manual evaluation into a 5-second CLI invocation.
+Planned M12: 13 WIs. CLI tool `bwfc-migrate` in `src/BlazorWebFormsComponents.MigrationAnalysis/`. Regex-based ASPX parsing (not Roslyn), control mapping registry from status.md (51 supported + ~15 unsupported), Green/Yellow/Red complexity scoring, Markdown + JSON output. Packaged as `dotnet tool`. Three-phase roadmap: M12 = analysis + CLI, Phase 2 = Roslyn + scaffolding, Phase 3 = Copilot agent.
 
 📌 Team update (2026-02-25): Milestone 12 planned — 13 WIs, "Migration Analysis Tool PoC". CLI tool for Web Forms app analysis with control mapping, gap identification, complexity scoring, and report generation. — decided by Forge
 
  Team update (2026-02-25): Consolidated audit reports now use `planning-docs/AUDIT-REPORT-M{N}.md` pattern for all milestone audits  decided by Beast
 
 ### Summary: Skins & Themes Research and PoC Architecture (2026-02-25)
 
-Deep-dived ASP.NET Web Forms Skins & Themes system (.NET 4.8) and produced two planning documents:
-
-**Key findings:**
-- Web Forms themes use `.skin` files in `App_Themes/{ThemeName}/` folders with control property declarations
-- Default skins (no SkinID) apply automatically; named skins (SkinID="x") are opt-in
-- `Theme` property overrides page declarations; `StyleSheetTheme` acts as defaults that pages can override
-- Skins apply during `PreInit` phase — maps to Blazor `OnInitialized`
-- Only appearance properties are themeable (not behavioral properties like DataSource)
-
-**Existing infrastructure:**
-- `SkinID` (string) and `EnableTheming` (bool) already exist on `BaseWebFormsComponent` but are marked `[Obsolete]`
-- All 51 components inherit these properties
-- Mature styling pipeline: `IStyle`, `WebColor`, `FontInfo`, `Style.cs`, `TableItemStyle`, `HasStyleExtensions`
-- CascadingParameter pattern already used for parent-child style composition in login controls
-- Zero runtime theming infrastructure exists today
-
-**Architecture decision:** Recommended CascadingValue ThemeProvider with C# configuration (Option A). Evaluated 4 options: (A) C# config, (B) .skin file parser, (C) CSS isolation, (D) JSON config. Option C rejected (can't set non-CSS properties). Option A chosen for type safety, IDE support, testability, and no build tooling requirement. Options B and D can layer on top in M11.
-
-**Suitability rating:** Medium — good foundations exist (SkinID, EnableTheming, styling infrastructure) but architectural gap (no ThemeProvider, no theme-reading logic in base classes).
-
-**Issues created:** #364-#368 (M10 PoC, 5 work items) + #369 (M11 planning)
+Researched ASP.NET Web Forms Skins & Themes (.NET 4.8). Key findings: `.skin` files in `App_Themes/`, default vs named skins (SkinID), Theme (override) vs StyleSheetTheme (defaults), skins apply at PreInit → maps to OnInitialized. Existing infrastructure: SkinID (string) + EnableTheming (bool) on BaseWebFormsComponent (marked [Obsolete]), mature styling pipeline (IStyle/WebColor/FontInfo/TableItemStyle), CascadingParameter pattern in login controls. Suitability: Medium.
 
-**Deliverables:**
-- `planning-docs/SKINS-THEMES-COMPATIBILITY-REPORT.md` — full research and compatibility analysis
-- `planning-docs/SKINS-THEMES-POC-PLAN.md` — M10 PoC architecture plan with 5 work items
+Architecture: CascadingValue ThemeProvider with C# config (Option A). Rejected CSS-only (can't set non-CSS properties). Options B (.skin parser) and D (JSON) can layer on in M11. Issues #364-#368 (M10 PoC) + #369 (M11). Deliverables: `planning-docs/SKINS-THEMES-COMPATIBILITY-REPORT.md` and `planning-docs/SKINS-THEMES-POC-PLAN.md`.
 
 📌 Team update (2026-02-25): Skins & Themes PoC architecture decided — CascadingValue ThemeProvider with C# configuration. 5 work items on M10 (#364-#368), M11 planning issue #369. — decided by Forge
 

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

@@ -38,47 +38,17 @@ Wrote 44 bUnit tests for P0 base class changes: AccessKey (4), ToolTip (8), Imag
  Team update (2026-02-23): Label AssociatedControlID switches rendered element (label vs span)  decided by Cyclops
  Team update (2026-02-23): Milestone 6 Work Plan ratified  54 WIs across P0/P1/P2 tiers  decided by Forge
 
-### Milestone 7: GridView Feature Tests — WI-03 + WI-06 + WI-08
+<!-- ⚠ Summarized 2026-02-25 by Scribe — M6 P2 and M7 test details condensed -->
 
-Wrote 24 bUnit tests across 3 new test files for GridView features:
+### Summary: Milestone 7 GridView Feature Tests (2026-02-24)
 
-**Selection.razor (WI-03, 7 tests):** SelectedIndex with SelectedRowStyle CSS, SelectedIndexChanging event with correct index, cancellation prevents selection, AutoGenerateSelectButton renders Select links, SelectedValue returns DataKeyNames key, SelectedIndex=-1 clears selection, SelectedRow returns correct data item. Used `FindComponent<GridView<T>>().Instance` to verify SelectedRow/SelectedValue properties.
+Wrote 24 bUnit tests (3 files): Selection (7 — SelectedIndex, events, AutoGenerateSelectButton, SelectedRow/Value), StyleSubComponents (8 — Row/Alternating/Header/Footer/EmptyData/Pager/Edit styles, priority chain), DisplayProperties (9 — Show/Hide header/footer, Caption, GridLines, CellPadding/Spacing, UseAccessibleHeader).
 
-**StyleSubComponents.razor (WI-06, 8 tests):** RowStyle applies to even-indexed data rows, AlternatingRowStyle applies to odd-indexed rows, HeaderStyle on thead tr, FooterStyle on tfoot tr, EmptyDataRowStyle on empty data, PagerStyle on pager row, EditRowStyle on row at EditIndex, style priority chain (Edit > Selected > Alternating > Row).
+### Summary: Milestone 6 P2 Feature Tests (2026-02-23)
 
-**DisplayProperties.razor (WI-08, 9 tests):** ShowHeader=false hides thead, ShowFooter=true shows tfoot, Caption renders caption element, CaptionAlign renders correct caption-side/text-align style, EmptyDataTemplate overrides EmptyDataText, GridLines renders rules attribute, UseAccessibleHeader renders th scope="col", CellPadding/CellSpacing render table attributes, ShowHeaderWhenEmpty shows header with no data.
+Wrote 41 bUnit tests (6 files): ListView CRUD events (12), DataGrid styles (11) + events (3), Menu LevelStyles (7), Panel BackImageUrl (3), Login Orientation (5).
 
-📌 Test pattern: GridView style sub-components use named RenderFragments (`<RowStyleContent>`, etc.) containing `<GridViewRowStyle BackColor="color" />`. The sub-component configures the GridView's TableItemStyle via CascadingParameter "ParentGridView". Styles render as inline `style` attributes on `<tr>` elements. — Rogue
-
-📌 Test pattern: GridView AlternatingRowStyle is always initialized (non-null `new TableItemStyle()`), so `GetRowStyle()` returns it for odd rows even when not configured. RowStyle only applies to even-indexed rows; to style ALL rows, set both RowStyle and AlternatingRowStyle. — Rogue
-
-📌 Test pattern: GridView with `AutoGenerateColumns="false"` renders in two passes: first pass initializes style sub-components (empty table), second pass renders table after BoundField children register via `AddColumn`. bUnit waits for both renders. — Rogue
-
-### Milestone 6: P2 Feature Tests — ListView CRUD, DataGrid Styles+Events, Menu Level Styles, Panel BackImageUrl, Login Orientation
-
-Wrote 41 bUnit tests across 6 new test files for P2 features:
-
-**CrudEvents.razor (ListView, 12 tests):** HandleCommand routes Edit→sets EditIndex+fires ItemEditing, Cancel→clears EditIndex+fires ItemCanceling, Delete→fires ItemDeleting+ItemDeleted, Insert→fires ItemInserting+ItemInserted, Update→fires ItemUpdating+ItemUpdated. Unknown command→fires ItemCommand. EditIndex=-1 shows ItemTemplate for all. EmptyItemTemplate renders when Items empty. InsertItemTemplate at FirstItem/LastItem positions. ItemEditing cancellation prevents EditIndex change. EditItemTemplate rendering verified via HandleCommand (EditIndex set confirmed; template re-evaluation is a known component gap).
-
-**StyleSubComponents.razor (DataGrid, 11 tests):** DataGridItemStyle on data rows, AlternatingItemStyle on odd rows, HeaderStyle on thead, FooterStyle on tfoot, PagerStyle on pager row, SelectedItemStyle at SelectedIndex, EditItemStyle at EditItemIndex. Caption+CaptionAlign render correctly. GridLines→rules attribute. UseAccessibleHeader→th scope=col. CellPadding+CellSpacing on table.
-
-**Events.razor (DataGrid, 3 tests):** PageIndexChanged fires when pager link clicked, SortCommand fires on sortable header click, SelectedIndex default is -1.
-
-**LevelStyles.razor (Menu, 7 tests):** LevelMenuItemStyles applies per-depth CssClass, Level 1 items get index 0 style, Level 2 items get index 1 style, LevelSelectedStyles applies after click, LevelSubMenuStyles applies background-color to submenu ul, Level styles override static/dynamic styles.
-
-**BackImageUrl.razor (Panel, 3 tests):** BackImageUrl renders as background-image in style, not set→no background-image, URL-encoded characters preserved.
-
-**LoginOrientation.razor (Login, 5 tests):** Default Orientation is Vertical (fields in separate rows), Horizontal puts all fields in one row with 4 tds, TextOnLeft labels align right, TextOnTop labels above inputs with colspan, Horizontal+TextOnTop puts both labels in same row.
-
-📌 Test pattern: ListView HandleCommand must be called via `cut.InvokeAsync()` because it calls StateHasChanged() which requires the Blazor Dispatcher context. Direct `await theListView.HandleCommand()` throws InvalidOperationException. — Rogue
-
-📌 Test pattern: DataGrid style sub-components use named RenderFragments (`<ItemStyleContent>`, `<HeaderStyleContent>`, etc.) containing `<DataGridItemStyle BackColor="color" />`. WebColor values must be declared as variables (`WebColor red = "Red";`) then passed as `BackColor="red"` — not string literals. — Rogue
-
-📌 Test pattern: Menu tests that use `FindAll("a")` must use `FindAll("li a")` to exclude the accessibility skip-link `<a>` rendered before the menu. JSInterop.Mode = JSRuntimeMode.Loose required for all Menu tests. — Rogue
-
-📌 Test pattern: Login control tests require AuthenticationStateProvider + NavigationManager mock services. Use `Orientation ori = Orientation.Horizontal;` variable pattern to avoid Razor enum name collision. Login renders 4 layout combos based on Orientation × TextLayout (Vertical/Horizontal × TextOnLeft/TextOnTop). — Rogue
-
-📌 Test pattern: Menu Orientation tests require JSInterop.Mode = JSRuntimeMode.Loose and @using BlazorWebFormsComponents.Enums. Login control tests require AuthenticationStateProvider and NavigationManager mock services. — Rogue
+📌 Key test patterns (consolidated): GridView styles use named RenderFragments + CascadingParameter "ParentGridView". AlternatingRowStyle always initialized. AutoGenerateColumns=false → two-pass rendering. ListView HandleCommand requires `cut.InvokeAsync()`. DataGrid WebColor values must be variables. Menu tests use `FindAll("li a")` to exclude skip-link. Login tests need AuthenticationStateProvider + NavigationManager mocks + `Orientation ori = Orientation.Horizontal` variable pattern. JSInterop.Mode = JSRuntimeMode.Loose for Menu/Login. — Rogue
 
  Team update (2026-02-24): M8 scope excludes version bump to 1.0 and release  decided by Jeffrey T. Fritz
  Team update (2026-02-24): PagerSettings shared sub-component created  may need bUnit tests  decided by Cyclops