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-1247-tarball/aws-agentcore-0.13.1.tgz

[notgitika]

LGTM but failing lint

[agentcore-cli-automation]

Looks good to merge. Clean dependency version bump from 0.3.0 → 0.4.0.

Verified:

• Package layout is unchanged (dist-assets/{index.html,index.js,index.css,favicon.svg}), so resolveUIDistDir and scripts/copy-assets.mjs continue to work without modification.
• The set of /api/* endpoints the frontend calls is identical between 0.3.0 and 0.4.0, so no new server routes are needed in web-server.ts.
• Custom headers (X-Agentcore-Local, x-session-id, Mcp-Session-Id) are unchanged, so the CORS allowlist and POST-header guard still match.
• index.html still references same-origin /index.js and /index.css, so the existing CSP header is fine.
• Runtime dependencies of @aws/agent-inspector itself didn't change between 0.3.0 and 0.4.0 — the rest of the package-lock churn is just normal lockfile reshuffling.

No CLI code changes are required and there's no telemetry surface area touched, so no instrumentation needed.

[avi-alpert]

Lint was failing due to package lock upgrading the lint version. closed and opened another #1249