Feature/cli migration improvements (FritzAndFriends#543)

* feat(cli): target .NET 10 Blazor SSR scaffolds

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

* Add WingtipToys benchmark run 27

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

* Fix master-page migration test failures

- TC23/TC28 expected: lowercase ContentPlaceHolder id= (AttributeStripTransform converts IDid at order 700)
- TC30/TC32 expected: add <Site>/<Content> wrapper from ContentWrapperTransform

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

* fix(Content): override Dispose(bool) to clear slot on removal from render tree

When a Content component is removed from the render tree (e.g. behind an
@if toggle), Blazor calls DisposeAsync() which routes through the base
class BaseWebFormsComponent.Dispose(bool disposing). The previous attempt
added IDisposable.Dispose() which is never called when IAsyncDisposable is
already implemented on the base class.

By overriding the protected virtual Dispose(bool) hook, the component now
calls MasterPageContext.SetContent(ContentPlaceHolderID, null) at disposal,
which triggers the subscribed ContentPlaceHolder to re-render showing its
default ChildContent.

Fixes: ContentPlaceHolder_ToggleOverride_SwitchesBetweenDefaultAndOverride

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

* fix: use NetworkIdle for ContentPlaceHolder_ToggleOverride Playwright test

WaitUntilState.DOMContentLoaded does not wait for the Blazor Server
circuit to establish, so the toggle button click could fire before
the @OnClick handler was registered. Aligns with the NetworkIdle
pattern used by every other interactive test in the file.

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

* docs(ai-team): Master page migration batch logging

Session: 2026-04-27-master-page-migration
Requested by: Jeffrey T. Fritz

Changes:
- Logged 2026-04-27 master-page-migration session
- Appended learnings to Forge, Cyclops, Bishop, Beast, Jubilee, Rogue, Colossus history files
- No product code modified

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

* Complete WingtipToys run28 benchmark and analysis

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

* .squad: Scribe archival and session log consolidation

- Archived decisions.md entries older than 2026-04-21 (201 blocks, 524KB  41KB)
- Merged 11 inbox decision files into decisions.md
- Added team update for semantic pattern infrastructure sprint to bishop, cyclops, forge, rogue history
- Summarized history.md files >= 15KB by archiving old entries:
  * bishop: 23.92 KB  5.56 KB
  * cyclops: 19.41 KB → 1.88 KB
  * forge: 29.42 KB  1.4 KB
  * rogue: 19.52 KB  3.14 KB
- Created orchestration logs for Bishop, Cyclops, Forge, Rogue, Coordinator
- Created session log for semantic-pattern-catalog work
- All history files now under 15KB threshold

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

* .squad: Scribe archival and session log consolidation

- Archive .squad/decisions.md to decisions-archive.md
- Reorganize team agent histories
- Consolidate multi-agent session logs
- Restructure skill catalogs

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

* feat(cli): complete semantic pattern infrastructure and WingtipToys acceptance tests

- Implement pattern infrastructure for query, action, and account pages
- Wire production and test registration for all semantic patterns
- Add focused concrete and integration tests for pattern workflows
- Update WingtipToys sample pages with latest Blazor patterns
- Add WingtipToysPlaywrightFixture for acceptance test automation
- Resolve merge conflicts and rebase onto upstream/dev

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

* feat(acceptance-tests): Add WingtipToys acceptance test suite

Complete the WingtipToys migration acceptance test coverage for the CLI migration improvements feature.

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

---------

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

Author: csharpfritz

.squad/casting-history.json .ai-team/casting-history.json.squad/casting-history.json renamed to .ai-team/casting-history.json

@@ -14,7 +14,8 @@
     "Breaking Bad",
     "Lost",
     "Marvel Cinematic Universe",
-    "DC Universe"
+    "DC Universe",
+    "Futurama"
   ],
   "universe_capacity": {
     "The Usual Suspects": 6,
@@ -30,6 +31,7 @@
     "Breaking Bad": 12,
     "Lost": 18,
     "Marvel Cinematic Universe": 25,
-    "DC Universe": 18
+    "DC Universe": 18,
+    "Futurama": 12
   }
 }

.squad/casting-policy.json .ai-team/casting-policy.json.squad/casting-policy.json renamed to .ai-team/casting-policy.json

@@ -0,0 +1,53 @@
+# {Name} — {Role}
+
+> {One-line personality statement — what makes this person tick}
+
+## Identity
+
+- **Name:** {Name}
+- **Role:** {Role title}
+- **Expertise:** {2-3 specific skills relevant to the project}
+- **Style:** {How they communicate — direct? thorough? opinionated?}
+
+## What I Own
+
+- {Area of responsibility 1}
+- {Area of responsibility 2}
+- {Area of responsibility 3}
+
+## How I Work
+
+- {Key approach or principle 1}
+- {Key approach or principle 2}
+- {Pattern or convention I follow}
+
+## Boundaries
+
+**I handle:** {types of work this agent does}
+
+**I don't handle:** {types of work that belong to other team members}
+
+**When I'm unsure:** I say so and suggest who might know.
+
+**If I review others' work:** On rejection, I may require a different agent to revise (not the original author) or request a new specialist be spawned. The Coordinator enforces this.
+
+## Model
+
+- **Preferred:** auto
+- **Rationale:** Coordinator selects the best model based on task type — cost first unless writing code
+- **Fallback:** Standard chain — the coordinator handles fallback automatically
+
+## Collaboration
+
+Before starting work, run `git rev-parse --show-toplevel` to find the repo root, or use the `TEAM ROOT` provided in the spawn prompt. All `.squad/` paths must be resolved relative to this root — do not assume CWD is the repo root (you may be in a worktree or subdirectory).
+
+Before starting work, read `.squad/decisions.md` for team decisions that affect me.
+After making a decision others should know, write it to `.squad/decisions/inbox/{my-name}-{brief-slug}.md` — the Scribe will merge it.
+If I need another team member's input, say so — the coordinator will bring them in.
+
+## Voice
+
+{1-2 sentences describing personality. Not generic — specific. This agent has OPINIONS.
+They have preferences. They push back. They have a style that's distinctly theirs.
+Example: "Opinionated about test coverage. Will push back if tests are skipped.
+Prefers integration tests over mocks. Thinks 80% coverage is the floor, not the ceiling."}

.squad/casting-registry.json .ai-team/casting-registry.json.squad/casting-registry.json renamed to .ai-team/casting-registry.json

@@ -0,0 +1,38 @@
+# Constraint Budget Tracking
+
+When the user or system imposes constraints (question limits, revision limits, time budgets), maintain a visible counter in your responses and in the artifact.
+
+## Format
+
+```
+📊 Clarifying questions used: 2 / 3
+```
+
+## Rules
+
+- Update the counter each time the constraint is consumed
+- When a constraint is exhausted, state it: `📊 Question budget exhausted (3/3). Proceeding with current information.`
+- If no constraints are active, do not display counters
+- Include the final constraint status in multi-agent artifacts
+
+## Example Session
+
+```
+Coordinator: Spawning agents to analyze requirements...
+📊 Clarifying questions used: 0 / 3
+
+Agent asks clarification: "Should we support OAuth?"
+Coordinator: Checking with user...
+📊 Clarifying questions used: 1 / 3
+
+Agent asks clarification: "What's the rate limit?"
+Coordinator: Checking with user...
+📊 Clarifying questions used: 2 / 3
+
+Agent asks clarification: "Do we need RBAC?"
+Coordinator: Checking with user...
+📊 Clarifying questions used: 3 / 3
+
+Agent asks clarification: "Should we cache responses?"
+Coordinator: 📊 Question budget exhausted (3/3). Proceeding without clarification.
+```

.ai-team/charter.md

@@ -0,0 +1,46 @@
+# Copilot Coding Agent — Squad Instructions
+
+You are working on a project that uses **Squad**, an AI team framework. When picking up issues autonomously, follow these guidelines.
+
+## Team Context
+
+Before starting work on any issue:
+
+1. Read `.squad/team.md` for the team roster, member roles, and your capability profile.
+2. Read `.squad/routing.md` for work routing rules.
+3. If the issue has a `squad:{member}` label, read that member's charter at `.squad/agents/{member}/charter.md` to understand their domain expertise and coding style — work in their voice.
+
+## Capability Self-Check
+
+Before starting work, check your capability profile in `.squad/team.md` under the **Coding Agent → Capabilities** section.
+
+- **🟢 Good fit** — proceed autonomously.
+- **🟡 Needs review** — proceed, but note in the PR description that a squad member should review.
+- **🔴 Not suitable** — do NOT start work. Instead, comment on the issue:
+  ```
+  🤖 This issue doesn't match my capability profile (reason: {why}). Suggesting reassignment to a squad member.
+  ```
+
+## Branch Naming
+
+Use the squad branch convention:
+```
+squad/{issue-number}-{kebab-case-slug}
+```
+Example: `squad/42-fix-login-validation`
+
+## PR Guidelines
+
+When opening a PR:
+- Reference the issue: `Closes #{issue-number}`
+- If the issue had a `squad:{member}` label, mention the member: `Working as {member} ({role})`
+- If this is a 🟡 needs-review task, add to the PR description: `⚠️ This task was flagged as "needs review" — please have a squad member review before merging.`
+- Follow any project conventions in `.squad/decisions.md`
+
+## Decisions
+
+If you make a decision that affects other team members, write it to:
+```
+.squad/decisions/inbox/copilot-{brief-slug}.md
+```
+The Scribe will merge it into the shared decisions file.

.ai-team/constraint-tracking.md

@@ -0,0 +1,166 @@
+### MasterPage Migration Bridge — Implementation Contract
+
+**Date:** 2026-04-27
+**By:** Forge (Lead Architect)
+**Requested by:** Jeffrey T. Fritz
+**Status:** PROPOSED
+
+---
+
+## Problem Statement
+
+Run 27 confirms the #1 toolkit gap: master-page conversion does not produce a usable Blazor layout. The generated `Site.razor` retains bundling tags and unconverted `<% %>` markup, requiring 14+ minutes of manual Layer 2 repair focused primarily on layout rewriting. The BWFC library has `MasterPage`, `Content`, and `ContentPlaceHolder` components, but neither the C# CLI migrator nor the PowerShell toolkit emits markup that uses them. The components themselves have a structural gap: `Content` registers with `MasterPage` via `CascadingParameter`, but `MasterPage` never cascades itself (no `<CascadingValue>` wrapping `ChildContent` in the .razor file). This means the Content→ContentPlaceHolder slot-filling mechanism is non-functional at runtime.
+
+---
+
+## Contract: 5 Work Areas
+
+### 1. Component Library (`src/BlazorWebFormsComponents/`)
+
+**1a. Fix MasterPage cascading (P0 — blocking):**
+- `MasterPage.razor` must wrap `@ChildContent` in `<CascadingValue Value="this">` so that `Content` and `ContentPlaceHolder` children receive the `[CascadingParameter] MasterPage` they expect.
+- Current `.razor` file does NOT cascade `this`; the `Content.razor.cs` `ParentMasterPage` is always `null`.
+
+**1b. MasterPage behavior contract:**
+- Renders NO wrapper element (matches Web Forms MasterPage behavior — no `<div>` or `<section>`)
+- `Head` RenderFragment → `<HeadContent>` (already implemented, keep)
+- `ChildContent` RenderFragment → rendered directly (already implemented, keep)
+- `Visible` parameter controls rendering (already implemented, keep)
+- `Title` / `MasterPageFile` remain `[Obsolete]` with guidance (already implemented, keep)
+- `EmptyLayout` is used via `@layout` to prevent layout recursion (already implemented, keep)
+
+**1c. ContentPlaceHolder behavior contract:**
+- Renders content from matching `Content` component if present; otherwise renders `ChildContent` (default content). Already coded in `.razor` — works once cascading is fixed.
+- Requires `ID` parameter to match with `Content.ContentPlaceHolderID`.
+- No wrapper element.
+
+**1d. Content behavior contract:**
+- Registers its `ChildContent` with the parent `MasterPage.ContentSections[ContentPlaceHolderID]`.
+- Renders nothing itself (already implemented — `.razor` is empty).
+- Requires `ContentPlaceHolderID` parameter.
+
+**1e. NOT in scope:**
+- Nested master pages (Web Forms `MasterPageFile` nesting). Document as unsupported; use nested Blazor layouts.
+- Runtime dynamic master-page switching. Out of scope.
+- `FindControl()` API on master pages. Not applicable in Blazor.
+
+### 2. C# CLI Migrator (`src/BlazorWebFormsComponents.Cli/`)
+
+**2a. MasterPageTransform — change output target (P0):**
+- Current: Replaces ALL `<asp:ContentPlaceHolder>` with `@Body` and prepends `@inherits LayoutComponentBase`.
+- New behavior for `.master` files: Emit a BWFC bridge layout instead of a raw Blazor layout.
+  - Prepend `@inherits LayoutComponentBase` (keep).
+  - Replace the PRIMARY ContentPlaceHolder (ID matching `MainContent|ContentPlaceHolder1|BodyContent`) with `@Body`.
+  - Replace OTHER ContentPlaceHolders with `<ContentPlaceHolder ID="OriginalID">` (preserving default content between tags).
+  - Strip `runat="server"` from `<head>` and `<form>` (keep existing behavior).
+  - Extract `<head>` content into `<HeadContent>` block (align with PS toolkit behavior).
+  - Add a TODO comment for head content review (keep).
+
+**2b. ContentWrapperTransform — preserve relationships (P1):**
+- Current: Strips ALL `<asp:Content>` wrappers, losing the `ContentPlaceHolderID` binding.
+- New behavior for `.aspx` child pages:
+  - Content targeting the PRIMARY ContentPlaceHolder (MainContent/ContentPlaceHolder1/BodyContent) → strip wrapper, keep inner content (current behavior, correct).
+  - Content targeting `HeadContent`/`head`/`TitleContent` → convert to `<HeadContent>...</HeadContent>`.
+  - Content targeting OTHER ContentPlaceHolderIDs → convert to `<Content ContentPlaceHolderID="OriginalID">...</Content>` (BWFC component, preserving the relationship).
+- This requires `ContentWrapperTransform` to be aware of which ContentPlaceHolder IDs exist. Options:
+  - **Option A (recommended):** Maintain a static list of "primary" IDs (`MainContent`, `ContentPlaceHolder1`, `BodyContent`) and "head" IDs (`HeadContent`, `head`, `TitleContent`). Anything else → preserve as `<Content>`.
+  - **Option B:** Parse the `.master` file first to extract ContentPlaceHolder IDs and pass them through pipeline context. More accurate, more complex.
+  - **Decision:** Start with Option A. It handles >95% of real-world cases. Option B can be added later if edge cases arise.
+
+**2c. New: Add CLI tests for master page transforms (P1):**
+- Test `.master` → layout with primary CPH → `@Body` + secondary CPH → `<ContentPlaceHolder>`.
+- Test `.aspx` with multiple Content blocks → primary stripped, head converted, others preserved.
+- Test self-closing ContentPlaceHolder variants.
+
+### 3. PowerShell Migration Toolkit (`migration-toolkit/scripts/bwfc-migrate.ps1`)
+
+**3a. ConvertFrom-MasterPage — align with CLI path (P1):**
+- Current behavior at lines 1536-1562 is mostly correct:
+  - Primary CPH IDs → `@Body` ✓
+  - Other CPH IDs → TODO comment with BWFC hint ✓
+- **Change:** Replace TODO comments for secondary ContentPlaceHolders with actual `<ContentPlaceHolder ID="...">` components instead of comment-only output.
+- Replace: `@* TODO: ContentPlaceHolder 'X' — BWFC provides... *@`
+- With: `<ContentPlaceHolder ID="X">` (preserving default content between the original tags) `</ContentPlaceHolder>`
+- Keep the `Write-ManualItem` hint for developer awareness.
+
+**3b. ConvertFrom-ContentWrappers (child pages) — align with CLI (P1):**
+- Lines 1338-1360 handle content extraction. Apply same logic as CLI:
+  - Primary CPH → strip wrapper (current behavior ✓)
+  - Head/Title CPH → convert to `<HeadContent>` (current behavior ✓)
+  - Other CPH → convert to `<Content ContentPlaceHolderID="X">` instead of stripping
+
+**3c. Validation:**
+- The `Test-BwfcControlPreservation` function should recognize `<ContentPlaceHolder>` and `<Content>` as valid BWFC components (add to the known-component list if not already present).
+
+### 4. Tests and Samples
+
+**4a. Fix existing tests (P0):**
+- The 5 existing test files in `src/BlazorWebFormsComponents.Test/MasterPage/` should continue passing after the cascading fix. They test MasterPage + ContentPlaceHolder rendering but do NOT test Content→ContentPlaceHolder slot filling (because it was broken). Verify no regressions.
+
+**4b. Add Content slot-filling tests (P0):**
+- `Content/SlotFilling.razor` — Test that `<Content ContentPlaceHolderID="X">` inside a `<MasterPage>` replaces the default content of `<ContentPlaceHolder ID="X">`.
+- `Content/MultipleSlots.razor` — Test multiple Content blocks targeting different ContentPlaceHolders.
+- `Content/UnmatchedContent.razor` — Test Content with a ContentPlaceHolderID that doesn't match any ContentPlaceHolder (should be silently ignored, not crash).
+- `Content/MixedDefaultAndOverride.razor` — Test one CPH with Content override, another with default content.
+
+**4c. Update sample page (P1):**
+- `samples/AfterBlazorServerSide/Components/Pages/ControlSamples/MasterPage/Index.razor` — Add a live demo section that actually renders the `<MasterPage>` + `<ContentPlaceHolder>` + `<Content>` components, not just static code snippets.
+
+**4d. CLI transform tests (P1):**
+- Add xUnit tests for `MasterPageTransform` and `ContentWrapperTransform` in the CLI test project.
+
+### 5. Documentation
+
+**5a. Update `docs/Migration/MasterPages.md` (P1):**
+- Add a "Bridge Components" section explaining the two-phase approach:
+  1. Phase 1 (automated): Toolkit converts `.master` to layout with BWFC `<ContentPlaceHolder>` bridge, converts child `.aspx` to pages with BWFC `<Content>` bridge.
+  2. Phase 2 (manual): Developer replaces BWFC bridge components with native Blazor patterns (`@Body`, `@section`).
+- Document the `Head` parameter behavior.
+- Document limitations (nested masters not supported).
+
+**5b. Update component doc if separate from migration doc (P1).**
+
+---
+
+## Edge Cases and Acceptable Limitations
+
+| Edge Case | Handling | Status |
+|-----------|----------|--------|
+| Nested master pages (`MasterPageFile` in a master) | Not supported. Document: use nested `@layout` directives. | Acceptable limitation |
+| Multiple ContentPlaceHolders with same ID | Last-write-wins in `ContentSections` dictionary. Document as undefined behavior. | Acceptable limitation |
+| Content without parent MasterPage | `ParentMasterPage` is null; Content renders nothing. No crash. | Already handled |
+| ContentPlaceHolder without parent MasterPage | Renders default `ChildContent`. No crash. | Already handled |
+| Dynamic master page switching at runtime | Not supported. Not a real migration scenario. | Acceptable limitation |
+| `<head runat="server">` containing `<asp:ContentPlaceHolder ID="HeadContent">` | CLI/PS both extract head metadata into `<HeadContent>` and replace HeadContent CPH. Well-handled. | Already handled |
+| Master page with NO primary CPH (only secondary CPHs) | No `@Body` emitted. Layout compiles but renders nothing in Body slot. Add a TODO warning. | P2 enhancement |
+| Very large master pages with inline code blocks (`<% %>`) | CLI/PS already flag these as TODO. Not auto-converted. | Acceptable limitation |
+
+---
+
+## Priority Summary
+
+| Priority | Item | Owner Suggestion |
+|----------|------|-----------------|
+| P0 | Fix MasterPage cascading (`<CascadingValue>`) | Component dev (Cyclops) |
+| P0 | Content slot-filling tests | Test dev (Rogue) |
+| P0 | Verify existing 5 MasterPage tests still pass | Test dev (Rogue) |
+| P1 | CLI MasterPageTransform: secondary CPH → `<ContentPlaceHolder>` | CLI dev (Bishop) |
+| P1 | CLI ContentWrapperTransform: secondary Content → `<Content>` | CLI dev (Bishop) |
+| P1 | CLI transform tests | CLI dev (Bishop) |
+| P1 | PS ConvertFrom-MasterPage: secondary CPH → `<ContentPlaceHolder>` | Toolkit dev (Bishop) |
+| P1 | PS content wrapper: secondary Content → `<Content>` | Toolkit dev (Bishop) |
+| P1 | Update docs/Migration/MasterPages.md | Doc dev (Beast) |
+| P1 | Update sample page with live demo | Sample dev (Jubilee) |
+| P2 | Warn when no primary CPH found | CLI/PS dev |
+
+---
+
+## Verification Criteria
+
+1. `dotnet build` succeeds with zero new warnings in BWFC library.
+2. All existing MasterPage tests pass (5 files, ~15 tests).
+3. New Content slot-filling tests pass (4+ new test files).
+4. CLI transforms produce correct output for `.master` with mixed primary/secondary CPHs.
+5. PS toolkit produces matching output structure.
+6. Next WingtipToys benchmark run (Run 28+) shows reduced Layer 2 repair time for layout.
+7. Sample page renders the bridge components live, not just as code snippets.