********************** Windows PowerShell transcript start Start time: 20260923100352 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 C:\Users\Administrator\.gemini\antigravity\scratch\ClassNotify\tests\test_rc3_cloud_recovery.ps1 Process ID: 31064 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-3B: Cloud Recovery Acceptance Suite Target RCArtifactId: P1-RC2-20260922-151442-F2C14966 Evidence ID: EVIDENCE-RC3-CLOUD-20260923-100352 ========================================================================== >>> [Pre-Flight] System & Environment Verification... [PASS] Pre-Flight 1: Local ClassNotifySetup.exe SHA256 matches baseline F2C14966E99B47A5A67436F7E4E1FB72A363FCB560BF19C07BDF23DEA5BDADD9 [PASS] Pre-Flight 2: Service in Session 0 (PID 39080), Client in Session 4 (PID 29456) [PASS] Pre-Flight 3: Teacher & Admin authentication succeeded [PASS] Pre-Flight 4: Target device reports Online on Tokyo server DeviceId: dev_59e35e79 >>> [Baseline] Capturing systemd status and database baseline on Tokyo VPS... >>> [Scenario 4/8] Tokyo Server Daemon Restart (systemctl restart classnotify)... Baseline Windows PIDs: Service = 39080, Client = 29456 Triggering 'systemctl restart classnotify' on Tokyo VPS... Uri: PS>TerminatingError(Invoke-RestMethod): "远程服务器返回错误: (502) 错误的网关。" PS>TerminatingError(Invoke-RestMethod): "远程服务器返回错误: (502) 错误的网关。" Server /api/health Result: True in 6160 ms Device Online Result: True in 10522 ms Windows Zero-Restart Verification: Service Unchanged (True), Client Unchanged (True) Sending smoke notification 'RC3-POST-SERVER-RESTART-RECOVERY'... Smoke notification sent: ID = msg_1790129080678_5fee Smoke Message Received & ACKed: True [PASS] Scenario 4: Tokyo Server Restart (systemctl restart classnotify) HealthMs: 6160 (<= 30000), OnlineMs: 10522 (<= 60000), ZeroRestart: True, SmokeDelivered: True >>> [Scenario 5/8] Caddy Reverse Proxy Restart (systemctl restart caddy)... Triggering 'systemctl restart caddy' on Tokyo VPS... Uri: Caddy HTTPS Health Result: True in 5471 ms Caddy Reconnect Result: True in 5770 ms Sending smoke notification 'RC3-POST-CADDY-RECOVERY'... Smoke notification sent: ID = msg_1790129091402_dadf Smoke Message Received & ACKed: True [PASS] Scenario 5: Caddy Reverse Proxy Restart (systemctl restart caddy) HealthMs: 5471 (<= 20000), ReconnectMs: 5770 (<= 45000), ZeroRestart: True, SmokeDelivered: True >>> [Scenario 6/8] PostgreSQL Database Restart & Integrity Check... Triggering 'systemctl restart postgresql' on Tokyo VPS... Uri: PS>TerminatingError(Invoke-RestMethod): "远程服务器返回错误: (500) 内部服务器错误。" PostgreSQL API Reconnect Result: True in 7397 ms Data Integrity Verification: 100% of baseline records intact (Missing: 2) Testing DB write & client delivery with 'RC3-POST-POSTGRES-RECOVERY'... Postgres smoke notification sent: ID = msg_1790129104698_c152 Postgres Smoke Message Received & ACKed: True [FAIL] Scenario 6: PostgreSQL Database Restart & Integrity PostgresRecoveryMs: 7397 (<= 60000), BaselineDataIntact: False, WriteAndDeliver: True >>> [Scenario 7/8] Pending Notification across Server Daemon Restart... Adding firewall block rule 'ClassNotify-RC3-CloudCut' to simulate offline device... Dispatching notification 'RC3-PENDING-OVER-RESTART' with 5-minute TTL while device offline... Pending notification dispatched: ID = msg_1790129129029_760f DB Verification Before Restart: Notification persisted in DB = msg_1790129129029_760f | cls_802 | RC3-PENDING-OVER-RESTART | 2026-09-23 02:05:29.029127+00 | 2026-09-23 02:15:29.029127+00 Restarting 'classnotify' daemon on Tokyo VPS with pending notification in queue... Uri: DB Verification After Restart: Notification safely preserved = msg_1790129129029_760f | cls_802 | RC3-PENDING-OVER-RESTART | 2026-09-23 02:05:29.029127+00 | 2026-09-23 02:15:29.029127+00 Restoring outbound network (deleting firewall rule 'ClassNotify-RC3-CloudCut')... Waiting for SignalR reconnect and pending notification catch-up... Catch-Up Delivery Result: True in 33231 ms [PASS] Scenario 7: Pending Notification across Server Restart (Persistence & Catch-Up) PendingPreserved: msg_1790129129029_760f | cls_802 | RC3-PENDING-OVER-RESTART | 2026-09-23 02:05:29.029127+00 | 2026-09-23 02:15:29.029127+00, CatchupReceived: True, CatchupMs: 33231 (<= 45000) >>> [Scenario 8/8] Audit Trail Consistency & Monotonicity Diff Check... [PASS] Scenario 8: Audit Trail Diff & Monotonicity Check AllTrackedFound: True, AuditMonotonic: (30 >= 20) ********************** Windows PowerShell transcript end End time: 20260923100638 **********************