chore(spell-check): allowlist PowerDisplay discovery terms and reword forbidden patterns

Resolves the check-spelling failure on the discovery-pipeline branch:
- expect.txt: add agentic, followups, threadpool, UIDs, yuleng, Zenbook
- verification doc: shorten commit SHA range to 7-char form (drops `fdb` token), move period inside parenthetical, "pre-existing" -> "preexisting"
- plan doc: add "that" to avoid the article-noun-article forbidden pattern

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Yu Leng (from Dev Box)

.github/actions/spell-check/expect.txt

@@ -26,6 +26,7 @@ advfirewall
 AFeature
 affordances
 AFX
+agentic
 agentskills
 AGGREGATABLE
 AHK
@@ -572,6 +573,7 @@ FOF
 FOFX
 FOLDERID
 folderpath
+followups
 FONTTYPE
 FORCEFILESYSTEM
 FORCEMINIMIZE
@@ -1856,6 +1858,7 @@ themeresources
 THH
 thickframe
 THISCOMPONENT
+threadpool
 throughs
 TILEDWINDOW
 TILLSON
@@ -1911,6 +1914,7 @@ ucrtd
 uefi
 uesc
 UIA
+UIDs
 UIEx
 uild
 uitests
@@ -2149,8 +2153,10 @@ xxxxxx
 ycombinator
 yinle
 yinyue
+yuleng
 YVIRTUALSCREEN
 zamora
+Zenbook
 ZEROINIT
 zonability
 zonable

docs/superpowers/plans/2026-05-11-powerdisplay-discovery-pipeline.md

@@ -601,7 +601,7 @@ Switch the orchestrator from three sequential phases to one `Task.WhenAll` over
 
 ## Task 6: Manual verification
 
-The 86 unit tests don't exercise `DiscoverMonitorsAsync` (they cover `DisplayClassifier` only). Functional correctness must be verified by running the app against real hardware. This task has no code steps — it's a checklist the implementer (or a reviewer) runs after the refactor commits land.
+The 86 unit tests don't exercise `DiscoverMonitorsAsync` (they cover `DisplayClassifier` only). Functional correctness must be verified by running the app against real hardware. This task has no code steps — it's a checklist that the implementer (or a reviewer) runs after the refactor commits land.
 
 **Files:** none.
 

docs/superpowers/verification/2026-05-11-powerdisplay-discovery-pipeline-verification.md

@@ -1,7 +1,7 @@
 # PowerDisplay Discovery Pipeline — Manual Verification
 
 **Date**: 2026-05-11
-**Scope**: Verify the per-monitor pipeline refactor of `DdcCiController.DiscoverMonitorsAsync` (commits `e6ec90fdb2..13e34836d9`)
+**Scope**: Verify the per-monitor pipeline refactor of `DdcCiController.DiscoverMonitorsAsync` (commits `e6ec90f..13e3483`)
 **Related**:
 - Spec: [../specs/2026-05-11-powerdisplay-discovery-pipeline-design.md](../specs/2026-05-11-powerdisplay-discovery-pipeline-design.md)
 - Plan: [../plans/2026-05-11-powerdisplay-discovery-pipeline.md](../plans/2026-05-11-powerdisplay-discovery-pipeline.md)
@@ -148,7 +148,7 @@ T2 No blocking sleep: Pass / Fail / Inconclusive
 
 If something fails, the most actionable signals:
 
-1. **Perf is worse than baseline** → confirm Release|x64 build (Debug builds are dramatically slower). Then check log for repeated retries (e.g., `GetPhysicalMonitors attempt 2 retrying`) — if a single hMonitor retries 3× × 200 ms, that's an extra 400 ms per pipeline.
+1. **Perf is worse than baseline** → confirm Release|x64 build; Debug builds are dramatically slower. Then check log for repeated retries (e.g., `GetPhysicalMonitors attempt 2 retrying`) — if a single hMonitor retries 3× × 200 ms, that's an extra 400 ms per pipeline.
 
 2. **Discovery completes but monitor count is wrong** → check log for:
    - `Failed to get GDI device name for hMonitor=0x...`
@@ -158,7 +158,7 @@ If something fails, the most actionable signals:
 
 3. **App crashes / hangs during discovery** → grab a dump. Most likely candidates:
    - Win32 `CapabilitiesRequestAndCapabilitiesReply` hung at firmware level (out of scope, monitor-specific)
-   - Deadlock in `_handleManager.UpdateHandleMap` lock (the lock semantics are unchanged from pre-refactor, so this would be a pre-existing bug surfaced by parallel timing)
+   - Deadlock in `_handleManager.UpdateHandleMap` lock (the lock semantics are unchanged from pre-refactor, so this would be a preexisting bug surfaced by parallel timing)
 
 4. **`OperationCanceledException` shows up in log unexpectedly** → check that the consumer isn't canceling the token early. `MainViewModel.RefreshMonitorsAsync` shouldn't cancel its own request; if it does, that's a separate bug.