[Pepps233]

Summary

Reject remaining Radius configuration and registration paths with clear migration instructions, and prevent stale Radius code from entering release payloads.

Reasoning

Removing a built-in integration alone leaves custom registrations and legacy selections able to restore access or fail without useful guidance.
Radius is prohibited in every environment; inactive credentials remain available for local cleanup.

Changes

• Reject Radius registrations, custom configuration, CLI selections, saved defaults, resumed sessions, and credential export.
• Report expected startup failures as concise error messages.
• Verify Radius is absent from both login methods while retaining local credential deletion.
• Replace transport fixtures with a neutral backend.
• Reject former integration modules and authentication markers in packaged payloads.
• Supersede historical approvals and document migration and validation.

Testing

• npm run check, the complete isolated ./test.sh, and offline compilation passed.
• Focused model-resolution and auth tests passed; the payload suite passed all 47 tests.
• Installed npm tarball hashes matched the reviewed archive.
• Installed CLI validation passed help, version, model listing, controlled prompt/reply, both login methods, legacy-configuration rejection, and clean exit.
• No Radius service, real provider credential, or paid inference was used.