********************** Windows PowerShell 脚本开始 开始时间: 20260922232827 用户名: DESKTOP-DJ40RL2\Administrator RunAs 用户: DESKTOP-DJ40RL2\Administrator 配置名称: 计算机: DESKTOP-DJ40RL2 (Microsoft Windows NT 10.0.28000.0) 主机应用程序: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -File C:\Users\Administrator\.gemini\antigravity\scratch\ClassNotify\tests\test_rc2_supplemental_b.ps1 进程 ID: 41276 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-20260922-232827 ========================================================================== >>> [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: 32692 [PASS] Pre-Flight 3: ClassNotify.Client is running in user session PID: 7292, Session: 4 [FAIL] 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_1790090964868_6e4b UIA Helper Execution Result: CLICKED_SUCCESSFULLY (Window: 'ClassNotify', Timestamp: 2026-09-22T15:29:28.5010051Z) [PASS] Criterion 1: UI Automation Invoke on the real WPF ACK button in the interactive Session 4 desktop NotificationId: msg_1790090964868_6e4b, Window: 'ClassNotify', ClientPid: 7292, SessionId: 4, InvokeTime: 2026-09-22T15:29:28.5010051Z, Status: Acknowledged >>> [Criterion 2/4] Client Downtime & Strict FIFO Reception Order (01 -> 02 -> 03)... Client process terminated: True Buffered 3 FIFO messages: f1=msg_1790090980031_fdb2, f2=msg_1790090980522_efe1, f3=msg_1790090981018_e640 Client restored by watchdog: PID 30952 in Session 4 Client Reception Order in Logs: f1_idx=287, f2_idx=295, f3_idx=297 (Strict: True) [PASS] Criterion 2: FIFO Order (01 -> 02 -> 03) received by Client (Primary) & Displayed in DB (Cross-Check) OrderInLogs: 01 (line 287) -> 02 (line 295) -> 03 (line 297), All Persisted in PostgreSQL >>> [Criterion 3/4] Real Dispatched -> TimedOut State Transition (SelfCheck)... [Attempt 1] Dispatching SelfCheck and isolating outbound reporting... Candidate CommandId: cmd_7e48ab304af44e0fa9d2f62ebdded168, 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_ab2b0ae0c2764cf3ada5daa34ed664a9, Initial Server Status: Dispatched, Dispatched: True Confirmed Command cmd_ab2b0ae0c2764cf3ada5daa34ed664a9 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_ab2b0ae0c2764cf3ada5daa34ed664a9, 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): 30952 Dispatched RestartClient command: ID = cmd_ea7d508ae750465182905beeb31e1430, isDispatched = True First execution completed locally: Client PID transitioned from A (30952) to B (38720) Server status while outbound blocked: Dispatched Confirmed Command cmd_ea7d508ae750465182905beeb31e1430 locked in Dispatched state on Server with local execution complete. Restoring network and restarting Service to trigger immediate reconnect catch-up of same CommandId... Client PID After Replay: 38720 (Expected: 38720) [PASS] Criterion 4: Same CommandId Replay (idempotency, duplicate suppression, exactly-once physical execution) CommandId: cmd_ea7d508ae750465182905beeb31e1430, Service Received Count: 1, Duplicate Log Found: True, Client PID: A (30952) -> B (38720) -> Replay B (38720), Physical Restarts: 1 ********************** Windows PowerShell 脚本结束 结束时间: 20260922233314 **********************