@golden-frijoles/cli 0.3.0 → 0.4.1

package/dist/commands/auth.js

@@ -181,6 +181,7 @@ exports.whoamiCommand = {
             return (0, exit_codes_1.exitForServerCode)(result.code);
         }
         const { account, credential, projects } = result.body;
+        const workspaces = result.body.workspaces ?? [];
         context.emit.ok({
             account,
             // The credential's id and LABEL. Never the token — `gf doctor`'s rule applies here too, and
@@ -190,9 +191,12 @@ exports.whoamiCommand = {
             tokenSource: context.auth.source,
             activeProject: context.auth.activeProject,
             projects,
+            workspaces,
         }, [
             `${account.email ?? account.userId}  on ${context.api.baseUrl}`,
             `credential: ${credential.label} (from ${describeSource(context.auth.source)})`,
+            // The tenant (workspaces S2.3): one line per workspace, so a person in two sees both.
+            ...workspaces.map((workspace) => `workspace: ${workspace.name}`),
             `active project: ${context.auth.activeProject ?? 'none — run `gf projects use <slug>`'}`,
             '',
             (0, output_1.table)(['PROJECT', 'ROLE'], projects.map((project) => [

package/dist/commands/north-star.d.ts

@@ -42,5 +42,22 @@ export type SyncPlan = {
  * Presentation only: whether the payload is VALID is the server's question, answered on `--yes`.
  */
 export declare function planSync(current: CurrentMetric[], proposed: SyncPayload): SyncPlan;
+/** One reason `--yes` would be refused, as data an agent can branch on instead of parsing the sentence below. */
+export type Blocker = {
+    kind: 'placeholders';
+    paths: string[];
+} | {
+    kind: 'value-source';
+    keys: string[];
+};
+export type DryRunVerdict = {
+    sendable: boolean;
+    blockers: Blocker[];
+};
+/**
+ * Would `--yes` be accepted? Every blocker the CLI knows of, in the order the dry run's sentence checks them.
+ * `sendable: true` means nothing HERE refuses it; whether the payload is valid is still the server's question.
+ */
+export declare function dryRunVerdict(plan: SyncPlan, unfilled: string[]): DryRunVerdict;
 export declare const northStarSetCommand: Command;
 export {};

package/dist/commands/north-star.js

@@ -12,6 +12,8 @@
 // sends nothing. A sync never replaces or deletes (think-skills C2): a new metric key is ADDED beside any existing
 // metric, and an input key that already exists MOVES to this metric. Both effects are named before anything is sent,
 // because neither can be undone by syncing again.
+// Under `--json` it also says, as data, whether `--yes` would be accepted: `sendable`, and `blockers` saying why not
+// (`dryRunVerdict`). The human sentence is rendered from that same verdict, so the two can't disagree.
 //
 // ── An unfilled template is refused here ──────────────────────────────────────────────────────────────────────────
 // The template's `<metric_key>` placeholders satisfy the schema (any non-empty string does), so the server would store
@@ -22,6 +24,7 @@ exports.northStarSetCommand = void 0;
 exports.readSyncBlock = readSyncBlock;
 exports.unfilledPaths = unfilledPaths;
 exports.planSync = planSync;
+exports.dryRunVerdict = dryRunVerdict;
 const node_fs_1 = require("node:fs");
 const node_path_1 = require("node:path");
 const args_1 = require("../args");
@@ -139,15 +142,27 @@ function issueLines(issues) {
     }
     return out;
 }
-/** The dry run's last sentence. It never invites a `--yes` that is certain to be refused. */
-function nextStep(plan, unfilled) {
+/**
+ * Would `--yes` be accepted? Every blocker the CLI knows of, in the order the dry run's sentence checks them.
+ * `sendable: true` means nothing HERE refuses it; whether the payload is valid is still the server's question.
+ */
+function dryRunVerdict(plan, unfilled) {
+    const blockers = [];
     if (unfilled.length > 0)
-        return 'Fill in the placeholders first: --yes refuses a file that still has them.';
+        blockers.push({ kind: 'placeholders', paths: unfilled });
     const refused = plan.inputs.filter((input) => input.change.startsWith('refused'));
-    if (refused.length > 0) {
-        return `--yes would be refused: an existing input's value source never changes (${refused.map((i) => i.key).join(', ')}). Use a new key, or keep its value source.`;
-    }
-    return 'Run again with --yes to send it.';
+    if (refused.length > 0)
+        blockers.push({ kind: 'value-source', keys: refused.map((input) => input.key) });
+    return { sendable: blockers.length === 0, blockers };
+}
+/** The dry run's last sentence, rendered from the verdict's first blocker. It never invites a refused `--yes`. */
+function nextStep(verdict) {
+    const [first] = verdict.blockers;
+    if (!first)
+        return 'Run again with --yes to send it.';
+    if (first.kind === 'placeholders')
+        return 'Fill in the placeholders first: --yes refuses a file that still has them.';
+    return `--yes would be refused: an existing input's value source never changes (${first.keys.join(', ')}). Use a new key, or keep its value source.`;
 }
 async function readCurrent(context, project) {
     const response = await context.api.get('/api/v1/cli/north-star', { project });
@@ -209,7 +224,8 @@ exports.northStarSetCommand = {
             return current;
         const plan = planSync(current, payload);
         if (!send) {
-            context.emit.ok({ dryRun: true, project, ...plan, unfilled }, `${describePlan(project, plan, unfilled)}\n\nDry run: nothing was sent. ${nextStep(plan, unfilled)}`);
+            const verdict = dryRunVerdict(plan, unfilled);
+            context.emit.ok({ dryRun: true, project, ...plan, unfilled, ...verdict }, `${describePlan(project, plan, unfilled)}\n\nDry run: nothing was sent. ${nextStep(verdict)}`);
             return exit_codes_1.EXIT.OK;
         }
         const response = await context.api.post('/api/v1/cli/north-star', { project, sync: payload });

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const VERSION = "0.3.0";
+export declare const VERSION = "0.4.1";

package/dist/version.js

@@ -10,4 +10,4 @@ exports.VERSION = void 0;
 //
 // It is a literal, and `version.test.ts` asserts it equals `package.json`'s — so the two cannot
 // drift, and the drift is caught by the unit gate rather than by someone reading `gf --version`.
-exports.VERSION = '0.3.0';
+exports.VERSION = '0.4.1';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@golden-frijoles/cli",
   "private": false,
-  "version": "0.3.0",
+  "version": "0.4.1",
   "description": "The Golden Frijoles CLI — create, roll out and kill feature flags from a terminal, or from an agent.",
   "bin": {
     "gf": "./dist/bin.js"