@greatstore/cli 0.0.47 → 0.1.0

package/CHANGELOG.md

@@ -3,6 +3,25 @@
 All notable changes to `@greatstore/cli` are recorded here. The format
 follows [Keep a Changelog](https://keepachangelog.com/).
 
+## 0.1.0 — 2026-08-19
+
+### Changed
+- When a component's `inputSchema` declares fields the component doesn't
+  accept, validation now reports them on a single line — naming the fields
+  (capped, with a `(+N more)` count past that) — instead of one error per
+  field. A schema/component mismatch stays readable instead of burying the
+  other diagnostics.
+
+## 0.0.48 — 2026-08-19
+
+### Changed
+- Component validation now warns when a component reaches for the page-level
+  `window.GreatStore` API. Components should interact with GreatStore through
+  the lifecycle props passed into them (`onSendMessage`, `onCallTool`,
+  `onGenerateStructuredContent`, …), which are wired to the surface the
+  component is mounted in; the warning points you there. It's a nudge, not a
+  build failure.
+
 ## 0.0.47 — 2026-08-18
 
 ### Changed

package/dist/cli.js

@@ -719,7 +719,7 @@ import * as fs4 from "fs";
 import * as path4 from "path";
 
 // src/version.ts
-var CLI_VERSION = true ? "0.0.47" : "0.0.0-dev";
+var CLI_VERSION = true ? "0.1.0" : "0.0.0-dev";
 
 // src/commands/apps/init.ts
 var NAME_REGEX = /^[a-z][a-z0-9_]*$/;
@@ -926,6 +926,45 @@ function analyzeComponentProps(root, sourcePath, sourceText) {
     };
   }
 }
+function usesWindowGreatStore(root, sourcePath, sourceText) {
+  const ts = loadTypeScript(root);
+  if (!ts) return false;
+  try {
+    const sourceFile = ts.createSourceFile(
+      sourcePath,
+      sourceText,
+      ts.ScriptTarget.Latest,
+      true,
+      ts.ScriptKind.TSX
+    );
+    let found = false;
+    const visit = (node) => {
+      if (found) return;
+      if (isGreatStoreOnGlobal(ts, node)) {
+        found = true;
+        return;
+      }
+      ts.forEachChild(node, visit);
+    };
+    visit(sourceFile);
+    return found;
+  } catch {
+    return false;
+  }
+}
+function isGreatStoreOnGlobal(ts, node) {
+  if (ts.isPropertyAccessExpression(node)) {
+    return isGlobalObject(ts, node.expression) && node.name.text === "GreatStore";
+  }
+  if (ts.isElementAccessExpression(node)) {
+    const arg = node.argumentExpression;
+    return isGlobalObject(ts, node.expression) && ts.isStringLiteralLike(arg) && arg.text === "GreatStore";
+  }
+  return false;
+}
+function isGlobalObject(ts, node) {
+  return ts.isIdentifier(node) && (node.text === "window" || node.text === "globalThis");
+}
 function loadTypeScript(root) {
   const localRequire = createRequire(path5.join(root, "package.json"));
   try {
@@ -1124,8 +1163,16 @@ function buildContext(paths) {
   }
   const sourceText = readIfPresent(sourcePath);
   const props = sourceText === null ? { ok: false, reason: `couldn't check props against the manifest \u2014 ${sourceFile} not found` } : analyzeComponentProps(root, sourcePath, sourceText);
+  const usesGlobal = sourceText === null ? false : usesWindowGreatStore(root, sourcePath, sourceText);
   return {
-    ctx: { name, manifestFile, sourceFile, manifest, props },
+    ctx: {
+      name,
+      manifestFile,
+      sourceFile,
+      manifest,
+      props,
+      usesWindowGreatStore: usesGlobal
+    },
     diagnostics
   };
 }
@@ -1200,17 +1247,28 @@ function componentPropsRule(ctx) {
       message: `prop \`${prop}\` is not declared in ${ctx.manifestFile}#inputSchema.properties, so nothing will ever pass it. Declare it in the schema, or drop it from the component.`
     });
   }
-  for (const field of schemaFields) {
-    if (declared.has(field)) continue;
+  const missing = schemaFields.filter((field) => !declared.has(field));
+  if (missing.length > 0) {
     diagnostics.push({
       severity: "error",
       rule: "props/missing",
       file: ctx.sourceFile,
-      message: `${ctx.manifestFile} declares inputSchema field \`${field}\`, but the component does not accept a \`${field}\` prop. Add it to the component's props, or remove it from the schema.`
+      message: missingFieldsMessage(ctx.manifestFile, missing)
     });
   }
   return diagnostics;
 }
+var MAX_LISTED_FIELDS = 8;
+function missingFieldsMessage(manifestFile, fields) {
+  if (fields.length === 1) {
+    const [field] = fields;
+    return `${manifestFile} declares inputSchema field \`${field}\`, but the component does not accept a \`${field}\` prop. Add it to the component's props, or remove it from the schema.`;
+  }
+  const listed = fields.slice(0, MAX_LISTED_FIELDS).map((f) => `\`${f}\``).join(", ");
+  const overflow = fields.length - MAX_LISTED_FIELDS;
+  const names = overflow > 0 ? `${listed} (+${overflow} more)` : listed;
+  return `${manifestFile} declares ${fields.length} inputSchema fields the component does not accept: ${names}. Add them to the component's props, or remove them from the schema.`;
+}
 function schemaFieldNames(inputSchema) {
   if (!inputSchema || typeof inputSchema !== "object") return null;
   const properties = inputSchema["properties"];
@@ -1294,6 +1352,19 @@ function manifestNameRule(ctx) {
   ];
 }
 
+// src/validation/rules/prefer-lifecycle-props.ts
+function preferLifecyclePropsRule(ctx) {
+  if (!ctx.usesWindowGreatStore) return [];
+  return [
+    {
+      severity: "warning",
+      rule: "globals/window-greatstore",
+      file: ctx.sourceFile,
+      message: "this component reads `window.GreatStore`, the host-page embed API. Components should interact with GreatStore through their injected lifecycle props (`onSendMessage`, `onCallTool`, `onGenerateStructuredContent`, \u2026) instead \u2014 those are wired to the surface the component is mounted in."
+    }
+  ];
+}
+
 // src/validation/types.ts
 function errorsIn(diagnostics) {
   return diagnostics.filter((d) => d.severity === "error");
@@ -1309,7 +1380,8 @@ function formatDiagnostic(d) {
 var RULES = [
   manifestNameRule,
   inputSchemaComplexityRule,
-  componentPropsRule
+  componentPropsRule,
+  preferLifecyclePropsRule
 ];
 function validateComponent(paths) {
   const { ctx, diagnostics } = buildContext(paths);
@@ -2732,7 +2804,7 @@ function parseVer(v) {
 }
 
 // src/index.ts
-var CHANGELOG = true ? "# Changelog\n\nAll notable changes to `@greatstore/cli` are recorded here. The format\nfollows [Keep a Changelog](https://keepachangelog.com/).\n\n## 0.0.47 \u2014 2026-08-18\n\n### Changed\n- `onGenerateStructuredContent` now takes a required third argument,\n  `fallback` \u2014 a schema-shaped object you supply. The component preview\n  renders it (there's no live store to generate against there), so a\n  generation-driven component previews as it would live. It's validated\n  against the schema and throws if the two don't line up.\n\n## 0.0.46 \u2014 2026-08-18\n\n### Added\n- Components now receive an `onGenerateStructuredContent(schema, prompt)`\n  prop: ask the store's assistant for content matching a JSON Schema (or a\n  Zod schema) and render what it returns, personalized to the shopper. It\n  works the same in the conversation on the storefront and every embed.\n  Added to the component template, the scaffolded `AGENTS.md` reference, and\n  prop validation.\n\n## 0.0.45 \u2014 2026-08-18\n\n### Changed\n- The auto-generated `AGENTS.md` banner now records the CLI version that\n  wrote it, so you can tell at a glance when it trails your installed CLI\n  and a `gs apps init` refresh is due.\n\n## 0.0.44 \u2014 2026-08-18\n\n### Added\n- New check: a component that still declares `onError` gets a warning\n  pointing at the async-component pattern that replaced it, with the\n  throw-vs-fallback caveat (a throw asks the assistant to retry, so\n  permanent failures should render a fallback rather than throw). Earlier\n  this surfaced as the generic \"prop isn't declared in the schema\"\n  warning, whose suggested fix was wrong for a former lifecycle callback.\n\n### Changed\n- `gs apps init` now always refreshes `AGENTS.md` (the agent guidance\n  file) so it tracks the installed CLI version instead of going stale.\n  The file carries a \"do not edit \u2014 auto-generated\" banner; your own\n  project files are still left untouched.\n\n## 0.0.43 \u2014 2026-08-18\n\n### Added\n- `gs apps build` and `gs apps push` now check each component before\n  building or uploading it. Findings are reported as **errors** (a\n  blocker \u2014 the component isn't built or uploaded) or **warnings** (it\n  builds and is ready to publish, but something is worth improving),\n  and a single run reports everything it found rather than stopping at\n  the first problem.\n- New check: a component's props and its `inputSchema.properties` must\n  agree. A schema field the component doesn't accept is an error; a prop\n  the schema doesn't declare is a warning, since nothing will ever pass\n  it. The props GreatStore injects (`onSendMessage`, `onCallTool`,\n  `onUpdateModelContext`, `onShowLightbox`, `onClose`, `storeData`,\n  `Image`) are exempt.\n\n## 0.0.42 \u2014 2026-08-15\n\n### Changed\n- `gs apps list` now works outside a project. With no `.gsrc` it lists the\n  components of the store you're signed in to, instead of erroring. The\n  commands that write files or change the store \u2014 `push`, `pull`, `publish`,\n  `unpublish`, `delete` \u2014 still require a project.\n\n## 0.0.41 \u2014 2026-08-14\n\n### Changed\n- Internal authentication rework. Re-run `gs login` after updating.\n\n## 0.0.40 \u2014 2026-07-24\n\n### Removed\n- `gs configure set` no longer accepts `--salesGuide` or\n  `--salesGuideFile`, and `gs configure show` no longer lists the field.\n\n## 0.0.39 \u2014 2026-07-21\n\n### Added\n- Components now receive an `Image` prop \u2014 a drop-in for `<img>` that\n  serves images at the size they're displayed. Render `<Image src=\u2026 />`\n  instead of `<img>`; pass `Image={\"img\"}` to preview a component\n  outside a store. Scaffolded into `gs apps init` and documented in\n  `AGENTS.md`.\n\n## 0.0.38 \u2014 2026-07-13\n\n### Added\n- `gs login --store <slug>` skips the store picker and signs in\n  directly to that store \u2014 fails immediately if your account doesn't\n  have access to it, instead of falling back to the picker.\n\n## 0.0.37 \u2014 2026-07-10\n\n### Added\n- Signing in now ends by choosing which store to work on \u2014 skipped\n  automatically when your account has exactly one. Commands default to\n  that store, so `--store` is rarely needed anymore.\n- `gs switch [<slug>]` changes the working store without signing in\n  again.\n- `gs apps init` no longer requires `--store` when your sign-in already\n  selected a store.\n\n### Changed\n- A `--store` flag or project `.gsrc` that names a different store than\n  the one you signed in to is now an error, so work can't accidentally\n  target the wrong store. Run `gs switch` to change stores.\n\n## 0.0.33 \u2014 2026-07-10\n\n### Changed\n- `gs apps push` now rejects a component whose `inputSchema` is too\n  complex for the assistant to call reliably: union keywords\n  (`anyOf`/`oneOf`/`allOf`/`$ref`/`not`), more than 8 KB serialized, or\n  more than 50 declared fields. Keep schemas to a small set of flat,\n  single-type fields \u2014 one canonical name per concept \u2014 and handle\n  aliases or edge cases in component code instead.\n\n## 0.0.32 \u2014 2026-06-18\n\n### Added\n- Chat components can expand an image into a full-screen, on-brand\n  lightbox via a new `onShowLightbox({ src, originRect })` prop. Wire it\n  to an image's `onClick` \u2014 pass the image URL and, for a smooth zoom,\n  the clicked element's `getBoundingClientRect()`. Use it for product\n  photos, swatches, or size charts the shopper may want to inspect up\n  close, instead of building your own overlay.\n\n## 0.0.31 \u2014 2026-06-18\n\n### Added\n- Components can read a secondary brand font from `--font-secondary`,\n  for a second layer of typography. Falls back to the primary font.\n\n### Changed\n- The brand font variable is now `--font-primary` (was `--font-sans`).\n\n## 0.0.30 \u2014 2026-06-17\n\n### Added\n- The agent skill documents a new way to give the assistant background\n  context without sending a visible message:\n  `window.GreatStore.updateModelContext(text)` on the page, and the\n  matching `onUpdateModelContext(text)` prop inside a chat component. Use\n  it to keep the assistant aware of what the shopper is doing \u2014 the\n  product they're viewing, what's in their cart, the variant they just\n  selected \u2014 so its replies stay on point. Each call replaces the previous\n  value, and nothing renders in the chat.\n\n## 0.0.29 \u2014 2026-06-12\n\n### Fixed\n- The \"update available\" notice actually fires now. It previously raced\n  a 1-second timeout against the npm registry and usually lost, so most\n  installs never saw it. The notice is now served instantly from a local\n  cache, refreshed in the background after each day's first invocation \u2014\n  it can lag one run behind a release, but it no longer adds latency or\n  goes silent on slow networks.\n\n## 0.0.28 \u2014 2026-06-12\n\n### Added\n- `gs configure` \u2014 view and edit the store configuration from the CLI:\n  display name, assistant name, sales guide, store link, extra origins,\n  theme, CSP host lists, and icon/logo uploads. Same fields and\n  behaviour as the dashboard's Configure panel.\n- `gs connectors` \u2014 manage the store's MCP connectors: list, add (with\n  a discovery probe before saving), remove, enable/disable, toggle the\n  Maker MCP, and health-check. Same behaviour as the dashboard's\n  Connectors panel.\n- `--store <slug>` on the new admin commands, so they work outside a\n  scaffolded component project (a `.gsrc` is still used when present).\n- The agent skill gains a store-administration reference: coding agents\n  can read the store's configuration and connectors to ground their\n  work, self-serve additive changes like origin allowlists and CSP\n  hosts (read-merge-write), and are told which changes need the\n  merchant's go-ahead first.\n\n### Changed\n- Component commands now live under `gs apps` (`gs apps push`,\n  `gs apps build`, \u2026), matching the dashboard's Apps panel. The old\n  top-level forms keep working as aliases, so existing scripts and\n  scaffolded projects are unaffected.\n- The skill's structured-content guide now teaches \"point, don't\n  paste\": name the SKU/product/collection and let GreatStore research\n  the catalog itself instead of inlining fetched specs; validate with\n  `gs connectors` that a connector exists for the data a prompt or\n  schema depends on (research can't exceed the wired-up connectors);\n  and never put shopper data in prompts \u2014 GreatStore already knows the\n  shopper, and identified shoppers get per-shopper cached responses.\n\n## 0.0.27 \u2014 2026-06-11\n\n### Changed\n- Skill code samples now carry an explicit reference-only disclaimer:\n  coding agents are told to re-express the logic in the host repo's\n  framework (React, Vue, Shopify Liquid, Svelte, \u2026) instead of\n  retrofitting the framework-free samples as-is.\n\n## 0.0.26 \u2014 2026-06-11\n\n### Added\n- The agent skill gains a \"GreatStore launchers\" recipe: a horizontally\n  scrollable row of AI-generated chips, each an engaging first-person\n  question about the current page that's sent to the assistant on tap.\n\n### Changed\n- Skill recipes are now one file each under `recipes/`, indexed from\n  SKILL.md by a table with description and use-case columns.\n\n## 0.0.25 \u2014 2026-06-11\n\n### Added\n- `gs skill` installs the GreatStore agent skill \u2014 a guide AI coding\n  agents use to build with GreatStore: AI content for your own UI, chat\n  entry points, page tools, custom in-chat components, push\n  notifications, and the store's MCP endpoints. Installs into\n  `./.claude/skills/`; use `--global` for `~/.claude/skills/`, or\n  `--dir <path>` for agents that read skills from somewhere else. Run\n  it again any time to update an installed copy.\n\n## 0.0.24 \u2014 2026-06-03\n\n### Changed\n- `gs init` in an existing project now fills in any scaffold files that\n  are missing (for example, the `AGENTS.md` design guide added in\n  0.0.23) and leaves your own files alone. Pass `--force` to refresh\n  every scaffold file to the latest version. Your pinned store\n  (`.gsrc`) is never rewritten either way.\n\n## 0.0.23 \u2014 2026-06-03\n\n### Added\n- `gs init` now scaffolds an `AGENTS.md` (with `CLAUDE.md` and\n  `GEMINI.md` symlinked to it) documenting the design rules every\n  component should follow \u2014 use `em` rather than `rem` for sizing, and\n  style from the provided brand CSS variables so components match the\n  store's theme. It doubles as guidance for AI coding agents.\n\n## 0.0.22 \u2014 2026-06-02\n\n### Added\n- `gs list` now shows a link to each component's page in the dashboard,\n  so you can jump straight to a component to preview or publish it. The\n  link is also included in `gs list --json`.\n\n## 0.0.21 \u2014 2026-05-31\n\n### Changed\n- The `gs init` component scaffold now shows how to write **async**\n  components that load data before they render \u2014 including validating\n  inputs up front and signalling a failure by throwing. The scaffolded\n  component no longer includes an `onError` prop; throw from an async\n  component to report a failure instead.\n\n## 0.0.20 \u2014 2026-05-29\n\n### Added\n- `gs pull`, `gs push`, and `gs publish` now accept several component\n  names at once (e.g. `gs publish header footer cart`). Each component\n  is reported on its own line and one failure no longer stops the rest.\n\n## 0.0.19 \u2014 2026-05-28\n\n### Fixed\n- `gs login` on Windows no longer opens a sign-in URL with parameters\n  stripped, which surfaced as a \"Missing redirect_uri or state\n  parameter\" page in the browser.\n\n## 0.0.18 \u2014 2026-05-28\n\n### Changed\n- Push and publish errors now name the specific reason \u2014 including\n  every failing field in `manifest.json` \u2014 instead of the previous\n  generic message.\n\n## 0.0.17 \u2014 2026-05-28\n\n### Added\n- Each command now prints a one-line upgrade notice when a newer\n  `@greatstore/cli` is available on npm.\n\n## 0.0.16 \u2014 2026-05-28\n\n### Changed\n- Simplified error messages.\n\n## 0.0.15 \u2014 2026-05-24\n\n### Added\n- Scaffolded `component.tsx` now declares the four injected lifecycle\n  props (`onSendMessage`, `onCallTool`, `onClose`, `onError`) on\n  `Props`. Use `onError(message)` to report expected failures (failed\n  fetch, host action rejected, invalid host state) so the AI can\n  recover on its next turn. Render-time crashes are reported for you.\n\n## 0.0.14 \u2014 2026-05-24\n\n### Changed\n- `gs build` output is now whitespace-minified \u2014 typically ~50% smaller.\n\n## 0.0.13 \u2014 2026-05-24\n\n### Changed\n- `gs build` prints the next-step hint (`gs push`, then `gs publish`).\n\n## 0.0.12 \u2014 2026-05-24\n\n### Fixed\n- `gs build` failing to load Vite in some setups.\n\n## 0.0.11 \u2014 2026-05-24\n\n### Added\n- Multi-component projects. `gs init` (no args) scaffolds the project\n  root; `gs init <name>` adds a component under `components/<name>/`.\n- `gs build [<name>]` \u2014 compiles every `components/<name>/bundle.js`.\n- `gs push` (no args) uploads only the components that changed.\n- `gs pull` (no args, or `*`) downloads every component. Locally\n  edited components are skipped; pass `--force` to overwrite.\n- Public `CHANGELOG.md`; `gs --version` prints recent entries.\n\n### Changed\n- A project folder ships to exactly one store. Only `gs init` accepts\n  `--store`; every other command reads the slug from `.gsrc`. The old\n  single-component layout is rejected with a migration hint.\n- `gs init` requires `--store <slug>` for a fresh root, and rejects\n  `--store` on an existing root.\n- `gs init` no longer writes `build.mjs` \u2014 scripts call `gs build`.\n\n## 0.0.10 \u2014 2026-05-23\n\n### Changed\n- The sign-in browser tab auto-closes once `gs login` finishes.\n\n## 0.0.9 \u2014 2026-05-23\n\n### Changed\n- Scaffolded manifests include a `displayName` so the admin UI has a\n  friendlier label.\n\n## 0.0.8 \u2014 2026-05-23\n\n### Changed\n- `gs push` and `gs publish` print a link to view the component.\n\n## 0.0.6 \u2014 2026-05-23\n\n### Changed\n- `gs --version` reads from the published package version.\n\n## 0.0.4 \u2014 2026-05-23\n\n### Changed\n- Scaffolded projects produce browser-ready bundles out of the box.\n\n## 0.0.3 \u2014 2026-05-23\n\n### Changed\n- Trimmed public README to the essentials.\n\n## 0.0.2 \u2014 2026-05-23\n\n### Fixed\n- Sign-in callback parameter handling.\n" : "";
+var CHANGELOG = true ? "# Changelog\n\nAll notable changes to `@greatstore/cli` are recorded here. The format\nfollows [Keep a Changelog](https://keepachangelog.com/).\n\n## 0.1.0 \u2014 2026-08-19\n\n### Changed\n- When a component's `inputSchema` declares fields the component doesn't\n  accept, validation now reports them on a single line \u2014 naming the fields\n  (capped, with a `(+N more)` count past that) \u2014 instead of one error per\n  field. A schema/component mismatch stays readable instead of burying the\n  other diagnostics.\n\n## 0.0.48 \u2014 2026-08-19\n\n### Changed\n- Component validation now warns when a component reaches for the page-level\n  `window.GreatStore` API. Components should interact with GreatStore through\n  the lifecycle props passed into them (`onSendMessage`, `onCallTool`,\n  `onGenerateStructuredContent`, \u2026), which are wired to the surface the\n  component is mounted in; the warning points you there. It's a nudge, not a\n  build failure.\n\n## 0.0.47 \u2014 2026-08-18\n\n### Changed\n- `onGenerateStructuredContent` now takes a required third argument,\n  `fallback` \u2014 a schema-shaped object you supply. The component preview\n  renders it (there's no live store to generate against there), so a\n  generation-driven component previews as it would live. It's validated\n  against the schema and throws if the two don't line up.\n\n## 0.0.46 \u2014 2026-08-18\n\n### Added\n- Components now receive an `onGenerateStructuredContent(schema, prompt)`\n  prop: ask the store's assistant for content matching a JSON Schema (or a\n  Zod schema) and render what it returns, personalized to the shopper. It\n  works the same in the conversation on the storefront and every embed.\n  Added to the component template, the scaffolded `AGENTS.md` reference, and\n  prop validation.\n\n## 0.0.45 \u2014 2026-08-18\n\n### Changed\n- The auto-generated `AGENTS.md` banner now records the CLI version that\n  wrote it, so you can tell at a glance when it trails your installed CLI\n  and a `gs apps init` refresh is due.\n\n## 0.0.44 \u2014 2026-08-18\n\n### Added\n- New check: a component that still declares `onError` gets a warning\n  pointing at the async-component pattern that replaced it, with the\n  throw-vs-fallback caveat (a throw asks the assistant to retry, so\n  permanent failures should render a fallback rather than throw). Earlier\n  this surfaced as the generic \"prop isn't declared in the schema\"\n  warning, whose suggested fix was wrong for a former lifecycle callback.\n\n### Changed\n- `gs apps init` now always refreshes `AGENTS.md` (the agent guidance\n  file) so it tracks the installed CLI version instead of going stale.\n  The file carries a \"do not edit \u2014 auto-generated\" banner; your own\n  project files are still left untouched.\n\n## 0.0.43 \u2014 2026-08-18\n\n### Added\n- `gs apps build` and `gs apps push` now check each component before\n  building or uploading it. Findings are reported as **errors** (a\n  blocker \u2014 the component isn't built or uploaded) or **warnings** (it\n  builds and is ready to publish, but something is worth improving),\n  and a single run reports everything it found rather than stopping at\n  the first problem.\n- New check: a component's props and its `inputSchema.properties` must\n  agree. A schema field the component doesn't accept is an error; a prop\n  the schema doesn't declare is a warning, since nothing will ever pass\n  it. The props GreatStore injects (`onSendMessage`, `onCallTool`,\n  `onUpdateModelContext`, `onShowLightbox`, `onClose`, `storeData`,\n  `Image`) are exempt.\n\n## 0.0.42 \u2014 2026-08-15\n\n### Changed\n- `gs apps list` now works outside a project. With no `.gsrc` it lists the\n  components of the store you're signed in to, instead of erroring. The\n  commands that write files or change the store \u2014 `push`, `pull`, `publish`,\n  `unpublish`, `delete` \u2014 still require a project.\n\n## 0.0.41 \u2014 2026-08-14\n\n### Changed\n- Internal authentication rework. Re-run `gs login` after updating.\n\n## 0.0.40 \u2014 2026-07-24\n\n### Removed\n- `gs configure set` no longer accepts `--salesGuide` or\n  `--salesGuideFile`, and `gs configure show` no longer lists the field.\n\n## 0.0.39 \u2014 2026-07-21\n\n### Added\n- Components now receive an `Image` prop \u2014 a drop-in for `<img>` that\n  serves images at the size they're displayed. Render `<Image src=\u2026 />`\n  instead of `<img>`; pass `Image={\"img\"}` to preview a component\n  outside a store. Scaffolded into `gs apps init` and documented in\n  `AGENTS.md`.\n\n## 0.0.38 \u2014 2026-07-13\n\n### Added\n- `gs login --store <slug>` skips the store picker and signs in\n  directly to that store \u2014 fails immediately if your account doesn't\n  have access to it, instead of falling back to the picker.\n\n## 0.0.37 \u2014 2026-07-10\n\n### Added\n- Signing in now ends by choosing which store to work on \u2014 skipped\n  automatically when your account has exactly one. Commands default to\n  that store, so `--store` is rarely needed anymore.\n- `gs switch [<slug>]` changes the working store without signing in\n  again.\n- `gs apps init` no longer requires `--store` when your sign-in already\n  selected a store.\n\n### Changed\n- A `--store` flag or project `.gsrc` that names a different store than\n  the one you signed in to is now an error, so work can't accidentally\n  target the wrong store. Run `gs switch` to change stores.\n\n## 0.0.33 \u2014 2026-07-10\n\n### Changed\n- `gs apps push` now rejects a component whose `inputSchema` is too\n  complex for the assistant to call reliably: union keywords\n  (`anyOf`/`oneOf`/`allOf`/`$ref`/`not`), more than 8 KB serialized, or\n  more than 50 declared fields. Keep schemas to a small set of flat,\n  single-type fields \u2014 one canonical name per concept \u2014 and handle\n  aliases or edge cases in component code instead.\n\n## 0.0.32 \u2014 2026-06-18\n\n### Added\n- Chat components can expand an image into a full-screen, on-brand\n  lightbox via a new `onShowLightbox({ src, originRect })` prop. Wire it\n  to an image's `onClick` \u2014 pass the image URL and, for a smooth zoom,\n  the clicked element's `getBoundingClientRect()`. Use it for product\n  photos, swatches, or size charts the shopper may want to inspect up\n  close, instead of building your own overlay.\n\n## 0.0.31 \u2014 2026-06-18\n\n### Added\n- Components can read a secondary brand font from `--font-secondary`,\n  for a second layer of typography. Falls back to the primary font.\n\n### Changed\n- The brand font variable is now `--font-primary` (was `--font-sans`).\n\n## 0.0.30 \u2014 2026-06-17\n\n### Added\n- The agent skill documents a new way to give the assistant background\n  context without sending a visible message:\n  `window.GreatStore.updateModelContext(text)` on the page, and the\n  matching `onUpdateModelContext(text)` prop inside a chat component. Use\n  it to keep the assistant aware of what the shopper is doing \u2014 the\n  product they're viewing, what's in their cart, the variant they just\n  selected \u2014 so its replies stay on point. Each call replaces the previous\n  value, and nothing renders in the chat.\n\n## 0.0.29 \u2014 2026-06-12\n\n### Fixed\n- The \"update available\" notice actually fires now. It previously raced\n  a 1-second timeout against the npm registry and usually lost, so most\n  installs never saw it. The notice is now served instantly from a local\n  cache, refreshed in the background after each day's first invocation \u2014\n  it can lag one run behind a release, but it no longer adds latency or\n  goes silent on slow networks.\n\n## 0.0.28 \u2014 2026-06-12\n\n### Added\n- `gs configure` \u2014 view and edit the store configuration from the CLI:\n  display name, assistant name, sales guide, store link, extra origins,\n  theme, CSP host lists, and icon/logo uploads. Same fields and\n  behaviour as the dashboard's Configure panel.\n- `gs connectors` \u2014 manage the store's MCP connectors: list, add (with\n  a discovery probe before saving), remove, enable/disable, toggle the\n  Maker MCP, and health-check. Same behaviour as the dashboard's\n  Connectors panel.\n- `--store <slug>` on the new admin commands, so they work outside a\n  scaffolded component project (a `.gsrc` is still used when present).\n- The agent skill gains a store-administration reference: coding agents\n  can read the store's configuration and connectors to ground their\n  work, self-serve additive changes like origin allowlists and CSP\n  hosts (read-merge-write), and are told which changes need the\n  merchant's go-ahead first.\n\n### Changed\n- Component commands now live under `gs apps` (`gs apps push`,\n  `gs apps build`, \u2026), matching the dashboard's Apps panel. The old\n  top-level forms keep working as aliases, so existing scripts and\n  scaffolded projects are unaffected.\n- The skill's structured-content guide now teaches \"point, don't\n  paste\": name the SKU/product/collection and let GreatStore research\n  the catalog itself instead of inlining fetched specs; validate with\n  `gs connectors` that a connector exists for the data a prompt or\n  schema depends on (research can't exceed the wired-up connectors);\n  and never put shopper data in prompts \u2014 GreatStore already knows the\n  shopper, and identified shoppers get per-shopper cached responses.\n\n## 0.0.27 \u2014 2026-06-11\n\n### Changed\n- Skill code samples now carry an explicit reference-only disclaimer:\n  coding agents are told to re-express the logic in the host repo's\n  framework (React, Vue, Shopify Liquid, Svelte, \u2026) instead of\n  retrofitting the framework-free samples as-is.\n\n## 0.0.26 \u2014 2026-06-11\n\n### Added\n- The agent skill gains a \"GreatStore launchers\" recipe: a horizontally\n  scrollable row of AI-generated chips, each an engaging first-person\n  question about the current page that's sent to the assistant on tap.\n\n### Changed\n- Skill recipes are now one file each under `recipes/`, indexed from\n  SKILL.md by a table with description and use-case columns.\n\n## 0.0.25 \u2014 2026-06-11\n\n### Added\n- `gs skill` installs the GreatStore agent skill \u2014 a guide AI coding\n  agents use to build with GreatStore: AI content for your own UI, chat\n  entry points, page tools, custom in-chat components, push\n  notifications, and the store's MCP endpoints. Installs into\n  `./.claude/skills/`; use `--global` for `~/.claude/skills/`, or\n  `--dir <path>` for agents that read skills from somewhere else. Run\n  it again any time to update an installed copy.\n\n## 0.0.24 \u2014 2026-06-03\n\n### Changed\n- `gs init` in an existing project now fills in any scaffold files that\n  are missing (for example, the `AGENTS.md` design guide added in\n  0.0.23) and leaves your own files alone. Pass `--force` to refresh\n  every scaffold file to the latest version. Your pinned store\n  (`.gsrc`) is never rewritten either way.\n\n## 0.0.23 \u2014 2026-06-03\n\n### Added\n- `gs init` now scaffolds an `AGENTS.md` (with `CLAUDE.md` and\n  `GEMINI.md` symlinked to it) documenting the design rules every\n  component should follow \u2014 use `em` rather than `rem` for sizing, and\n  style from the provided brand CSS variables so components match the\n  store's theme. It doubles as guidance for AI coding agents.\n\n## 0.0.22 \u2014 2026-06-02\n\n### Added\n- `gs list` now shows a link to each component's page in the dashboard,\n  so you can jump straight to a component to preview or publish it. The\n  link is also included in `gs list --json`.\n\n## 0.0.21 \u2014 2026-05-31\n\n### Changed\n- The `gs init` component scaffold now shows how to write **async**\n  components that load data before they render \u2014 including validating\n  inputs up front and signalling a failure by throwing. The scaffolded\n  component no longer includes an `onError` prop; throw from an async\n  component to report a failure instead.\n\n## 0.0.20 \u2014 2026-05-29\n\n### Added\n- `gs pull`, `gs push`, and `gs publish` now accept several component\n  names at once (e.g. `gs publish header footer cart`). Each component\n  is reported on its own line and one failure no longer stops the rest.\n\n## 0.0.19 \u2014 2026-05-28\n\n### Fixed\n- `gs login` on Windows no longer opens a sign-in URL with parameters\n  stripped, which surfaced as a \"Missing redirect_uri or state\n  parameter\" page in the browser.\n\n## 0.0.18 \u2014 2026-05-28\n\n### Changed\n- Push and publish errors now name the specific reason \u2014 including\n  every failing field in `manifest.json` \u2014 instead of the previous\n  generic message.\n\n## 0.0.17 \u2014 2026-05-28\n\n### Added\n- Each command now prints a one-line upgrade notice when a newer\n  `@greatstore/cli` is available on npm.\n\n## 0.0.16 \u2014 2026-05-28\n\n### Changed\n- Simplified error messages.\n\n## 0.0.15 \u2014 2026-05-24\n\n### Added\n- Scaffolded `component.tsx` now declares the four injected lifecycle\n  props (`onSendMessage`, `onCallTool`, `onClose`, `onError`) on\n  `Props`. Use `onError(message)` to report expected failures (failed\n  fetch, host action rejected, invalid host state) so the AI can\n  recover on its next turn. Render-time crashes are reported for you.\n\n## 0.0.14 \u2014 2026-05-24\n\n### Changed\n- `gs build` output is now whitespace-minified \u2014 typically ~50% smaller.\n\n## 0.0.13 \u2014 2026-05-24\n\n### Changed\n- `gs build` prints the next-step hint (`gs push`, then `gs publish`).\n\n## 0.0.12 \u2014 2026-05-24\n\n### Fixed\n- `gs build` failing to load Vite in some setups.\n\n## 0.0.11 \u2014 2026-05-24\n\n### Added\n- Multi-component projects. `gs init` (no args) scaffolds the project\n  root; `gs init <name>` adds a component under `components/<name>/`.\n- `gs build [<name>]` \u2014 compiles every `components/<name>/bundle.js`.\n- `gs push` (no args) uploads only the components that changed.\n- `gs pull` (no args, or `*`) downloads every component. Locally\n  edited components are skipped; pass `--force` to overwrite.\n- Public `CHANGELOG.md`; `gs --version` prints recent entries.\n\n### Changed\n- A project folder ships to exactly one store. Only `gs init` accepts\n  `--store`; every other command reads the slug from `.gsrc`. The old\n  single-component layout is rejected with a migration hint.\n- `gs init` requires `--store <slug>` for a fresh root, and rejects\n  `--store` on an existing root.\n- `gs init` no longer writes `build.mjs` \u2014 scripts call `gs build`.\n\n## 0.0.10 \u2014 2026-05-23\n\n### Changed\n- The sign-in browser tab auto-closes once `gs login` finishes.\n\n## 0.0.9 \u2014 2026-05-23\n\n### Changed\n- Scaffolded manifests include a `displayName` so the admin UI has a\n  friendlier label.\n\n## 0.0.8 \u2014 2026-05-23\n\n### Changed\n- `gs push` and `gs publish` print a link to view the component.\n\n## 0.0.6 \u2014 2026-05-23\n\n### Changed\n- `gs --version` reads from the published package version.\n\n## 0.0.4 \u2014 2026-05-23\n\n### Changed\n- Scaffolded projects produce browser-ready bundles out of the box.\n\n## 0.0.3 \u2014 2026-05-23\n\n### Changed\n- Trimmed public README to the essentials.\n\n## 0.0.2 \u2014 2026-05-23\n\n### Fixed\n- Sign-in callback parameter handling.\n" : "";
 var HELP = `gs \u2014 GreatStore CLI (v${CLI_VERSION})
 
 Usage:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@greatstore/cli",
-  "version": "0.0.47",
+  "version": "0.1.0",
   "description": "CLI for administering GreatStore stores and authoring custom components.",
   "license": "UNLICENSED",
   "type": "module",