From 1e15c8cc6b8b939a98d3a684c80ef269e6e0d59d Mon Sep 17 00:00:00 2001
From: iris <iris@hyperhive.local>
Date: Thu, 2 Jul 2026 12:02:02 +0200
Subject: [PATCH] fix(dashboard): replace stale 'manager' with 'submitter' in
 approval UI text
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Two operator-visible strings and one code comment still referenced 'the
manager' in the approval card UI:

- init_config card description: 'manager customises agent.nix before
  spawn' -> 'submitting agent customises agent.nix before spawn'
- deny form data-prompt: 'sent to manager' -> 'sent to submitter'
  (the deny note goes to the ApprovalResolved submitter, not a fixed
  manager role)
- code comment: 'surfaced to the manager via' -> 'surfaced to the
  submitting agent via'
- builds.html meta text: 'manager learns each outcome' -> 'the
  submitting agent learns each outcome'

The 'manager' role is no longer structural — root-ness is topological.
Any agent with the approvals tool group can submit; the note/event routes
to the submitter.
---
 frontend/packages/dashboard/src/builds.html | 2 +-
 frontend/packages/dashboard/src/call.js     | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/frontend/packages/dashboard/src/builds.html b/frontend/packages/dashboard/src/builds.html
index c0ad63ed..596b50ff 100644
--- a/frontend/packages/dashboard/src/builds.html
+++ b/frontend/packages/dashboard/src/builds.html
@@ -58,7 +58,7 @@
     <!-- M3T4 1NPUTS: select inputs to nix flake update in /meta/. -->
     <section class="builds-pane" id="builds-pane-meta" data-tab-pane="meta"
              role="tabpanel" aria-labelledby="builds-tab-meta">
-      <p class="meta">select inputs to <code>nix flake update</code> in <code>/meta/</code>. selected agents rebuild in sequence after the lock bump; manager learns each outcome via the usual <code>rebuilt</code> system event.</p>
+      <p class="meta">select inputs to <code>nix flake update</code> in <code>/meta/</code>. selected agents rebuild in sequence after the lock bump; the submitting agent learns each outcome via the usual <code>rebuilt</code> system event.</p>
       <div id="meta-inputs-section">
         <p class="meta">loading…</p>
       </div>
diff --git a/frontend/packages/dashboard/src/call.js b/frontend/packages/dashboard/src/call.js
index 7500fe53..2440c6df 100644
--- a/frontend/packages/dashboard/src/call.js
+++ b/frontend/packages/dashboard/src/call.js
@@ -399,7 +399,7 @@ export function renderApprovals() {
     } else {
       body.append(el('span', { class: 'meta' },
         isInit
-          ? 'scaffold proposed config repo — manager customises agent.nix before spawn'
+          ? 'scaffold proposed config repo — submitting agent customises agent.nix before spawn'
           : 'new sub-agent — container will be created on approve'));
     }
     li.append(body);
@@ -407,12 +407,12 @@ export function renderApprovals() {
     // ── decision actions ─────────────────────────────────────────
     // Deny prompts the operator for an optional reason; the submit
     // handler stashes it into a hidden `note` input that rides along
-    // on the POST and is surfaced to the manager via
+    // on the POST and is surfaced to the submitting agent via
     // HelperEvent::ApprovalResolved { note }.
     const denyForm = el('form', {
       method: 'POST', action: '/api/deny/' + a.id,
       class: 'inline', 'data-async': '', 'data-no-refresh': '',
-      'data-prompt': 'reason for denying (optional, sent to manager):',
+      'data-prompt': 'reason for denying (optional, sent to submitter):',
     });
     denyForm.append(el('button', { type: 'submit', class: 'btn btn-deny' }, 'DENY'));
     li.append(el('div', { class: 'approval-actions' },