fix(dev): cancel readiness retries on abort

[Hweinstock]

Problem

waitForPort left active sockets and scheduled retries alive after abort. In CI, the supervisor's 60ms abort test instead ran for about 60 seconds and timed out; the original #2041 Windows run eventually lost its runner.

Solution

Abort now destroys the active socket, clears the pending retry, removes its listener, and rejects immediately. The TCP test also closes accepted sockets and awaits listener shutdown.

Testing

• Windows unit CI passed in 3m24s.
• Supervisor suite passed 25 consecutive runs; the abort test completes in about 60ms.
• Supervisor, project dev, and port tests passed: 31/31.
• Prettier and tsc --noEmit passed.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Small, well-scoped test-only fix. The change correctly addresses both sides of the lingering handle problem:

1. createServer((socket) => socket.destroy()) — waitForPort opens a real TCP connection (src/io/port.ts:60) that the server accepts. Previously nothing destroyed the server-side accepted socket, so its handle could keep Bun's event loop alive on Windows.
2. Awaiting server.close() via its callback ensures the listener is fully released before the test returns, rather than relying on the previous fire-and-forget call.

The PR description accurately explains the Windows CI hang, the fix matches the described root cause, and no production code is touched. Nothing to change here.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.41%. Comparing base (f1a651c) to head (5ae5799).

Files with missing lines	Patch %	Lines
src/io/port.ts	85.71%	3 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #2109 +/- ##
============================================
- Coverage 97.42% 97.41% -0.02% 
============================================
Files 429 429 Lines 26314 26330 +16 ============================================
+ Hits 25637 25649 +12 - Misses 677 681 +4 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[Hweinstock]

Related: #2110

[tejaskash]

Thanks for the fix!

[Hweinstock]

Problem

waitForPort left active sockets and scheduled retries alive after abort. In CI, the supervisor's 60ms abort test instead ran for about 60 seconds and timed out; the original #2041 Windows run eventually lost its runner.

Solution

Abort now destroys the active socket, clears the pending retry, removes its listener, and rejects immediately. The TCP test also closes accepted sockets and awaits listener shutdown.

Testing

• Windows unit CI passed in 3m24s.
• Supervisor suite passed 25 consecutive runs; the abort test completes in about 60ms.
• Supervisor, project dev, and port tests passed: 31/31.
• Prettier and tsc --noEmit passed.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Small, well-scoped test-only fix. The change correctly addresses both sides of the lingering handle problem:

1. createServer((socket) => socket.destroy()) — waitForPort opens a real TCP connection (src/io/port.ts:60) that the server accepts. Previously nothing destroyed the server-side accepted socket, so its handle could keep Bun's event loop alive on Windows.
2. Awaiting server.close() via its callback ensures the listener is fully released before the test returns, rather than relying on the previous fire-and-forget call.

The PR description accurately explains the Windows CI hang, the fix matches the described root cause, and no production code is touched. Nothing to change here.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.41%. Comparing base (f1a651c) to head (5ae5799).

Files with missing lines	Patch %	Lines
src/io/port.ts	85.71%	3 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #2109 +/- ##
============================================
- Coverage 97.42% 97.41% -0.02% 
============================================
Files 429 429 Lines 26314 26330 +16 ============================================
+ Hits 25637 25649 +12 - Misses 677 681 +4 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[Hweinstock]

Related: #2110

[tejaskash]

Thanks for the fix!

[Hweinstock]

Problem

waitForPort left active sockets and scheduled retries alive after abort. In CI, the supervisor's 60ms abort test instead ran for about 60 seconds and timed out; the original #2041 Windows run eventually lost its runner.

Solution

Abort now destroys the active socket, clears the pending retry, removes its listener, and rejects immediately. The TCP test also closes accepted sockets and awaits listener shutdown.

Testing

• Windows unit CI passed in 3m24s.
• Supervisor suite passed 25 consecutive runs; the abort test completes in about 60ms.
• Supervisor, project dev, and port tests passed: 31/31.
• Prettier and tsc --noEmit passed.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Small, well-scoped test-only fix. The change correctly addresses both sides of the lingering handle problem:

1. createServer((socket) => socket.destroy()) — waitForPort opens a real TCP connection (src/io/port.ts:60) that the server accepts. Previously nothing destroyed the server-side accepted socket, so its handle could keep Bun's event loop alive on Windows.
2. Awaiting server.close() via its callback ensures the listener is fully released before the test returns, rather than relying on the previous fire-and-forget call.

The PR description accurately explains the Windows CI hang, the fix matches the described root cause, and no production code is touched. Nothing to change here.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.41%. Comparing base (f1a651c) to head (5ae5799).

Files with missing lines	Patch %	Lines
src/io/port.ts	85.71%	3 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #2109 +/- ##
============================================
- Coverage 97.42% 97.41% -0.02% 
============================================
Files 429 429 Lines 26314 26330 +16 ============================================
+ Hits 25637 25649 +12 - Misses 677 681 +4 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[Hweinstock]

Related: #2110

[tejaskash]

Thanks for the fix!

[Hweinstock]

Problem

waitForPort left active sockets and scheduled retries alive after abort. In CI, the supervisor's 60ms abort test instead ran for about 60 seconds and timed out; the original #2041 Windows run eventually lost its runner.

Solution

Abort now destroys the active socket, clears the pending retry, removes its listener, and rejects immediately. The TCP test also closes accepted sockets and awaits listener shutdown.

Testing

• Windows unit CI passed in 3m24s.
• Supervisor suite passed 25 consecutive runs; the abort test completes in about 60ms.
• Supervisor, project dev, and port tests passed: 31/31.
• Prettier and tsc --noEmit passed.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Small, well-scoped test-only fix. The change correctly addresses both sides of the lingering handle problem:

1. createServer((socket) => socket.destroy()) — waitForPort opens a real TCP connection (src/io/port.ts:60) that the server accepts. Previously nothing destroyed the server-side accepted socket, so its handle could keep Bun's event loop alive on Windows.
2. Awaiting server.close() via its callback ensures the listener is fully released before the test returns, rather than relying on the previous fire-and-forget call.

The PR description accurately explains the Windows CI hang, the fix matches the described root cause, and no production code is touched. Nothing to change here.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.41%. Comparing base (f1a651c) to head (5ae5799).

Files with missing lines	Patch %	Lines
src/io/port.ts	85.71%	3 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #2109 +/- ##
============================================
- Coverage 97.42% 97.41% -0.02% 
============================================
Files 429 429 Lines 26314 26330 +16 ============================================
+ Hits 25637 25649 +12 - Misses 677 681 +4 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[Hweinstock]

Related: #2110

[tejaskash]

Thanks for the fix!

[Hweinstock]

Problem

waitForPort left active sockets and scheduled retries alive after abort. In CI, the supervisor's 60ms abort test instead ran for about 60 seconds and timed out; the original #2041 Windows run eventually lost its runner.

Solution

Abort now destroys the active socket, clears the pending retry, removes its listener, and rejects immediately. The TCP test also closes accepted sockets and awaits listener shutdown.

Testing

• Windows unit CI passed in 3m24s.
• Supervisor suite passed 25 consecutive runs; the abort test completes in about 60ms.
• Supervisor, project dev, and port tests passed: 31/31.
• Prettier and tsc --noEmit passed.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Small, well-scoped test-only fix. The change correctly addresses both sides of the lingering handle problem:

1. createServer((socket) => socket.destroy()) — waitForPort opens a real TCP connection (src/io/port.ts:60) that the server accepts. Previously nothing destroyed the server-side accepted socket, so its handle could keep Bun's event loop alive on Windows.
2. Awaiting server.close() via its callback ensures the listener is fully released before the test returns, rather than relying on the previous fire-and-forget call.

The PR description accurately explains the Windows CI hang, the fix matches the described root cause, and no production code is touched. Nothing to change here.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.41%. Comparing base (f1a651c) to head (5ae5799).

Files with missing lines	Patch %	Lines
src/io/port.ts	85.71%	3 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #2109 +/- ##
============================================
- Coverage 97.42% 97.41% -0.02% 
============================================
Files 429 429 Lines 26314 26330 +16 ============================================
+ Hits 25637 25649 +12 - Misses 677 681 +4 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[Hweinstock]

Related: #2110

[tejaskash]

Thanks for the fix!

[Hweinstock]

Problem

waitForPort left active sockets and scheduled retries alive after abort. In CI, the supervisor's 60ms abort test instead ran for about 60 seconds and timed out; the original #2041 Windows run eventually lost its runner.

Solution

Abort now destroys the active socket, clears the pending retry, removes its listener, and rejects immediately. The TCP test also closes accepted sockets and awaits listener shutdown.

Testing

• Windows unit CI passed in 3m24s.
• Supervisor suite passed 25 consecutive runs; the abort test completes in about 60ms.
• Supervisor, project dev, and port tests passed: 31/31.
• Prettier and tsc --noEmit passed.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Small, well-scoped test-only fix. The change correctly addresses both sides of the lingering handle problem:

1. createServer((socket) => socket.destroy()) — waitForPort opens a real TCP connection (src/io/port.ts:60) that the server accepts. Previously nothing destroyed the server-side accepted socket, so its handle could keep Bun's event loop alive on Windows.
2. Awaiting server.close() via its callback ensures the listener is fully released before the test returns, rather than relying on the previous fire-and-forget call.

The PR description accurately explains the Windows CI hang, the fix matches the described root cause, and no production code is touched. Nothing to change here.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.41%. Comparing base (f1a651c) to head (5ae5799).

Files with missing lines	Patch %	Lines
src/io/port.ts	85.71%	3 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #2109 +/- ##
============================================
- Coverage 97.42% 97.41% -0.02% 
============================================
Files 429 429 Lines 26314 26330 +16 ============================================
+ Hits 25637 25649 +12 - Misses 677 681 +4 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[Hweinstock]

Related: #2110

[tejaskash]

Thanks for the fix!

[Hweinstock]

Problem

waitForPort left active sockets and scheduled retries alive after abort. In CI, the supervisor's 60ms abort test instead ran for about 60 seconds and timed out; the original #2041 Windows run eventually lost its runner.

Solution

Abort now destroys the active socket, clears the pending retry, removes its listener, and rejects immediately. The TCP test also closes accepted sockets and awaits listener shutdown.

Testing

• Windows unit CI passed in 3m24s.
• Supervisor suite passed 25 consecutive runs; the abort test completes in about 60ms.
• Supervisor, project dev, and port tests passed: 31/31.
• Prettier and tsc --noEmit passed.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Small, well-scoped test-only fix. The change correctly addresses both sides of the lingering handle problem:

1. createServer((socket) => socket.destroy()) — waitForPort opens a real TCP connection (src/io/port.ts:60) that the server accepts. Previously nothing destroyed the server-side accepted socket, so its handle could keep Bun's event loop alive on Windows.
2. Awaiting server.close() via its callback ensures the listener is fully released before the test returns, rather than relying on the previous fire-and-forget call.

The PR description accurately explains the Windows CI hang, the fix matches the described root cause, and no production code is touched. Nothing to change here.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.41%. Comparing base (f1a651c) to head (5ae5799).

Files with missing lines	Patch %	Lines
src/io/port.ts	85.71%	3 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #2109 +/- ##
============================================
- Coverage 97.42% 97.41% -0.02% 
============================================
Files 429 429 Lines 26314 26330 +16 ============================================
+ Hits 25637 25649 +12 - Misses 677 681 +4 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[Hweinstock]

Related: #2110

[tejaskash]

Thanks for the fix!

[Hweinstock]

Problem

waitForPort left active sockets and scheduled retries alive after abort. In CI, the supervisor's 60ms abort test instead ran for about 60 seconds and timed out; the original #2041 Windows run eventually lost its runner.

Solution

Abort now destroys the active socket, clears the pending retry, removes its listener, and rejects immediately. The TCP test also closes accepted sockets and awaits listener shutdown.

Testing

• Windows unit CI passed in 3m24s.
• Supervisor suite passed 25 consecutive runs; the abort test completes in about 60ms.
• Supervisor, project dev, and port tests passed: 31/31.
• Prettier and tsc --noEmit passed.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Small, well-scoped test-only fix. The change correctly addresses both sides of the lingering handle problem:

1. createServer((socket) => socket.destroy()) — waitForPort opens a real TCP connection (src/io/port.ts:60) that the server accepts. Previously nothing destroyed the server-side accepted socket, so its handle could keep Bun's event loop alive on Windows.
2. Awaiting server.close() via its callback ensures the listener is fully released before the test returns, rather than relying on the previous fire-and-forget call.

The PR description accurately explains the Windows CI hang, the fix matches the described root cause, and no production code is touched. Nothing to change here.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.41%. Comparing base (f1a651c) to head (5ae5799).

Files with missing lines	Patch %	Lines
src/io/port.ts	85.71%	3 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## refactor #2109 +/- ##
============================================
- Coverage 97.42% 97.41% -0.02% 
============================================
Files 429 429 Lines 26314 26330 +16 ============================================
+ Hits 25637 25649 +12 - Misses 677 681 +4 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[Hweinstock]

Related: #2110

[tejaskash]

Thanks for the fix!