@golden-frijoles/cli 0.2.1 → 0.4.0

package/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+

package/README.md

@@ -80,6 +80,21 @@ else** — no progress lines, no warnings. A failure is a JSON document too, on
 `--help` output and these envelopes are pinned by golden-file tests. They do not change on a copy
 edit.
 
+## Sending a North Star: `gf north-star set`
+
+The `north-star` coach in the Golden Frijoles plugin leaves `Roadmap/00-strategy/north-star.md`, with the metric and
+its inputs in one ```json block under `## Sync payload`. This command sends that block to your project:
+
+```bash
+gf north-star set Roadmap/00-strategy/north-star.md          # dry run: shows what would change, sends nothing
+gf north-star set Roadmap/00-strategy/north-star.md --yes    # sends it once (project owners only)
+```
+
+A sync never replaces or deletes. A new metric key is **added** beside an existing North Star, and an input key that
+already exists **moves** to this metric. The dry run says so before anything is sent, and to revise a North Star you
+reuse its key. The server validates the block and prints its `issues` on a 400. A file that still has the template's
+`<…>` placeholders is refused before anything is sent.
+
 ## Exit codes
 
 | Code | Name | Means |

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/index.js

@@ -13,6 +13,7 @@ const flags_read_1 = require("./flags-read");
 const flags_write_1 = require("./flags-write");
 const flags_history_1 = require("./flags-history");
 const flags_sync_1 = require("./flags-sync");
+const north_star_1 = require("./north-star");
 const keys_1 = require("./keys");
 const doctor_1 = require("./doctor");
 const config_1 = require("./config");
@@ -39,6 +40,7 @@ exports.COMMANDS = [
     flags_history_1.flagsDiffCommand,
     flags_history_1.flagsHistoryCommand,
     flags_sync_1.flagsSyncCommand,
+    north_star_1.northStarSetCommand,
     keys_1.keysLsCommand,
     keys_1.keysCreateCommand,
     keys_1.keysRevokeCommand,

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

@@ -0,0 +1,46 @@
+import type { Command } from '../command';
+type SyncPayload = {
+    metric?: {
+        key?: unknown;
+        name?: unknown;
+        description?: unknown;
+    };
+    inputs?: unknown;
+};
+type CurrentInput = {
+    key: string;
+    name: string;
+    valueSource: string;
+    sourceEvent: string | null;
+};
+type CurrentMetric = {
+    key: string;
+    name: string;
+    description: string | null;
+    inputs: CurrentInput[];
+};
+/** The one ```json block under `## Sync payload`. Throws a sentence a person can act on. */
+export declare function readSyncBlock(markdown: string): unknown;
+/** Every string value still shaped like a template placeholder, as a path: `metric.key`, `inputs[1].sourceEvent`. */
+export declare function unfilledPaths(value: unknown, path?: string): string[];
+export type InputChange = {
+    key: string;
+    name: string;
+    change: string;
+};
+export type SyncPlan = {
+    metric: {
+        key: string;
+        name: string;
+        change: 'new' | 'updated' | 'unchanged';
+    };
+    otherMetrics: string[];
+    inputs: InputChange[];
+};
+/**
+ * What a sync of `proposed` would do to `current`, in the route's own terms (upsert on key, never delete).
+ * Presentation only: whether the payload is VALID is the server's question, answered on `--yes`.
+ */
+export declare function planSync(current: CurrentMetric[], proposed: SyncPayload): SyncPlan;
+export declare const northStarSetCommand: Command;
+export {};

package/dist/commands/north-star.js

@@ -0,0 +1,231 @@
+"use strict";
+// think-skills S3 (D6) — `gf north-star set <file>`: the North Star workshop's metric reaches the engine.
+//
+// ── A thin shell over one route ───────────────────────────────────────────────────────────────────────────────────
+// The `north-star` coach leaves `Roadmap/00-strategy/north-star.md`, whose `## Sync payload` section holds exactly one
+// ```json block. This command reads that block and nothing else, and sends it to `/api/v1/cli/north-star`. The SERVER
+// validates it (`northStarSyncSchema`) and its `issues` are printed verbatim on a 400, the same rule `flags-write.ts`
+// follows: one judge of what a valid North Star is, and it lives on the server.
+//
+// ── Dry run by default ────────────────────────────────────────────────────────────────────────────────────────────
+// Without `--yes` it makes ONE request, a GET of the project's current North Star, prints what a sync would do, and
+// 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.
+//
+// ── 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
+// them. A value still shaped `<…>` is a file the coach never finished, not a North Star; `--yes` refuses it with
+// nothing sent. That is a check on the TEMPLATE, not a second copy of the schema.
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.northStarSetCommand = void 0;
+exports.readSyncBlock = readSyncBlock;
+exports.unfilledPaths = unfilledPaths;
+exports.planSync = planSync;
+const node_fs_1 = require("node:fs");
+const node_path_1 = require("node:path");
+const args_1 = require("../args");
+const exit_codes_1 = require("../exit-codes");
+const output_1 = require("../output");
+const flags_read_1 = require("./flags-read");
+const SECTION = '## Sync payload';
+/** The one ```json block under `## Sync payload`. Throws a sentence a person can act on. */
+function readSyncBlock(markdown) {
+    const lines = markdown.replace(/\r\n/g, '\n').split('\n');
+    const start = lines.findIndex((line) => line.trim() === SECTION);
+    if (start === -1)
+        throw new Error(`no "${SECTION}" section — is this the file the north-star coach wrote?`);
+    const end = lines.findIndex((line, i) => i > start && line.startsWith('## '));
+    const body = lines.slice(start + 1, end === -1 ? undefined : end).join('\n');
+    const fences = [...body.matchAll(/^```json\n([\s\S]*?)\n```$/gm)];
+    if (fences.length !== 1) {
+        throw new Error(`expected exactly one \`\`\`json block under "${SECTION}", found ${fences.length}`);
+    }
+    let parsed;
+    try {
+        parsed = JSON.parse(fences[0][1]);
+    }
+    catch (err) {
+        throw new Error(`the json block does not parse: ${err instanceof Error ? err.message : String(err)}`);
+    }
+    // An object, or it is not a North Star at all: `null` or a list would otherwise reach the planner as a stack trace.
+    if (!parsed || typeof parsed !== 'object' || Array.isArray(parsed)) {
+        throw new Error('the json block must be an object with `metric` and `inputs`');
+    }
+    return parsed;
+}
+/** Every string value still shaped like a template placeholder, as a path: `metric.key`, `inputs[1].sourceEvent`. */
+function unfilledPaths(value, path = '') {
+    if (typeof value === 'string')
+        return /^<.*>$/.test(value.trim()) ? [path || '(value)'] : [];
+    if (Array.isArray(value))
+        return value.flatMap((item, i) => unfilledPaths(item, `${path}[${i}]`));
+    if (value && typeof value === 'object') {
+        return Object.entries(value).flatMap(([key, item]) => unfilledPaths(item, path ? `${path}.${key}` : key));
+    }
+    return [];
+}
+/**
+ * What a sync of `proposed` would do to `current`, in the route's own terms (upsert on key, never delete).
+ * Presentation only: whether the payload is VALID is the server's question, answered on `--yes`.
+ */
+function planSync(current, proposed) {
+    const metricKey = String(proposed.metric?.key ?? '');
+    const metricName = String(proposed.metric?.name ?? '');
+    const existing = current.find((m) => m.key === metricKey);
+    const description = proposed.metric?.description ?? null;
+    const metricChange = !existing
+        ? 'new'
+        : existing.name !== metricName || (existing.description ?? null) !== description
+            ? 'updated'
+            : 'unchanged';
+    const owner = new Map();
+    for (const metric of current)
+        for (const input of metric.inputs)
+            owner.set(input.key, { metric: metric.key, input });
+    const inputs = (Array.isArray(proposed.inputs) ? proposed.inputs : []).map((input) => {
+        const key = String(input?.key ?? '');
+        const name = String(input?.name ?? '');
+        const found = owner.get(key);
+        let change;
+        if (!found)
+            change = 'new';
+        else if (found.input.valueSource !== input?.valueSource) {
+            // The route refuses this (an existing input's value source never changes), so say so before sending.
+            change = `refused: value source is ${found.input.valueSource}`;
+        }
+        else if (found.metric !== metricKey)
+            change = `moved from ${found.metric}`;
+        else if (found.input.name !== name ||
+            (found.input.sourceEvent ?? undefined) !== (input?.sourceEvent ?? undefined))
+            change = 'updated';
+        else
+            change = 'unchanged';
+        return { key, name, change };
+    });
+    return {
+        metric: { key: metricKey, name: metricName, change: metricChange },
+        otherMetrics: current.filter((m) => m.key !== metricKey).map((m) => m.key),
+        inputs,
+    };
+}
+function describePlan(project, plan, unfilled) {
+    const lines = [
+        `North Star for ${project}:`,
+        '',
+        `  metric  ${plan.metric.key}  "${plan.metric.name}"  ${plan.metric.change}`,
+    ];
+    if (plan.otherMetrics.length > 0) {
+        lines.push(`  This project already has ${plan.otherMetrics.length === 1 ? 'another North Star' : `${plan.otherMetrics.length} other North Stars`}: ${plan.otherMetrics.join(', ')}.`, '  A sync ADDS this one beside it. It never replaces or deletes. To revise one, reuse its key.');
+    }
+    lines.push('', (0, output_1.table)(['INPUT', 'NAME', 'CHANGE'], plan.inputs.map((input) => [input.key, input.name, input.change])));
+    if (unfilled.length > 0) {
+        lines.push('', `Not filled in yet (still a template placeholder): ${unfilled.join(', ')}.`);
+    }
+    return lines.join('\n');
+}
+/** Zod's flattened `issues`, as lines. Anything else is shown as JSON rather than guessed at. */
+function issueLines(issues) {
+    if (!issues || typeof issues !== 'object')
+        return [];
+    const { formErrors, fieldErrors } = issues;
+    if (!Array.isArray(formErrors) && (!fieldErrors || typeof fieldErrors !== 'object')) {
+        return [`  ${JSON.stringify(issues)}`];
+    }
+    const out = (Array.isArray(formErrors) ? formErrors : []).map((message) => `  - ${String(message)}`);
+    for (const [field, messages] of Object.entries((fieldErrors ?? {}))) {
+        for (const message of Array.isArray(messages) ? messages : [messages])
+            out.push(`  - ${field}: ${String(message)}`);
+    }
+    return out;
+}
+/** The dry run's last sentence. It never invites a `--yes` that is certain to be refused. */
+function nextStep(plan, unfilled) {
+    if (unfilled.length > 0)
+        return 'Fill in the placeholders first: --yes refuses a file that still has them.';
+    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.';
+}
+async function readCurrent(context, project) {
+    const response = await context.api.get('/api/v1/cli/north-star', { project });
+    if (response.kind === 'network') {
+        context.emit.fail('network', response.message);
+        return exit_codes_1.EXIT.SERVER;
+    }
+    if (response.kind === 'error') {
+        context.emit.fail(response.code, response.message);
+        return (0, exit_codes_1.exitForServerCode)(response.code);
+    }
+    return Array.isArray(response.body.metrics) ? response.body.metrics : [];
+}
+exports.northStarSetCommand = {
+    path: ['north-star', 'set'],
+    summary: "send a North Star workshop's metric and inputs to the project",
+    usage: 'gf north-star set <file> [--yes] [--project <slug>]',
+    needsAuth: true,
+    detail: `Reads the one \`\`\`json block under "## Sync payload" in <file> — the
+  Roadmap/00-strategy/north-star.md the north-star coach writes.
+
+  Without --yes it is a DRY RUN: it reads the project's current North Star, prints what a sync
+  would do, and sends nothing. With --yes it sends the block once and prints the result.
+
+  ⚠️ A sync never replaces or deletes. A new metric key is ADDED beside an existing North Star,
+  and an input key that already exists MOVES to this metric. To revise a North Star, reuse its key.
+  Owner-only to send; any member can dry-run.`,
+    flags: [
+        { name: 'yes', describe: 'send it (without this, nothing is sent)' },
+        { name: 'project', value: '<slug>', describe: 'the project (default: the remembered one)' },
+    ],
+    async run(context) {
+        const file = context.args.positionals[0];
+        if (!file) {
+            context.emit.fail('invalid', 'Usage: `gf north-star set <file>` — e.g. Roadmap/00-strategy/north-star.md.');
+            return exit_codes_1.EXIT.USAGE;
+        }
+        const project = (0, flags_read_1.resolveProject)(context);
+        if (!project)
+            return (0, flags_read_1.missingProject)(context);
+        let payload;
+        try {
+            payload = readSyncBlock((0, node_fs_1.readFileSync)((0, node_path_1.resolve)(context.cwd, file), 'utf8'));
+        }
+        catch (err) {
+            context.emit.fail('invalid', `${file}: ${err instanceof Error ? err.message : String(err)}. Nothing was sent.`);
+            return exit_codes_1.EXIT.USAGE;
+        }
+        const unfilled = unfilledPaths(payload);
+        const send = (0, args_1.boolFlag)(context.args, 'yes');
+        // Refused BEFORE any request: a template the coach never finished is not something to read the project for, let
+        // alone write.
+        if (send && unfilled.length > 0) {
+            context.emit.fail('invalid', `${file} still has template placeholders (${unfilled.join(', ')}). Fill them in, then run this again. Nothing was sent.`, { unfilled });
+            return exit_codes_1.EXIT.USAGE;
+        }
+        const current = await readCurrent(context, project);
+        if (typeof current === 'number')
+            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)}`);
+            return exit_codes_1.EXIT.OK;
+        }
+        const response = await context.api.post('/api/v1/cli/north-star', { project, sync: payload });
+        if (response.kind === 'network') {
+            context.emit.fail('network', `${response.message} It may or may not have been applied — run the dry run to see.`);
+            return exit_codes_1.EXIT.SERVER;
+        }
+        if (response.kind === 'error') {
+            const issues = response.body.issues;
+            if (context.emit.json)
+                context.emit.fail(response.code, response.message, issues ? { issues } : undefined);
+            else
+                context.emit.fail(response.code, [response.message, ...issueLines(issues)].join('\n'));
+            return (0, exit_codes_1.exitForServerCode)(response.code);
+        }
+        context.emit.ok({ project, metric: response.body.metric, inputsSynced: response.body.inputsSynced, plan }, `${describePlan(project, plan, [])}\n\nok · North Star ${response.body.metric} synced to ${project} · ${response.body.inputsSynced} input${response.body.inputsSynced === 1 ? '' : 's'}.`);
+        return exit_codes_1.EXIT.OK;
+    },
+};

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const VERSION = "0.2.1";
+export declare const VERSION = "0.4.0";

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.2.1';
+exports.VERSION = '0.4.0';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@golden-frijoles/cli",
   "private": false,
-  "version": "0.2.1",
+  "version": "0.4.0",
   "description": "The Golden Frijoles CLI — create, roll out and kill feature flags from a terminal, or from an agent.",
   "bin": {
     "gf": "./dist/bin.js"
@@ -21,7 +21,7 @@
     "golden-frijoles",
     "agent"
   ],
-  "license": "UNLICENSED",
+  "license": "Apache-2.0",
   "sideEffects": false,
   "publishConfig": {
     "access": "public"
@@ -33,7 +33,7 @@
   },
   "dependencies": {
     "@golden-frijoles/kit": "0.5.2",
-    "@golden-frijoles/sdk": "^0.5.0"
+    "@golden-frijoles/sdk": ">=0.5.0 <0.7.0"
   },
   "devDependencies": {
     "typescript": "^5.5.4"