@gaia-ai/ui 0.10.0 → 0.11.1

package/dist/src/ui-home.d.ts

@@ -10,15 +10,6 @@ export interface HomeConnection {
     jsonapiPrefix?: string | undefined;
     authPlugins: unknown[];
     configPath?: string | undefined;
-    /** The dropsh auth profile the cockpit READS as (`gaia_run` is session-only). */
-    authProfile?: string | undefined;
-    /**
-     * GAIA-233: the dropsh auth profile the cockpit WRITES as, named beside the
-     * read profile so both scopes are declared in one place. `session` holds no
-     * `update gaia_ticket`, and `conductor_id` is additionally field-gated on
-     * `assign gaia conductor`.
-     */
-    writeProfile?: string | undefined;
 }
 /**
  * Resolve the agent-launch command builder from the home config. Turns a TUI

package/dist/src/ui-home.js

@@ -5,6 +5,12 @@
 // holds no connection-precedence rule of its own (AC-6).
 import { dirname, resolve } from 'node:path';
 import { findProjectGaiaDir, homeGaiaDir, shellQuote, } from '@gaia-ai/core';
+// GAIA-391: the two read/write auth-profile members are gone. A connection used
+// to declare two dropsh auth profiles that differed only by OAuth scope, and the
+// cockpit had to name one for reads and one for writes; GAIA-359 moved capability
+// onto OG ranks, so both resolved to the same role. The connection now declares
+// ONE default provider and nothing has to choose. AC2's grep over
+// `gaia-cli/*/src` is the guard, so the retired names are not spelled here.
 /**
  * Resolve the agent-launch command builder from the home config. Turns a TUI
  * prompt into the shell command herdr runs. Defaults to `claude` (an empty

package/dist/src/ui.d.ts

@@ -67,7 +67,6 @@ export interface BuildWriteClientOptions {
     baseUrl: string;
     jsonapiPrefix: string;
     plugins: GaiaConnectionConfig['plugins'];
-    profile: string;
 }
 /** Test/composition seams for `gaia ui`. */
 export interface UiDeps {

package/dist/src/ui.js

@@ -8,17 +8,24 @@ import { createHttpClient, createJsonApiClient } from 'dropsh/plugin';
 import { applyOpentuiLibc, reExecUnderBun, resolveBunBinary, shouldReExecUnderBun, } from './bun-runtime.js';
 import { parseTarget, resolveHere, UI_VIEW_MODES, } from './route.js';
 import { resolveAgentCommand, resolveProjectRooting, } from './ui-home.js';
-/** The auth profile `gaia ui` writes as. Reads stay on `session`. */
-const WRITE_PROFILE = 'pm';
 /**
- * Build a second JSON:API client under a different auth profile, from the
- * plugins core already constructed. `@dropsh/plugin-oauth2@0.5.7` derives its
- * plugin id from the profile id, so `session` and `pm` are distinct plugins and
- * BOTH resolve in one process — the old profile-dedupe that collapsed them is
- * fixed (measured: `providers: … session, pm`).
+ * Build the write-side JSON:API client from the plugins core already
+ * constructed, resolving the connection's DEFAULT auth provider.
  *
- * Throws a catchable error when the connection declares no such profile; the
- * caller degrades explicitly rather than aborting the cockpit.
+ * GAIA-391: no profile is named any more. This used to resolve a second,
+ * differently-SCOPED provider (`pm`) beside the reads' `session`, because at
+ * granularity `role` the requested scope alone decided which role a token
+ * carried. GAIA-359 moved capability onto OG ranks, so both scopes resolved to
+ * the same role and the split was ceremony.
+ *
+ * It is still a second CLIENT, and that is not an oversight (spec D6): the READ
+ * client lives inside dropsh — the TUI renders within the dropsh program, which
+ * resolves auth itself — and is unreachable from here. Two client objects, ONE
+ * identity.
+ *
+ * Throws when the connection declares no usable provider — the caller catches
+ * it and runs the cockpit read-only rather than aborting, because a connection
+ * with no resolvable provider still reads.
  */
 async function buildWriteClientDefault(o) {
     const http = createHttpClient();
@@ -27,7 +34,6 @@ async function buildWriteClientDefault(o) {
         plugins: o.plugins,
         http,
         now: () => Date.now(),
-        profile: o.profile,
     });
     return createJsonApiClient({
         baseUrl: o.baseUrl,
@@ -252,8 +258,16 @@ export async function cmdUi(deps = {}) {
         });
     }
     catch (err) {
-        logger.error({}, err instanceof Error ? err.message : String(err));
-        process.exitCode = 1;
+        // `fail`, not `logger.error`: a connection config that will not resolve is
+        // the most user-facing error this command has, and the logger writes to
+        // `$HOME/log.txt` whenever stdout is not a TTY. Sent to the log sink it
+        // came out as `exit 1` and NOT ONE LINE of output — which is exactly how
+        // CI reported it, with the actual cause (a missing top-level
+        // `workspace_id`) sitting in a file nobody on that runner would think to
+        // read. The log keeps its copy; stderr gets the one a human reads.
+        const message = err instanceof Error ? err.message : String(err);
+        logger.error({}, message);
+        fail(`gaia ui: ${message}`);
         return;
     }
     const notice = deps.updateCheck
@@ -269,33 +283,37 @@ export async function cmdUi(deps = {}) {
         jsonapiPrefix: resolved.site.jsonapi_prefix,
         authPlugins: resolved.plugins,
         configPath: resolved.config_path,
-        authProfile: 'session',
-        writeProfile: WRITE_PROFILE,
     };
     // GAIA-233: the write client, built here because this package already holds
     // the constructed plugins and imports dropsh — the renderer stays
     // dropsh-decoupled and receives a finished object.
     //
-    // A connection declaring only `session` is a supported configuration, not an
-    // error: the cockpit still reads everything. So the failure is EXPLICIT
-    // rather than fatal — no write client is injected, `writeProfile` names the
-    // profile the write will really use, and the popup says so. The server's own
-    // 403 then surfaces verbatim; there is one failure path for "wrong scope" and
-    // "no scope" alike.
+    // GAIA-391 emptied this fallback of the PROFILE concept but kept the fallback
+    // itself, and the difference is the point. It used to point the write profile
+    // at the read one, because a connection declaring the reads' provider and not
+    // the writes' was an ordinary configuration; that rename is gone along with
+    // both fields, and there is no profile left to name.
+    //
+    // What remains is why it was a `catch` and not a `fail`: a connection with NO
+    // resolvable auth provider still READS. `resolveAuth` throws
+    // `Multiple auth profiles configured (); none active` for a plugins[] that
+    // yields none, and a `@gaia-ai/addon-auth-basic` connection reaches this line
+    // the same way. Aborting there would take the whole cockpit down over a write
+    // seam it may never use. So no write client is injected, the renderer falls
+    // back to the read client, and the server's own 403 is the operator's answer —
+    // Decision 1's single failure path, minus the profile it used to name.
     let writeClient;
     try {
         writeClient = await (deps.buildWriteClient ?? buildWriteClientDefault)({
             baseUrl: resolved.site.base_url,
             jsonapiPrefix: resolved.site.jsonapi_prefix ?? '/jsonapi',
             plugins: resolved.plugins,
-            profile: WRITE_PROFILE,
         });
     }
     catch (err) {
-        connection.writeProfile = connection.authProfile;
-        logger.warn({ profile: WRITE_PROFILE }, `gaia ui: no '${WRITE_PROFILE}'-scoped write client ` +
+        logger.warn({}, 'gaia ui: no write client could be built ' +
             `(${err instanceof Error ? err.message : String(err)}); ` +
-            `edits will be attempted as '${connection.authProfile}'.`);
+            'edits will be attempted through the read client.');
     }
     const rooting = resolveProjectRooting(cwd, homedir());
     const project = deps.project;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gaia-ai/ui",
-  "version": "0.10.0",
+  "version": "0.11.1",
   "description": "GAIA project-first cockpit: the `gaia ui` command plugin (renderer resolved dynamically).",
   "type": "module",
   "license": "MIT",
@@ -26,9 +26,9 @@
     "directory": "gaia-cli/ui"
   },
   "dependencies": {
-    "@gaia-ai/core": "^0.10.0",
-    "@gaia-ai/addon-herdr": "^0.10.0",
+    "@gaia-ai/core": "^0.11.1",
+    "@gaia-ai/addon-herdr": "^0.11.1",
     "commander": "^12.1.0",
-    "dropsh": "^0.5.8"
+    "dropsh": "^0.6.1"
   }
 }