tumwater 0.1.2 → 0.2.0

package/dist/src/ui/gui/gui-client-settings.js

@@ -1,6 +1,8 @@
+// vocabulary: plain
 /** The dashboard's Settings view, browser-side: the curated top-level config keys
  * (EDITABLE_CONFIG_KEYS's set, mirrored here for the labels) as label + current value +
- * inline field + Save + Clear, one row per key. Values load once through GET /api/config when
+ * inline field + Save + Clear, one row per key (the Notify row also has Send test, which
+ * posts to POST /api/notify-test). Values load once through GET /api/config when
  * the view is first opened — no polling loop of its own; a re-click of the tab refetches, like
  * the other views' refresh-on-open. Save posts {key, value} to POST /api/config-set — the
  * same setConfigKey write path `tumwater config set` uses — and Clear posts {key} to
@@ -9,8 +11,18 @@
  * success/error toast pattern the composer's send uses (showFlash). Spliced into
  * gui-client.ts's script, reaching its helpers (esc, $, getJson, postJson, showFlash) through
  * that concatenation. A second card, "Health check", runs the same checks as `tumwater doctor`
- * through GET /api/doctor on each open (and on its Re-run button) and paints the report. */
+ * through GET /api/doctor on each open (and on its Re-run button) and paints the report; a
+ * third, "Disabled roles", lists every disabled role (GET /api/retire), each with an Enable
+ * button (POST /api/role-enable) and — for a role that still keeps worktree/branch leftovers — a
+ * two-click Retire button (POST /api/retire). */
 export const GUI_CLIENT_SETTINGS_JS = String.raw `  // settings-view:start
+  // One home for turning a thrown value into the message a flash shows: the fetch/parse/post
+  // helpers throw the server's JSON-decoded value, which for the server's own errors is an
+  // {error} object (its message on the .message field) — the three Save/Clear/Brief catch
+  // blocks that flash the outcome share this coercion so the wording cannot drift.
+  function clientErrorMessage(err) {
+    return err && err.message ? err.message : String(err);
+  }
   // The curated keys, in display order: [key, label]. Mirrors the server's
   // EDITABLE_CONFIG_KEYS (src/config/config-editable-keys.ts) by hand — the settings test pins
   // this list's keys and order to that constant.
@@ -21,7 +33,7 @@ export const GUI_CLIENT_SETTINGS_JS = String.raw `  // settings-view:start
     ["maxDailyCostUsd", "Daily spend cap (USD)"],
     ["quietHours", "Quiet hours"],
     ["notify", "Notify hook"],
-    ["agents", "Agent backends (JSON)"],
+    ["backends", "Agent backends (JSON)"],
   ];
   // One row per key: the current value into an inline field (esc'd, like every rendered
   // value on the page), Save submits the row's form. A null (unset) key renders empty —
@@ -39,38 +51,124 @@ export const GUI_CLIENT_SETTINGS_JS = String.raw `  // settings-view:start
       "<input class='field' id='set-" + k[0] + "' value='" + esc(settingsFieldValue(d[k[0]])) + "'>" +
       "<button type='submit' class='btn btn-sm'>Save</button>" +
       "<button type='button' class='btn btn-sm rowaction' data-action='unset'>Clear</button>" +
+      (k[0] === "notify" ? "<button type='button' class='btn btn-sm rowaction' data-action='notify-test' title='Runs the saved hook once with a synthetic merge_failed event'>Send test</button>" : "") +
       "</form>").join("");
   }
   // The view's one panel: built once, values fetched on each open of the tab (the boot's
   // switchView calls fetchSettings) — no polling loop of its own.
   function buildSettingsView() {
     buildOnce("settings-view", "<div class='view-head'><div><h1>Settings</h1>" +
-      "<p>The fleet-wide settings an operator edits from here; everything else lives in tumwater.json or the CLI.</p></div></div>" +
+      "<p>The team-wide settings you edit from here; everything else lives in tumwater.json or the CLI.</p></div></div>" +
       "<div class='card' id='settingscard'><div class='empty'>Loading…</div></div>" +
-      "<div class='card' id='doctorcard'><div class='settings-row'><strong>Health check</strong>" +
+      "<div class='card' id='doctorcard'><div class='settings-row'><strong>Health</strong>" +
       "<span>The same checks as <code>tumwater doctor</code>.</span>" +
+      "<label><input type='checkbox' data-action='doctor-problems'> Problems only</label>" +
       "<button type='button' class='btn btn-sm' data-action='doctor-rerun'>Re-run</button></div>" +
-      "<div id='doctorbody'><div class='empty'>Checking…</div></div></div>");
+      "<div id='doctorbody'><div class='empty'>Checking…</div></div></div>" +
+      "<div class='card' id='retirecard'><div class='empty'>Loading…</div></div>" +
+      "<div class='card' id='briefcard'><div class='empty'>Loading…</div></div>");
   }
   // The Health check card's body: header, one row per check (level badge, name, detail), the
   // verdict — everything esc'd. The pill is built inline (gui-client.ts's pill sits outside
-  // this region). A missing checks array renders no rows.
-  function renderDoctorReport(d) {
+  // this region). A missing checks array renders no rows. With problems (the Problems only
+  // checkbox), only the warn and fail rows render and a hidden-count line names how many ok
+  // rows were cut, mirroring tumwater doctor --problems's problemsOnly/renderDoctorProblems.
+  function renderDoctorReport(d, problems) {
     const tones = { ok: "green", warn: "amber", fail: "red" };
-    const rows = (Array.isArray(d.checks) ? d.checks : []).map((c) =>
+    const all = Array.isArray(d.checks) ? d.checks : [];
+    const checks = problems ? all.filter((c) => c.level !== "ok") : all;
+    const hidden = all.length - checks.length;
+    const rows = checks.map((c) =>
       "<div class='settings-row'><span class='pill t-" + (tones[c.level] || "amber") + "'>" + esc(c.level) + "</span>" +
       "<strong>" + esc(c.name) + "</strong><span>" + esc(c.detail) + "</span></div>").join("");
-    return "<p>" + esc(d.header) + "</p>" + rows + "<p>" + esc(d.verdict) + "</p>";
+    return "<p>" + esc(d.header) + "</p>" + rows +
+      (problems && hidden > 0 ? "<p class='empty'>" + hidden + " " + (hidden === 1 ? "ok check" : "ok checks") + " hidden</p>" : "") +
+      "<p>" + esc(d.verdict) + "</p>";
   }
+  // The last resolved doctor report and whether the card paints only its problems; the
+  // Problems only checkbox toggles the latter and repaints the cached body without rerunning
+  // the checks.
+  let lastDoctor = null;
+  let doctorProblems = false;
   async function fetchDoctor() {
     buildSettingsView();
     const body = $("doctorbody");
     body.innerHTML = "<div class='empty'>Checking…</div>";
     try {
-      body.innerHTML = renderDoctorReport(await getJson("/api/doctor"));
+      const report = await getJson("/api/doctor");
+      lastDoctor = report;
+      body.innerHTML = renderDoctorReport(report, doctorProblems);
+    } catch (err) {
+      body.innerHTML = errorPanel("Health checks could not run", err, "empty");
+    }
+  }
+  function toggleDoctorProblems(checked) {
+    doctorProblems = checked;
+    const body = $("doctorbody");
+    if (lastDoctor !== null) body.innerHTML = renderDoctorReport(lastDoctor, doctorProblems);
+  }
+  // The Disabled roles card: every role set to enabled: false (GET /api/retire), each with an
+  // Enable button (POST /api/role-enable) and — for a role that still keeps a worktree, branch,
+  // merge ref, or paused marker — a two-click Retire button (POST /api/retire), the same removal
+  // as tumwater retire --role <id>. A role the safety rails object to shows the objections and
+  // the CLI's --force command instead: the dashboard never forces.
+  let lastRetirable = null;
+  const retireSlot = confirmSlot(paintRetirable);
+  function renderRetirable(d, armed) {
+    const rows = (d.roles || []).map((r) => {
+      const hasLeftovers = (r.wouldRemove || []).length > 0;
+      const head = "<strong>" + esc(r.role) + "</strong>" +
+        (hasLeftovers ? "<span>would remove " + r.phrases.map(esc).join(", ") + "</span>" : "<span>no leftovers to remove</span>") +
+        "<button type='button' class='btn btn-sm' data-action='enable' data-role='" + esc(r.role) + "'>Enable</button>";
+      if (r.objections.length > 0) {
+        return "<div class='settings-row'>" + head + r.objections.map((o) => "<span>" + esc(o) + "</span>").join("") +
+          "<code>tumwater retire --role " + esc(r.role) + " --force</code></div>";
+      }
+      const retireBtn = hasLeftovers ? "<button type='button' class='btn btn-sm' data-action='retire' data-role='" + esc(r.role) + "'>" +
+        (armed(r.role) ? "Confirm retire" : "Retire") + "</button>" : "";
+      return "<div class='settings-row'>" + head + retireBtn + "</div>";
+    }).join("");
+    return "<div class='settings-row'><strong>Disabled roles</strong><span>Roles set to enabled: false — re-enable one, or remove the leftovers " +
+      "the same way <code>tumwater retire --role &lt;id&gt;</code> does.</span></div>" +
+      (rows || "<div class='empty'>No role is disabled.</div>");
+  }
+  function paintRetirable() {
+    if (lastRetirable) $("retirecard").innerHTML = renderRetirable(lastRetirable, retireSlot.armed);
+  }
+  async function fetchRetirable() {
+    buildSettingsView();
+    try {
+      lastRetirable = await getJson("/api/retire");
+      paintRetirable();
+    } catch (err) {
+      $("retirecard").innerHTML = errorPanel("Disabled roles could not load", err, "empty");
+    }
+  }
+  // The row's Enable button: re-enable the role through POST /api/role-enable (writing
+  // roles.<base>.enabled), flash the server's message, and refetch so the card drops the row.
+  async function enableRole(role) {
+    try {
+      const d = await postJson("/api/role-enable", { role: role });
+      showFlash(d.message);
+    } catch (err) {
+      showFlash("error: " + clientErrorMessage(err));
+    }
+    await fetchRetirable();
+  }
+  // First click arms the role's button; a second within the confirm window posts the retire.
+  async function confirmRetire(role) {
+    if (!retireSlot.armed(role)) {
+      retireSlot.arm(role);
+      return;
+    }
+    retireSlot.disarm();
+    try {
+      const d = await postJson("/api/retire", { role: role });
+      showFlash(d.message);
     } catch (err) {
-      body.innerHTML = errorPanel("Health check could not run", err, "empty");
+      showFlash("error: " + clientErrorMessage(err));
     }
+    await fetchRetirable();
   }
   async function fetchSettings() {
     buildSettingsView();
@@ -101,7 +199,7 @@ export const GUI_CLIENT_SETTINGS_JS = String.raw `  // settings-view:start
       const d = await postJson("/api/config-set", { key: key, value: value });
       showFlash(d && d.oldValue === null ? "Saved " + key + " (was unset)" : "Saved " + key);
     } catch (err) {
-      showFlash("error: " + (err && err.message ? err.message : String(err)));
+      showFlash("error: " + clientErrorMessage(err));
     }
   }
   // The row's Clear button: retract the key through /api/config-unset, then refetch so the
@@ -115,7 +213,43 @@ export const GUI_CLIENT_SETTINGS_JS = String.raw `  // settings-view:start
       showFlash(d && d.oldValue !== undefined ? "Unset " + key + " (was " + JSON.stringify(d.oldValue) + ")" : "Nothing to unset for " + key + " — it was already the default");
       await fetchSettings();
     } catch (err) {
-      showFlash("error: " + (err && err.message ? err.message : String(err)));
+      showFlash("error: " + clientErrorMessage(err));
+    }
+  }
+  // The Notify row's Send test button: POST /api/notify-test runs the saved hook once, the same
+  // test that "tumwater notify --test" runs. The hook can take up to 10 s, so say so first.
+  async function testNotify() {
+    showFlash("Sending a test notification…");
+    try {
+      const d = await postJson("/api/notify-test", {});
+      showFlash((d.passed ? "" : "error: ") + d.message);
+    } catch (err) {
+      showFlash("error: " + clientErrorMessage(err));
+    }
+  }
+  // The Brief card: the brief file's name and the prompt in a textarea, filled from
+  // GET /api/brief on each open. The form is deliberately not a settings-row, so the boot's
+  // delegated settings submit listener never routes it to saveSetting.
+  async function fetchBrief() {
+    buildSettingsView();
+    const card = $("briefcard");
+    try {
+      const d = await getJson("/api/brief");
+      card.innerHTML = "<form class='brief-form'><strong>Brief</strong> <span class='settings-key'>" + esc(d.file) + "</span>" +
+        "<textarea class='field' id='brief-text' rows='12'>" + esc(d.prompt) + "</textarea>" +
+        "<button type='submit' class='btn btn-sm'>Save</button></form>";
+    } catch (err) {
+      card.innerHTML = errorPanel("Brief could not load", err, "empty");
+    }
+  }
+  // Save posts the textarea's text to POST /api/brief — the same checks and commit as
+  // tumwater brief --file — and flashes the outcome.
+  async function saveBrief(form) {
+    try {
+      const d = await postJson("/api/brief", { prompt: form.querySelector("textarea").value });
+      showFlash(!d.changed ? "Brief unchanged" : d.committed ? "Brief saved (committed to main)" : "Brief saved");
+    } catch (err) {
+      showFlash("error: " + clientErrorMessage(err));
     }
   }
   // settings-view:end

package/dist/src/ui/gui/gui-client-sound.js

@@ -1,6 +1,7 @@
+// vocabulary: plain
 /** The dashboard's sound layer, browser-side: one short synthesized cue when a new needs-you
  * alert appears (a failing loop, a red main, a spent budget, a lost server), scoped from
- * docs/feature-gui-audio-sound-effects.md to the alerts cue — the one moment the fleet
+ * docs/feature-gui-audio-sound-effects.md to the alerts cue — the one moment the team
  * genuinely needs a human. Client-side only: Web Audio is a browser built-in, so the zero
  * runtime dependencies principle holds, and every path degrades to silence — no AudioContext,
  * no user gesture yet, or a muted preference all leave the page quiet and error-free. Spliced