# JarvisJr Web — Vercel Deployment Roadmap

> **App:** `jarvisjr-web`
> **Repo:** `learning_ai_jarvis_jr` → `web/`
> **Status:** 🔴 Blocked — `file:` ref

---

## Current State

- **Framework:** Next.js 16.1.6, React 19.2.3, TailwindCSS v4
- **Output:** Vercel-aware
- **Dependencies:** 6 `@bytelyst/*` — **1 via `file:` ref** (`ui`), 5 via Gitea
- **Build:** `next build --webpack`
- **Client-side focused** — dashboard, history, progress, store, settings pages

## Gaps to Fix

### Gap 1: Convert `file:` ref to registry ref (~5 min)

**File:** `web/package.json`

```diff
- "@bytelyst/ui": "file:../../learning_ai_common_plat/packages/ui",
+ "@bytelyst/ui": "^0.1.0",
```

- [ ] Update `package.json`
- [ ] Run `pnpm install`
- [ ] Verify `pnpm build` passes

### Gap 2: Registry Access on Vercel (~5 min)

Once Caddy is configured on the Azure VM (see [SECURE_API_EXPOSURE.md](../single_azure_vm/docker/SECURE_API_EXPOSURE.md)), Gitea will be accessible at `https://gitea.bytelyst.com`.

- [ ] Update `.npmrc`:
  ```
  @bytelyst:registry=https://gitea.bytelyst.com/api/packages/ByteLyst/npm/
  //gitea.bytelyst.com/api/packages/ByteLyst/npm/:_authToken=${GITEA_NPM_TOKEN}
  ```
- [ ] Set `GITEA_NPM_TOKEN` as a Vercel environment variable

## Deployment Steps

### Step 1: Fix `file:` ref (~5 min)

### Step 2: Fix registry access (~5 min)

### Step 3: Create Vercel Project (~5 min)

- [ ] Connect `learning_ai_jarvis_jr` repo
- [ ] Set **Root Directory** to `web`
- [ ] Framework preset: **Next.js**

### Step 4: Environment Variables (~5 min)

- [ ] `NEXT_PUBLIC_PLATFORM_URL` = `https://api.bytelyst.com/platform`
- [ ] `NEXT_PUBLIC_BACKEND_URL` = `https://api.bytelyst.com/jarvisjr`

### Step 5: Verify (~5 min)

- [ ] Test dashboard page loads
- [ ] Verify agent card grid renders
- [ ] Test sidebar navigation

### Step 6: Domain (~5 min)

- [ ] Add custom domain (e.g., `app.jarvisjr.app`)

## Estimated Total Effort: ~30 minutes
