test(web): cover slot-actions and progress-block logic

[selfcontained]

Summary

Routine test-enforcer maintenance run. Local suite was already green (42nd+ consecutive) with no failures, no flakes, and no unrelated CI issues — so this run added coverage per the carried-forward next_focus (agent-surfaces block components).

Changes

• slot-actions.test.tsx (13 tests): SlotActions' main-action selection algorithm (primary promotion, non-destructive fallback, order-independence of authored position), the menu-needed threshold logic (including the some-vs-every empty-array edge case), the confirm-dialog open/cancel/confirm wiring and payload (blockId/actionId/baseRevision), readOnly/durable-interaction locking, and authored-disabled aria-disabled wiring.
• progress-block.test.tsx (10 tests): ProgressBlockView's percent calculation, value/max clamping (both directions), the non-positive-max divide-by-zero guard, round-vs-floor rounding, label/title precedence for the heading vs. the progress line, the three-way ARIA-label fallback chain, tone-driven fill class, and detail-markdown gating.

Both files were built against pre-existing, unmodified source (slot-actions.tsx, progress-block.tsx) — no product code changed.

Verification

• Manual mutation battery: 24 behavior-changing mutations across both source files, all reverted after confirming a test failure. 1 mutant (handleClick's own action.disabled || readOnly guard) is confirmed unobservable — already fully covered by ActionRefButton's own click-blocking when disabled/authored-disabled, verified against the whole 217-test agent-surfaces suite. Recorded as a code-cleanup note in the test-enforcer backlog, not treated as a test gap.
• One general-purpose review agent reviewed the diff; it found 2 real pnpm run check type errors (an invalid tone: "danger" value for ProgressBlock, which deliberately excludes danger; and a string[] return type that should have tolerated null from getAttribute) and 2 duplicate tests with no unique mutation-kill value. All four fixed; mutation kill for the affected assertion re-verified after the fix.
• pnpm run check, pnpm run format, pnpm run test (server 186f/3279t, web 130f/1911t, ext 9f/60t), pnpm run finalize:web, pnpm run test:e2e (198 passed/12 skipped), and pnpm run test:e2e:live (11/11, zero leaked tmux sessions) all green.
• CI scan of the last 50 runs found no cross-branch flakes — all failures were confined to one other in-flight WIP branch's own issues (unrelated to this change).

Deliberately not tested: Radix DropdownMenu's open-menu contents (item ordering, destructive separator, busy spinner in the trigger) — no precedent exists elsewhere in this repo's apps/web suite for opening a Radix dropdown in jsdom (likely missing PointerEvent/hasPointerCapture polyfills), so this is an intentionally-deferred gap, not an oversight.

🤖 Generated with Claude Code