Harness spec 3.3.0: the Subagents setting is Min and Max, one range with two handles, counting the agent itself

loop.json subagents.setting: min/max are "Min" and "Max" (not fewest/most), with a hint and a short
form saying the numbers include the session's own agent - 1 is the agent alone, Max 4 the agent and
up to three subagents. team.md §2 and subagents.md §4 state that, and the UI rule: one range from 1
to the cap with two handles (a slider; two numbers on one line in a terminal). team_add says the
size includes the caller. Conformance team: max 2 is the lead and one task subagent.

Still 3.3.0, unreleased: edited in place.

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

harness/README.md

@@ -88,8 +88,10 @@ Written ahead of both implementations as LLeMbas CLI 02c7282; both carry it in t
   limit, else "This model serves one request at a time: name another model, on another server,
   for subagents." — and nothing else is picked. A member is refused for these too, and still only
   waits for a full model.
-- **The offer**: the `agents {min, max}` setting is shown as **Subagents** (*fewest*, *most*;
-  `loop.json` `subagents.setting`), and with it the team tools, when subagents are enabled and at
+- **The offer**: the `agents {min, max}` setting is shown as **Subagents** (**Min**, **Max**;
+  `loop.json` `subagents.setting`) — one range from 1 to the cap with two handles, and a hint that
+  the numbers count the session's own agent: 1 is the agent alone, Max 4 the agent and up to three
+  subagents — and with it the team tools, when subagents are enabled and at
   least one model could serve: the session's, with the capacity, or any usable model off its
   one-model server. `context.note.team_own` tells the model, and `subagents.setting.own` the
   person, when the session's model cannot serve subagents itself.