feat(team)!: move the default team onto the account

__tests__/helpers.ts

@@ -125,6 +125,8 @@ export interface AuthAccountFixture {
     readonly name: string;
     readonly apiKey: string;
     readonly endpoint: string;
+    readonly team?: string;
+    readonly teamId?: string;
 }
 
 export interface PrintedAuthLoginOptions {
@@ -449,6 +451,10 @@ export async function writeAuthFile(
             `name = "${account.name}"`,
             `api_key = "${account.apiKey}"`,
             `endpoint = "${account.endpoint}"`,
+            ...(account.team === undefined ? [] : [`team = "${account.team}"`]),
+            ...(account.teamId === undefined
+                ? []
+                : [`team_id = "${account.teamId}"`]),
             "",
         ]),
     ].join("\n");
@@ -458,6 +464,29 @@ export async function writeAuthFile(
     return filePath;
 }
 
+// Seeds a saved account whose default team is already chosen — the state
+// every team-aware command reads. Written straight into auth.toml because the
+// commands that would otherwise set it (`oo team use`, `oo auth login`) need a
+// membership request of their own.
+export async function writeAuthFileWithDefaultTeam(
+    sandbox: CliSandbox,
+    team: string,
+    options: { teamId?: string } = {},
+): Promise<string> {
+    return await writeAuthFile(sandbox, {
+        accounts: [
+            {
+                id: "user-1",
+                name: "Alice",
+                apiKey: "secret-1",
+                endpoint: defaultAuthEndpoint,
+                team,
+                ...(options.teamId === undefined ? {} : { teamId: options.teamId }),
+            },
+        ],
+    });
+}
+
 export function createConnectorTargetFixture(
     overrides: Partial<OomolConnectorTarget> = {},
 ): OomolConnectorTarget {

contrib/skills/shared/oo/references/connector-execution.md

@@ -170,9 +170,9 @@ the user said:
 
 - If the user does not mention any team, add nothing extra. The run then uses
   the team selected by the `OO_TEAM_ID` / `OO_TEAM_NAME` environment variables
-  when set, then the `identity.team` config default when one is set, and their
-  personal identity otherwise — omitting the flags does not force a personal
-  run. Check `oo team current` when you need to know which one applies.
+  when set, then the default team saved on their account when one is set, and
+  their personal identity otherwise — omitting the flags does not force a
+  personal run. Check `oo team current` when you need to know which one applies.
 - If the user asks to run as a specific team (for example "run this as Acme" or
   "use my Acme team"), add `--team "<name>"`, using the team name the user gave:
 

docs/self-hosted-connector.md

@@ -179,7 +179,7 @@ adapts as follows:
 
 - **Team identity is not supported.** `--team` is rejected with exit code `2` on
   `oo connector run`, `oo connector proxy`, and `oo connector apps`, and any
-  configured `identity.team` default and the `OO_TEAM_ID` / `OO_TEAM_NAME`
+  saved account default team and the `OO_TEAM_ID` / `OO_TEAM_NAME`
   environment variables are ignored. `--personal` is accepted (it is already
   the effective behavior).
 - **Async lifecycle waiting is unavailable.** `--wait` and `--wait-result` fail

docs/self-hosted-connector.zh-CN.md

@@ -159,7 +159,7 @@ oo connector run gmail --action send_email --data '@payload.json'
 自部署运行时暴露的能力比 OOMOL 服务更小，CLI 会做如下适配：
 
 - **不支持团队身份。** `oo connector run`、`oo connector proxy` 与 `oo connector
-  apps` 上的 `--team` 会以退出码 `2` 被拒绝，任何已配置的 `identity.team` 默认值
+  apps` 上的 `--team` 会以退出码 `2` 被拒绝，账号保存的默认团队
   和 `OO_TEAM_ID` / `OO_TEAM_NAME` 环境变量都会被忽略；`--personal` 可以使用
   （它本就是实际行为）。
 - **无法等待异步生命周期。** `--wait` 与 `--wait-result` 会以既有的「不支持」