Prod fixes

[khaliqgant]

Summary

Production fixes for routing issues and WebSocket stability.

1. Fix /api/repos/accessible and /api/repos/search returning 404

Problem: Express was matching /accessible and /search as the :id parameter in the /:id wildcard route, returning 404.

Solution: Moved specific routes (/accessible, /search) before the /:id wildcard in repos.ts. Added clear comment marking the wildcard routes section.

Files: src/cloud/api/repos.ts

2. Fix user presence constantly flipping online/offline

Problem: Users were rapidly cycling between online/offline status every second.

Root cause: In App.tsx, the currentUser object passed to usePresence was recreated on every render, causing callbacks to be recreated and effects to re-run (disconnect/reconnect).

Solution:

• Memoized the presenceUser object in App.tsx using useMemo
• Refactored usePresence hook to use refs instead of direct state in callbacks

Files: src/dashboard/react-components/App.tsx, src/dashboard/react-components/hooks/usePresence.ts

3. Fix /api/workspaces/:id/members and /api/invites returning 404

Problem: teamsRouter was mounted at /api/teams, but its routes define full paths like /workspaces/:workspaceId/members.

Solution: Changed mount path from /api/teams to /api.

Files: src/cloud/server.ts

4. Connected providers checkmarks on onboarding page

Shows checkmarks next to already-authenticated providers.

Files: src/dashboard/app/app/page.tsx

Test plan

• Verify /api/repos/accessible returns repository list
• Verify /api/repos/search?q=test returns search results
• Verify user presence is stable (no rapid online/offline cycling)
• Verify /api/workspaces/:id/members returns member list
• Verify /api/invites returns pending invitations

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR fixes critical production issues affecting routing, WebSocket stability, and database schema updates for billing integration.

Key Changes:

• Fixed Express route matching issues causing 404 errors for specific API endpoints
• Resolved WebSocket reconnection loops by memoizing user objects and using refs in hooks
• Updated database schema to support Stripe customer IDs for billing

Reviewed changes

Copilot reviewed 13 out of 14 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/cloud/api/repos.ts	Relocated /accessible and /search routes before wildcard /:id route to fix 404 errors
src/cloud/server.ts	Changed teams router mount point from /api/teams to /api to match route definitions
src/dashboard/react-components/hooks/usePresence.ts	Refactored to use refs instead of direct state dependencies to prevent reconnection loops
src/dashboard/react-components/App.tsx	Memoized presence user object to prevent unnecessary re-renders and WebSocket reconnections
src/dashboard/app/app/page.tsx	Added connected provider checkmarks on onboarding page
src/cloud/db/schema.ts	Added stripeCustomerId column to users table
src/cloud/db/migrations/*	Migration files for adding Stripe customer ID and dropping SSH fields
src/cloud/api/billing.ts	Updated billing endpoints to use database-stored user data instead of session
.trajectories/*	Trajectory tracking files for completed work

Comments suppressed due to low confidence (1)

src/cloud/db/migrations/0008_stripe_customer_id.sql:1

• The migration drops SSH-related columns from workspaces table, but the migration name only references 'stripe_customer_id'. Consider either splitting this into separate migrations or updating the migration name to reflect all changes (e.g., '0008_add_stripe_customer_id_drop_ssh').

ALTER TABLE "users" ADD COLUMN "stripe_customer_id" varchar(255);--> statement-breakpoint

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The ref initialization and update are separated, which could lead to subtle bugs. Consider moving the ref declaration closer to where it's used (around line 276) or adding a comment explaining why it's declared early but also updated later in the hook.

Suggested change

	currentUserRef.current = currentUser; // Keep ref in sync with prop
	// Keep a mutable reference to the latest `currentUser` so that callbacks
	// defined later in this hook (e.g. the WebSocket connect handler) can read
	// the up-to-date value without needing to be recreated on every render.
	currentUserRef.current = currentUser;

[Copilot]

The condition connectedProviders.includes('openai') appears twice in this file (lines 551, 558-559, 570, 575, and 604) specifically for the 'codex' provider. This hardcoded relationship between codex and openai should be extracted into a helper function or constant to improve maintainability and make the relationship explicit.