CI: update the Named Pipe first-invoke assertion for the new-session treatment

The 1.11.0 new-session treatment changed the first console attach response: on
a fresh proxy the first invoke_expression now carries the 'New server session'
notice and normalizes the working directory to the home directory (prefixing
the pipeline with Set-Location), instead of the old 'Switched to console'
notice. The Linux Named Pipe integration test still asserted 'Switched to
console' and failed (run 28006458461) -- a stale expectation, not a product
bug: the run log shows 'New server session ... now at /home/runner', confirming
the feature works on Linux. Update the first-call assertion to expect 'New
server session' plus the date (Get-Date still runs in the same call). Other
workflows do not assert the old strings; macos-terminal-test is manual-only and
talks to the DLL pipe directly (bypassing the proxy), so it is unaffected.

Author: yotsuda

.github/workflows/cross-platform-test.yml

@@ -572,20 +572,22 @@ jobs:
           } else {
 
           # Test: invoke_expression with Get-Date (first call).
-          # Since v1.9 (commit 32f0f56), the "switched to a sibling pipe" path no longer
-          # bails with "Pipeline NOT executed" — it folds the switch notice into the
-          # response and runs the pipeline in the same call. So the first call should
-          # show BOTH the "Switched to console" notice AND the actual Get-Date result.
+          # On a fresh proxy this is the first console attach for the agent — the
+          # resume / cold-start boundary — so the response carries the "New server
+          # session" notice and the working directory is normalized to $HOME (the
+          # pipeline is prefixed with a Set-Location), after which the Get-Date still
+          # runs in the same call. So the first call should show BOTH the "New server
+          # session" notice AND the actual Get-Date result.
           Write-Host "`n=== Test: invoke_expression (Get-Date) - First call ===" -ForegroundColor Yellow
           $invokeRequest = '{"jsonrpc":"2.0","id":10,"method":"tools/call","params":{"name":"invoke_expression","arguments":{"pipeline":"Get-Date -Format yyyy-MM-dd"}}}'
           $response = Send-JsonRpc $invokeRequest 60000
           Write-Host "Response (truncated): $($response.Substring(0, [Math]::Min(200, $response.Length)))..."
 
           $today = Get-Date -Format "yyyy-MM-dd"
-          if ($response -match "Switched to console" -and $response -match $today) {
-            Write-Host "First invoke_expression: PASSED (switched + executed in one call)" -ForegroundColor Green
+          if ($response -match "New server session" -and $response -match $today) {
+            Write-Host "First invoke_expression: PASSED (new-session treatment + executed in one call)" -ForegroundColor Green
           } else {
-            throw "First invoke_expression did not return both ''Switched to console'' and today''s date ($today)"
+            throw "First invoke_expression did not return both ''New server session'' and today''s date ($today)"
           }
 
           # Test: invoke_expression with Get-Date (second call - reuses existing pipe, no switch notice)