fix(web): use uuid for client-generated ids

[iscekic]

Summary

• Replaces browser crypto.randomUUID() calls in Cloud Agent, App Builder, and shared upload client code with the existing uuid package.
• Keeps generated values as UUID v4 strings for attachment paths, upload item IDs, terminal tab IDs, and profile draft IDs while avoiding runtimes where crypto.randomUUID is unavailable.

Verification

N/A

Visual Changes

N/A

Reviewer Notes

• Automated checks run locally: pnpm format, focused web upload tests, web typecheck, and git diff --check.
• Full monorepo typecheck was skipped in favor of the targeted web package check.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

All 7 crypto.randomUUID() calls in client-side React components and hooks are correctly replaced with uuidv4() from the existing uuid package, using a consistent import pattern already established in the codebase.

Files Reviewed (7 files)

• apps/web/src/components/app-builder/AppBuilderChat.tsx
• apps/web/src/components/app-builder/AppBuilderLanding.tsx
• apps/web/src/components/cloud-agent-next/CloudChatPage.tsx
• apps/web/src/components/cloud-agent-next/NewSessionPanel.tsx
• apps/web/src/components/cloud-agent/ProfilesListDialog.tsx
• apps/web/src/hooks/useCloudAgentAttachmentUpload.ts
• apps/web/src/hooks/useImageUpload.ts

---

Fix these issues in Kilo Cloud

---

_{Reviewed by claude-4.6-sonnet-20260217 · 340,476 tokens}

_{Review guidance: REVIEW.md from base branch main}

[RSO]

Ideally we'd have some type of compatibility layer in the lint rules that automatically detects these 🤔