fix(ui): fix model name editing on the model config form

[Valyrian-Code]

Summary

Two related problems with the model name field and its "Edit Auto-Generated Name" pencil button on the model form (/models/new, including ?edit=true):

1. Pencil submitted the form. The button had no explicit type, so as a child of the <form> it defaulted to type="submit" and fired the updateModelConfig action on click — the form saved and navigated away instead of just toggling name editing. Fixed by setting type="button", matching the sibling "fetch models" button.

2. Renaming in edit mode silently did nothing. A ModelConfig's metadata.name is immutable in Kubernetes, so an update can never rename the resource. The pencil is now disabled in edit mode — consistent with the namespace, provider, and model fields, which are already disabled when editing — and a hint clarifies that the name can't be changed after creation.

Fixes #1947

Changes

• ui/src/components/models/new/BasicInfoSection.tsx:
  • add type="button" to the edit-name pencil so it no longer submits the form
  • disable the pencil in edit mode and show a "name can't be changed after creation" hint

Testing

• On /models/new?edit=true, clicking the pencil no longer triggers a network call or form submission.
• In edit mode the name field is read-only with the hint; create mode is unchanged (the auto-generated name is still editable).

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds an explicit button type to prevent unintended form submission when clicking the “edit model name” icon button.

Changes:

• Set type="button" on the edit-model-name button to avoid default submit behavior inside a form.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

This pull request has been marked as stale because of no activity in the last 15 days. It will be closed in the next 5 days unless it is tagged "no stalebot" or other activity occurs.

[Valyrian-Code]

The failing build (app) check is unrelated to this change, it's a QEMU/binfmt emulation failure while building the sandbox-runtime image in the build-kagent-adk step:

installing: amd64 cannot register "/usr/bin/qemu-x86_64" to /proc/sys/fs/binfmt_misc/register: no such file or directory
#36 ERROR: process "... git clone ... sandbox-runtime ... npm run build ..." did not complete successfully: exit code: 132
make: *** [Makefile:283: build-kagent-adk] Error 1

This PR only adds type="button" and an isEditMode guard to a single UI component, so it can't affect the Go app image build. Every other check (go-unit-tests, go-lint, ui build, python, helm, snyk) is green. @peterj would you be able to re-run the failed build (app) job so this can merge? Thanks for the review!