feat: instrument telemetry for deploy command (CLI + TUI)

[Hweinstock]

Description

Adds telemetry instrumentation to the deploy command (CLI + TUI), following the same pattern as #1202 (create telemetry). Emits cli.command_run events with command_group: 'deploy' for all modes (deploy, dry-run, diff).

Related Issue

Closes #

Documentation PR

N/A - no user-facing documentation changes needed.

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

[agentcore-cli-automation]

Reviewed end-to-end. The telemetry instrumentation follows the pattern established by #1202 and the docs in src/cli/telemetry/README.md, and the refactor of command.tsx cleanly separates telemetry-wrapped execution from output/exit logic.

Things I checked and that look good:

• The CLI wrapper at command.tsx:51-59 returns an OperationResult-shaped value to withCommandRunTelemetry, so success/failure telemetry is recorded before any output is printed or process.exit is called. Since withCommandRun awaits sink.flush() in its finally, the flush completes before the process.exit(0/1/2) calls in the handler.
• The two TUI effects in useDeployFlow.ts (deploy effect at L548, diff effect at L736) are correctly guarded by diffMode/!diffMode, so exactly one telemetry event is emitted per run. The deploy effect also runs a pre-deploy diff internally but is still a single command_run, which matches what you'd want.
• DEFAULT_DEPLOY_ATTRS + override ({ ...DEFAULT_DEPLOY_ATTRS, mode: 'diff' as const }) handles the case where context isn't ready yet without dropping the event or emitting a wrong mode.
• Schema migration has_diff → mode is complete — no stray references anywhere under src/, tests updated accordingly.
• computeDeployAttrs tests in utils.test.ts use plain objects rather than mocks — exactly the style called out in the review guidelines.
• Counts emitted (runtime_count, gateway_target_count, etc.) are aggregate only; no names/paths leak into telemetry.

All CI checks are green. LGTM.