@agent-team-foundation/first-tree-hub 0.12.10 → 0.14.0

package/dist/{bootstrap-CW73oEYn.mjs → bootstrap-C15ZBOCC.mjs}

@@ -552,6 +552,7 @@ const serverConfigSchema = defineConfig({
 		host: field(z.string().default("127.0.0.1"), { env: "FIRST_TREE_HUB_HOST" }),
 		publicUrl: field(z.string().optional(), { env: "FIRST_TREE_HUB_PUBLIC_URL" })
 	},
+	workspace: { root: field(z.string().default(join(DEFAULT_DATA_DIR, "workspaces")), { env: "FIRST_TREE_HUB_WORKSPACES_ROOT" }) },
 	secrets: {
 		jwtSecret: field(z.string(), {
 			env: "FIRST_TREE_HUB_JWT_SECRET",
@@ -690,19 +691,19 @@ function resolveServerUrl(flagValue) {
 		const url = Reflect.get(server, "url");
 		if (typeof url === "string" && url.length > 0) return url;
 	}
-	throw new Error("Server URL not configured.\n  Provide via: --server <url>, FIRST_TREE_HUB_SERVER_URL env var, or\n  first-tree-hub config set -c server.url <url>");
+	throw new Error("Server URL not configured.\n  Provide via: --server <url>, FIRST_TREE_HUB_SERVER_URL env var, or\n  first-tree-hub client config set server.url <url>");
 }
 /**
 * Resolve the current member access JWT from persisted credentials.
 *
 * Unified-user-token milestone: the CLI has a single credential store and a
-* single onboarding path (`first-tree-hub client connect`). The legacy
+* single onboarding path (`first-tree-hub connect <token>`). The legacy
 * `FIRST_TREE_HUB_TOKEN` env var is no longer read — callers get a clear
-* error pointing at `client connect` instead.
+* error pointing at `connect <token>` instead.
 */
 function resolveAccessToken() {
 	const creds = loadCredentials();
-	if (!creds) throw new Error("No credentials found. Run `first-tree-hub client connect <server-url>` to sign in.");
+	if (!creds) throw new Error("No credentials found. Run `first-tree-hub connect <token>` to sign in.");
 	return creds.accessToken;
 }
 /**
@@ -783,7 +784,7 @@ const DEFAULT_MIN_VALIDITY_MS = 3e4;
 async function ensureFreshAccessToken(opts) {
 	const minValidityMs = opts?.minValidityMs ?? DEFAULT_MIN_VALIDITY_MS;
 	const creds = loadCredentials();
-	if (!creds) throw new Error("No credentials found. Run `first-tree-hub client connect <server-url>` to sign in.");
+	if (!creds) throw new Error("No credentials found. Run `first-tree-hub connect <token>` to sign in.");
 	if (!isTokenStale(creds.accessToken, minValidityMs)) return creds.accessToken;
 	if (inflightRefresh) return inflightRefresh;
 	inflightRefresh = (async () => {
@@ -830,7 +831,7 @@ function isTokenStale(token, minValidityMs) {
 * calls the file is empty, and a concurrent `loadCredentials()` (e.g. a
 * background daemon refreshing while the user runs a foreground CLI command)
 * reads "" → `JSON.parse` throws → we fall back to "no credentials" and
-* surface a misleading "run `client connect` again" error. write-to-temp +
+* surface a misleading "run `connect <token>` again" error. write-to-temp +
 * rename gives readers an all-or-nothing view: they see the old file or the
 * new file, never a half-written one. Server-side the sliding-window design
 * already accepts last-writer-wins semantics for the refresh token itself