fix: add -g flag to bundle install instructions

[Hweinstock]

Description

The bundle script outputs an npm install <tarball> instruction after building, but without -g the CLI binary is not linked globally and the agentcore command is not available. This adds the -g flag to the install instruction.

Related Issue

N/A

Documentation PR

N/A

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.

[agentcore-cli-automation]

Looks good to merge. The change correctly aligns the printed install instruction with the intended global install (matches the documented usage npm install -g <path-to-tar> for testing the CLI end-to-end). Single-line, low-risk fix; no tests or telemetry needed.

[github-actions]

Package Tarball

aws-agentcore-0.14.2.tgz

How to install

gh release download pr-1348-tarball --repo aws/agentcore-cli --pattern "*.tgz" --dir /tmp/pr-tarball
npm install -g /tmp/pr-tarball/aws-agentcore-0.14.2.tgz

[agentcore-devx-automation]

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

[agentcore-devx-automation]

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