Skip to content
CI

Public hardening followups (Codex CLI docs, Slice 3, capability evidence, auto-block, vault v3 design) #9

Sign in to view logs

Public hardening followups (Codex CLI docs, Slice 3, capability evidence, auto-block, vault v3 design)

Public hardening followups (Codex CLI docs, Slice 3, capability evidence, auto-block, vault v3 design) #9

Triggered via pull request April 27, 2026 22:29
@ARHAEEMARHAEEM
synchronize #1
codex/public-hardening-followups
Status Failure
Total duration 6m 55s
Artifacts –

ci.yml

on: pull_request
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

40 errors and 4 warnings
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > happy path: correct OTP on first try -> vault written, exit 0: packages/mcp-server/test/integration/login-runner.integration.test.js#L54
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:54:59
packages/mcp-server/test/daemon/cloudflared-named-provider.test.js > stop() > SIGTERM first; if the process doesn't exit within the grace window, escalate to SIGKILL (POSIX): packages/mcp-server/test/daemon/cloudflared-named-provider.test.js#L447
AssertionError: expected [ 'SIGTERM' ] to include 'SIGKILL' ❯ packages/mcp-server/test/daemon/cloudflared-named-provider.test.js:447:29
packages/extension/tests/validate-command.test.ts > validateCommand > case-insensitive blacklist matching > matches CODE.EXE the same as code.exe on Windows: packages/extension/tests/validate-command.test.ts#L241
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:241:9
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\Windsurf - Next\Windsurf - Next.exe as wrong-runtime: packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:159:42
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\cursor\Cursor.exe as wrong-runtime: packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:159:42
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\Microsoft VS Code\Code.exe as wrong-runtime: packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:159:42
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: missing on disk > returns missing for stale Windows path: packages/extension/tests/validate-command.test.ts#L141
AssertionError: expected 'unknown' to be 'missing' // Object.is equality Expected: "missing" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:141:9
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: node-shaped + exists > returns ok for Windows node.exe path that exists: packages/extension/tests/validate-command.test.ts#L127
AssertionError: expected 'unknown' to be 'ok' // Object.is equality Expected: "ok" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:127:9
packages/extension/tests/detect-ide-status-command.test.ts > detectIdeStatus — command-field validation > extracts command from a TOML config (Codex CLI shape) and flags wrong-runtime: packages/extension/tests/detect-ide-status-command.test.ts#L142
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/detect-ide-status-command.test.ts:142:34
packages/extension/tests/detect-ide-status-command.test.ts > detectIdeStatus — command-field validation > flags a JSON config where command points at the VS Code Electron host: packages/extension/tests/detect-ide-status-command.test.ts#L58
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/detect-ide-status-command.test.ts:58:34
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > happy path: correct OTP on first try -> vault written, exit 0: packages/mcp-server/test/integration/login-runner.integration.test.js#L54
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:54:59
packages/mcp-server/test/daemon/cloudflared-named-provider.test.js > stop() > SIGTERM first; if the process doesn't exit within the grace window, escalate to SIGKILL (POSIX): packages/mcp-server/test/daemon/cloudflared-named-provider.test.js#L447
AssertionError: expected [ 'SIGTERM' ] to include 'SIGKILL' ❯ packages/mcp-server/test/daemon/cloudflared-named-provider.test.js:447:29
packages/extension/tests/validate-command.test.ts > validateCommand > case-insensitive blacklist matching > matches CODE.EXE the same as code.exe on Windows: packages/extension/tests/validate-command.test.ts#L241
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:241:9
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\Windsurf - Next\Windsurf - Next.exe as wrong-runtime: packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:159:42
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\cursor\Cursor.exe as wrong-runtime: packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:159:42
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\Microsoft VS Code\Code.exe as wrong-runtime: packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:159:42
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: missing on disk > returns missing for stale Windows path: packages/extension/tests/validate-command.test.ts#L141
AssertionError: expected 'unknown' to be 'missing' // Object.is equality Expected: "missing" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:141:9
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: node-shaped + exists > returns ok for Windows node.exe path that exists: packages/extension/tests/validate-command.test.ts#L127
AssertionError: expected 'unknown' to be 'ok' // Object.is equality Expected: "ok" Received: "unknown" ❯ packages/extension/tests/validate-command.test.ts:127:9
packages/extension/tests/detect-ide-status-command.test.ts > detectIdeStatus — command-field validation > extracts command from a TOML config (Codex CLI shape) and flags wrong-runtime: packages/extension/tests/detect-ide-status-command.test.ts#L142
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/detect-ide-status-command.test.ts:142:34
packages/extension/tests/detect-ide-status-command.test.ts > detectIdeStatus — command-field validation > flags a JSON config where command points at the VS Code Electron host: packages/extension/tests/detect-ide-status-command.test.ts#L58
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality Expected: "wrong-runtime" Received: "unknown" ❯ packages/extension/tests/detect-ide-status-command.test.ts:58:34
packages/mcp-server/test/integration/manual-login-runner.integration.test.js > manual-login-runner (integration) > exits 2 {reason:'cancelled'} when the browser closes before the session cookie appears: packages/mcp-server/test/integration/manual-login-runner.integration.test.js#L78
AssertionError: expected 5 to be 2 // Object.is equality - Expected + Received - 2 + 5 ❯ packages/mcp-server/test/integration/manual-login-runner.integration.test.js:78:18
packages/mcp-server/test/integration/manual-login-runner.integration.test.js > manual-login-runner (integration) > emits awaiting_user, then writes vault + .reinit + exits 0 after auto-login: packages/mcp-server/test/integration/manual-login-runner.integration.test.js#L55
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ packages/mcp-server/test/integration/manual-login-runner.integration.test.js:55:60
packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js > login -> reinit -> tier (integration harness) > [expected: green — H1 refuted in this harness] headless phase recovery restores isPro after empty-browserData headed bootstrap: packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js#L283
Error: runner setup failed (code 5); cannot witness H1 ❯ packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js:283:1
packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js > login -> reinit -> tier (integration harness) > [regression: H2] PerplexityClient infers Pro from can_use_computer when experiments omits server_is_pro (HEADLESS_ONLY): packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js#L207
Error: runner setup failed (code 5); cannot witness H2 ❯ packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js:207:1
packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js > login -> reinit -> tier (integration harness) > [expected: green] runner writes vault + cache with isPro:true (sanity): packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js#L169
AssertionError: expected 5 to be +0 // Object.is equality - Expected + Received - 0 + 5 ❯ packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js:169:1
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > exits 2 {reason:'auto_unsupported'} when /login/email returns 404 HTML (real-site shape): packages/mcp-server/test/integration/login-runner.integration.test.js#L115
AssertionError: expected 5 to be 2 // Object.is equality - Expected + Received - 2 + 5 ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:115:20
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > exits 2 {reason:'otp_timeout'} when parent never sends OTP: packages/mcp-server/test/integration/login-runner.integration.test.js#L100
AssertionError: expected 5 to be 2 // Object.is equality - Expected + Received - 2 + 5 ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:100:18
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > exits 2 {reason:'sso_required'} when the email triggers SSO: packages/mcp-server/test/integration/login-runner.integration.test.js#L86
AssertionError: expected 5 to be 2 // Object.is equality - Expected + Received - 2 + 5 ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:86:18
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > retries up to 2x on wrong OTP, then exits 2 {reason:'otp_rejected'}: packages/mcp-server/test/integration/login-runner.integration.test.js#L72
AssertionError: expected 0 to be greater than or equal to 2 ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:72:24
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > happy path: correct OTP on first try -> vault written, exit 0: packages/mcp-server/test/integration/login-runner.integration.test.js#L54
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:54:59
packages/mcp-server/test/integration/manual-login-runner.integration.test.js > manual-login-runner (integration) > emits awaiting_user, then writes vault + .reinit + exits 0 after auto-login: packages/mcp-server/test/integration/manual-login-runner.integration.test.js#L55
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ packages/mcp-server/test/integration/manual-login-runner.integration.test.js:55:60
packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js > login -> reinit -> tier (integration harness) > [expected: green — H1 refuted in this harness] headless phase recovery restores isPro after empty-browserData headed bootstrap: packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js#L283
Error: runner setup failed (code 5); cannot witness H1 ❯ packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js:283:1
packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js > login -> reinit -> tier (integration harness) > [regression: H2] PerplexityClient infers Pro from can_use_computer when experiments omits server_is_pro (HEADLESS_ONLY): packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js#L207
Error: runner setup failed (code 5); cannot witness H2 ❯ packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js:207:1
packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js > login -> reinit -> tier (integration harness) > [expected: green] runner writes vault + cache with isPro:true (sanity): packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js#L169
AssertionError: expected 5 to be +0 // Object.is equality - Expected + Received - 0 + 5 ❯ packages/mcp-server/test/integration/login-tier-end-to-end.integration.test.js:169:1
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > exits 2 {reason:'auto_unsupported'} when /login/email returns 404 HTML (real-site shape): packages/mcp-server/test/integration/login-runner.integration.test.js#L115
AssertionError: expected 5 to be 2 // Object.is equality - Expected + Received - 2 + 5 ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:115:20
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > exits 2 {reason:'otp_timeout'} when parent never sends OTP: packages/mcp-server/test/integration/login-runner.integration.test.js#L100
AssertionError: expected 5 to be 2 // Object.is equality - Expected + Received - 2 + 5 ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:100:18
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > exits 2 {reason:'sso_required'} when the email triggers SSO: packages/mcp-server/test/integration/login-runner.integration.test.js#L86
AssertionError: expected 5 to be 2 // Object.is equality - Expected + Received - 2 + 5 ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:86:18
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > retries up to 2x on wrong OTP, then exits 2 {reason:'otp_rejected'}: packages/mcp-server/test/integration/login-runner.integration.test.js#L72
AssertionError: expected 0 to be greater than or equal to 2 ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:72:24
packages/mcp-server/test/integration/login-runner.integration.test.js > login-runner (integration) > happy path: correct OTP on first try -> vault written, exit 0: packages/mcp-server/test/integration/login-runner.integration.test.js#L54
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ packages/mcp-server/test/integration/login-runner.integration.test.js:54:59
packages/mcp-server/test/integration/health-check.integration.test.js > health-check runner (integration) > returns {valid:true, tier:'Pro', modelCount:2} for a good session: packages/mcp-server/test/integration/health-check.integration.test.js#L45
Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ packages/mcp-server/test/integration/health-check.integration.test.js:45:5
build-and-test (ubuntu-latest, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test (ubuntu-latest, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test (windows-latest, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test (windows-latest, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/