feat: add read-only datasets TUI

[nborges-aws]

Adds an interactive, read-only TUI for the eval dataset command tree. Follows conventional menu → list → detail → JSON flow. Bare commands eval dataset, eval dataset list, eval dataset get now open TUI flows instead of missing flag error messaging.

Screens

Path	Screen
eval dataset	RouterScreen menu
eval dataset list / eval dataset get	DatasetPicker using PaginatedTablePicker
eval dataset get/:datasetId	ResourceDetailScreen
eval dataset get/:datasetId/json	JsonDetail

Testing

• Added dataset.screen.test.tsx covering navigation, menu filtering, metadata rendering, etc.
• bun run test (892 pass, 0 fail)

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[codecov-commenter]

Codecov Report

❌ Patch coverage is 99.39024% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 96.96%. Comparing base (2d79b36) to head (84034b5).
⚠️ Report is 1 commits behind head on refactor.

Files with missing lines	Patch %	Lines
src/components/DatasetPicker.tsx	98.38%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##           refactor    #1932      +/-   ##
============================================
+ Coverage     96.94%   96.96%   +0.01%     
============================================
  Files           360      364       +4     
  Lines         20596    20758     +162     
============================================
+ Hits          19966    20127     +161     
- Misses          630      631       +1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jariy17]

Seperate the update commands in their own PR

[jariy17]

Seperate the write only dataset handlers into their own pr.

[nborges-aws]

This PR was incorrectly pulling in commits from the dataset update CLI command PR. That's why this file was showing up. The PR is now showing the correct commits/diff now that I've fixed conflicts and rebased

[Hweinstock]

should we use AgentCoreCLIError.from here?

[nborges-aws]

Hmm yeah looking into it now, this is a good call out. It would probably make the most sense to use AgentCoreCLIError.from inside ResourceDetailScreen and the other shared resources. That way the its standardized across all screens. The call site would then just do:
detail.isError ? detail.error : null