WEDGE-PROGRESSION: deadline-fire + nt_create_event polarity
Two surgical fixes from 2026-05-28 that take VdSwap from 1 (stuck since
AUDIT-049 on 10 May) to 6 — first real gameplay-direction rendering
progression. Boot now reaches host_ns=208s (was 51s post-2.V, 767ms
pre-2.V).
2.AF (xenia-app/main.rs:2475, +18 LOC):
Per-round drain of Scheduler::timed_waits in coord_pre_round, right
after fire_due_timers. advance_to_next_wake_if_due was only called
from coord_idle_advance (zero-threads-runnable path), so under load
expired wait-deadlines never fired. tid=5's 42.95ms deadline sat
unfired 29s+ in 2.V trace. Post-fix: tid=5 Blocked->Ready, events
13M->45M (3.5x), boot reaches 152s.
2.AI (xenia-kernel/exports.rs:3043, +16 LOC):
Fix manual_reset polarity inversion in nt_create_event:
-let manual_reset = ctx.gpr[5] != 0;
+let manual_reset = ctx.gpr[5] == 0;
Canary reference: xenia-canary xboxkrnl_threading.cc:620
ev->Initialize(!event_type, !!initial_state)
manual_reset = !event_type, so event_type=0 (NotificationEvent) ->
manual, event_type=1 (SynchronizationEvent) -> auto. Our Ke-path
(ensure_dispatcher_object) was already correct; Nt-path was inverted.
Sylpheed's frame-sync Event (event_type=1 + initial_state=1) was
mis-classified manual-reset+signaled, staying signaled forever ->
tid=1 main loop spun at 23kHz (2,798x canary's 60Hz). Post-fix:
tid=1 NtWait calls 3,233,583->51 (63,400x drop), VdSwap 2->6 (3x
rendering progression), boot reaches 208s.
Tests: 300 xenia-cpu / 227 xenia-kernel / 5 xenia-app / 19 xenia-path
+ ~30 smaller - all PASS, 0 regressions. Determinism preserved:
2x cold runs bit-identical at 65,691,821 events.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
acd1656753