********************** Windows PowerShell transcript start Start time: 20260923063843 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_b.ps1 Process ID: 37564 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 B Target RCArtifactId: P1-RC2-20260922-151442-F2C14966 Evidence ID: EVIDENCE-RC2-SUPPLEMENTAL-B-20260923-063842 ========================================================================== >>> [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: 36732, 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/4] Real ACK via UI Automation Invoke in Session 4... Urgent notification sent: ID = msg_1790116732168_4f43 UIA Helper Execution Result: CLICKED_SUCCESSFULLY (Window: 'ClassNotify', Timestamp: 2026-09-22T22:38:56.4708451Z) [PASS] Criterion 1: UI Automation Invoke on the real WPF ACK button in the interactive Session 4 desktop NotificationId: msg_1790116732168_4f43, Window: 'ClassNotify', ClientPid: 36732, SessionId: 4, InvokeTime: 2026-09-22T22:38:56.4708451Z, Status: Acknowledged >>> [Criterion 2/4] Client Downtime & Strict FIFO Reception Order (01 -> 02 -> 03)... Client process terminated: False Buffered 3 FIFO messages: f1=msg_1790116746164_902a, f2=msg_1790116746642_bde8, f3=msg_1790116747116_d558 Client restored by watchdog: PID 41692 in Session 4 Client Reception Order in Logs: f1_idx=440, f2_idx=442, f3_idx=445 (Strict: True) [PASS] Criterion 2: FIFO Order (01 -> 02 -> 03) received by Client (Primary) & Displayed in DB (Cross-Check) OrderInLogs: 01 (line 440) -> 02 (line 442) -> 03 (line 445), All Persisted in PostgreSQL >>> [Criterion 3/4] Real Dispatched -> TimedOut State Transition (SelfCheck)... [Attempt 1] Dispatching SelfCheck and isolating outbound reporting... Candidate CommandId: cmd_a21fdb8f4397455da9f34cb92fb05530, Initial Server Status: Succeeded, Dispatched: True [TEST_ATTEMPT_INVALID] Result was reported before firewall rule engaged. Retrying with new CommandId... [Attempt 2] Dispatching SelfCheck and isolating outbound reporting... Candidate CommandId: cmd_8d201952879c4a4c96ded2e00ff214c6, Initial Server Status: Dispatched, Dispatched: True Confirmed Command cmd_8d201952879c4a4c96ded2e00ff214c6 is locked in 'Dispatched' state on Server. Waiting 140s for Server Normalizer... Waiting for timeout transition... (10s / 140s) Waiting for timeout transition... (20s / 140s) Waiting for timeout transition... (30s / 140s) Waiting for timeout transition... (40s / 140s) Waiting for timeout transition... (50s / 140s) Waiting for timeout transition... (60s / 140s) Waiting for timeout transition... (70s / 140s) Waiting for timeout transition... (80s / 140s) Waiting for timeout transition... (90s / 140s) Waiting for timeout transition... (100s / 140s) Waiting for timeout transition... (110s / 140s) Waiting for timeout transition... (120s / 140s) Waiting for timeout transition... (130s / 140s) Waiting for timeout transition... (140s / 140s) Firewall rule removed, network restored. [PASS] Criterion 3: Real Dispatched -> TimedOut State Transition (Status: TimedOut, ResultCode: -4) CommandId: cmd_8d201952879c4a4c96ded2e00ff214c6, API Status: TimedOut, ResultCode: -4, PostgreSQL Verified: True >>> [Criterion 4/4] Same CommandId Replay via Reconnect Catch-up... [Attempt 1] Ensuring device is online... Device Online Status: True Client PID Before Replay Test (A): 41692 Dispatched RestartClient command: ID = cmd_bf915aa286cf47388d34b8abb72c9485, isDispatched = True First execution completed locally: Client PID transitioned from A (41692) to B (17412) First execution recorded locally in command_ledger.json. Simulating WAN ACK loss by setting Server status to Dispatched... Server DB Status for catch-up replay verified: Dispatched Triggering Reconnect to execute DeviceHub catch-up of the SAME CommandId (cmd_bf915aa286cf47388d34b8abb72c9485)... Duplicate detection confirmed in Service log: [2026-09-23 06:42:38.270] [INF] Duplicate remote command cmd_bf915aa286cf47388d34b8abb72c9485 received. Returning cached result without re-executing. Client PID After Replay: 17412 (Expected: 17412) [PASS] Criterion 4: Same CommandId Replay (idempotency, duplicate suppression, exactly-once physical execution) CommandId: cmd_bf915aa286cf47388d34b8abb72c9485, Service Received Count: 2, Duplicate Log Found: True, Client PID: A (41692) -> B (17412) -> Replay B (17412), Physical Restarts: 1 ********************** Windows PowerShell transcript end End time: 20260923064243 **********************