PAB-25: scope Nevermind auth by backend origin

[pablopunk]

This PR scopes Nevermind authentication credentials by backend origin, allowing each backend environment (e.g., production, preview, custom) to maintain its own independent auth snapshot rather than sharing a single global credential.

Key changes:

• Per-origin auth storage: Auth credentials are now stored in a new nevermind-auth-by-origin.json file that maps each backend base URL to its own StoredAuth entry, replacing the previous single-snapshot nevermind-auth.json file.

• Active origin tracking: A new setActiveNevermindAuthBaseUrl function sets the currently active backend origin. All auth reads, writes, and clears are scoped to that origin. The main process calls this function on startup, during sign-in, deep-link auth, environment switches, and whenever the active base URL changes.

• Legacy migration: On first read, if the new per-origin store is empty and a legacy single-auth file exists, it is automatically migrated into the new store format and the old file is renamed to .bak. Corrupt legacy files are left untouched.

• Selective sign-out: clearNevermindAuth now removes only the active origin's entry from the store instead of deleting the entire auth file, preserving credentials for other backends.

• Backend switching: Switching backend environments no longer unconditionally signs out and re-signs in. Instead, it reuses existing stored credentials for the target origin if available, only prompting a fresh sign-in when no credentials exist for that origin.

• Tests: New test suite covering legacy migration, corrupt file handling, migration idempotency, and per-origin credential isolation.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nvm	Ready	Preview, Comment	Jul 12, 2026 4:47pm

[kody-ai]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	❌
Security	✅
Business Logic	❌

Access your configuration settings here.

​