@tmustier/pi-agent-teams 0.1.2 → 0.3.0

package/README.md

@@ -20,6 +20,17 @@ Additional Pi-specific capabilities:
 - **Git worktrees** — optionally give each teammate its own worktree so they work on isolated branches without conflicting edits.
 - **Session branching** — clone the leader's conversation context into a teammate so it starts with full awareness of the work so far, instead of from scratch.
 
+## UI style
+
+The extension supports two UI styles:
+
+- **normal** (default): "Team leader" + "Teammate <name>"
+- **soviet**: "Chairman" + "Comrade <name>" (in soviet mode, the system decides names for you)
+
+Configure via:
+- env: `PI_TEAMS_STYLE=normal|soviet`
+- command: `/team style normal` or `/team style soviet`
+
 ## Install
 
 **Option A — install from npm:**
@@ -46,9 +57,16 @@ Verify with `/team id` — it should print the current team info.
 
 ## Quick start
 
+The fastest way to get going is `/swarm`:
+
 ```
-# In a Pi session with the extension loaded:
+/swarm build the auth module               # agent spawns a team and coordinates the work
+/swarm                                     # agent asks you what to do, then swarms on it
+```
+
+Or drive it manually:
 
+```
 /team spawn alice                          # spawn a teammate (fresh session, shared workspace)
 /team spawn bob branch worktree            # spawn with leader context + isolated worktree
 
@@ -58,7 +76,10 @@ Verify with `/team id` — it should print the current team info.
 /team dm alice Check the edge cases too    # direct message
 /team broadcast Wrapping up soon           # message everyone
 
+/tw                                        # open the interactive widget panel
+
 /team shutdown alice                       # graceful shutdown (handshake)
+/team shutdown                             # stop all teammates (leader session remains active)
 /team cleanup                              # remove team artifacts when done
 ```
 
@@ -79,25 +100,35 @@ Or let the model drive it with the delegate tool:
 
 ## Commands
 
-All commands live under `/team`.
+### Shortcuts
 
-### Teammates
+| Command | Description |
+| --- | --- |
+| `/swarm [task]` | Tell the agent to spawn a team and work on a task |
+| `/tw` | Open the interactive widget panel |
+| `/team-widget` | Open the interactive widget panel (alias for `/tw`) |
+
+### Team management
+
+All management commands live under `/team`.
 
 | Command | Description |
 | --- | --- |
 | `/team spawn <name> [fresh\|branch] [shared\|worktree]` | Start a teammate |
 | `/team list` | List teammates and their status |
+| `/team panel` | Interactive widget panel (same as `/tw`) |
+| `/team style <normal\|soviet>` | Set UI style (normal/soviet) |
 | `/team send <name> <msg>` | Send a prompt over RPC |
 | `/team steer <name> <msg>` | Redirect an in-flight run |
 | `/team dm <name> <msg>` | Send a mailbox message |
 | `/team broadcast <msg>` | Message all teammates |
 | `/team stop <name> [reason]` | Abort current work (resets task to pending) |
 | `/team shutdown <name> [reason]` | Graceful shutdown (handshake) |
-| `/team shutdown` | Shutdown leader + all teammates |
+| `/team shutdown` | Stop all teammates (leader session remains active) |
 | `/team kill <name>` | Force-terminate |
 | `/team cleanup [--force]` | Delete team artifacts |
 | `/team id` | Print team/task-list IDs and paths |
-| `/team env <name>` | Print env vars to start a manual worker |
+| `/team env <name>` | Print env vars to start a manual teammate |
 
 ### Tasks
 
@@ -119,6 +150,7 @@ All commands live under `/team`.
 | --- | --- | --- |
 | `PI_TEAMS_ROOT_DIR` | Storage root (absolute or relative to `~/.pi/agent`) | `~/.pi/agent/teams` |
 | `PI_TEAMS_DEFAULT_AUTO_CLAIM` | Whether spawned teammates auto-claim tasks | `1` (on) |
+| `PI_TEAMS_STYLE` | UI style (`normal` or `soviet`) | `normal` |
 
 ## Storage layout
 
@@ -136,13 +168,22 @@ All commands live under `/team`.
 
 ## Development
 
+### Quality gate
+
+```bash
+npm run check
+```
+
+Runs strict TypeScript typechecking (`npm run typecheck`) and ESLint (`npm run lint`).
+
 ### Smoke test (no API keys)
 
 ```bash
-node scripts/smoke-test.mjs
+npm run smoke-test
+# or: npx tsx scripts/smoke-test.mts
 ```
 
-Filesystem-level test of the task store, mailbox, and team config.
+Filesystem-level smoke test of the task store, mailbox, team config, and protocol parsers.
 
 ### E2E RPC test (spawns pi + one teammate)
 
@@ -150,7 +191,7 @@ Filesystem-level test of the task store, mailbox, and team config.
 node scripts/e2e-rpc-test.mjs
 ```
 
-Starts a leader in RPC mode, spawns a worker, runs a shutdown handshake, verifies cleanup. Sets `PI_TEAMS_ROOT_DIR` to a temp directory so nothing touches `~/.pi/agent/teams`.
+Starts a leader in RPC mode, spawns a teammate, runs a shutdown handshake, verifies cleanup. Sets `PI_TEAMS_ROOT_DIR` to a temp directory so nothing touches `~/.pi/agent/teams`.
 
 ### tmux dogfooding
 
@@ -159,7 +200,7 @@ Starts a leader in RPC mode, spawns a worker, runs a shutdown handshake, verifie
 tmux attach -t pi-teams
 ```
 
-Starts a leader + one tmux window per worker for interactive testing.
+Starts a leader + one tmux window per teammate for interactive testing.
 
 ## License
 

package/docs/claude-parity.md

@@ -12,12 +12,14 @@ This document tracks **feature parity gaps** between:
 
 - `pi-agent-teams` (Pi extension)
 
+> Terminology note: the extension supports `PI_TEAMS_STYLE=normal|soviet`. These docs often say "comrade" for parity with Claude Teams, but in **normal** style you’ll see "teammate" and "team leader" in the UI.
+
 ## Scope / philosophy
 
 - Target the **same coordination primitives** as Claude Teams:
   - shared task list
   - mailbox messaging
-  - long-lived teammates
+  - long-lived comrades
 - Prefer **inspectable, local-first artifacts** (files + lock files).
 - Avoid guidance that bypasses Claude feature gating; we only document behavior.
 - Accept that some Claude UX (terminal keybindings + split-pane integration) may not be achievable in Pi without deeper TUI/terminal integration.
@@ -31,18 +33,18 @@ Legend: ✅ implemented • 🟡 partial • ❌ missing
 | Enablement | `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` + settings | N/A | Pi extension is always available when installed/loaded. | — |
 | Team config | `~/.claude/teams/<team>/config.json` w/ members | ✅ | Implemented via `extensions/teams/team-config.ts` (stored under `~/.pi/agent/teams/...` or `PI_TEAMS_ROOT_DIR`). | P0 |
 | Task list (shared) | `~/.claude/tasks/<taskListId>/` + states + deps | ✅ | File-per-task + deps (`blockedBy`/`blocks`); `/team task dep add|rm|ls`; self-claim skips blocked tasks. | P0 |
-| Self-claim | Teammates can self-claim next unassigned, unblocked task; file locking | ✅ | Implemented: `claimNextAvailableTask()` + locks; enabled by default (`PI_TEAMS_DEFAULT_AUTO_CLAIM=1`). | P0 |
-| Explicit assign | Lead assigns task to teammate | ✅ | `/team task assign` sets owner + pings via mailbox. | P0 |
-| “Message” vs “broadcast” | Send to one teammate or all teammates | ✅ | `/team dm` + `/team broadcast` use mailbox; `/team send` uses RPC. Broadcast recipients = team config workers + RPC-spawned map + active task owners; manual tmux workers self-register into `config.json` on startup. | P0 |
-| Teammate↔teammate messaging | Teammates can message each other directly | ✅ | Workers register `team_message` LLM-callable tool; sends via mailbox + CC's leader with `peer_dm_sent` notification. | P1 |
-| Display modes | In-process selection (Shift+Up/Down); split panes (tmux/iTerm) | ❌ | Pi has a widget + commands, but no terminal-level teammate navigation/panes. | P2 |
+| Self-claim | Comrades can self-claim next unassigned, unblocked task; file locking | ✅ | Implemented: `claimNextAvailableTask()` + locks; enabled by default (`PI_TEAMS_DEFAULT_AUTO_CLAIM=1`). | P0 |
+| Explicit assign | Lead assigns task to comrade | ✅ | `/team task assign` sets owner + pings via mailbox. | P0 |
+| “Message” vs “broadcast” | Send to one comrade or all comrades | ✅ | `/team dm` + `/team broadcast` use mailbox; `/team send` uses RPC. Broadcast recipients = team config workers + RPC-spawned map + active task owners; manual tmux workers self-register into `config.json` on startup. | P0 |
+| Comrade↔comrade messaging | Comrades can message each other directly | ✅ | Workers register `team_message` LLM-callable tool; sends via mailbox + CC's leader with `peer_dm_sent` notification. | P1 |
+| Display modes | In-process selection (Shift+Up/Down); split panes (tmux/iTerm) | ❌ | Pi has a widget + commands, but no terminal-level comrade navigation/panes. | P2 |
 | Delegate mode | Lead restricted to coordination-only tools | ✅ | `/team delegate [on|off]` toggles; `pi.on("tool_call")` blocks `bash/edit/write`; `PI_TEAMS_DELEGATE_MODE=1` env. Widget shows `[delegate]`. | P1 |
-| Plan approval | Teammate can be "plan required" and needs lead approval to implement | ✅ | `/team spawn <name> plan` sets `PI_TEAMS_PLAN_REQUIRED=1`; worker restricted to read-only tools; submits plan via `plan_approval_request`; `/team plan approve|reject <name>`. | P1 |
-| Shutdown handshake | Lead requests shutdown; teammate can approve/reject | ✅ | Full protocol: `shutdown_request` → `shutdown_approved` or `shutdown_rejected` (when worker is busy). `/team shutdown <name>` (graceful) + `/team kill` (force). | P1 |
-| Cleanup team | “Clean up the team” removes shared resources after teammates stopped | ✅ | `/team cleanup [--force]` deletes only `<teamsRoot>/<teamId>` after safety checks. | P1 |
-| Hooks / quality gates | `TeammateIdle`, `TaskCompleted` hooks | ❌ | Add optional hook runner in leader on idle/task-complete events (script execution + exit-code gating). | P2 |
+| Plan approval | Comrade can be "plan required" and needs lead approval to implement | ✅ | `/team spawn <name> plan` sets `PI_TEAMS_PLAN_REQUIRED=1`; worker restricted to read-only tools; submits plan via `plan_approval_request`; `/team plan approve|reject <name>`. | P1 |
+| Shutdown handshake | Lead requests shutdown; comrade can approve/reject | ✅ | Full protocol: `shutdown_request` → `shutdown_approved` or `shutdown_rejected` (when worker is busy). `/team shutdown <name>` (graceful) + `/team kill <name>` (force). | P1 |
+| Cleanup team | “Clean up the team” removes shared resources after comrades stopped | ✅ | `/team cleanup [--force]` deletes only `<teamsRoot>/<teamId>` after safety checks. | P1 |
+| Hooks / quality gates | `ComradeIdle`, `TaskCompleted` hooks | ❌ | Add optional hook runner in leader on idle/task-complete events (script execution + exit-code gating). | P2 |
 | Task list UX | Ctrl+T toggle; show all/clear tasks by asking | 🟡 | Widget + `/team task list` show blocked/deps; `/team task show <id>`; `/team task clear [completed|all]`. No Ctrl+T toggle yet. | P0 |
-| Shared task list across sessions | `CLAUDE_CODE_TASK_LIST_ID=...` | ✅ | `PI_TEAMS_TASK_LIST_ID` env on leader + worker; `/team task use <taskListId>` switches the leader (and newly spawned workers). Existing workers need a restart to pick up changes. Persisted in config.json. | P1 |
+| Shared task list across sessions | `CLAUDE_CODE_TASK_LIST_ID=...` | ✅ | `PI_TEAMS_TASK_LIST_ID` env is **worker-side** (for manually started workers). The leader switches task lists via `/team task use <taskListId>` (persisted in `config.json`). Newly spawned workers inherit the new task list ID; existing workers need a restart to pick up changes. | P1 |
 
 ## Prioritized roadmap
 
@@ -64,7 +66,7 @@ Legend: ✅ implemented • 🟡 partial • ❌ missing
 4) **Shutdown handshake** ✅
    - Full protocol: `shutdown_request` → `shutdown_approved` / `shutdown_rejected`
    - Worker rejects when busy (streaming + active task), auto-approves when idle
-   - Leader command: `/team shutdown <name> [reason...]` (graceful), `/team kill` as force
+   - Leader command: `/team shutdown <name> [reason...]` (graceful), `/team kill <name>` as force
 
 5) **Plan approval** ✅
    - `/team spawn <name> [fresh|branch] [shared|worktree] plan` sets `PI_TEAMS_PLAN_REQUIRED=1`
@@ -80,7 +82,7 @@ Legend: ✅ implemented • 🟡 partial • ❌ missing
 
 7) **Cleanup** ✅
    - `/team cleanup [--force]` deletes only `<teamsRoot>/<teamId>` after safety checks.
-   - Refuses if RPC teammates are running or there are `in_progress` tasks unless `--force`.
+   - Refuses if RPC comrades are running or there are `in_progress` tasks unless `--force`.
 
 8) **Peer-to-peer messaging** ✅
    - Workers register `team_message` LLM-callable tool (recipient + message params)
@@ -93,10 +95,10 @@ Legend: ✅ implemented • 🟡 partial • ❌ missing
 
 ### P2: UX + “product-level” parity
 
-10) **Better teammate interaction UX**
+10) **Better comrade interaction UX**
    - Explore whether Pi’s TUI API can support:
-     - selecting a teammate from the widget
-     - “entering” a teammate transcript view
+     - selecting a comrade from the widget
+     - “entering” a comrade transcript view
    - (Optional) tmux integration for split panes.
 
 11) **Hooks / quality gates**
@@ -107,7 +109,9 @@ Legend: ✅ implemented • 🟡 partial • ❌ missing
 
 ## Where changes would land (code map)
 
-- Leader orchestration + commands + tool: `extensions/teams/leader.ts`
+- Leader orchestration: `extensions/teams/leader.ts`
+- Leader `/team` command dispatch: `extensions/teams/leader-team-command.ts`
+- Leader LLM tool (`teams`): `extensions/teams/leader-teams-tool.ts`
 - Worker mailbox polling + self-claim + protocols: `extensions/teams/worker.ts`
 - Task store + locking: `extensions/teams/task-store.ts`, `extensions/teams/fs-lock.ts`
 - Mailbox store + locking: `extensions/teams/mailbox.ts`
@@ -118,5 +122,5 @@ Legend: ✅ implemented • 🟡 partial • ❌ missing
 
 - Keep tests hermetic by setting `PI_TEAMS_ROOT_DIR` to a temp directory.
 - Extend:
-  - `scripts/smoke-test.mjs` for filesystem-only behaviors (deps, claiming, locking)
+  - `scripts/smoke-test.mts` (run via `npm run smoke-test`) for filesystem-only behaviors (deps, claiming, locking)
   - `scripts/e2e-rpc-test.mjs` for protocol flows (shutdown handshake, plan approval)

package/docs/field-notes-teams-setup.md

@@ -4,12 +4,14 @@ Date: 2026-02-07
 
 Goal: dogfood the Teams extension to implement its own roadmap (Claude parity), and capture anything that surprised/confused us while setting it up.
 
+> Terminology note: the extension supports `PI_TEAMS_STYLE=normal|soviet`. In normal style the UI says "teammate" and "team leader"; in soviet style it says "comrade" and "chairman".
+
 ## Test run: test1
 
 Decisions: tmux session `pi-teams-test1`; `PI_TEAMS_ROOT_DIR=~/projects/pi-agent-teams/test1`; `teamId=0baaa0e6-8020-4d9a-bf33-c1a65f99a2f7`; workers started manually in tmux (not `/team spawn`).
 
 First impressions:
-- Manual tmux workers are usable. Initially the leader showed “(no teammates)” because it only tracked RPC-spawned workers; now manual workers **upsert themselves into `config.json` on startup**, and the leader widget renders online workers from team config.
+- Manual tmux workers are usable. Initially the leader showed “(no comrades)” because it only tracked RPC-spawned workers; now manual workers **upsert themselves into `config.json` on startup**, and the leader widget renders online workers from team config.
 - Pinning `PI_TEAMS_ROOT_DIR` made reruns/id discovery predictable (no “find the new folder” step).
 - tmux workflow feels close to Claude-style split panes; bootstrap ergonomics still need smoothing.
 - Surprise: `/team spawn <name> branch` failed once with `Entry <id> not found` (branch-from leaf missing on disk); `/team spawn <name> fresh` worked.
@@ -73,9 +75,9 @@ First impressions:
 
 - **tmux vs `/team spawn`**: `/team spawn` uses `pi --mode rpc` subprocesses.
   - Pros: simple, managed lifecycle.
-  - Cons: you don’t see a full interactive teammate UI like Claude’s split-pane mode.
+  - Cons: you don’t see a full interactive comrade UI like Claude’s split-pane mode.
   - We manually started workers in separate tmux windows (setting `PI_TEAMS_WORKER=1`, `PI_TEAMS_TEAM_ID=...`, etc). This now shows up in the leader widget because workers upsert themselves into `config.json`, and the leader renders online workers from team config.
-  - Update: leader now renders teammates from `team config` and also auto-adds unknown senders on idle notifications (so manual tmux workers feel first-class).
+  - Update: leader now renders comrades from `team config` and also auto-adds unknown senders on idle notifications (so manual tmux workers feel first-class).
   - Improvement idea: optional spawn mode that starts a worker in a new tmux pane/window.
 
 - **Two messaging paths** (`/team send` vs `/team dm`):
@@ -84,7 +86,7 @@ First impressions:
   - Improvement idea: clearer naming and/or a single “message” command with a mode flag.
 
 - **Runaway tasks / timeboxing**: a vague task prompt can turn into a long “research spiral”.
-  - In manual-tmux mode, there isn’t a great way (yet) for the leader to *steer* an in-flight run (unlike `/team steer` for RPC-spawned teammates).
+  - In manual-tmux mode, there isn’t a great way (yet) for the leader to *steer* an in-flight run (unlike `/team steer` for RPC-spawned comrades).
   - Improvement idea: add a mailbox-level “steer” protocol message that workers can treat as an in-flight follow-up if they’re currently running.
 
 - **Failure semantics are underspecified**: tool failures show up in the worker UI, but our task store currently only supports `pending|in_progress|completed`.

package/docs/smoke-test-plan.md

@@ -0,0 +1,139 @@
+# pi-agent-teams — Runtime Smoke Test Plan
+
+## Prerequisites
+
+- `pi` CLI installed (`pi --version` → `0.52.x+`)
+- `node_modules/` present (run `npm install` or symlink from main repo)
+- `npx tsx` available for running `.mts` test scripts
+
+## 1. Automated Unit Smoke Test (no interactive session)
+
+Exercises all core primitives directly via `tsx`:
+
+```bash
+npx tsx scripts/smoke-test.mts
+# or: npm run smoke-test
+```
+
+**What it tests** (overview):
+
+| Module           | Coverage                                                        |
+|------------------|-----------------------------------------------------------------|
+| `names.ts`       | `sanitizeName` character replacement, edge cases                |
+| `fs-lock.ts`     | `withLock` returns value, cleans up lock file                   |
+| `mailbox.ts`     | `writeToMailbox`, `popUnreadMessages`, read-once semantics      |
+| `task-store.ts`  | CRUD, `startAssignedTask`, `completeTask`, `claimNextAvailable`,|
+|                  | `unassignTasksForAgent`, dependencies, `clearTasks`             |
+| `team-config.ts` | `ensureTeamConfig` (idempotent), `upsertMember`, `setMemberStatus`, `loadTeamConfig` |
+| `protocol.ts`    | Structured message parsers (valid + invalid JSON + wrong type)  |
+| Pi CLI           | `pi --version` executes (skipped in CI if `pi` not on PATH)     |
+
+**Expected result:** `PASSED: <n>  FAILED: 0`
+
+## 2. Extension Loading Test
+
+Verify Pi can load the extension entry point without crashing:
+
+```bash
+pi --no-extensions -e extensions/teams/index.ts --help
+```
+
+**Expected:** exits 0, shows Pi help output (no TypeScript/import errors).
+
+## 3. Interactive Smoke Test (manual)
+
+### 3a. Launch Pi with the extension
+
+```bash
+# From the repo root:
+pi --no-extensions -e extensions/teams/index.ts
+```
+
+Or, if the extension is symlinked into `~/.pi/agent/extensions/pi-agent-teams`:
+
+```bash
+pi   # auto-loads from extensions dir
+```
+
+### 3b. Check extension is active
+
+```
+/team help
+```
+
+**Expected:** shows usage lines for `/team spawn`, `/team task`, etc.
+
+### 3c. Spawn a teammate ("comrade" in soviet style)
+
+```
+/team spawn agent1 fresh shared
+```
+
+**Expected:** notification "Spawned agent1" or similar, widget shows `Teammate agent1: idle` (or `Comrade agent1: idle` in soviet style).
+
+### 3d. Create and assign a task
+
+```
+/team task add agent1: Say hello
+/team task list
+```
+
+**Expected:** task #1 created, assigned to agent1, status `pending` → `in_progress`.
+
+### 3e. Verify mailbox delivery
+
+```
+/team dm agent1 ping from lead
+```
+
+**Expected:** "DM queued for agent1" notification.
+
+### 3f. Delegate via tool
+
+Ask the model:
+> "Delegate a task to agent1: write a haiku about coding"
+
+**Expected:** the `teams` tool is invoked, task created and assigned.
+
+### 3g. Shutdown
+
+```
+/team shutdown agent1
+/team kill agent1
+```
+
+**Expected:** agent1 goes offline, widget updates.
+
+Optional: stop all teammates without ending the leader session:
+
+```
+/team shutdown
+```
+
+**Expected:** all teammates stop; leader remains active until you exit it (e.g. ctrl+d).
+
+## 4. Worker-side Smoke (verifying child process)
+
+To test the worker role directly:
+
+```bash
+PI_TEAMS_WORKER=1 \
+PI_TEAMS_TEAM_ID=test-team \
+PI_TEAMS_AGENT_NAME=agent1 \
+PI_TEAMS_LEAD_NAME=team-lead \
+PI_TEAMS_STYLE=normal \
+pi --no-extensions -e extensions/teams/index.ts --mode rpc
+```
+
+**Expected:** process starts in RPC mode, registers `team_message` tool, polls mailbox.
+
+## 5. Checklist Summary
+
+| # | Test                          | Method     | Status |
+|---|-------------------------------|------------|--------|
+| 1 | Unit primitives (60 asserts)  | Automated  | ✅     |
+| 2 | Extension loading             | CLI        | ✅     |
+| 3 | Interactive spawn/task/dm     | Manual     | 📋     |
+| 4 | Worker-side RPC               | Manual     | 📋     |
+
+✅ = verified in this run, 📋 = documented for manual execution.

package/eslint.config.js

@@ -0,0 +1,74 @@
+// @ts-check
+import eslint from "@eslint/js";
+import tseslint from "typescript-eslint";
+
+export default tseslint.config(
+	{
+		ignores: [
+			"node_modules/**",
+			"dist/**",
+			"build/**",
+			"coverage/**",
+			".artifacts/**",
+			".research/**",
+			".resume-sessions/**",
+		],
+	},
+
+	eslint.configs.recommended,
+	...tseslint.configs.recommended,
+
+	{
+		files: ["extensions/**/*.ts", "scripts/**/*.ts", "scripts/**/*.mts"],
+		rules: {
+			// ━━ Project invariants (AGENTS.md) ━━
+			"@typescript-eslint/no-explicit-any": "error",
+			"@typescript-eslint/no-non-null-assertion": "error",
+			"@typescript-eslint/ban-ts-comment": [
+				"error",
+				{
+					"ts-ignore": true,
+					"ts-expect-error": true,
+					"ts-nocheck": true,
+					"ts-check": false,
+				},
+			],
+
+			// Imports/types
+			"@typescript-eslint/consistent-type-imports": [
+				"error",
+				{ prefer: "type-imports", disallowTypeAnnotations: false },
+			],
+
+			// General correctness
+			eqeqeq: ["error", "always"],
+
+			// Prefer TS-aware unused-vars
+			"no-unused-vars": "off",
+			"@typescript-eslint/no-unused-vars": [
+				"warn",
+				{
+					argsIgnorePattern: "^_",
+					varsIgnorePattern: "^_",
+					caughtErrorsIgnorePattern: "^_",
+				},
+			],
+		},
+	},
+
+	// Scripts/tests: console is expected
+	{
+		files: ["scripts/**/*.ts", "scripts/**/*.mts"],
+		rules: {
+			"no-console": "off",
+		},
+	},
+
+	// Extension source: discourage stray console.log
+	{
+		files: ["extensions/**/*.ts"],
+		rules: {
+			"no-console": "warn",
+		},
+	},
+);