brl-subagent 2.3.9 → 2.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENT.md CHANGED
@@ -66,6 +66,11 @@ delegation-heavy work.
66
66
  - Background fan-out: `tasks: [...], background: true` — one background agent per task, one id per task in task order, one wake per agent.
67
67
  - retryRunId: pass a failed run's id to re-run it with its recorded task and params; explicit parameters override the originals.
68
68
 
69
+ ## Deadlines and retries
70
+
71
+ - `timeout` (ms) is a **deadline, not a ceiling** — an explicit value is honored as given; 30 minutes is only the default for a background run that passes none. Background expiry aborts the session (the run ends `stopped`); foreground expiry kills the process.
72
+ - `retryOnTimeout` applies to **foreground runs only**. A timed-out background run is not auto-retried: re-dispatch it with `retryRunId` if that is the right call.
73
+
69
74
  ## Mechanics pointer
70
75
 
71
76
  Presets and templates are documented in the schema, not here. Judgment only:
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  > Multi-agent orchestration for [pi](https://github.com/earendil-works/pi) — chain, parallel, and dependency-graph delegation to isolated subagents with per-step model routing, preset-driven tool scoping, thinking-level control, and background execution with live monitoring, real abort, and per-agent timeouts.
4
4
 
5
- **Version:** 2.3.9 · **Author:** Azmeen Afandi / [Beeroo Labs](https://beeroolabs.com) · **License:** MIT
5
+ **Version:** 2.4.0 · **Author:** Azmeen Afandi / [Beeroo Labs](https://beeroolabs.com) · **License:** MIT
6
6
 
7
7
  ---
8
8
 
@@ -11,10 +11,10 @@
11
11
  `brl-subagent` is **one of the most capable subagent orchestration extensions for pi** — one `delegate_task` tool that spawns fully isolated subagent processes, each with its own model, context window, tool permissions, and thinking level.
12
12
 
13
13
  - **Multi-step delegation, natively** — chain, parallel, and dependency-graph modes with per-step model routing, so a complex task fans out exactly as you design it.
14
- - **True background execution** — live monitor, real abort (`stop_subagent`), per-agent timeouts, and hard caps. Nothing orphans; nothing leaks.
14
+ - **True background execution** — live monitor, real abort (`stop_subagent`), per-agent timeouts, and a 30-minute default deadline for runs that don't set one. Nothing orphans; nothing leaks.
15
15
  - **Preset-driven tool scoping** — every subagent runs with exactly the tools its job needs, restricted by preset or per-call `tools`/`excludeTools`, with auto-route that picks the right preset when you don't.
16
16
  - **Templates with slots** — saved, file-backed task templates with `${param}` placeholders for workflows you run again and again.
17
- - **Safety by default** — task-fence injection protection, sanitized error paths, owner-only persistence, and a 975+ test suite pinning every contract against the real pi SDK.
17
+ - **Safety by default** — task-fence injection protection, sanitized error paths, owner-only persistence, and a 1200+ test suite pinning every contract against the real pi SDK.
18
18
 
19
19
  ---
20
20
 
@@ -59,11 +59,18 @@ pi remove npm:brl-subagent # uninstall
59
59
  | `/brl-subagent history` | Browse past subagent runs |
60
60
  | `/brl-subagent monitor` | Live monitor running subagents |
61
61
  | `/brl-subagent dashboard` | Live observability dashboard |
62
+ | `/brl-subagent compliance` | Compliance reports (file access, secrets exposure, full summary) |
62
63
  | `/brl-subagent retry` | Browse failed runs to retry |
63
64
  | `/brl-subagent reset` | Reset all configuration |
64
65
 
65
66
  All settings persist across sessions.
66
67
 
68
+ ### Environment variables
69
+
70
+ - `BRL_LOG_LEVEL` — minimum level written to the log file. One of `debug`,
71
+ `info` (default), `warn`, `error`. Read once at module load; unrecognised
72
+ values fall back to `info`. Runtime changes go through `setLogLevel()`.
73
+
67
74
  ---
68
75
 
69
76
  ## delegate_task parameters
@@ -82,7 +89,7 @@ All settings persist across sessions.
82
89
  | `inheritSystemPrompt` | boolean | `true` | Whether to inherit the main agent's system prompt. Set `false` to save tokens. |
83
90
  | `thinkingLevel` | string | — | `off` / `minimal` / `low` / `medium` / `high` / `xhigh`. Capped at user's configured max. |
84
91
  | `outputFile` | string | — | Path for the subagent to write full findings. Returns only a summary. |
85
- | `timeout` | number | — | Max milliseconds. Exceeded → SIGTERM (5s grace) → SIGKILL. Background runs are additionally hard-capped at 30 minutes, so a larger value is silently shortened. |
92
+ | `timeout` | number | — | Max milliseconds. Foreground: exceeded → SIGTERM (5s grace) → SIGKILL. Background: the session is aborted and the run ends `stopped` with the timeout reason. A background run with no explicit `timeout` gets the 30-minute default deadline — an explicit timeout is honored as given (a default, not a ceiling). A raw value `≥ 2^31-1` normalizes to no timeout (for a background run, the 30-minute default then applies). |
86
93
  | `cwd` | string | — | Working directory. Defaults to conductor's cwd. |
87
94
  | `background` | boolean | `false` | Spawn as an independent background session; returns an ID immediately. With `tasks` it fans out (one background agent per task, one ID per task), and the conductor is woken once per agent as each finishes. See [Background execution](#background-execution). |
88
95
  | `priority` | string | — | Concurrency priority: `critical` / `high` / `normal` / `low`. Defaults to `normal`; higher-priority delegations queue ahead. `tasks[]` / `graph[]` steps can set `priority` per unit (see below). |
@@ -98,7 +105,7 @@ All settings persist across sessions.
98
105
  | `approvalMode` | string | — | `auto` / `writes` / `always`. Default is user config (`/brl-subagent approval`). `always` is rejected for background runs. |
99
106
  | `force` | boolean | `false` | Dispatch anyway past a capability pre-flight block; the block is downgraded to a warning. |
100
107
  | `retryRunId` | string | — | Re-run a previously failed run with its recorded task and params. |
101
- | `retryOnTimeout` | boolean | `false` | Retry once if the subagent times out. The second timeout is a final failure. |
108
+ | `retryOnTimeout` | boolean | `false` | Retry once if a **foreground** subagent times out. The second timeout is a final failure. Background runs are not auto-retried — re-dispatch with `retryRunId`. |
102
109
 
103
110
  **Capability pre-flight:** before spawning, the extension checks that the resolved toolset can actually do the task — a run/execute/test/compile/benchmark task with no `bash`, or an exploration task (search/grep/find/list/locate/glob) with none of `find`/`ls`/`grep`/`bash`. Such a dispatch is **rejected** by default; `force: true` downgrades the rejection to a **warning**. `force` never suppresses an `outputFile`-without-write conflict — that stays a hard error. Warnings are surfaced in the returned result in every mode.
104
111
 
@@ -108,7 +115,7 @@ All settings persist across sessions.
108
115
 
109
116
  **Fan-out origins are the exception.** Parallel/chain/graph units are recorded per unit, and those records deliberately snapshot **no** `background`, so retrying a unit is a **single run in the foreground**. Pass `background: true` explicitly if you want a background retry.
110
117
 
111
- **Not restored:** `chain` / `tasks` / `graph` and `params` are discarded, so retrying a multi-step run silently degrades to a single task — re-issue it fresh for those shapes. `retryOnTimeout` is **explicit-only**: it is never restored from the recorded run and takes effect only when you pass it on the retry call (it arms a deadline for *this* call).
118
+ **Not restored:** `chain` / `tasks` / `graph` and `params` are discarded, so retrying a multi-step run silently degrades to a single task — re-issue it fresh for those shapes. `retryOnTimeout` is **explicit-only**: it is never restored from the recorded run and takes effect only when you pass it on the retry call (foreground only; it arms a deadline for *this* call).
112
119
 
113
120
  **`template` is asymmetric:** the original run's template is **not** restored, but a `template` you supply explicitly on the retry call **does** take effect (it is resolved before the retry merge, issue #175) — its body wins over the recorded `task`.
114
121
 
@@ -273,7 +280,7 @@ The built-in `code-review` template's slot is `${target}` (its companion `securi
273
280
 
274
281
  ## Background execution
275
282
 
276
- Set `background: true` to spawn the subagent as an independent session that returns an ID immediately and keeps running. Its progress is tracked via `getAgent` and the live monitor while the main session continues. (Steering via `steerAgent` currently records the message in the transcript and marks the agent as steered — delivery to the live session is pending pi's extension API.)
283
+ Set `background: true` to spawn the subagent as an independent session that returns an ID immediately and keeps running. Its progress is tracked via `getAgent` and the live monitor while the main session continues. Steering via `steerAgent` delivers the message into the agent's live session — it is queued while the agent runs and delivered after the current tool call finishes, before the next model call. Repeat steers work, and a delivery failure surfaces as a real tool error rather than a recorded-but-undelivered steer.
277
284
 
278
285
  **System prompt semantics:** background sessions are spawned with the same built prompt as foreground subagents (base prompt when `inheritSystemPrompt: true`, custom prompt, preset guidance, and subagent instructions). Like pi's own `--append-system-prompt`, supplying this prompt **replaces** any discovered `.pi/APPEND_SYSTEM.md` / global `APPEND_SYSTEM.md` content — this matches foreground subagent behavior exactly. With `inheritSystemPrompt: true` (the default) your conductor session's instructions — including its own appended content — are inherited through the base prompt.
279
286
 
@@ -281,7 +288,7 @@ Set `background: true` to spawn the subagent as an independent session that retu
281
288
 
282
289
  **Background safety controls (issue #28):** background agents honor the same safety controls as foreground runs — no more unattended sessions that bypass approval, git isolation, deadlines, or cost:
283
290
 
284
- - **Per-agent timeout** — the deadline is armed immediately after the prompt is issued, so in-prompt preflight (auth, model resolution) counts toward it. Background timeouts are hard-capped at 30 minutes — a larger `timeout` is silently shortened. On expiry the session is aborted and the agent ends with status `stopped` and the timeout reason. Timeout values are normalized (`0`/negative/`NaN`/`Infinity`/`≥ 2^31` → no timeout) and a double-fire guard prevents the timer from acting on an already-settled agent.
291
+ - **Per-agent timeout** — the deadline is armed immediately after the prompt is issued, so in-prompt preflight (auth, model resolution) counts toward it. A background run with no explicit `timeout` gets a 30-minute default deadline (the issue #28 orphan protection); an explicit timeout is honored as given — 30 minutes is the default, not a ceiling. On expiry the session is aborted and the agent ends with status `stopped` and the timeout reason. Timeout values are normalized (`0`/negative/`NaN`/`Infinity`/`≥ 2^31` → no timeout, which for a background run means the 30-minute default) and a double-fire guard prevents the timer from acting on an already-settled agent.
285
292
  - **Session cost limit (R5)** — the cost check runs before the background spawn, so a session at its limit cannot bypass it by delegating to background. For a background fan-out the whole batch is checked up front as per-task estimate × N.
286
293
  - **Approval mode** — `approvalMode: 'always'` is rejected for background agents (there is no interactive dialog to approve a diff while running unattended); `'writes'` silently auto-approves with a warning logged. For a fan-out, `'always'` rejects the whole batch before any spawn and `'writes'` warns once for the batch.
287
294
  - **gitMode branch isolation** — with `gitMode: 'branch'` a work branch is created before the run, the agent's changes are committed at teardown so the diff is real, the diff is captured and surfaced via `get_subagent_result`, and the branch is then switched away from and deleted. This requires a clean working tree — a dirty tree is refused loudly rather than risking the base branch. `gitMode: 'branch'` is rejected for background fan-out — see [Background fan-out](#background-fan-out).
@@ -296,6 +303,11 @@ Three checks reject the fan-out up front, before any spawn: `approvalMode: 'alwa
296
303
 
297
304
  If a spawn fails mid-loop, fan-out stops and reports the failed task plus the IDs already started; an abort mid-loop stops further spawns. Either way, the agents already started stay detached and still wake the conductor. Everything else is unchanged: single background, foreground parallel, the `MAX_PARALLEL_TASKS` cap (8), a live-monitor row per agent, `get_subagent_result` / `steer_subagent` / `stop_subagent` by agent ID, per-agent timeouts, and a single `'writes'` approval warning for the batch.
298
305
 
306
+ ## Contributing
307
+
308
+ See [CONTRIBUTING.md](CONTRIBUTING.md) for setup, the branch model (`main` = releases, `dev` = integration),
309
+ the worktree workflow, and the test gates. Development docs live in [`.development/`](.development/).
310
+
299
311
  ## Changelog
300
312
 
301
313
  See [CHANGELOG.md](CHANGELOG.md) for the release history.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "brl-subagent",
3
- "version": "2.3.9",
4
- "description": "Subagent extension for pi with configurable model and thinking mode via selection UI",
3
+ "version": "2.4.0",
4
+ "description": "Subagent delegation for pi — blocking or background runs, chain/parallel/graph modes, presets and task templates, live monitor, and dispatch capability guards.",
5
5
  "keywords": [
6
6
  "pi-package"
7
7
  ],
@@ -25,7 +25,9 @@
25
25
  ]
26
26
  },
27
27
  "scripts": {
28
- "typecheck": "tsc --noEmit"
28
+ "typecheck": "tsc --noEmit",
29
+ "docs:arch": "node scripts/docs-arch.mjs --write",
30
+ "docs:decisions": "node scripts/docs-decisions.mjs --write"
29
31
  },
30
32
  "peerDependencies": {
31
33
  "@earendil-works/pi-agent-core": "*",
@@ -35,13 +37,13 @@
35
37
  "typebox": "*"
36
38
  },
37
39
  "devDependencies": {
38
- "@earendil-works/pi-agent-core": "^0.87.0",
39
- "@earendil-works/pi-ai": "^0.87.0",
40
- "@earendil-works/pi-coding-agent": "^0.87.0",
41
- "@earendil-works/pi-tui": "^0.87.0",
40
+ "@earendil-works/pi-agent-core": "^1.0.0",
41
+ "@earendil-works/pi-ai": "^1.0.0",
42
+ "@earendil-works/pi-coding-agent": "^1.0.0",
43
+ "@earendil-works/pi-tui": "^1.0.0",
42
44
  "jiti": "^2.7.0",
43
- "typebox": "^1.3.25",
44
- "typescript": "^5.9.3",
45
+ "typebox": "^1.3.34",
46
+ "typescript": "7.0.2",
45
47
  "vitest": "^5.0.0"
46
48
  },
47
49
  "overrides": {
@@ -1,3 +1,4 @@
1
+ // Purpose: Session-bound concurrency queue: slot acquisition/release, priority insertion, and progress counters.
1
2
  /**
2
3
  * brl-subagent — Concurrency Controller (F8)
3
4
  *
package/src/diff.ts CHANGED
@@ -1,3 +1,4 @@
1
+ // Purpose: Parses git unified diffs into structured per-file summaries and hunks for the result UI.
1
2
  /**
2
3
  * brl-subagent — Git Diff Parser (P5)
3
4
  *
package/src/event-bus.ts CHANGED
@@ -1,3 +1,4 @@
1
+ // Purpose: In-memory lifecycle pub/sub (`subagent:*` events) for extensions and the completion wake.
1
2
  import type { SubagentEvent, SubagentEventType, SubagentEventListener } from './types';
2
3
 
3
4
  // Event listeners by type
package/src/git.ts CHANGED
@@ -1,3 +1,4 @@
1
+ // Purpose: Branch-based git workflow for worktree runs: branch creation, diff capture, switch-back, cleanup.
1
2
  /**
2
3
  * brl-subagent — Git Integration (P3)
3
4
  *
package/src/history.ts CHANGED
@@ -1,3 +1,4 @@
1
+ // Purpose: Run-record store: creation, finalization, retry lookup, and history pruning.
1
2
  /**
2
3
  * brl-subagent — Run History
3
4
  *