agents: remove the hive-level /effort control too

mara on #5034: "effort shares /models fate". The per-agent web UI no
longer sets effort: the `/effort` slash command, the effort picker,
`POST /api/effort`, `Bus::set_effort`, the `hyperhive-effort` writer,
`EFFORT_LEVELS`/`is_valid_effort` and the ACP effort-list payload are
gone, and `lib/modelEffort.ts` with them. The effort chip is
display-only and shows its source (`effort_source` in `/api/state`);
on ACP it stays hidden while the session offers no effort level.

The read side is unchanged: with no swarm value an agent runs an
existing `hyperhive-effort` file, else its agent.nix effort, else
medium. Existing files are not touched.

Refs #5034

frontend/packages/agent/src/lib/loginAction.ts

@@ -2,7 +2,7 @@
 // (this agent's own backend, `hive-agent/src/web_ui/auth.rs`), so a
 // plain `fetch` is safe (unlike `pauseAction.ts`'s dashboard-origin
 // actions). Same `{ ok, detail }` shape and `redirect: 'manual'` /
-// broad-2xx-4xx-treated-as-ok contract as `modelEffort.ts` — none of
+// broad-2xx-4xx-treated-as-ok contract as `termActions.ts` — none of
 // these three routes actually redirect today, but the same tolerant
 // check costs nothing and keeps every same-origin POST in this package
 // behaving identically.

frontend/packages/agent/src/lib/modelEffort.ts

@@ -1,38 +0,0 @@
-// POST `/api/effort` — same-origin (this agent's own
-// backend), so a plain `fetch` is safe unlike pause/resume (see
-// pauseAction.ts). `redirect: 'manual'` + the broad "ok" check below is
-// ported from app.js unchanged — the endpoints don't actually redirect
-// today, but treating an opaque redirect as success costs nothing and
-// matches the existing contract exactly.
-async function post(
-  path: string,
-  field: string,
-  value: string,
-): Promise<{ ok: boolean; detail?: string }> {
-  try {
-    const resp = await fetch(path, {
-      method: "POST",
-      headers: { "Content-Type": "application/x-www-form-urlencoded" },
-      body: new URLSearchParams({ [field]: value }),
-      redirect: "manual",
-    });
-    const ok =
-      resp.ok ||
-      resp.type === "opaqueredirect" ||
-      (resp.status >= 200 && resp.status < 400);
-    if (ok) return { ok: true };
-    const detail = await resp.text().catch(() => "");
-    return {
-      ok: false,
-      detail: `http ${resp.status}${detail ? " — " + detail : ""}`,
-    };
-  } catch (err) {
-    return {
-      ok: false,
-      detail: err instanceof Error ? err.message : String(err),
-    };
-  }
-}
-
-export const postEffort = (level: string) =>
-  post("api/effort", "effort", level);

frontend/packages/agent/src/lib/pauseAction.ts

@@ -5,8 +5,7 @@
 // origin, but accessed directly they're different ports) and this way
 // hive-c0re doesn't need to grow CORS headers for it — the tradeoff is
 // an opaque, unreadable response, which is fine here since the caller
-// doesn't need to read it, only trigger a state refresh afterward (same
-// shape as `postEffort` in modelEffort.ts). `credentials:
+// doesn't need to read it, only trigger a state refresh afterward. `credentials:
 // 'include'` matches the cookie-sending behavior of the plain <form>
 // submit this replaces.
 //

frontend/packages/agent/src/lib/termActions.ts

@@ -1,6 +1,5 @@
-// Same-origin fetch POST helpers for the term-input slash commands —
-// same shape as modelEffort.ts's `post()` ({ ok, detail } rather than
-// throwing), reused by TermInput.tsx.
+// Same-origin fetch POST helpers for the term-input slash commands
+// ({ ok, detail } rather than throwing), reused by TermInput.tsx.
 async function post(
   path: string,
   body?: URLSearchParams,