nexus/ui/src/components/onboarding/TelegramStep.tsx
Nexus Dev 3a41ec7b9c feat(nexus): design system phase 3 raw utility sweep
Third phase of the DESIGN.md migration. Removes every raw Tailwind
color palette utility (bg-red-*, text-amber-*, border-blue-*, etc.)
from component source and replaces them with the semantic tokens
introduced in phases 1 and 2.

Scope:
  - 84 files touched under ui/src/
  - ~420 raw palette utility instances replaced
  - 23 hardcoded hex fallbacks replaced with var(--token) refs
  - Zero raw palette utilities remain in component source
    (verified with rg '(bg|text|border|ring)-(red|blue|green|amber|
    yellow|cyan|violet|purple|pink|slate|zinc|neutral|sky|teal|
    emerald|indigo|rose|orange|fuchsia)-[0-9]+' ui/src)

Mapping rules applied:
  - red-* -> destructive
  - amber-/yellow-/orange-* -> warning
  - green-/emerald-* -> success
  - blue-/cyan-/sky-* -> primary (info/in-progress) or muted-foreground
  - slate-/gray-/zinc-/neutral-* -> muted / muted-foreground / border
  - violet-/purple-/pink-/indigo-/rose-/teal-* -> collapsed to
    primary or muted (most were one-off decorative choices, not
    role-bearing). Role-bearing uses go through lib/agent-role-colors
    which was rewritten in phase 2.
  - Opacity modifiers preserved (/10, /15, /20, etc.)
  - dark: variant duplicates removed (theme tokens auto-switch)

Hardcoded hex fallbacks fixed:
  - #6366f1 (indigo) -> var(--primary) / var(--volt)
  - #64748b (slate) -> var(--muted-foreground) / var(--silver)
  - #4f46e5 (indigo) -> var(--primary)
  - #89b4fa (old Catppuccin blue) -> var(--primary) / #faff69
  - OrgChart status dots (#22d3ee/#4ade80/#facc15/#f87171/#a3a3a3)
    -> var(--primary) / var(--success) / var(--warning) /
    var(--destructive) / var(--muted-foreground) per status
  - VoiceWaveform fallback #89b4fa -> #faff69 (volt)

Legitimate hex values left untouched (12 total):
  - lib/color-contrast.ts WCAG reference constants
  - lib/worktree-branding.ts contrast fallback references
  - lib/mention-chips.ts runtime-generated SVG fills
  - context/ThemeContext.tsx theme metadata brand hexes
  - components/ThemeSeedInput.tsx user-facing hex picker

Ambiguous decisions (flagged for visual QA):
  - AgentDetail.tsx invocation-source badges (timer/assignment/
    on_demand) collapsed to primary/muted — visual distinction
    is reduced, labels still differ. Consider chart-role slots
    if differentiation matters.
  - AgentDetail.tsx mixed-opacity amber banners: bg-warning/60
    against new warning base reads heavier than original amber-50
    base.
  - Live-state dots in KanbanBoard/AgentDetail: bg-blue-* ->
    bg-primary — will glow volt in dark mode, probably desirable.

Verification:
  - npx tsc --noEmit in ui/ — zero errors introduced. Pre-existing
    errors in AgentConfigForm, command.tsx, useKeyboardShortcuts,
    usePiperTts, useVadRecorder, PersonalAssistant remain, all
    unrelated to color work.
  - Dev server on :6100 returns 200.

Not changed in this commit:
  - ui/src/lib/company-routes.ts — separate routing fix for broken
    Assistant/ContentStudio/Convert links, committed next.
  - Test files — a few will need assertion updates but are out of
    phase 3 scope.

Phase 4 follow-ups (rounded-xl/2xl collapse, soft shadow removal,
gradient removal) noted in .planning/AUDIT-RADIUS-SHADOWS.md.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-10 17:40:32 +00:00

159 lines
4.9 KiB
TypeScript

// [nexus] Phone access onboarding step — Telegram bridge with BotFather guided setup
import { useState } from "react";
import { Button } from "@/components/ui/button";
import { Input } from "@/components/ui/input";
import { cn } from "@/lib/utils";
interface TelegramStepProps {
onNext: () => void;
onBack: () => void;
}
export function TelegramStep({ onNext, onBack }: TelegramStepProps) {
const [token, setToken] = useState("");
const [validating, setValidating] = useState(false);
const [botUsername, setBotUsername] = useState<string | null>(null);
const [error, setError] = useState<string | null>(null);
async function handleValidate() {
if (!token.trim()) return;
setValidating(true);
setError(null);
setBotUsername(null);
try {
const res = await fetch("/api/telegram/token", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({ token: token.trim() }),
});
if (res.ok) {
const data = await res.json();
setBotUsername(data.botUsername ?? data.bot_username ?? null);
} else {
let msg = "Invalid token";
try {
const data = await res.json();
if (data?.error) msg = data.error;
} catch {
// ignore parse errors
}
setError(msg);
}
} catch {
setError("Could not reach the server. Check your connection and try again.");
} finally {
setValidating(false);
}
}
return (
<div className="flex flex-col gap-6">
{/* Telegram as current option */}
<div className="flex flex-col gap-4">
<p className="text-sm font-medium">Telegram Bot</p>
{/* BotFather instructions */}
<div className="flex flex-col gap-3">
<p className="text-sm text-muted-foreground">Set up your bot in 4 steps:</p>
<ol className="flex flex-col gap-3 list-none pl-0">
{[
<>Open Telegram and search for <span className="font-mono text-xs bg-muted px-1.5 py-0.5 rounded">@BotFather</span></>,
<>Send <span className="font-mono text-xs bg-muted px-1.5 py-0.5 rounded">/newbot</span> and follow the prompts to create a bot</>,
<>Copy the bot token -- it looks like <span className="font-mono text-xs bg-muted px-1.5 py-0.5 rounded">123456:ABC-DEF...</span></>,
"Paste the token below and click Validate",
].map((instruction, i) => (
<li key={i} className="flex items-start gap-3 text-sm text-muted-foreground">
<span className="flex h-6 w-6 shrink-0 items-center justify-center rounded-full bg-muted text-xs font-medium text-foreground">
{i + 1}
</span>
<span className="mt-0.5">{instruction}</span>
</li>
))}
</ol>
</div>
{/* Token input */}
<div className="flex flex-col gap-2">
<label htmlFor="telegram-token" className="text-sm font-medium leading-none">
Bot token
</label>
<Input
id="telegram-token"
type="text"
placeholder="Paste bot token here"
value={token}
onChange={(e) => {
setToken(e.target.value);
setBotUsername(null);
setError(null);
}}
disabled={validating}
autoComplete="off"
className="font-mono text-sm"
/>
{/* Success state */}
{botUsername && (
<p className={cn("text-sm", "text-[color:var(--chart-2)]")}>
Connected to @{botUsername}
</p>
)}
{/* Error state */}
{error && (
<p className="text-sm text-destructive bg-destructive/10 rounded-md px-3 py-2">
{error}
</p>
)}
</div>
</div>
{/* Future bridges note */}
<p className="text-sm text-muted-foreground">
Discord and WhatsApp bridges coming in a future update.
</p>
{/* Actions */}
<div className="flex flex-col gap-2">
<Button
type="button"
onClick={handleValidate}
disabled={!token.trim() || validating}
variant="outline"
className="w-full"
>
{validating ? "Validating..." : "Validate Token"}
</Button>
<Button
type="button"
onClick={onNext}
disabled={!botUsername}
className="w-full"
>
Continue
</Button>
<Button
type="button"
variant="ghost"
onClick={onNext}
className="w-full"
>
Skip
</Button>
<Button
type="button"
variant="ghost"
onClick={onBack}
className="w-full"
>
Back
</Button>
</div>
</div>
);
}