let members use chat

The owner authorized this explicitly. Two refusals removed together, because
they were always one guard in two places: the wholesale isSuperAdmin middleware
in api/chat/chat.ts, and the chat socket's 403 in server.tsx.

They were right for the day they stood. A turn spawned claude as the OWNER and
every transcript path resolved through the owner's home, so a granted member
would have read the owner's sessions and run an agent as them.

What replaced them, rather than what deleted them:

  the turn runs as the member    spawnClaudeAsMember through sudo setpriv,
                                 proven against a real account by reading file
                                 ownership rather than trusting the process
  the credential is theirs       --reset-env plus an allowlist, so the owner's
                                 proxy variables cannot cross
  the transcripts are theirs     ChatIdentity carries a home from resolveHomeDir
                                 and claude-sessions cannot invent one
  the sessions are theirs        every session records its owner and all six
                                 sidecar commands refuse a mismatch

Also adds the precondition host asked for in 10: a member whose claude is not
signed in gets the instruction rather than a turn that dies on an auth error and
reads as a broken agent. Not installed and not signed in are separate messages
because they need different actions.

registry.ts and registry.test.ts now describe chat as confined in fact rather
than ahead of its implementation. The comments at both former guards say what
had to exist first, and that a revert should go back to a refusal rather than to
a narrower one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/servers/api/chat/chat.ts

@@ -51,26 +51,25 @@ import { registerAgentPanelRoutes } from './agent-panels-routes';
 
 export const chatRouter = createRouter();
 
-// ── Chat is grantable, and its machinery is not ready for a member. This is that gap, held open on purpose ──
+// ── Chat reached members on 2026-08-12 ──
 //
-// The `chat` capability moved from `execution` to `confined` so the owner can grant it and the route resolves.
-// The agent underneath has NOT moved: `claude-manager.ts` drives turns through the Agent SDK, which spawns
-// `claude` itself with no way to hand it a uid, and every transcript path here resolves through the owner's
-// home. So a member reaching this router would read the owner's session list and run an agent as the owner —
-// which is the whole thing the confinement work exists to prevent.
+// A wholesale `isSuperAdmin` refusal stood here from the day `chat` became grantable until tonight. It said
+// the machinery was not ready, and it was right: a turn spawned `claude` as the OWNER, and every transcript
+// path resolved through the owner's home, so a granted member would have read the owner's sessions and run an
+// agent as them.
 //
-// Refused wholesale rather than per-route, and reads rather than just writes: `listClaudePwds` returns the
-// directory names of the owner's projects, which is not a member's business either.
+// What replaced it, rather than what deleted it:
 //
-// What lifts this is per-user agents: the turn becomes its own process under `runAs`, with the member's own
-// HOME so `~/.claude` and their transcripts are theirs. docs/per-user-linux-accounts.md § stage 5. Delete this
-// middleware then — it is the only thing standing between a granted member and the owner's agent.
-chatRouter.use(async (ctx, next) => {
-  if (!(await isSuperAdmin(ctx.get('user')))) {
-    throw errors.FORBIDDEN('Chat is not available to members yet — the agent still runs as the server owner.');
-  }
-  return next();
-});
+//   - the turn runs as the member — `spawnClaudeAsMember` through `sudo setpriv`, proven against a real
+//     account by `spawn-as-member.live.test.ts` reading file ownership rather than trusting the process
+//   - the credential is theirs — `--reset-env` plus an allowlist, so the owner's proxy variables cannot cross
+//   - the transcripts are theirs — `ChatIdentity` carries a home resolved from `resolveHomeDir`, and this file
+//     no longer knows how to invent one
+//   - the sessions are theirs — every session records its owner, and all six sidecar commands refuse a
+//     mismatch rather than acting on whoever matched
+//
+// Each of those is a separate commit with its own reasoning, and each was found wanting at least once by a
+// reviewer who had not written it. If you are reverting this, revert to a refusal — not to a narrower one.
 
 // The working directory a request operates on: an explicit ?cwd= (a chosen pwd), else the default
 // general_chat_sessions dir. Claude groups sessions by cwd, so this selects which project group we read.

src/servers/api/chat/websocket.ts

@@ -19,6 +19,7 @@ import { join } from 'path';
 import { getOwnerHomeDir, getEmailAccountsDir } from '../../../servers/data-path';
 import { getUserSettings, getEmailAccounts, getChatEventsSince, appendChatEvent, getUserById } from 'officerdb';
 import { resolveHomeDir } from '@@/user-home';
+import { claudeLoginState } from '@@/os-user-claude';
 import { mkdirSync } from 'node:fs';
 import { logger } from './logger';
 
@@ -368,6 +369,30 @@ async function handleClaudeCodeChat(
     return;
   }
 
+  // A member has to sign `claude` in themselves, once, with their own Anthropic account — the platform cannot
+  // do it for them without lending them the owner's credential, which is the thing this whole feature exists
+  // to avoid. Without this check their turn spawns, `claude` exits on an auth error, and it surfaces as "the
+  // agent is broken" — the exact confusion `/agent-status` was built to prevent, arriving through a different
+  // door. The refusal carries the instruction so the answer is the same whether the UI asked or not.
+  if (identity.kind === 'member') {
+    const state = await claudeLoginState({ email, osUser: identity.run.osUser });
+    if (!state.installed) {
+      sendToClient(ws, {
+        type: 'error',
+        message: 'Claude is not installed in your home yet — ask the server owner to reprovision your account.',
+      });
+      return;
+    }
+    if (!state.loggedIn) {
+      sendToClient(ws, {
+        type: 'error',
+        message:
+          'Open a terminal and run `claude` once to sign in with your own Anthropic account. It stays signed in.',
+      });
+      return;
+    }
+  }
+
   const home = identity.kind === 'member' ? identity.run.home : getOwnerHomeDir(email);
 
   const cwd = await resolveChatCwd(msg, email, userId, home);