fix(docs): update deployment documentation and conversation ui

[Israeltheminer]

• Change internal network name from poc2_internal to tale_internal
• Update Docker image references from ghcr.io/your-org/poc2/tale-rag:latest to ghcr.io/your-org/tale/tale-rag:latest
• Modify GitHub issues link to point to the correct repository
• Enhance Conversations component to show an empty state when no conversations and no email providers are configured
• Adjust SignUpForm to conditionally display password requirements

Summary by CodeRabbit

Release Notes

• Documentation

  • Updated deployment guides with current container image references and Docker network naming conventions.

• New Features

  • Added empty-state UI for conversations that prompts users to enable email integration.

• Improvements

  • Password requirements tips in the sign-up form now display only when entering a password, improving clarity.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request introduces updates to support email-based conversations functionality and documentation refactoring. Changes include renaming Docker references and network names from poc2 to tale across deployment documentation; adding a new ActivateConversationsEmptyState React component to prompt users to configure email integrations; modifying the conversations component to fetch email provider data and conditionally render an empty state when no conversations exist and no email provider is configured; and updating the sign-up form to conditionally display password requirements only when a password value is present.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20–30 minutes

• Documentation changes in docs/ are straightforward naming/reference updates (homogeneous refactoring pattern)
• New activate-conversations-empty-state.tsx is a simple, presentational component with minimal logic
• conversations.tsx requires careful review of the emailProviders data fetch logic and the conditional rendering path to ensure the early return for the empty state doesn't inadvertently skip other initialization or side effects
• sign-up-form.tsx conditional rendering change is localized but should be verified to ensure password guidance visibility doesn't negatively impact UX during form interaction
• Verify the routing link in the new component correctly constructs the integrations settings URL with the email tab parameter

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between a492a00 and c9ed0a9.

📒 Files selected for processing (5)

• docs/deployment-modes.md (1 hunks)
• docs/tale-rag-deployment.md (4 hunks)
• services/platform/app/(app)/dashboard/[id]/conversations/components/activate-conversations-empty-state.tsx (1 hunks)
• services/platform/app/(app)/dashboard/[id]/conversations/components/conversations.tsx (4 hunks)
• services/platform/components/auth/sign-up-form.tsx (2 hunks)

🧰 Additional context used

📓 Path-based instructions (5)

**/*

📄 CodeRabbit inference engine (.cursor/rules/workspace_rules.mdc)

Use English only for ALL user-facing content including UI components, labels, buttons, dialogs, forms, toast messages, error messages, success messages, comments, documentation, README files, variable names, function names, and type names

Files:

• docs/deployment-modes.md
• services/platform/app/(app)/dashboard/[id]/conversations/components/conversations.tsx
• docs/tale-rag-deployment.md
• services/platform/components/auth/sign-up-form.tsx
• services/platform/app/(app)/dashboard/[id]/conversations/components/activate-conversations-empty-state.tsx

**/*.{tsx,jsx}

📄 CodeRabbit inference engine (.cursor/rules/figma_rules.mdc)

**/*.{tsx,jsx}: Avoid specifying font-['Inter:Regular',_sans-serif] as it should be the default
Only specify font-family when using non-default fonts like font-['Inter:Medium',_sans-serif]
Ensure font-family matches font-weight (Inter:Regular with font-normal, Inter:Medium with font-medium)
Use leading-normal instead of leading-[normal] in Tailwind classes
Use standard font size classes instead of arbitrary values: text-[12px] → text-xs, text-[14px] → text-sm, text-[16px] → text-base, text-[18px] → text-lg, text-[20px] → text-xl, text-[24px] → text-2xl
Use semantic spacing classes: p-[4px] → p-1, p-[8px] → p-2, m-[4px] → m-1, m-[8px] → m-2
Convert pixel values to rem using the 16px base for width and height measurements: w-[278px] → w-[17.375rem], h-[48px] → h-[3rem], min-w-[120px] → min-w-[7.5rem], max-w-[400px] → max-w-[25rem]
NEVER use hardcoded colors like text-gray-500, bg-gray-100, border-gray-200; ALWAYS use design system semantic colors: text-foreground for primary text, text-muted-foreground for secondary text and icons, bg-background for main backgrounds, bg-muted for subtle backgrounds and hover states, border-border for borders
ALWAYS use the Table component instead of custom flex layouts; use Table, TableHeader, TableBody, TableRow, TableHead, TableCell components with proper column widths using rem units and semantic colors

Files:

• services/platform/app/(app)/dashboard/[id]/conversations/components/conversations.tsx
• services/platform/components/auth/sign-up-form.tsx
• services/platform/app/(app)/dashboard/[id]/conversations/components/activate-conversations-empty-state.tsx

**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (.cursor/rules/workspace_rules.mdc)

**/*.{ts,tsx,js,jsx}: Use Vercel AI SDK with OpenAI - import from 'ai' and '@ai-sdk/openai', never use raw OpenAI SDK or OpenRouter
Never hallucinate API keys - always use environment variables and existing .env configuration
Use camelCase for function names (e.g., getUserData)
Use SCREAMING_SNAKE_CASE for constants (e.g., API_BASE_URL, MAX_RETRIES)
Use feature flags with enums (TypeScript) or const objects (JavaScript) with UPPERCASE_WITH_UNDERSCORE naming
Implement error handling with try-catch pattern: check for result.error and display descriptive toast messages using result.error as title

Files:

• services/platform/app/(app)/dashboard/[id]/conversations/components/conversations.tsx
• services/platform/components/auth/sign-up-form.tsx
• services/platform/app/(app)/dashboard/[id]/conversations/components/activate-conversations-empty-state.tsx

**/app/**/*.tsx

📄 CodeRabbit inference engine (.cursor/rules/workspace_rules.mdc)

In Next.js App Router, use page.tsx as server components by default; use 'use client' only for interactions and state

Files:

• services/platform/app/(app)/dashboard/[id]/conversations/components/conversations.tsx
• services/platform/app/(app)/dashboard/[id]/conversations/components/activate-conversations-empty-state.tsx

**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/workspace_rules.mdc)

**/*.{ts,tsx}: Use kebab-case for file names (e.g., user-profile.tsx)
Use PascalCase for component names (e.g., UserProfile)
Use descriptive messages as toast title (never generic 'Error'), with optional description for additional context only
Follow component structure: 'use client' directive, imports, interface Props, hooks, effects, event handlers, then render
Prioritize data fetching methods in order: Server Actions (preferred), Route Handlers (when needed), Client-side (minimal use)
Use React.memo for expensive components to optimize performance
Use Next.js Image component for all images instead of native img tags
Use dynamic imports for code splitting

Files:

• services/platform/app/(app)/dashboard/[id]/conversations/components/conversations.tsx
• services/platform/components/auth/sign-up-form.tsx
• services/platform/app/(app)/dashboard/[id]/conversations/components/activate-conversations-empty-state.tsx

🧬 Code graph analysis (1)

services/platform/app/(app)/dashboard/[id]/conversations/components/conversations.tsx (1)

services/platform/app/(app)/dashboard/[id]/conversations/components/activate-conversations-empty-state.tsx (1)

• ActivateConversationsEmptyState (9-33)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Build services/platform

🔇 Additional comments (5)

docs/deployment-modes.md (1)

164-164: LGTM! Documentation update aligns with infrastructure rename.

The network name update from poc2_internal to tale_internal is consistent with the broader PR objectives to rename the project infrastructure.

services/platform/components/auth/sign-up-form.tsx (1)

166-184: Good UX improvement! Conditionally showing password requirements reduces visual clutter.

Showing password requirements only when the user starts typing provides a cleaner initial state while still offering guidance when needed. The validation schema (lines 20-29) still enforces all requirements.

docs/tale-rag-deployment.md (1)

174-174: LGTM! Comprehensive documentation updates for the infrastructure rename.

All references have been consistently updated from poc2 to tale:

• Container image paths updated to ghcr.io/your-org/tale/tale-rag:latest
• Network name changed to tale_internal
• Volume name changed to tale_rag-data
• GitHub repository URL updated to tale/issues

These changes align with the PR's objectives and maintain documentation consistency.

Also applies to: 180-180, 287-287, 310-310, 346-346

services/platform/app/(app)/dashboard/[id]/conversations/components/conversations.tsx (1)

75-79: Good implementation of email providers check.

The email providers query follows the same conditional pattern as the conversations query and correctly handles the loading state with optional chaining (emailProviders?.length ?? 0).

Also applies to: 85-85

services/platform/app/(app)/dashboard/[id]/conversations/components/activate-conversations-empty-state.tsx (1)

1-33: LGTM! Well-structured empty state component following all coding guidelines.

The component correctly:

• Uses semantic design system colors (text-muted-foreground, text-foreground, ring-border)
• Uses standard size classes (size-6, size-4, text-lg, text-sm)
• Uses semantic spacing tokens (mb-5, mb-2, my-6, mx-4, px-4, mr-2)
• Implements the Button with asChild pattern for proper Next.js Link integration
• Routes to the integrations page with the ?tab=email query parameter for better UX