fix: address double function implementation failing tsc

[Hweinstock]

Problem

The tsc is failing (again)

$ tsc --noEmit
src/handlers/project/buildDeploy.screen.test.tsx:65:11 - error TS2300: Duplicate identifier 'resolveProjectResources'.

65     async resolveProjectResources() {
             ~~~~~~~~~~~~~~~~~~~~~~~


Found 1 error in src/handlers/project/buildDeploy.screen.test.tsx:65

https://github.com/aws/agentcore-cli/actions/runs/33790922020/job/100784295618

Solution

remove the duplicates

Verification

bun run typecheck

[agentcore-devx-automation]

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

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Trivial and correct typecheck fix. The pre-PR fakeBackend in src/handlers/project/buildDeploy.screen.test.tsx declared resolveProjectResources twice (lines 59–61 and again at 65–67), causing TS2300: Duplicate identifier. Removing the second copy leaves one resolveProjectResources and one resolveDeployedResources, which matches the ProjectBackend interface. Nothing else to flag — no telemetry/mocking implications for a test-only dedup. Good to merge.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.15%. Comparing base (a665955) to head (003dee1).
⚠️ Report is 1 commits behind head on refactor.

Additional details and impacted files

@@            Coverage Diff            @@
##           refactor    #2192   +/-   ##
=========================================
  Coverage     97.15%   97.15%           
=========================================
  Files           542      542           
  Lines         37728    37728           
=========================================
  Hits          36653    36653           
  Misses         1075     1075           

☔ 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.

[github-actions]

Thanks for the report, @codecov-commenter — feedback like this is exactly
how we catch the things we missed. Because this PR is already
closed, the team won't see follow-up comments here.

Would you mind opening a new issue so we can track it properly?
https://github.com/aws/agentcore-cli/issues/new/choose

If this is a security issue, please report it privately via
https://aws.amazon.com/security/vulnerability-reporting/ instead
of a public issue.