chore: use shared FormRadio component in endpointWizard

[nborges-aws]

Description

EndpointWizard.tsx was added before the FormRadioGroup shared component was created, as until now was using its own radio button logic.

This PR updates endpoint wizard to use the shared component, aligning it to the style and handling the rest of the TUI uses.

Before:

After:

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe): Tech debt

Testing

How have you tested the change?

• bun run test (2854 pass, 0 fail)
• 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)

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Looks good

Nice, focused refactor extracting the radio-list rendering into a reusable FormRadioGroup. The behavior in VersionStep is preserved (key handling, focus semantics, sort order, "latest" default in create mode), tests were updated to assert the new bordered layout, and no other call sites still rely on the removed detail field.

A couple of small observations, none of which I think block merging:

• FormRadioGroup lives in src/components/ while the other reusable UI primitives (spinner, stepper, dialog, key-hint, etc.) live in src/components/ui/ and typically have a colocated .test.tsx. Might be worth moving it under ui/ and adding a lightweight unit test in a follow-up, especially since it's meant to be reused.
• In the loaded state the wizard now shows both a bold name ("choose a harness version") and a muted helpText ("which harness version should this endpoint serve?"), while the pending/error/empty branches still render just the original muted <Question>. The header text visibly changes as the versions query resolves. If that's not intentional, consider either dropping name (pass an empty string, or extend FormRadioGroup to make it optional) or rendering an equivalent bold header in the other branches too.

Neither is a correctness issue — feel free to address in a follow-up.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 76.00000% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.08%. Comparing base (831025c) to head (5bd6779).

Files with missing lines	Patch %	Lines
src/components/EndpointWizard.tsx	75.00%	6 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##           refactor    #2197      +/-   ##
============================================
- Coverage     97.09%   97.08%   -0.02%     
============================================
  Files           544      544              
  Lines         37834    37839       +5     
============================================
- Hits          36736    36735       -1     
- Misses         1098     1104       +6     

☔ 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.

[notgitika]

The PR itself LGTM but I would maybe try to address this portion that the harness reviewer added above

In the loaded state the wizard now shows both a bold name ("choose a harness version") and a muted helpText ("which harness version should this endpoint serve?"), while the pending/error/empty branches still render just the original muted . The header text visibly changes as the versions query resolves. If that's not intentional, consider either dropping name (pass an empty string, or extend FormRadioGroup to make it optional) or rendering an equivalent bold header in the other branches too.

[agentcore-devx-automation]

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