fix: build CLI before running integration tests

[Hweinstock]

Description

Problem

PR fixes two issues:

• integ tests don't run on fresh build: CI: running integ tests locally uses stale version. #1283
• e2e tests command doesn't work.

Solution

• run build before integ tests.
• add a script for running e2e tests in dev account. Note: this is separate from run-e2e-local.sh, which attempts to simulate CI locally. run-e2e-dev.sh runs the tests in a dev account, not CI.

Testing

• npm run test:e2e no longer errors.
• npm run test:integ runs the integ tests.

Related Issue

N/A

Documentation PR

N/A

Type of Change

• New feature
• Other (please describe): Developer workflow improvement — new script for local E2E testing

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

[agentcore-cli-automation]

LGTM — small, well-scoped change.

Verified:

• The test:integ build prefix is correct: integ-tests spawn dist/cli/index.mjs via src/test-utils/cli-runner.ts, so a stale or missing dist/ would silently run an old build (or fail). Adding npm run build && makes npm run test:integ self-contained for local dev. The CI workflow (.github/workflows/build-and-test.yml) already runs npm run build before npm run test:integ, so this introduces a redundant rebuild in CI, but that's negligible.
• This is consistent with the existing test:tui pattern (npm run build:harness && vitest run --project tui).
• scripts/run-e2e-dev.sh is a purely additive dev convenience and mirrors the structure of run-e2e-local.sh. The default test (strands-bedrock.test.ts) sensibly only requires Bedrock creds, not the API-key secrets that run-e2e-local.sh fetches.