Sonny: lead.md in 16 KiB, the same rules in fewer words

sonny/FEATURES.md

@@ -47,7 +47,7 @@ per feature; group small things into the row they belong to.
 | Several leads in one folder (`/lead`) | experimental | added 10-29 #365; each store notes its last lead 10-29 #376 | Parallel conversations in one project without a second folder | ? |
 | Tasks: the lead starts agents and picks each one's folder: a git worktree by default, a worktree of a repository inside its folder (`folder`), or an empty folder of its own (`own_folder`) (`sonny task`) | shipped | added 10-26 #142, #162; brief names its copy 10-28 #234; copies isolated, done tasks removed 10-28 #227; worktree starts with the lead's build folders 10-28 #286; the lead picks the folder, outside git tasks share the lead's folder 10-30 #409; a start lists the folders gone tasks left, with their sizes 10-30 | In git, tasks get worktrees so they never step on the lead or each other; outside git the folder is often one unit (shared caches, its own build tools), so the lead decides whether a task shares it, takes a worktree of one repository in it, or starts empty | ? |
 | Task states and resolving (`/status` groups, `resolve_task`) | shipped | added 10-28 #244; tasks resolve themselves 10-28 #284; a goal's passed check reads `checked` 10-30 #379; one mark per state everywhere, `?` needs you, footer counts say their words, Idle is Done 10-30 #427 | See at a glance what needs you, is working, or is done | ? |
-| Lead and task roles as editable files (`~/.agents/agents/lead.md`, `task.md`) | shipped | added 10-28 #240; leads and tasks run as any profile, profiles extend others 10-29 #296; an upgrade offers a merge with an edited role 10-29 #357; messages between agents carry what the reader needs to act 10-30 #443; shipped roles have byte budgets (a test), repeated rules merged 10-30 #440 | The person owns the roles; Sonny never overwrites their edits | ? |
+| Lead and task roles as editable files (`~/.agents/agents/lead.md`, `task.md`) | shipped | added 10-28 #240; leads and tasks run as any profile, profiles extend others 10-29 #296; an upgrade offers a merge with an edited role 10-29 #357; messages between agents carry what the reader needs to act 10-30 #443; shipped roles have byte budgets (a test), repeated rules merged 10-30 #440; lead.md in 16 KiB, the same rules in fewer words 10-30 | The person owns the roles; Sonny never overwrites their edits | ? |
 | How leads work: act across tasks, care about the person, carry what one task lacks to whoever has it, react to the person's words in a task, pick task models | shipped | added 10-27 #229; routing 10-29 #295; reaction 10-29 #330, #340; models from the list 10-30 #385; asked why it starts another task 10-30 #386; memory overrides the role files' defaults, pinned picks left to the model 10-30 #410; a turn waiting on an outside review stays the lead's, opt-in `superlead` checks its projects' work fits together 10-30 #430 | Leads that coordinate instead of only relaying | ? |
 | Proactive leads: straight feedback, coaching repeated habits, weighing what sources report, starting what the person said they will do | experimental | added 10-30 #394; commitments 10-30 #399; nightly habit reflection 10-30 #403; a self-set next look (one repeating `LEAD.next` trigger at the earliest time something held goes stale, skipped while the person writes, later when looks find nothing, none when nothing is open; no fixed heartbeat) 10-30 #433; the look repeats (`every` or `cron`), with a ready skip-while-writing check and a name example 10-30 | Agents that flag what the person missed, say what they see unsugared, and follow through without being asked; a lead hears only when something happens, so what goes stale quietly needs a look it sets itself | ? |
 | Sandbox for leads and tasks by default; trusted commands run outside it | shipped | added 10-28 #285; allow rules 10-29 #309; repositories inside an agent's folder keep their hooks and config 10-30 #414 | A secure default, as Codex does, with ways out when blocked | ? |