docs: migrate doc templates + apps to renamed boolean modifiers (#268) (#342)

Migrates the remaining doc-pipeline templates, doc apps, and compiled
guide pages to the WinUI-aligned boolean modifier names introduced in
#296 / #268:

  .Visible            -> .IsVisible
  .Disabled(x)        -> .IsEnabled(!x)         (inverted)
  .Selectable         -> .IsTextSelectionEnabled
  .ReadOnly           -> .IsReadOnly
  .Editable           -> .IsEditable
  .Closable           -> .IsClosable
  .Active             -> .IsActive
  .DisabledFocusable  -> .IsDisabledFocusable
  .LightDismiss       -> .IsLightDismissEnabled

The original PR migrated first-party code, samples, and a handful of
doc apps. This sweep covers the rest: 8 remaining doc apps, 8
templates, and the 10 compiled guide pages that reference them.
Compiled output regenerated with `mur docs compile` (recipes pages
patched in place to preserve their inlined snippets).

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

Author: codemonkeychris

docs/_pipeline/apps/commanding/App.cs

@@ -199,7 +199,7 @@ public override Element Render()
                     // Inline button — Command<T> doesn't have a Button(cmd, arg) overload
                     // by design, so call .Execute(arg) directly from the click handler.
                     Button(delete.Label, () => delete.Execute?.Invoke(item))
-                        .Disabled(!delete.IsEnabled)))
+                        .IsEnabled(delete.IsEnabled)))
         ).Padding(24);
     }
 }

docs/_pipeline/apps/dialogs-and-flyouts/App.cs

@@ -176,7 +176,7 @@ public override Element Render()
                 () => setOpen(!open)),
             Popup(popupContent, isOpen: open,
                 onClosed: () => setOpen(false))
-                .LightDismiss()
+                .IsLightDismissEnabled()
                 .Offset(120, 0)
         ).Padding(24);
     }

docs/_pipeline/apps/forms/doc-manifest.yaml

@@ -21,7 +21,7 @@ screenshots:
     region: client
     format: png
   - id: keep-submit-reachable
-    description: "Form using .Immediate() on NumberBox and .DisabledFocusable() on Submit so keyboard users can always reach the button"
+    description: "Form using .Immediate() on NumberBox and .IsDisabledFocusable() on Submit so keyboard users can always reach the button"
     component: KeepSubmitReachableDemo
     region: client
     format: png

docs/_pipeline/apps/recipe-login/App.cs

@@ -58,7 +58,7 @@ error is null
                 ? Empty()
                 : TextBlock(error).Foreground("#C42B1C"),
             Button(submitting ? "Signing in…" : "Sign in", () => _ = Submit())
-                .Disabled(!canSubmit)
+                .IsEnabled(canSubmit)
         ).Padding(20).Width(320);
         // </snippet:render>
     }

docs/_pipeline/apps/recipe-multi-step-form/App.cs

@@ -87,9 +87,9 @@ Element StepSummary() => VStack(8,
             Heading("Create your account"),
             body,
             HStack(8,
-                Button("Back", () => setStep(step - 1)).Disabled(step == 0),
+                Button("Back", () => setStep(step - 1)).IsEnabled(step != 0),
                 Button(step == 2 ? "Submit" : "Next",
-                    () => setStep(step + 1)).Disabled(!canAdvance || step == 2)
+                    () => setStep(step + 1)).IsEnabled(canAdvance && step != 2)
             )
         ).Padding(20).Width(380);
         // </snippet:render>

docs/_pipeline/apps/recipe-paginated-list/App.cs

@@ -110,7 +110,7 @@ public override Element Render()
                 : Button(
                     loadingMore ? "Loading more…" : $"Load more ({commits.EstimatedRemaining} remaining)",
                     () => commits.FetchNext()
-                  ).Disabled(loadingMore).Padding(8);
+                  ).IsEnabled(!loadingMore).Padding(8);
 
         return VStack(0,
             Heading($"Commits ({commits.TotalCount ?? loadedItems.Length})").Padding(20),

docs/_pipeline/apps/status-and-info/App.cs

@@ -15,15 +15,15 @@ class InfoBarSeveritiesDemo : Component
     public override Element Render() => VStack(8,
         SubHeading("InfoBar — severity fluents"),
         InfoBar("Saving…", "Your changes are being written.")
-            .Informational().Closable(false),
+            .Informational().IsClosable(false),
         InfoBar("Saved", "Your changes were saved.")
-            .Success().Closable(false),
+            .Success().IsClosable(false),
         InfoBar("Slow connection",
             "Some assets may not load until the network recovers.")
-            .Warning().Closable(false),
+            .Warning().IsClosable(false),
         InfoBar("Save failed",
             "The destination drive is read-only.")
-            .Error().Closable(false)
+            .Error().IsClosable(false)
     ).Padding(24);
 }
 // </snippet:infobar-severities>
@@ -47,7 +47,7 @@ public override Element Render()
                 OnClosed = () => setOpen(false),
                 Severity = Microsoft.UI.Xaml.Controls.InfoBarSeverity.Informational,
             },
-            Button("Show again", () => setOpen(true)).Disabled(open)
+            Button("Show again", () => setOpen(true)).IsEnabled(!open)
         ).Padding(24);
     }
 }
@@ -106,7 +106,7 @@ public override Element Render() => VStack(12,
         // Determinate ring at 60%.
         ProgressRing(0.6).Width(48).Height(48),
         // Indeterminate spinner.
-        ProgressRing().Active().Width(48).Height(48)
+        ProgressRing().IsActive().Width(48).Height(48)
     ).Padding(24);
 }
 // </snippet:progress-ring>

docs/_pipeline/apps/text-and-media/App.cs

@@ -26,7 +26,7 @@ class TextBlockModifiersDemo : Component
 {
     public override Element Render() => VStack(8,
         TextBlock("Bold + sized").Bold().FontSize(18),
-        TextBlock("Selectable so the user can copy.").Selectable(),
+        TextBlock("Selectable so the user can copy.").IsTextSelectionEnabled(),
         TextBlock(
             "A long paragraph that demonstrates wrapping behavior. " +
             "Without TextWrapping, content stays on one line and is " +

docs/_pipeline/templates/accessibility.md.dt

@@ -177,7 +177,7 @@ matches the stale handle and `args.Cancel = true` wedges focus on a
 neighboring page element. Always flip `isActive` to false in the same
 state batch that unmounts the container, or apply the trap to an
 element that stays in the tree across the open/closed transition
-(an always-mounted overlay with `.Visible(open)` rather than
+(an always-mounted overlay with `.IsVisible(open)` rather than
 `When(open, ...)`).
 <!-- /ai:caveat -->
 
@@ -281,7 +281,7 @@ The standard accessible modal combines three primitives: a controlled
 `isOpen` boolean, a `UseFocusTrap` keyed on it, and a
 `UseAnnounce` that announces "Dialog opened" on first render and
 "Dialog closed" on dismiss. The trap container should stay mounted
-across the open/closed transition (use `.Visible(open)` not
+across the open/closed transition (use `.IsVisible(open)` not
 `When(open, ...)`) so focus is released cleanly when `isActive`
 flips false — see the caveat above. The
 [modal-dialog recipe](recipes/modal-dialog.md) wires all three end
@@ -311,17 +311,17 @@ keeps them keyboard- and pointer-interactive.
 
 ## Common Mistakes
 
-### Disabled Submit with no `.DisabledFocusable()`
+### Disabled Submit with no `.IsDisabledFocusable()`
 
 ```csharp
 // Don't:
-Button("Submit", onSubmit).Disabled(!form.IsValid)
+Button("Submit", onSubmit).IsEnabled(form.IsValid)
 ```
 
 A disabled button is removed from the Tab order. The user fixes the
 last field, presses Tab to reach Submit, focus skips past the still-
 disabled button, and they're stranded with no keyboard route. Use
-`.DisabledFocusable(!form.IsValid)` on the button — it keeps the
+`.IsDisabledFocusable(!form.IsValid)` on the button — it keeps the
 button keyboard-focusable while presenting as disabled. The
 [Forms page](forms.md#keeping-submit-reachable) covers the full
 shape (it composes with `.Immediate()` on commit-on-blur inputs).
@@ -338,7 +338,7 @@ Button("Save", onSave)
 focus and pointer hit-testing still work. The result is a button the
 user can Tab to and click but a screen reader user cannot discover.
 If the control should not be exposed to assistive tech, it should
-not exist for keyboard users either; use `.Disabled(true)` or pull it
+not exist for keyboard users either; use `.IsEnabled(false)` or pull it
 from the tree with `When(...)`. Use `.AccessibilityHidden()` only on
 decorative elements that don't accept focus (icons, ornamental
 borders, redundant labels).

docs/_pipeline/templates/cheat-sheet.md.dt

@@ -91,7 +91,7 @@ Full coverage on [Controls](controls.md).
 | Text | `.FontSize(n)` `.Bold()` `.SemiBold()` `.Opacity(n)` |
 | Color | `.Background(token)` `.Foreground(token)` `.WithBorder(token, thickness?)` |
 | Shape | `.CornerRadius(n)` |
-| Behavior | `.Disabled(bool)` `.Visible(bool)` `.ToolTip(s)` |
+| Behavior | `.IsEnabled(bool)` `.IsVisible(bool)` `.ToolTip(s)` |
 | Keying | `.WithKey(s)` |
 | Flex | `.Flex(grow?, shrink?, basis?)` |
 | Themed | `.RequestedTheme(ElementTheme)` `.Backdrop(BackdropKind)` |
@@ -149,7 +149,7 @@ so the reconciler can move rows rather than rebuild them.
 the function-component cache holds it across parent re-renders.
 
 **Disable submit during async work.** A single `submitting` bool
-covers both the button's `.Disabled(...)` and the spinner label.
+covers both the button's `.IsEnabled(...)` and the spinner label.
 
 ## Rules