DeepSeek TUI's latest docs make auth-source diagnosis, Nix installs, and auto-mode cost attribution easier to publish correctly

Today's accepted developer signal stays on the TUI track: the official README and install docs now clarify `deepseek auth status`, credential precedence, `auth clear`, a documented Nix path, and how auto routing is billed against the model that actually ran.

Accepted developer update

Today's safe publishable change is again on the DeepSeek TUI track. There is no newer official local-deployment or Claude Code delta strong enough to publish today, but the TUI docs kept getting more operational for real developer setups.

What changed upstream

The newest official README and install docs now close several gaps that older setup posts still leave fuzzy:

Credential-source diagnosis is now documented: the README now tells users to run deepseek auth status to see whether the active key is coming from saved config, keyring, or DEEPSEEK_API_KEY.
Credential cleanup is explicit: the same README now documents deepseek auth clear --provider deepseek as the supported way to remove or rotate a saved key.
Credential precedence is clearer: upstream now says saved config keys take precedence over keyring and environment variables, which matters when a machine keeps using the wrong DeepSeek account.
Nix is now a documented install path: the official install docs now include nix run github:Hmbown/DeepSeek-TUI plus flake examples, so Nix and NixOS users no longer need to rely on an inferred community-only path.
Auto-mode billing is easier to explain correctly: the README now says the route that actually ran is what cost tracking is charged against, even though auto mode begins with a small Flash routing call.

Why this matters for crawlable setup pages

This is not just documentation polish. It changes what a technically trustworthy DeepSeek TUI setup guide should tell readers:

Wrong-key debugging should start with a documented source check, not guesswork.
Teams rotating credentials need an official cleanup command, not just shell-export advice.
Nix users now have a first-party install surface worth indexing directly.
Auto mode can be recommended more confidently when cost attribution is tied to the real routed model.

What we rejected today

DeepSeek local development: the official DeepSeek V4 Flash model card still points to the same vLLM, SGLang, Docker Model Runner, quantization browser, and curl validation baseline already covered in the maintained local-deployment guide.
DeepSeek in Claude Code / Cloud Code: the official DeepSeek integration docs still use the same Anthropic-compatible environment recipe and July 24, 2026 alias-deprecation warning already published on this site on May 20.
Community gateway, GGUF, and Desktop posts: useful discovery leads only, but still below the bar for safe publication without a newer official or reproducible milestone.

Editorial takeaway

Today's public update belongs on the DeepSeek TUI guide, the dedicated /deepseek-tui landing page, and the news stream. It does not affect stocked plans, pricing cards, or any purchasable inventory surface.