fix(logs): wire up cli telemetry and model user errors

[Hweinstock]

Description

Two changes to improve telemetry coverage for the logs command:

1. Wire up CLI telemetry (commands/logs/command.tsx): handleLogs and handleLogsEval are now wrapped in withCommandRunTelemetry. Before this, only the interactive TUI path emitted cli.command_run; the CLI path recorded nothing.

2. Model user errors (tui/screens/logs/useLogsFlow.ts): Two conditions that returned plain new Error(...) now return ValidationError.

Related Issue

Closes #

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-devx-automation]

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

[github-actions]

Package Tarball

aws-agentcore-0.17.0.tgz

How to install

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

[agentcore-cli-automation]

Looks good to merge.

Verified:

• withCommandRunTelemetry wiring in command.tsx is consistent with existing usage in other CLI commands (e.g. validate, import, status).
• LogsAttrs (has_query, has_level_filter) and LogsEvalsAttrs (has_follow) schemas already exist in schemas/command-run.ts, matching the attributes passed in.
• ValidationError extends BaseError with defaultSource: 'user', so classifyError will correctly emit source: 'user' and category: 'ValidationError' for the two now-typed conditions in useLogsFlow.
• CLI path (handleLogs/handleLogsEval) and TUI path (useLogsFlow) are distinct call sites — no double-counting risk.
• requireProject() remains outside the telemetry wrapper (unchanged behavior, not a regression).

[Hweinstock]

eventually, we'll want this in telemetry, but right now it kills the process on failure, so OOS for here.