feat: upgrade agent inspector to 0.4.0

[avi-alpert]

Description

Upgrade agent inspector to 0.4.0 which includes showing available tools in Harness settings when agentcore dev is run in a project with a harness.

Related Issue

Closes #

Documentation PR

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

How have you tested the change?

• I ran npm run test:unit and npm run test:integ
• I ran npm run typecheck
• I ran npm run lint
• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-0.13.1.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-1249-tarball/aws-agentcore-0.13.1.tgz

[agentcore-cli-automation]

Reviewed the diff. This is a straightforward version bump of @aws/agent-inspector from 0.3.0 → 0.4.0. The package only ships static frontend assets (dist-assets/index.html, index.js, index.css, favicon.svg) that are served statically by web-server.ts via resolveUIDistDir() — the CLI doesn't import any code from it. The 0.3.0 vs 0.4.0 tarballs have identical file layouts, so no path changes are needed in scripts/copy-assets.mjs or web-server.ts. No CLI-side feature work means no new telemetry is required here (the "available tools in Harness settings" change is entirely inside the inspector frontend). LGTM 🚀