Clarify credential storage wording across authentication UI and docs (#49361)

## Why

Credentials can use a keyring backend, so describing all login and logout operations as reads or writes to `auth.json` is misleading.

## What changed

- Remove the API-key onboarding claim that keys are stored in `auth.json`.
- Describe authentication storage and credential-removal errors in terms of stored credentials and the selected backend.
- Label the doctor output's auth-file path as the file backend or fallback, and document why startup checks also consider `config.toml` when credentials may be in a keyring.

## Testing

Add API-key entry snapshots for terminal widths of 80 and 40 columns.

GitOrigin-RevId: 87189f422448b88721ea2d7448930ece63102803
This commit is contained in:
Celia Chen
2026-09-29 20:46:44 +00:00
committed by copyberry
parent 995138d71a
commit 94d642d8b4
6 changed files with 73 additions and 14 deletions
+1
View File
@@ -750,6 +750,7 @@ fn value<'a>(parsed: &'a [ParsedDetail], label: &str) -> Option<&'a str> {
fn display_label(label: &str) -> String {
match label {
"auth file" => "auth.json path (file backend/fallback)",
"codex-linux-sandbox helper" => "linux helper",
"optional reachability failed" => "optional reachability",
"check for update on startup" => "startup update check",