[UMBRELLA ☂️] Asgardeo JavaScript SDK Suite – Framework & Platform Coverage

## Overview

This is an umbrella tracking issue for the **Asgardeo SDK Suite**, covering framework- and platform-specific SDKs.
The goal is to provide consistent, first-class developer experiences across popular JavaScript runtimes, frameworks, and meta-frameworks.

This issue tracks the current coverage, gaps, and related sub-issues for individual SDKs.

## SDK Coverage & Status

### Core & Runtime SDKs
- [x] **JavaScript SDK** (Core / Framework-agnostic)
- [x] **Browser SDK**
- [x] **Node.js SDK**
- [x] **Express.js SDK**

### Framework SDKs
- [x] **React SDK**
↳ https://github.com/asgardeo/javascript/issues/58
- [x] **Next.js SDK**
↳ https://github.com/asgardeo/javascript/issues/67
- [ ] **Vue.js SDK**
↳ https://github.com/asgardeo/javascript/issues/349
- [ ] **Nuxt SDK**
↳ https://github.com/asgardeo/javascript/issues/350

### Integrations
- [x] **React Router SDK**
- [x] **TanStack Router SDK**
↳ https://github.com/asgardeo/javascript/issues/152
- [ ] **`@next/auth` SDK**
↳ https://github.com/asgardeo/javascript/issues/364

## Goals

- Ensure feature parity and consistent DX across all SDKs
- Provide framework-native abstractions where applicable
- Align APIs, configuration patterns, and documentation across the SDK suite
- Enable scalable expansion as new frameworks gain adoption

## Scope

This umbrella issue is intended for:
- Tracking SDK coverage and gaps
- Linking related feature / implementation issues
- Aligning roadmap discussions across the SDK suite

Individual SDKs should be discussed and implemented in their respective linked issues.

Start by reviewing the linked issues for Vue (#349), Nuxt (#350), and @next/auth (#364), along with the checked-off SDK links to understand current coverage. No files, tests, or entry points are named here; completion is limited to tracking gaps and linking individual implementation issues, so this is not a standalone first contribution.

Written by the indexing model from the issue text.