fix: wait for Blazor circuit before form interaction in tests

The WebFormsForm Playwright tests were racing against Blazor Server
circuit establishment. During prerendering, the form renders without
@onsubmit:preventDefault, so clicking submit before the circuit is
ready causes a full-page POST that resets component state.

Changes:
- Add data-interactive attribute to WebFormsForm when in interactive mode
- Wait for form[data-interactive] in tests before filling/submitting
- Tighten input locators to match actual field names (username, email)

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

Author: csharpfritz

.squad/agents/cyclops/history.md

@@ -987,3 +987,12 @@ foreach (var warning in warnings) {
 - `@onsubmit:preventDefault` prevents default form submission in interactive mode
 
 **Build:** ✅ 0 errors on net8.0;net9.0;net10.0
+
+### Playwright Locator Fix for WebFormsFormTests (2025-07-15)
+
+**Summary:** Fixed two failing Playwright tests in `WebFormsFormTests.cs` where locators were matching the always-visible migration guidance card instead of the actual results card.
+
+**Key Learning — data-audit-control naming convention:**
+- Demo pages use `data-audit-control` attributes prefixed with the component name, e.g. `webforms-form-results` not just `form-results`.
+- Always use the exact `[data-audit-control='...']` selector in Playwright tests rather than fuzzy text-based locators like `text=Request.Form` or `:has-text()`, which can match unrelated visible sections.
+- When a section is conditionally rendered (e.g., gated by `@if (isPostBack)`), the test locator must target that specific section's attribute, not generic text that may appear elsewhere on the page.

.squad/decisions/inbox/copilot-directive-avoid-security.md

@@ -0,0 +1,4 @@
+### 2026-04-07T14-16-06Z: User directive
+**By:** Jeffrey T. Fritz (via Copilot)
+**What:** Avoid security topics (auth, identity, FormsAuthentication, Membership/Roles) for now - they can get gnarly.
+**Why:** User request - captured for team memory

.squad/decisions/inbox/cyclops-request-form-design.md

@@ -0,0 +1,26 @@
+# Decision: FormShim wraps IFormCollection with null-safe degradation
+
+**Author:** Cyclops  
+**Date:** 2026-07-31  
+**Status:** Implemented  
+
+## Context
+
+Migrated Web Forms code-behind frequently uses `Request.Form["fieldName"]` to read POST data. The existing `RequestShim` had `Cookies`, `QueryString`, and `Url` but no `Form`.
+
+## Decision
+
+Created `FormShim` as a public class (not an interface implementation) that wraps `IFormCollection?` and provides `NameValueCollection`-like API. The `RequestShim.Form` property follows the same graceful degradation pattern as `Cookies`:
+
+1. **SSR mode (HttpContext available):** wraps `HttpContext.Request.Form` via `FormShim`
+2. **Non-form-encoded requests:** catches `InvalidOperationException` → returns empty `FormShim(null)`
+3. **Interactive mode (no HttpContext):** logs warning once → returns empty `FormShim(null)`
+
+## Why not implement IFormCollection?
+
+`FormShim` targets `NameValueCollection` semantics (Web Forms API), not `IFormCollection` (ASP.NET Core API). The indexer, `GetValues()`, `AllKeys` surface matches what migrated code actually calls. Implementing `IFormCollection` would add unnecessary API surface and file upload concerns.
+
+## Impact
+
+- Unblocks any migrated code-behind that reads `Request.Form["key"]`
+- No breaking changes — new property on existing class

.squad/decisions/inbox/cyclops-ssr-optout-pattern.md

@@ -0,0 +1,19 @@
+# Decision: SSR Opt-Out Pattern via ExcludeFromInteractiveRouting
+
+**Author:** Cyclops  
+**Date:** 2025-07-24  
+**Status:** Implemented  
+
+## Context
+
+The sample app uses `@rendermode="InteractiveServer"` on `<Routes>` in `App.razor`, meaning all pages run interactively via SignalR. Pages that need real HTTP POST (like the Request.Form demo) can't function because there's no form data in interactive mode.
+
+## Decision
+
+Modified `App.razor` to use `HttpContext.AcceptsInteractiveRouting()` for conditional render mode assignment. Pages that need SSR add `@attribute [ExcludeFromInteractiveRouting]` — the standard Microsoft pattern for .NET 8+.
+
+**Impact:** This is non-breaking. All existing pages continue as InteractiveServer. Only pages explicitly decorated with the attribute will render as SSR.
+
+## Applies To
+
+Any future sample page or migration demo that needs real HTTP request/response semantics (form POSTs, Request.Form, Request.Cookies during POST, etc.) should use this same attribute.

samples/AfterBlazorServerSide.Tests/Migration/WebFormsFormTests.cs

@@ -77,10 +77,10 @@ public async Task WebFormsForm_InitialLoad_ShowsFormWithoutResults()
             });
 
             // Form inputs should be visible (name and email)
-            var nameInput = page.Locator("input[name='name'], input#name, input[id*='name' i]").First;
+            var nameInput = page.Locator("input[name='username'], input#username").First;
             await Assertions.Expect(nameInput).ToBeVisibleAsync();
 
-            var emailInput = page.Locator("input[name='email'], input#email, input[id*='email' i]").First;
+            var emailInput = page.Locator("input[name='email'], input#email").First;
             await Assertions.Expect(emailInput).ToBeVisibleAsync();
 
             // Submit button should be visible
@@ -115,13 +115,19 @@ public async Task WebFormsForm_SubmitForm_ShowsRequestFormValues()
                 Timeout = 30000
             });
 
+            // Wait for Blazor Server interactive circuit — the WebFormsForm component
+            // renders data-interactive="true" only after the circuit is established.
+            // Without this wait, the prerendered form lacks @onsubmit:preventDefault
+            // and clicking submit causes a full-page POST that resets component state.
+            await page.WaitForSelectorAsync("form[data-interactive]", new() { Timeout = 10000 });
+
             // Fill in the name field
-            var nameInput = page.Locator("input[name='name'], input#name, input[id*='name' i]").First;
+            var nameInput = page.Locator("input[name='username'], input#username").First;
             await nameInput.FillAsync("TestUser");
             await page.Keyboard.PressAsync("Tab");
 
             // Fill in the email field
-            var emailInput = page.Locator("input[name='email'], input#email, input[id*='email' i]").First;
+            var emailInput = page.Locator("input[name='email'], input#email").First;
             await emailInput.FillAsync("test@example.com");
             await page.Keyboard.PressAsync("Tab");
 
@@ -167,8 +173,11 @@ public async Task WebFormsForm_SubmitForm_StaysOnSamePage()
                 Timeout = 30000
             });
 
+            // Wait for Blazor Server interactive circuit
+            await page.WaitForSelectorAsync("form[data-interactive]", new() { Timeout = 10000 });
+
             // Fill a field and submit
-            var nameInput = page.Locator("input[name='name'], input#name, input[id*='name' i]").First;
+            var nameInput = page.Locator("input[name='username'], input#username").First;
             await nameInput.FillAsync("NavigationTest");
             await page.Keyboard.PressAsync("Tab");
 

src/BlazorWebFormsComponents/WebFormsForm.razor

@@ -11,6 +11,7 @@
     <form @ref="_formRef"
           method="@MethodString"
           action="@Action"
+          data-interactive="true"
           @onsubmit="HandleSubmit"
           @onsubmit:preventDefault
           @attributes="HtmlAttributes">