feat: add workspaces with isolated channels, members, and invite system

[mahata]

Summary

• Add workspace support with path-based routing (/w/:slug/...), per-workspace admin roles, invite links (1-hour expiry, multi-use), and one Durable Object per workspace for WebSocket connections
• Existing data auto-migrates into a seeded default workspace; new users with no workspaces auto-join default
• All channels, messages, and memberships are fully isolated per workspace

Database changes

• 3 new tables: workspaces, workspace_members, workspace_invites
• channels table rebuilt with workspace_id NOT NULL column (unique index now scoped to (workspace_id, name))
• Migration 0002 uses PRAGMA defer_foreign_keys to safely handle the table rebuild on D1
• Drizzle snapshot JSON added for migration 0002

New files

• hono/auth/requireWorkspaceMember.ts / requireWorkspaceAdmin.ts — middleware
• hono/routes/workspaces.ts — workspace CRUD
• hono/routes/workspaceAdmin.ts — admin routes (invites, members)
• hono/routes/workspaceInvite.ts — invite acceptance
• hono/components/WorkspacesPage.tsx + CSS — workspace list UI

Modified files

• hono/app.tsx — new route registrations and workspace middleware
• hono/routes/channels.ts, messages.ts, ws.ts — scoped under /w/:slug/
• hono/routes/index.tsx — workspace redirect logic
• hono/components/ChatPage.tsx — workspace context in UI
• hono/static/ChatPage.ts — workspace-scoped API URLs
• hono/db/schema.ts — 3 new tables, modified channels
• e2e/app.spec.ts — updated page title assertion

Testing

• 112 unit tests passing, lint clean, build successful
• Migration tested against local D1 (fresh install) and production D1 (upgrade with existing data)
• Already deployed to production (mlack.uk)

[Copilot]

Pull request overview

Adds first-class workspace support across the app, including workspace-scoped routing (/w/:slug/...), isolated data access, admin/member roles, and invite-based onboarding.

Changes:

• Introduces workspaces, workspace_members, and workspace_invites tables plus a migration to backfill existing data into a seeded default workspace.
• Updates channel/message/WS routes and client-side API calls to be workspace-scoped under /w/:slug/....
• Adds workspace UI (workspace list page) and admin endpoints for invite/member management, plus updated tests.

Show a summary per file

File	Description
hono/types.ts	Adds workspace-related types and context variables.
hono/static/ChatPage.ts	Scopes REST API calls under /w/:slug/api.
hono/routes/ws.ts	Moves WS endpoint to /w/:slug/ws and namespaces Durable Object by workspace slug.
hono/routes/ws.test.ts	Updates WS route tests for workspace-scoped paths and DO name.
hono/routes/workspaces.ts	Adds endpoints to list/create workspaces.
hono/routes/workspaceInvite.ts	Adds invite acceptance flow for joining a workspace.
hono/routes/workspaceAdmin.ts	Adds admin endpoints for invites and member role management.
hono/routes/messages.ts	Scopes messages endpoint under workspace and validates channel belongs to workspace.
hono/routes/messages.test.ts	Updates tests for workspace-scoped messages endpoint.
hono/routes/index.tsx	Adds workspace selection/redirect logic and /w/:slug chat page rendering.
hono/routes/index.test.tsx	Updates/extends tests for workspace redirect and workspace chat route behavior.
hono/routes/channels.ts	Scopes channel endpoints under workspace and enforces workspace isolation.
hono/routes/channels.test.ts	Updates tests for workspace-scoped channel endpoints.
hono/deployment.test.ts	Ensures new routes/components can be imported for deployment compatibility.
hono/db/seed.sql	Seeds default workspace and workspace-scoped general channel.
hono/db/schema.ts	Adds new workspace tables and rebuilds channels with workspace_id + scoped uniqueness.
hono/db/migrations/meta/0002_snapshot.json	Drizzle snapshot for the new schema/migration.
hono/db/migrations/meta/_journal.json	Registers migration 0002_add_workspaces.
hono/db/migrations/0002_add_workspaces.sql	Creates new tables, seeds default, rebuilds/migrates channels, backfills workspace members.
hono/components/WorkspacesPage.tsx	Adds server-rendered workspace list page.
hono/components/WorkspacesPage.css	Styling for the workspace list UI.
hono/components/ChatPage.tsx	Adds workspace context (title/header + data attributes) to chat page.
hono/components/ChatPage.test.ts	Updates/extends tests for workspace-scoped ChatPage rendering.
hono/auth/requireWorkspaceMember.ts	Adds middleware to enforce workspace membership and load workspace context.
hono/auth/requireWorkspaceAdmin.ts	Adds middleware to enforce admin role within a workspace.
hono/app.tsx	Registers new routes and applies workspace membership middleware to /w/:slug/....
e2e/app.spec.ts	Updates title assertion for workspace-scoped chat page.

Copilot's findings

• Files reviewed: 27/27 changed files
• Comments generated: 7

[Copilot]

Variables marks workspace and workspaceMember as always present, but they’re only set by requireWorkspaceMember for /w/:slug... routes. On routes like /api/workspaces (which only uses requireUser) these values will be undefined at runtime while TypeScript treats them as defined, which can lead to unsafe c.get("workspace") usage. Make these variables optional (or split Env types for workspace-scoped vs global routes) so the typing matches reality.

Suggested change

	workspace: Workspace;
	workspaceMember: WorkspaceMember;
	workspace?: Workspace;
	workspaceMember?: WorkspaceMember;

[Copilot]

New users with zero workspace memberships are inserted into the default workspace with role member. On a fresh install there may be no existing workspace admins (migration only promotes an existing member during upgrade), which means nobody can create invites or new workspaces and the system can’t be bootstrapped. Consider making the first member of the default workspace an admin when no members exist yet (or relax the workspace-creation restriction).

Suggested change

	await db.insert(workspaceMembers).values({
	workspaceId: defaultWorkspace.id,
	userEmail: user.email,
	role: "member",
	const existingDefaultWorkspaceMembers = await db
	.select({ userEmail: workspaceMembers.userEmail })
	.from(workspaceMembers)
	.where(eq(workspaceMembers.workspaceId, defaultWorkspace.id));
	const initialRole = existingDefaultWorkspaceMembers.length === 0 ? "admin" : "member";
	await db.insert(workspaceMembers).values({
	workspaceId: defaultWorkspace.id,
	userEmail: user.email,
	role: initialRole,

[Copilot]

Because requireWorkspaceMember is applied to /w/:slug in app.tsx, unauthenticated requests to /w/:slug will return a JSON 401 from the middleware, so this handler’s redirect-to-login branch is unreachable and the behavior for page routes is inconsistent with / (which redirects). Either remove the redundant session check here or adjust the middleware/page routing so unauthenticated users get an HTML redirect instead of JSON.

Suggested change

	const user = session.get("user") as User | undefined;
	if (!user) {
	return c.redirect("/auth/login");
	}
	const user = session.get("user") as User;

[Copilot]

This endpoint loads all workspaces and filters them in JS. That does unnecessary DB work and won’t scale as workspace count grows. Prefer selecting only the user’s workspaces in SQL (e.g., where inArray(workspaces.id, workspaceIds) or a join from workspace_members to workspaces).

[Copilot]

seed.sql hard-codes workspace_id = 1 when inserting the general channel. If the default workspace’s id isn’t 1 (e.g., if data already exists or autoincrement has advanced), this will create a channel pointing at the wrong/non-existent workspace. Use a subquery to look up the workspace id by slug (or insert the workspace with an explicit id).

Suggested change

	INSERT OR IGNORE INTO channels (name, workspace_id, created_by_email) VALUES ('general', 1, 'system');
	INSERT OR IGNORE INTO channels (name, workspace_id, created_by_email)
	SELECT 'general', id, 'system'
	FROM workspaces
	WHERE slug = 'default';

[Copilot]

The list rendering is missing a stable key on the <li> (or the <a>) element. This produces React/JSX warnings and can cause incorrect DOM diffing if the list changes. Add a key (e.g., w.id or w.slug) to the mapped element.

[Copilot]

Invite acceptance is implemented as a GET that mutates server state (inserts workspace/channel membership). This can be triggered unintentionally by link prefetching/crawlers and also enables “forced join” if a logged-in user is induced to load the URL. Consider serving a confirmation page on GET and performing the mutation on POST (with CSRF), or otherwise ensuring idempotent/non-mutating GET behavior.