README + diagram: the roles as they are, one coordinator, one repo agent per repo, one agent per plugin

The swarm section and the delegation diagram named a gate-keeper that checks each merge; that role
does not exist. The roles are one coordinator agent that puts the merges onto the pilot in order, one
repo agent per repository that handles its branches and watches the work being done in it, and one
agent per plugin. The harness paragraph, the kitchen list, the alt text, the diagram's second circle,
its caption and its legend say so, and the Experimental shelf's "roaming agent" becomes an agent per
plugin. The PNG is re-rendered at 2x.

README.md

@@ -750,10 +750,11 @@ can be seen on the pilot server as soon as it joins the pilot.
 
 **Bring your own harness.** dx-maps works with whatever AI coding agent or agent harness you already
 use. The repo gives you the branch strategy below, the checks (`bun run gates:pre`) and the Plugin
-Studio; it does not ship a harness. Roles such as a coordinator that puts the merges onto the pilot in order, or a
-gate-keeper that reads each change before it joins the pilot, are jobs your harness gives to its agents.
+Studio; it does not ship a harness. The roles are one coordinator agent that puts the merges onto the pilot
+in order, one repo agent per repository that handles its branches and watches the work being done in it,
+and one agent per plugin; your harness gives these jobs to its agents.
 
-![The delegation model: the pilot branch (development) at the centre behind the pilot lock; publishing to the landing branch (main) and its outputs below it; inside the Plugin Studio; eight plugins around it, each owned by one agent; a coordinator and a gate-keeper over the agents; below, how a change joins the pilot and then reaches the landing branch, in four steps, the three outputs, and how it scales: one PR branch per plugin, a self-hosted git service, and publishing to a public host only from the landing branch](documentation/readme-images/delegation-model.png)
+![The delegation model: the pilot branch (development) at the centre behind the pilot lock; publishing to the landing branch (main) and its outputs below it; inside the Plugin Studio; eight plugins around it, each owned by one agent; a coordinator and a repo agent over the plugin agents; below, how a change joins the pilot and then reaches the landing branch, in four steps, the three outputs, and how it scales: one PR branch per plugin, a self-hosted git service, and publishing to a public host only from the landing branch](documentation/readme-images/delegation-model.png)
 
 <sub>[Open the diagram full size](documentation/readme-images/delegation-model.png): on a phone its small text needs it.</sub>
 
@@ -842,8 +843,9 @@ So the project works like a busy kitchen:
 2. **Only one change joins the pilot at a time.** Whoever holds the *pilot lock* first catches up with
    everyone else's latest work, fixes any clash itself and runs every check; the change goes into the
    pilot branch only if nothing fails. The pilot branch always works.
-3. **Someone keeps order.** A coordinator can put the merges onto the pilot in order, and a gate-keeper can read
-   each change by its content before it joins the pilot. Your harness gives these jobs to its agents.
+3. **Someone keeps order.** One coordinator agent puts the merges onto the pilot in order, and one repo agent
+   per repository handles its branches and watches the work being done in it. Your harness gives these jobs
+   to its agents.
 4. **The landing branch moves only when a person approves a publish**, after the checks pass on that exact version.
    The pilot server follows the pilot branch; the landing server rebuilds from the landing branch.
 

documentation/readme-images/src/delegation-model.svg

@@ -116,14 +116,14 @@
 <text x="614.1" y="556.0" text-anchor="middle" font-size="12" font-weight="800" fill="#155e75">Experimental</text>
 <text x="614.1" y="570.0" text-anchor="middle" font-size="10.5" fill="#155e75">shelf · 5 plugins</text>
 <circle cx="543.4" cy="351.1" r="40" fill="#ecfeff" stroke="#0891b2" stroke-width="2.5"/>
-<text x="543.4" y="349.1" text-anchor="middle" font-size="12" font-weight="700" fill="#155e75">roaming</text>
-<text x="543.4" y="364.1" text-anchor="middle" font-size="12" font-weight="700" fill="#155e75">agent</text>
+<text x="543.4" y="349.1" text-anchor="middle" font-size="12" font-weight="700" fill="#155e75">an agent</text>
+<text x="543.4" y="364.1" text-anchor="middle" font-size="12" font-weight="700" fill="#155e75">per plugin</text>
 <circle cx="690" cy="248" r="56" fill="#f5f3ff" stroke="#7c3aed" stroke-width="3.5"/>
 <text x="690" y="254" text-anchor="middle" font-size="14" font-weight="800" fill="#4c1d95">coordinator</text>
 <circle cx="812" cy="248" r="56" fill="#f1f5f9" stroke="#334155" stroke-width="3.5"/>
-<text x="812" y="254" text-anchor="middle" font-size="14" font-weight="800" fill="#1e293b">gate-keeper</text>
-<text x="884" y="192" font-size="17" fill="#4c1d95">a coordinator puts the merges in order;</text>
-<text x="884" y="216" font-size="17" fill="#1e293b">a gate-keeper checks each one by its content</text>
+<text x="812" y="254" text-anchor="middle" font-size="14" font-weight="800" fill="#1e293b">repo agent</text>
+<text x="884" y="192" font-size="17" fill="#4c1d95">one coordinator puts the merges in order;</text>
+<text x="884" y="216" font-size="17" fill="#1e293b">a repo agent per repo runs its branches and watches the work</text>
 <text x="750" y="1502" text-anchor="middle" font-size="20" font-weight="800" fill="#1e3a8a">one owner per plugin, in its own branch · a second reader for every change</text>
 <rect x="36" y="110" width="304" height="280" rx="14" fill="#f8fafc" stroke="#e2e8f0" stroke-width="2"/>
 <circle cx="64" cy="142" r="11" fill="#166534" stroke="#14532d" stroke-width="2.5"/>
@@ -141,7 +141,7 @@
 <circle cx="64" cy="334" r="11" fill="#f5f3ff" stroke="#7c3aed" stroke-width="2.5"/>
 <text x="88" y="339" font-size="15" fill="#334155">coordinator — orders merges</text>
 <circle cx="64" cy="366" r="11" fill="#f1f5f9" stroke="#334155" stroke-width="2.5"/>
-<text x="88" y="371" font-size="15" fill="#334155">gate-keeper — checks each merge</text>
+<text x="88" y="371" font-size="15" fill="#334155">repo agent — one per repo</text>
 <rect x="60" y="1536" width="1380" height="232" rx="20" fill="#fef2f2" stroke="#fca5a5" stroke-width="2"/>
 <text x="750" y="1578" text-anchor="middle" font-size="22" font-weight="800" fill="#7f1d1d">How a change joins the pilot — one at a time, so many plugins can be built at once</text>
 <rect x="80.0" y="1600" width="305" height="148" rx="14" fill="#fff" stroke="#dc2626" stroke-width="2"/>