gigabuddy 0.4.0 → 0.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gigabuddy",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Command-line sign-in for Gigabuddy. Authenticates your machine and configures npm for @gigabuddy packages.",
   "type": "module",
   "license": "MIT",

package/src/lib/commands.d.ts

@@ -20,21 +20,16 @@ export declare function resolveEnv(options: {
 export declare function activeAccount(explicit?: string): ResolvedAccount;
 export declare function signIn(env: Env, account?: string): Promise<UserCredentials>;
 /**
- * `gigabuddy login` — sign in AND set npm up, because for this client they are
- * one act. Installing `@gigabuddy` packages is what the CLI is for: nothing
- * else on the machine reads the credential this writes (the agent client
- * custodies its own), so a sign-in that stops short of npm has left the user
- * with a file and no capability.
- *
- * There is no prompt, and deliberately so. The device flow cannot complete
- * without a human approving a code in a browser, so "is anyone there?" is
- * already answered yes by the time we get here — and TTY detection would get
- * it wrong anyway for the SSH and devcontainer cases, silently skipping setup
- * for someone who just approved. We tell them exactly what was written
- * instead; `--no-npm` is there for the rare credential-file-only case.
+ * `gigabuddy login` — sign in. npm registry setup is OPT-IN (`--npm`), not
+ * part of a plain login: the registry is a pre-release surface we run
+ * internally, and this client's day job is now the account/agent gate — a
+ * sign-in no longer implies "I'm here to npm-install". (The original
+ * everything-in-one-act default dates from when installing `@gigabuddy`
+ * packages was the CLI's sole purpose; that stopped being true.) A plain
+ * login prints the one-liner for getting npm access, and `login --npm`
+ * remains the whole npm ceremony — sign in first if needed, then mint.
  */
 export declare function loginCommand(env: Env, options?: {
-    npm?: boolean;
     account?: string;
 }): Promise<void>;
 /**
@@ -71,6 +66,22 @@ export interface SetupRunner {
  * custodies its own credential; our sign-in is neither needed nor offered here.
  */
 export declare function setupCommand(runner?: SetupRunner): void;
+export interface UpdateRunner {
+    /** The latest published version on npm, or null when it can't be read. */
+    latestVersion(): string | null;
+    /** Run `npm i -g gigabuddy@latest` with output flowing to the user. Returns exit code. */
+    installLatest(): number;
+    /** Re-run the idempotent plugin refresh. Returns exit code, or 'missing' with no claude binary. */
+    refreshPlugin(): number | 'missing';
+}
+/**
+ * `gigabuddy update` — bring everything gigabuddy on this machine current.
+ * Doctor DIAGNOSES and never mutates; this is the verb that acts. There are
+ * only two things to act on: this CLI (npm global) and the Claude Code plugin
+ * shell (idempotent marketplace refresh). The agent server needs nothing —
+ * the plugin launches `@gigabuddy/agent@latest` via npx, so it updates itself.
+ */
+export declare function updateCommand(current: string, runner?: UpdateRunner): Promise<void>;
 export declare function statusCommand(account?: string): Promise<void>;
 /**
  * `gigabuddy accounts` — every account on this machine, who each is signed in