0.34.0

Connecta 0.34.0 rebuilds the operator UI around an Overview with connector health, endpoints, people and agents, a Needs attention list with fix prompts, and a connection map (#867). Maintainers now land on Overview at /; Endpoints moves to /endpoints, and /access redirects there. Update bookmarks, links and browser automation that expected Endpoints at /. Members still get their member page on every operator page path. The upgrade steps are in documentation/migration-0.34.md.

The redesign carries through Connectors, Endpoints, the access matrix, Tokens, Settings, Activity and the member page, with warm neutral surfaces, one accent, self-hosted Hanken Grotesk and JetBrains Mono, and light and dark themes. Configuration uses tiles, connector tools open in a schema drawer, Activity groups calls by request, and Account holds Sign out and Change token. Default browser titles now join the product and owner with ·; set branding.pageTitle explicitly if an integration needs the old title. Custom titles stay unchanged. Activity outcome links can use failed or succeeded; older exact outcome values still filter by that value. Custom activity stores may optionally report describe().optionSources.retentionDays as "config" or "default" so Settings can distinguish an explicit retention setting; existing stores need no change.

Agents in a pool without an owner no longer discover Google Workspace connectors whose subject is a mapping function (#873). Those connectors previously appeared but failed calls with auth_required; now they are absent from discovery, search, describe, skills and code mode, and calls by address fail unknown_address. Saved program returns are rechecked too. To give an agent Workspace access, use a pool with the intended person's Workspace address as its owner, such as alice@example.com; do not add an owner to a shared pool just to restore discovery. People, agents in owned pools and fixed-subject connectors keep their behavior.

Pools can now take a one-line description of 1 to 500 characters, appended to that pool's MCP instructions after This endpoint: (#872). Pools without a description and plain /mcp keep their instructions. The auth guide now documents group tiers: pick the most capable pool everyone present is cleared for, use the base pool when anyone is unknown, and build personal pools on that person's highest tier (#875). Shipped docs also correct operator, provider and deployment guidance (#866). Repository development and CI now use pnpm (#877); installed deployments, the Node template and npm publishing keep using npm. Upgrading from 0.33.0 needs no storage migration or token rotation. Deployments that do not use the operator UI or mapping-subject Workspace connectors in owner-less agent pools can ignore the UI and discovery migration steps; all new configuration fields are optional.