2 Commits

Include renames

Author	SHA1	Message	Date
HomerandClaude Opus 5.5	3a206959b6	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>	2026-11-09 18:04:24 +00:00
HomerandClaude Opus 5.5	02c7282e74	Harness spec 3.3.0: subagents — the word, the model, capacity, the offer ... - "Subagent" in every text a person or a model reads; "helper" retired (the team area's step helper_done is now task_done). - A subagent runs on the session's model unless the person named another in this session's own messages; task's and team_add's `model` is refused otherwise. No setting chooses a subagent's model. - Capacity: another model on the session's model's one-model server is refused; the session's model as its own subagent needs parallel >= 2 or no limit; no fallback. - The agents {min, max} setting is shown as Subagents, offered when a model could serve; context.note.team_own when the session's model cannot. - subagents.md, loop.json subagents, conformance/subagents.json (26 cases). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-09 16:56:31 +00:00