Merge pull request asgardeo#2540 from brionmario/refactor-thunder-rebrand-4

[Chunk 1] Rebrand `Thunder` -> `ThunderID`

Author: brionmario

.agent/skills/console/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: console
-description: Navigate and interact with the Thunder Console UI. Use when exploring the Thunder admin console, testing UI changes, creating users/applications/roles, or debugging the frontend.
+description: Navigate and interact with the ThunderID Console UI. Use when exploring the ThunderID admin console, testing UI changes, creating users/applications/roles, or debugging the frontend.
 allowed-tools: Bash(playwright-cli:*) Bash(npx:*)
 ---
 
-# Thunder Console Navigation with playwright-cli
+# ThunderID Console Navigation with playwright-cli
 
 ## Resolving the Console Base URL
 
@@ -13,30 +13,30 @@ Before running any commands, determine the console base URL. Do NOT hardcode a U
 1. **Check `deployment.yaml`** at `backend/cmd/server/repository/conf/deployment.yaml` for the `server.hostname` and `server.port`. If the backend is serving the console (production mode), the URL is `https://{hostname}:{port}/console`.
 2. **Check `vite.config.ts`** at `frontend/apps/console/vite.config.ts` for the development server `PORT` (default `5191`) and `HOST` (default `localhost`). If the frontend development server is running separately, the URL is `https://{HOST}:{PORT}/console`.
 3. **Check environment variables**: `PORT`, `HOST`, or `BASE_URL` may override the defaults.
-4. **If unable to resolve**, ask the user for the Thunder Console URL.
+4. **If unable to resolve**, ask the user for the ThunderID Console URL.
 
 Use the resolved URL as `{CONSOLE_URL}` in all commands below (e.g., `{CONSOLE_URL}`).
 
 ## Quick Start
 
 ```bash
 # Open Console (redirects to sign-in gate)
-playwright-cli open {CONSOLE_URL} -s=thunder
+playwright-cli open {CONSOLE_URL} -s=thunderid
 
 # After authenticating (see below), navigate directly
-playwright-cli goto {CONSOLE_URL}/users -s=thunder
+playwright-cli goto {CONSOLE_URL}/users -s=thunderid
 
 # Snapshot the page to see element refs
-playwright-cli snapshot -s=thunder
+playwright-cli snapshot -s=thunderid
 
 # Interact with elements using refs from snapshot
-playwright-cli click e15 -s=thunder
+playwright-cli click e15 -s=thunderid
 
 # Take a screenshot
-playwright-cli screenshot -s=thunder
+playwright-cli screenshot -s=thunderid
 
 # Close the browser
-playwright-cli close -s=thunder
+playwright-cli close -s=thunderid
 ```
 
 ## Prerequisites
@@ -47,11 +47,11 @@ If `playwright-cli` is not installed:
 npm install -g @playwright/cli@latest
 ```
 
-All commands use the named session `-s=thunder` so the browser persists across commands.
+All commands use the named session `-s=thunderid` so the browser persists across commands.
 
 ## Authentication
 
-Thunder Console requires authentication. The sign-in form is dynamically rendered by the Asgardeo SDK, so always use `snapshot` to get element refs before interacting.
+ThunderID Console requires authentication. The sign-in form is dynamically rendered by the Asgardeo SDK, so always use `snapshot` to get element refs before interacting.
 
 Default credentials: `admin` / `admin`
 
@@ -60,42 +60,42 @@ Default credentials: `admin` / `admin`
 ```bash
 # 0. Accept self-signed certs first (see Troubleshooting for details)
 #    Open blank session, navigate to each origin, click through cert warnings
-playwright-cli open -s=thunder
+playwright-cli open -s=thunderid
 # Accept backend cert, then console cert, then gate cert (see Troubleshooting)
 
 # 1. Navigate to the console (auto-redirects to /gate/signin)
-playwright-cli goto {CONSOLE_URL} -s=thunder
+playwright-cli goto {CONSOLE_URL} -s=thunderid
 
 # 2. Snapshot to see the login form elements
-playwright-cli snapshot -s=thunder
+playwright-cli snapshot -s=thunderid
 
 # 3. Fill username (use the ref from snapshot for the username input)
-playwright-cli fill <username-ref> "admin" -s=thunder
+playwright-cli fill <username-ref> "admin" -s=thunderid
 
 # 4. Fill password (use the ref from snapshot for the password input)
-playwright-cli fill <password-ref> "admin" -s=thunder
+playwright-cli fill <password-ref> "admin" -s=thunderid
 
 # 5. Click Sign In (use the ref from snapshot for the submit button)
-playwright-cli click <submit-ref> -s=thunder
+playwright-cli click <submit-ref> -s=thunderid
 
 # 6. Verify redirect to console home
-playwright-cli snapshot -s=thunder
+playwright-cli snapshot -s=thunderid
 
 # 7. Save auth state for reuse
-playwright-cli state-save thunder-auth -s=thunder
+playwright-cli state-save thunderid-auth -s=thunderid
 ```
 
 ### Reuse Saved Auth
 
 ```bash
-playwright-cli open -s=thunder
-playwright-cli state-load thunder-auth -s=thunder
-playwright-cli goto {CONSOLE_URL} -s=thunder
+playwright-cli open -s=thunderid
+playwright-cli state-load thunderid-auth -s=thunderid
+playwright-cli goto {CONSOLE_URL} -s=thunderid
 ```
 
 ## Route Map
 
-The Thunder Console base path is `/console`. Append routes below to the resolved `{CONSOLE_URL}`. The sidebar is organized into categories.
+The ThunderID Console base path is `/console`. Append routes below to the resolved `{CONSOLE_URL}`. The sidebar is organized into categories.
 
 ### Sidebar Navigation
 
@@ -147,82 +147,82 @@ The Thunder Console base path is `/console`. Append routes below to the resolved
 ### Navigate to a Page
 
 ```bash
-playwright-cli goto {CONSOLE_URL}/users -s=thunder
-playwright-cli snapshot -s=thunder
+playwright-cli goto {CONSOLE_URL}/users -s=thunderid
+playwright-cli snapshot -s=thunderid
 ```
 
 ### Navigate via Sidebar
 
 ```bash
 # Snapshot to see sidebar element refs
-playwright-cli snapshot -s=thunder
+playwright-cli snapshot -s=thunderid
 # Click a sidebar item by its ref
-playwright-cli click <sidebar-item-ref> -s=thunder
+playwright-cli click <sidebar-item-ref> -s=thunderid
 ```
 
 ### Create a Resource (e.g., User)
 
 ```bash
 # Navigate to users list
-playwright-cli goto {CONSOLE_URL}/users -s=thunder
-playwright-cli snapshot -s=thunder
+playwright-cli goto {CONSOLE_URL}/users -s=thunderid
+playwright-cli snapshot -s=thunderid
 
 # Click the "Add User" or create button
-playwright-cli click <create-button-ref> -s=thunder
-playwright-cli snapshot -s=thunder
+playwright-cli click <create-button-ref> -s=thunderid
+playwright-cli snapshot -s=thunderid
 
 # Fill the creation form fields using refs from snapshot
-playwright-cli fill <field-ref> "value" -s=thunder
+playwright-cli fill <field-ref> "value" -s=thunderid
 
 # Submit
-playwright-cli click <submit-ref> -s=thunder
-playwright-cli snapshot -s=thunder
+playwright-cli click <submit-ref> -s=thunderid
+playwright-cli snapshot -s=thunderid
 ```
 
 ### Search in a List
 
 ```bash
-playwright-cli goto {CONSOLE_URL}/users -s=thunder
-playwright-cli snapshot -s=thunder
-playwright-cli fill <search-input-ref> "john" -s=thunder
-playwright-cli snapshot -s=thunder
+playwright-cli goto {CONSOLE_URL}/users -s=thunderid
+playwright-cli snapshot -s=thunderid
+playwright-cli fill <search-input-ref> "john" -s=thunderid
+playwright-cli snapshot -s=thunderid
 ```
 
 ### Inspect an Element
 
 ```bash
-playwright-cli eval "el => el.getAttribute('data-testid')" <ref> -s=thunder
-playwright-cli eval "el => el.textContent" <ref> -s=thunder
+playwright-cli eval "el => el.getAttribute('data-testid')" <ref> -s=thunderid
+playwright-cli eval "el => el.textContent" <ref> -s=thunderid
 ```
 
 ### Take a Screenshot
 
 ```bash
-playwright-cli screenshot -s=thunder
-playwright-cli screenshot --filename=console-users.png -s=thunder
+playwright-cli screenshot -s=thunderid
+playwright-cli screenshot --filename=console-users.png -s=thunderid
 ```
 
 ## Troubleshooting
 
-- **Redirected to `/gate/signin`**: Auth expired. Re-authenticate or run `playwright-cli state-load thunder-auth -s=thunder`.
-- **Elements not found in snapshot**: Page may still be loading. Wait a moment and run `playwright-cli snapshot -s=thunder` again.
-- **HTTPS certificate errors**: Thunder uses self-signed certificates on multiple origins (gate, console, backend). The browser will block navigation with `ERR_CERT_AUTHORITY_INVALID`. To bypass, open a blank session first, then navigate via JS `eval` to trigger Chrome's interstitial error page, and click through it:
+- **Redirected to `/gate/signin`**: Auth expired. Re-authenticate or run `playwright-cli state-load thunderid-auth -s=thunderid`.
+- **Elements not found in snapshot**: Page may still be loading. Wait a moment and run `playwright-cli snapshot -s=thunderid` again.
+- **HTTPS certificate errors**: ThunderID uses self-signed certificates on multiple origins (gate, console, backend). The browser will block navigation with `ERR_CERT_AUTHORITY_INVALID`. To bypass, open a blank session first, then navigate via JS `eval` to trigger Chrome's interstitial error page, and click through it:
 
   ```bash
   # 1. Open a blank browser session
-  playwright-cli open -s=thunder
+  playwright-cli open -s=thunderid
 
   # 2. Navigate to the target URL (triggers cert error page)
-  playwright-cli eval "window.location.assign('{CONSOLE_URL}')" -s=thunder
+  playwright-cli eval "window.location.assign('{CONSOLE_URL}')" -s=thunderid
 
   # 3. Click through the cert warning
-  playwright-cli snapshot -s=thunder          # find the "Advanced" button ref
-  playwright-cli click <advanced-ref> -s=thunder
-  playwright-cli snapshot -s=thunder          # find the "Proceed to localhost (unsafe)" link ref
-  playwright-cli click <proceed-ref> -s=thunder
+  playwright-cli snapshot -s=thunderid          # find the "Advanced" button ref
+  playwright-cli click <advanced-ref> -s=thunderid
+  playwright-cli snapshot -s=thunderid          # find the "Proceed to localhost (unsafe)" link ref
+  playwright-cli click <proceed-ref> -s=thunderid
   ```
 
   **Important**: You must accept certs for **each origin** the console talks to. The console redirects to the gate for auth, which calls the backend. If the backend cert is not accepted in the same browser session, API calls will silently fail. Resolve the backend port from `deployment.yaml` (`server.port`) and the gate port from the console's runtime config. Accept certs for each origin before proceeding.
 
 - **Login form not visible**: The Asgardeo SDK renders the form dynamically. Take a snapshot after a brief wait. If you see a loading spinner, snapshot again after a few seconds.
-- **Session lost**: Run `playwright-cli list` to check active sessions. Start a new one with `playwright-cli open -s=thunder`.
+- **Session lost**: Run `playwright-cli list` to check active sessions. Start a new one with `playwright-cli open -s=thunderid`.

.github/workflows/pr-builder.yml

@@ -416,7 +416,7 @@ jobs:
         run: |
           cat coverage/console/console-coverage-shard-*/lcov.info > coverage/console-merged-lcov.info
 
-      - name: 📊 Upload `@thunder/console` Unit Test Coverage Report to Codecov
+      - name: 📊 Upload `@thunderid/console` Unit Test Coverage Report to Codecov
         uses: codecov/codecov-action@b9fd7d16f6d7d1b5d2bec1a2887e65ceed900238 # v4
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
@@ -426,7 +426,7 @@ jobs:
           name: Frontend Console App Unit Tests
           fail_ci_if_error: false
 
-      - name: 📊 Upload `@thunder/gate` Unit Test Coverage Report to Codecov
+      - name: 📊 Upload `@thunderid/gate` Unit Test Coverage Report to Codecov
         uses: codecov/codecov-action@b9fd7d16f6d7d1b5d2bec1a2887e65ceed900238 # v4
         with:
           token: ${{ secrets.CODECOV_TOKEN }}

.vscode/settings.json

@@ -1,4 +1,5 @@
 {
+  "files.insertFinalNewline": true,
   "[typescriptreact][javascriptreact][typescript][javascript][json]": {
     "editor.formatOnSave": true,
     "editor.defaultFormatter": "esbenp.prettier-vscode",

AGENTS.md

@@ -1,6 +1,6 @@
 # Project Overview
 
-Thunder is a lightweight user and identity management product. Go backend + React frontend in a monorepo. It provides authentication and authorization via OAuth2/OIDC, flexible orchestration flows, and individual auth mechanisms (password, passwordless, social login).
+ThunderID is a lightweight user and identity management product. Go backend + React frontend in a monorepo. It provides authentication and authorization via OAuth2/OIDC, flexible orchestration flows, and individual auth mechanisms (password, passwordless, social login).
 
 - [ARCHITECTURE.md](ARCHITECTURE.md)
 - For build and running - [Makefile](Makefile) and [README.md](README.md)

ARCHITECTURE.md

@@ -22,7 +22,7 @@ backend/internal/
 frontend/apps/
   gate/         # login/registration SPA  (@asgardeo/react — app-native mode)
   console/      # admin SPA               (@asgardeo/react — redirect mode)
-frontend/packages/      # @thunder/contexts · design · hooks · i18n · utils · types · logger
+frontend/packages/      # @thunderid/contexts · design · hooks · i18n · utils · types · logger
 samples/apps/           # react-sdk-sample · react-api-based-sample · react-vanilla-sample
 ```
 

build.ps1

@@ -1798,7 +1798,7 @@ function Run-Frontend {
 
         Write-Host "Starting frontend applications in the background..."
         # Start frontend processes in background
-        $frontendProcess = Start-Process -FilePath "cmd.exe" -ArgumentList "/c", "pnpm", "-r", "--parallel", "--filter", "@thunder/console", "--filter", "@thunder/gate", "dev" -PassThru -NoNewWindow
+        $frontendProcess = Start-Process -FilePath "cmd.exe" -ArgumentList "/c", "pnpm", "-r", "--parallel", "--filter", "@thunderid/console", "--filter", "@thunderid/gate", "dev" -PassThru -NoNewWindow
         $script:FRONTEND_PID = $frontendProcess.Id
     }
     finally {

build.sh

@@ -1164,7 +1164,7 @@ function run_frontend() {
 
     echo "Starting frontend applications in the background..."
     # Start frontend processes in background
-    pnpm -r --parallel --filter "@thunder/console" --filter "@thunder/gate" dev &
+    pnpm -r --parallel --filter "@thunderid/console" --filter "@thunderid/gate" dev &
     FRONTEND_PID=$!
 
     # Return to script directory

docs/AGENTS.md

@@ -1,19 +1,19 @@
 ---
 title: AGENTS
-description: AI agents should use this file when creating and reviewing documentation content for Thunder. It contains the standards, guidelines, and requirements that must be followed to ensure high-quality documentation.
+description: AI agents should use this file when creating and reviewing documentation content for ThunderID. It contains the standards, guidelines, and requirements that must be followed to ensure high-quality documentation.
 ---
 
-# Thunder Documentation Creation Instructions
+# ThunderID Documentation Creation Instructions
 
-Follow these instructions when creating new documentation content for Thunder. Adhere to all guidelines to ensure consistency, clarity, and quality.
+Follow these instructions when creating new documentation content for ThunderID. Adhere to all guidelines to ensure consistency, clarity, and quality.
 
 ## Scope and Boundaries
 
 
 ### Audience
 
-- Your primary audience is Thunder users, including system administrators, developers, and IT professionals.
-- Assume the audience has a basic understanding of IT concepts but may be unfamiliar with Thunder specifics.
+- Your primary audience is ThunderID users, including system administrators, developers, and IT professionals.
+- Assume the audience has a basic understanding of IT concepts but may be unfamiliar with ThunderID specifics.
 - Avoid jargon and explain concepts clearly.
 
 ### What You Must Do
@@ -26,7 +26,7 @@ Follow these instructions when creating new documentation content for Thunder. A
 
 ## Authoring Standards
 
-You must follow these standards when creating documentation content for Thunder.
+You must follow these standards when creating documentation content for ThunderID.
 
 ### Voice and Tone
 
@@ -46,11 +46,11 @@ You must follow these standards when creating documentation content for Thunder.
 - Do not alternate between long and short forms unless formally introduced.
 
 **Correct:**
-- Thunder Console  
+- ThunderID Console  
 - Passkey Authentication  
 
 **Incorrect:**
-- Thunder console  
+- ThunderID console  
 - Console  
 - Passkey auth  
 
@@ -313,7 +313,7 @@ When Vale feedback is provided through CI checks:
 
 ## Vocabulary Guidelines
 
-Strictly follow these vocabulary guidelines when writing Thunder documentation.
+Strictly follow these vocabulary guidelines when writing ThunderID documentation.
 
 ### Use of "Multiple"
 

docs/README.md

@@ -1,3 +1,3 @@
-# Thunder Documentation ⚡
+# ThunderID Documentation ⚡
 
-Documentation for **Thunder** - a modern identity management suite. This documentation covers installation, configuration, development, and contribution guidelines for the Thunder platform.
+Documentation for **ThunderID** - a modern identity management suite. This documentation covers installation, configuration, development, and contribution guidelines for the ThunderID platform.

docs/content/community/contributing/contributing-code/configure-and-run.mdx

@@ -249,7 +249,7 @@ cors:
 
 ```bash
 cd frontend
-pnpm --filter @thunder/gate dev
+pnpm --filter @thunderid/gate dev
 ```
 
 ### Setting up the <ProductName /> Console Application
@@ -298,7 +298,7 @@ cors:
 6. Run the <ProductName /> Console application.
 
 ```bash
-pnpm --filter @thunder/console dev
+pnpm --filter @thunderid/console dev
 ```
 
 This will run the <ProductName /> Console application on `https://localhost:5191/console`.