********************** Windows PowerShell transcript start Start time: 20260923091912 Username: DESKTOP-DJ40RL2\Administrator RunAs User: DESKTOP-DJ40RL2\Administrator Configuration Name: Machine: DESKTOP-DJ40RL2 (Microsoft Windows NT 10.0.28000.0) Host Application: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -File tests/test_rc2_supplemental_c.ps1 Process ID: 14796 PSVersion: 5.1.28000.2704 PSEdition: Desktop PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.28000.2704 BuildVersion: 10.0.28000.2704 CLRVersion: 4.0.30319.42000 WSManStackVersion: 3.0 PSRemotingProtocolVersion: 2.3 SerializationVersion: 1.1.0.1 ********************** ========================================================================== ClassNotify P1 RC2 — Gate RC-2: Supplemental Verification Suite C Target RCArtifactId: P1-RC2-20260922-151442-F2C14966 Evidence ID: EVIDENCE-RC2-SUPPLEMENTAL-C-20260923-091912 ========================================================================== >>> [Pre-Flight] System & Environment Verification... [PASS] Pre-Flight 1: Local ClassNotifySetup.exe SHA256 matches baseline F2C14966E99B47A5A67436F7E4E1FB72A363FCB560BF19C07BDF23DEA5BDADD9 [PASS] Pre-Flight 2: ClassNotifyService is RUNNING in Session 0 PID: 41472 [PASS] Pre-Flight 3: ClassNotify.Client is running in user session PID: 39140, Session: 4 [PASS] Pre-Flight 4: Session 4 is interactive Active console State: Active console [PASS] Pre-Flight 5: Device bound to cls_802 in t_beijing_no4 DeviceId: dev_59e35e79 [PASS] Pre-Flight 6: Teacher & Admin authentication succeeded >>> [Criterion 1/2] Client Downtime & Strict FIFO Reception Order (01 -> 02 -> 03)... Original Client.exe SHA256: DCC1B4B7FC639B97A42F6375F31433B678E29436985117AA33D8FC8A2A5C174F [Unavailable Check 1/3] ClientCount: 0, ServiceRunning: True, DeviceOnline: True [Unavailable Check 2/3] ClientCount: 0, ServiceRunning: True, DeviceOnline: True [Unavailable Check 3/3] ClientCount: 0, ServiceRunning: True, DeviceOnline: True Client 100% Unavailable Verification: True Buffered 3 FIFO messages during client downtime: f1=msg_1790126362992_5f50, f2=msg_1790126363487_428e, f3=msg_1790126363976_5ee7 Client executable restored, SHA256 Integrity: True Client restored by watchdog: PID 37408 in Session 4 Client Reception Order in Logs: f1_idx=433, f2_idx=439, f3_idx=441 (Strict: True) [PASS] Criterion 1: Client Downtime & Strict FIFO Reception Order (01 -> 02 -> 03) UnavailableDuringSends: True, HashVerified: True, LogOrder: 01 (line 433) -> 02 (line 439) -> 03 (line 441), DB Verified: True >>> [Criterion 2/2] Same CommandId Replay via Natural Dispatched Race & Catch-up... [Attempt 1/5] Ensuring device online and client running... Device Online: True, Client PID Before (A): 37408 Candidate: cmd_917e36b4441e4fda9a6ae1d7358c2f1f, PID Transition: 37408 -> 40252, Server Status: Dispatched PERFECT! Captured natural race window: Command cmd_917e36b4441e4fda9a6ae1d7358c2f1f executed locally, Server locked in Dispatched! Triggering Reconnect to prompt DeviceHub catch-up of cmd_917e36b4441e4fda9a6ae1d7358c2f1f... Duplicate detection confirmed in Service log: [2026-09-23 09:19:48.140] [INF] Duplicate remote command cmd_917e36b4441e4fda9a6ae1d7358c2f1f received. Returning cached result without re-executing. Client PID After Replay: 40252 (Expected: 40252) Final Server Command Status: Succeeded [PASS] Criterion 2: Same CommandId Replay via Natural Dispatched Race & Catch-up CommandId: cmd_917e36b4441e4fda9a6ae1d7358c2f1f, ReceivedCount: 2, DuplicateLog: True, Client PID: A (37408) -> B (40252) -> Replay B (40252), Physical Restarts: 1, Final Server Status: Succeeded ********************** Windows PowerShell transcript end End time: 20260923091951 **********************