fix(project): point the no-targets error at project deploy

[jariy17]

resolveExistingTarget told the user to hand-write aws-targets.json with an example account id when a project declared no deployment targets:

No deployment targets are configured for project 'orders'. Add /path/agentcore/aws-targets.json, for example:

[{ "name": "default", "account": "111122223333", "region": "us-east-1" }]

A freshly created project hits this on its first agentcore project status, because create writes an empty aws-targets.json and only deploy fills it. Deploying is what the user should do, so the message now says so:

No deployment targets are configured for project 'orders'. Please deploy your project using 'agentcore project deploy'.

The missing-file and empty-array branches reported the same thing once the path/example was dropped, so they merge into one targets.length === 0 check. The unknown---target branch is unchanged — it still lists the declared target names, which is the useful fix for a typo.

This is a shared helper, so deploy, remove, and invoke get the same clearer message when a project has no targets.

[agentcore-devx-automation]

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

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Small, well-scoped change. Replacing the "hand-edit aws-targets.json" instruction with a pointer to agentcore project deploy matches the current UX where the deploy path auto-provisions the default target (see provisionDefaultTarget around line 1033), so the old guidance was stale.

A few things I verified:

• TARGETS_EXAMPLE is still referenced by the deploy path (manager.tsx lines 926/932), so it isn't dead code.
• Collapsing the "file missing" and "empty targets" branches into a single targets.length === 0 check is fine here — resolveExistingTarget is a read path and doesn't need to distinguish the two cases (the deploy path still handles them separately).
• Other tests that match on the substring "No deployment targets are configured" (manager.test.ts:742, project.test.ts:1366, deploy/index.test.ts:380, invoke.screen.test.tsx:111) still pass with the new message since that substring is preserved.

No telemetry concerns (no new feature surface) and no test-mocking concerns. Nothing blocking from me.

[codecov-commenter]

Codecov Report

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

Additional details and impacted files

@@             Coverage Diff              @@
##           refactor    #2196      +/-   ##
============================================
- Coverage     97.15%   97.15%   -0.01%     
============================================
  Files           542      542              
  Lines         37728    37723       -5     
============================================
- Hits          36653    36648       -5     
  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.