datagrok-tools 6.7.6 → 6.7.8

package/.devcontainer/PACKAGES_DEV.md

@@ -66,7 +66,7 @@ Host machine
 │  │    │       └── <folder>/     ← bind mount of user's repo   │  │
 │  │    ├── /var/run/docker.sock  ← host Docker for stand mgmt  │  │
 │  │    ├── entrypoint.sh         ← bind-mounted from tools/    │  │
-│  │    ├── Claude Code + MCP plugins (Jira, GitHub)            │  │
+│  │    ├── Claude Code + MCP plugins (GitHub, Jira)            │  │
 │  │    ├── Playwright + Chrome for testing                     │  │
 │  │    └── grok CLI for build/publish/test                     │  │
 │  └────────────────────────────────────────────────────────────┘  │
@@ -197,15 +197,25 @@ Based on `node:22-bookworm-slim`. Pre-installed:
 
 Runs as **root** in compose (entrypoint drops to `node` user for the main process).
 
-## MCP plugins: Jira and GitHub
+## MCP plugins: GitHub and Jira
 
 The agent uses MCP plugins to search for similar issues, read context, and update
-status. Set tokens in `.env` or the agent will ask interactively on first use.
+status. Tickets are GitHub issues (`datagrok-ai/public`); Jira holds only read-only
+`GROK-NNNNN` history. Set tokens in `.env` or the agent will ask interactively on first use.
 
-### Jira (Atlassian)
+### GitHub
 
 ```bash
 # Inside tools-dev, register the MCP server:
+claude mcp add github -s user -- \
+  npx -y @modelcontextprotocol/server-github
+```
+
+Requires `GITHUB_TOKEN` in the environment (already passed from `.env`).
+
+### Jira (optional, read-only history)
+
+```bash
 claude mcp add mcp-atlassian -s user -- \
   npx -y mcp-atlassian \
   --jira-url "$JIRA_URL" \
@@ -213,15 +223,6 @@ claude mcp add mcp-atlassian -s user -- \
   --jira-token "$JIRA_TOKEN"
 ```
 
-### GitHub
-
-```bash
-claude mcp add github -s user -- \
-  npx -y @modelcontextprotocol/server-github
-```
-
-Requires `GITHUB_TOKEN` in the environment (already passed from `.env`).
-
 ## Testing
 
 ### grok test (Puppeteer-based)

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> datagrok-tools@6.7.6 build /home/runner/work/public/public/tools
+> datagrok-tools@6.7.8 build /home/runner/work/public/public/tools
 > node build.js
 
 Successfully compiled 51 files with Babel.

package/CHANGELOG.md

@@ -1,7 +1,12 @@
 # Datagrok-tools changelog
 
-## v.next
+## 6.7.8 (2026-10-13)
 
+* Fixed `grok api` (and every command other than `grok s`) exiting with code 1 and its usage text in 6.7.7: the new `--send-email` flag reached every command as `send-email: false`, which `grok api` rejected as an unknown option
+
+## 6.7.7 (2026-10-09)
+
+* GROK-21156: `grok s users invite [<email>] [--prefix <P>] [--send-email]`: invites a user and prints a link that logs them in (no email sent; the email may be omitted); `--prefix` starts the code with `<P>`; `--send-email` mails the invitation instead
 * `grok test --skip-gc` launches the browser without `--expose-gc`, so the test runner skips its garbage collection after every test; a suite of small unit tests runs several times faster (ComputeUtils driver tests: 92 s to 19 s)
 * `grok setup` installs corepack when it is missing instead of asking for it by hand: Node 25 no longer bundles corepack, so every fresh checkout on current Node stopped at that step
 * `grok setup` also removes the `.js`/`.d.ts` files the npm-era tsc emitted beside js-api and library sources: the workspace emits into `dist/`, and a leftover `js-api/grok.js` shadowed the `grok` command in cmd.exe

package/CLAUDE.md

@@ -220,7 +220,7 @@ Based on `node:22-bookworm-slim`. Pre-installed:
 | `demo` | + world, test_db, northwind |
 | `full` | + grok_spawner, JKG, demo DBs |
 
-See `.devcontainer/PACKAGES_DEV.md` for detailed usage docs, architecture diagram, MCP plugin setup (Jira/GitHub), and troubleshooting.
+See `.devcontainer/PACKAGES_DEV.md` for detailed usage docs, architecture diagram, MCP plugin setup (GitHub/Jira), and troubleshooting.
 
 ### `grok server` / `grok s` Command
 

package/GROK_S.md

@@ -16,6 +16,7 @@ browser or a logged-in session.
 |-------------------------------------------------------------|--------------------------------------------------------|
 | Create / update a user                                      | `grok s users save --json user.json`                   |
 | Block / unblock a user                                      | `grok s users block <login>` / `users unblock <login>` |
+| Invite a user, get a login link                             | `grok s users invite [<email>] [--prefix <P>]`         |
 | Create / update a group                                     | `grok s groups save --json group.json`                 |
 | Add or remove users in a group                              | `grok s groups add-members <group> <user>...`          |
 | List members of a group                                     | `grok s groups list-members <group>`                   |
@@ -165,8 +166,17 @@ personal groups.
 ```bash
 grok s users block   alice.mendel        # accept login, UUID, or namespace:name
 grok s users unblock alice.mendel
+grok s users invite  alice@corp.com      # prints a login link; no email is sent
+grok s users invite                      # same, for an account with no email
+grok s users invite  --prefix ALEX-      # code starts with ALEX- (letters, digits, - and _, up to 32)
+grok s users invite  alice@corp.com --send-email   # mail the invitation instead
 ```
 
+`users invite` creates the user in state `new` and prints `<server>?inviteCode=<code>`. The
+link logs straight in as that user, every time, for a year. Inviting the same email again
+prints a new link, and the earlier ones keep working. An account that has already been used
+cannot be sent a link.
+
 Both commands resolve the argument to a full user record first, so the server receives
 the entire object (matching the Python client's `grok.users.block(user)`). Blocking
 flips `status` to `Blocked` and terminates active sessions; unblocking restores `Active`.
@@ -616,9 +626,12 @@ entities shared with that account, and the target's own users never get their co
 
 ```bash
 grok s pull --since 10y --type project,connection,query,script,group,layout   --out ./bundle --host dev --admin
-grok s push ./bundle --host prod --admin --on-conflict skip
+grok s push ./bundle --host prod --admin --on-conflict adopt
 ```
 
+`adopt` keeps one copy of what both instances already have, such as shared groups and spaces;
+`skip` would leave them alone and fail everything in the bundle that points at them.
+
 **Move a whole instance one space at a time.** Placement is exclusive on the server — one project
 holding an entity takes it from every other — so a single bundle carrying every space has its
 projects competing, and a stand-sized push spends its time taking rows back off each other. Scoped

package/README.md

@@ -106,7 +106,8 @@ For more information on configuring connections, refer to the [Connections](http
   `config.yaml`): `grok report fetch <instance> <number>` downloads the report zip, `grok report read
   <zip|json|instance number>` prints one normalized JSON object (flags `--extract-screenshot`,
   `--extract-d42`, `--extract-client-log`), `grok report resolve <instance> <number>` marks it resolved.
-  `ticket`, `comment`, `label`, `attach` talk to JIRA with `JIRA_TOKEN`. See `grok report --help`.
+  `ticket`, `comment`, `label`, `attach` talk to JIRA with `JIRA_TOKEN`; porting them to GitHub Issues
+  is pending. See `grok report --help`.
 - `check` checks package content (function signatures, import statements of external modules,
   etc.). The check is also run during package publication.
 - `init` modifies a package template by adding config files for linters, IDE, and so on

package/bin/commands/server.js

@@ -111,6 +111,7 @@ async function server(argv) {
     if (entity === 'groups' && (verb === 'list-members' || verb === 'list-memberships')) return await handleGroupListMembers(dapi, verb, rest, argv, output);
     if (entity === 'users' && verb === 'block') return await handleUserBlock(dapi, rest, output);
     if (entity === 'users' && verb === 'unblock') return await handleUserUnblock(dapi, rest, output);
+    if (entity === 'users' && verb === 'invite') return await handleUserInvite(dapi, rest, argv, output);
     if (entity === 'tables' && verb === 'download') return await handleTablesDownload(dapi, rest, argv, output);
     if (entity === 'tables' && verb === 'upload') return await handleTablesUpload(dapi, rest, output);
     if (entity === 'packages' && verb === 'install') return await handlePackagesInstall(dapi, rest, argv, output);
@@ -214,6 +215,20 @@ async function handleUserUnblock(dapi, rest, output) {
   if (output !== 'quiet') console.log(`Unblocked ${user?.login ?? rest[0]}`);
   return true;
 }
+async function handleUserInvite(dapi, rest, argv, output) {
+  const email = rest[0] !== undefined ? String(rest[0]) : undefined;
+  const prefix = argv.prefix !== undefined ? String(argv.prefix) : undefined;
+  if (argv['send-email'] && (!email || prefix !== undefined)) {
+    (0, _serverOutput.printError)(new Error('Usage: grok s users invite <email> --send-email (no --prefix: only a link has a code)'));
+    return false;
+  }
+  const link = await dapi.users.invite(email, !!argv['send-email'], prefix);
+  if (output === 'json') (0, _serverOutput.printOutput)({
+    email: email ?? null,
+    link: link || null
+  }, output);else if (link) console.log(link);else if (output !== 'quiet') console.log(`Invitation sent to ${email}`);
+  return true;
+}
 async function handleTablesDownload(dapi, rest, argv, output) {
   const name = rest[0];
   if (!name) {
@@ -949,6 +964,10 @@ Special commands:
                                                       List parent groups
   grok s users block <id-or-login>                    Block a user from the platform
   grok s users unblock <id-or-login>                  Unblock a previously blocked user
+  grok s users invite [<email>] [--prefix <P>] [--send-email]
+                                                      Invite a user; prints a login link (no email sent).
+                                                      --prefix starts the code with <P> (e.g. ALEX-);
+                                                      --send-email mails the invitation instead
   grok s tables upload <name> <file.csv|file.d42>     Upload a CSV or d42 binary as a Datagrok table
   grok s tables download <name|Project:Table|id> [-O <file>]
                                                       Download a table as CSV (stdout by default)

package/bin/grok.js

@@ -1,9 +1,12 @@
 #!/usr/bin/env node
+// minimist sets every boolean option to false when it is absent, and commands such as `grok api`
+// reject any key they do not expect — so each boolean reaches only the commands that read it.
+const commandBooleans = {dartium: ['test', 'stresstest'], 'send-email': ['server', 's']};
 const argv = require('minimist')(process.argv.slice(2), {
   alias: {k: 'key', h: 'help', r: 'recursive'},
-  boolean: ['dartium'],
+  boolean: Object.keys(commandBooleans),
   // keep versions verbatim — minimist would coerce '1.10' to the number 1.1
-  string: ['version'],
+  string: ['version', 'prefix'],
 });
 // minimist maps `--no-retry` to `{retry: false}`, so the `args['no-retry']` checks in
 // test.ts / playwright-runner.ts never fired and `--no-retry` was silently ignored
@@ -59,8 +62,9 @@ function printUsage(command) {
 }
 
 const command = argv['_'][0];
-if (command !== 'test' && command !== 'stresstest')
-  delete argv.dartium;
+for (const [flag, owners] of Object.entries(commandBooleans))
+  if (!owners.includes(command))
+    delete argv[flag];
 if (command in commands) {
   try {
     if (argv['help']) {

package/bin/utils/node-dapi.js

@@ -595,6 +595,20 @@ class NodeUsersDataSource extends NodeHttpDataSource {
   async unblock(user) {
     await this.client.post('/public/v1/users/unblock', user);
   }
+
+  /**
+   * Creates the invitee (status `new`) and returns a link that logs them in, sending no email; the
+   * email may be omitted, and [prefix] goes in front of the link's code. With [sendEmail] the
+   * server mails the invitation and returns '' instead.
+   */
+  async invite(email, sendEmail = false, prefix) {
+    return this.client.post(`/users/invite${buildQuery({
+      email: email ?? '',
+      target: 'Datagrok',
+      link: sendEmail ? undefined : true,
+      prefix
+    })}`);
+  }
 }
 exports.NodeUsersDataSource = NodeUsersDataSource;
 class NodeConnectionsDataSource extends NodeHttpDataSource {

package/package.json

@@ -4,7 +4,7 @@
     "type": "git",
     "url": "https://github.com/datagrok-ai/public.git"
   },
-  "version": "6.7.6",
+  "version": "6.7.8",
   "description": "Utility to upload and publish packages to Datagrok",
   "homepage": "https://github.com/datagrok-ai/public/tree/master/tools#readme",
   "dependencies": {
@@ -90,7 +90,7 @@
     "update:ivp-parser": "esbuild plugins/ivp-parser.entry.mjs --bundle --format=cjs --platform=node --alias:diff-grok=../libraries/compute-utils/node_modules/diff-grok --outfile=plugins/ivp-parser.bundle.cjs",
     "debug-source-map": "node build.js --source-maps",
     "test": "vitest run --project unit",
-    "test:server": "vitest run --project unit bin/__tests__/node-dapi bin/__tests__/server bin/__tests__/migrate bin/__tests__/keypair",
+    "test:server": "vitest run --project unit bin/__tests__/node-dapi bin/__tests__/server bin/__tests__/migrate bin/__tests__/keypair bin/__tests__/grok-cli",
     "test:watch": "vitest --project unit",
     "test:integration": "vitest run --project integration",
     "test:all": "vitest run"