@turbobase/cli 1.1.7

package/LICENSE

@@ -0,0 +1,48 @@
+TurboBase CLI — Software Licence
+
+Copyright (c) 2025-2026 Adam Kundrat. All rights reserved.
+
+This software is proprietary. It is licensed, not sold.
+
+The repository's root LICENSE governs the SOURCE, and grants no rights to
+anyone. This file governs the PUBLISHED PACKAGE, which is a compiled artifact
+handed to customers on a public registry: a customer who installs it needs the
+right to run it, and "no rights granted" would not give them that.
+
+1. GRANT. Subject to your compliance with these terms and to an active
+   agreement with the copyright holder covering the TurboBase service, you are
+   granted a non-exclusive, non-transferable, non-sublicensable, revocable
+   licence to install and run this software, for the sole purpose of
+   authoring, testing, and deploying extensions to TurboBase instances you are
+   authorised to access. Installing it on your own machines and on continuous
+   integration runners you control is permitted under this grant.
+
+2. RESTRICTIONS. You may not: copy this software except as reasonably required
+   to install and run it under Section 1; modify, adapt, translate, or create
+   derivative works of it; reverse engineer, decompile, or disassemble it, or
+   otherwise attempt to derive its source code, except to the extent
+   applicable law expressly permits despite this limitation; redistribute,
+   publish, sublicense, sell, rent, lease, or otherwise make it available to
+   any third party; or remove, obscure, or alter this notice.
+
+3. RESERVATION. All rights not expressly granted here are reserved by the
+   copyright holder. This licence covers this software only. It grants no
+   rights in the TurboBase service, which is governed by your service
+   agreement, and no rights in any trademark.
+
+4. THIRD-PARTY COMPONENTS. This software incorporates third-party open source
+   components that remain governed by their own licences. Nothing here limits
+   any right you hold in those components under those licences.
+
+5. NO WARRANTY. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
+   KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+   MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.
+
+6. LIMITATION OF LIABILITY. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE
+   FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER IN AN ACTION OF
+   CONTRACT, TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION WITH
+   THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+7. TERMINATION. This licence terminates automatically if you breach any of
+   these terms, and when your agreement covering the TurboBase service ends.
+   On termination you must stop using this software and delete all copies.

package/README.md

@@ -0,0 +1,119 @@
+# turbobase
+
+The `turbobase` CLI authors, tests, and deploys **TurboBase extensions** — hooks
+and conduits — against a running TurboBase instance. It talks to the instance
+over its HTTP API using a personal access token (PAT); it is **not** a way to
+stand up TurboBase yourself (instances are provisioned and operated as a managed
+service — see [console.turbobase.io](https://console.turbobase.io/)).
+
+Every subcommand wraps the same library functions the in-product authoring MCP
+server uses, so the CLI and the Claude Code surface never drift.
+
+## Install
+
+```sh
+curl -fsSL https://console.turbobase.io/install-cli.sh | bash
+```
+
+On Windows: `powershell -c "irm https://console.turbobase.io/install-cli.ps1 | iex"`.
+
+The installer verifies the download's checksum, installs into `~/.turbobase`,
+and puts `turbobase` on your PATH — no sudo, no package manager. It also fetches
+a private Node.js if the machine has none at v22 or newer.
+
+This npm package is the same CLI for anyone who would rather manage it alongside
+their other global tools:
+
+```sh
+npm install -g @turbobase/cli
+turbobase --version
+```
+
+`turbobase ext test` and `turbobase ext replay` need two native packages that the
+one-line install leaves out; `turbobase ext extras install` fetches them on demand
+(an npm install already has them as dependencies).
+
+## Authenticate
+
+Mint a PAT in your TurboBase app under **Settings › Access tokens**, then paste
+it. This is the only sign-in path — there is no browser flow today.
+
+```sh
+turbobase auth login --base-url https://acme.turbobase.app --token tb_pat_xxxxxxxx
+```
+
+**The instance you last signed in to becomes the ACTIVE default** — every
+command uses it when you don't pass `--base-url`, so you never repeat the flag
+for the instance you're working on. `--base-url` is only needed to reach a
+*different* stored instance. On login the CLI probes the instance and warns if
+the base URL doesn't serve the `/v1` API (the local-dev trap of pointing at the
+app dev-server port instead of the instance API) or if the token is rejected —
+pass `--no-verify` to skip the probe.
+
+```sh
+turbobase auth status                 # active instance (*) + every stored sign-in
+turbobase auth use https://beta.turbobase.app   # switch the active default (no PAT re-paste)
+turbobase auth logout                 # remove the active sign-in (--base-url <url> / --all)
+```
+
+Credentials are stored in `~/.turbobase/credentials` (0600) as
+`{ active, tenants: { "<base-url>": { token } } }`. Override the directory with
+`TURBOBASE_HOME`.
+
+## Author → test → deploy
+
+```sh
+turbobase project types                          # generate types.ts from the instance catalog
+turbobase ext new hook --record salesOrder --field memo
+turbobase project samples                   # fixtures from the live catalog
+turbobase ext test hooks/<file>.ts           # dry-run in the production-parity sandbox
+turbobase ext deploy hooks/<file>.ts         # POST /v1/extensions (lands active)
+turbobase ext logs <id>                      # tail the deployed extension's logs
+```
+
+The surface is seven groups: `auth` (sign-in + the credential store), `project`
+(scaffold, types, grounding, adopt), `ext` (author → verify → ship → observe,
+plus the marketplace), `apps` (hosted apps), `kb` (knowledge-base writes),
+`sandbox` (ephemeral local instances), and `mcp` (the authoring server).
+
+Run `turbobase --help` for the groups, `turbobase <group> --help` for what is in
+one.
+
+## Output & interactivity
+
+On an interactive terminal the CLI renders colour, a spinner for long-running
+calls, a live stage + percent bar for `--follow` jobs, aligned tables (`auth status`,
+`apps list`, `ext binding`), and boxed result cards. When a command needs an
+instance and several are stored with no active default, it arrow-picks one
+instead of erroring.
+
+Colour + animation are **chrome on stderr**; command results — ids, tables, JSON,
+`--reporter` output, streamed job logs — stay on **stdout**, so pipes and
+captured output are never disturbed. Colour is off automatically when stdout
+isn't a TTY, and can be forced off with `--no-color` (before the command) or
+`NO_COLOR=1`. `--json` / `--reporter` output is always plain.
+
+## Offline commands (no instance required)
+
+`ext lint`, `ext test`, `ext replay --fixture`, `ext new`, `project init` and
+`project ci` run fully offline.
+The rest resolve an instance + PAT from your credential store and fail with a
+clear message when you're not signed in.
+
+`turbobase mcp` (the local authoring server that `turbobase project init` wires
+into `.mcp.json`) runs from a published install — no source checkout needed.
+
+## Version
+
+This CLI is versioned independently of the instance runtime. It targets the
+instance HTTP API and is forward/backward tolerant across platform releases.
+
+Node 22 or newer. `turbobase ext test` and `turbobase ext replay` load a native
+`isolated-vm` binary, and prebuilt binaries exist only for current Node
+releases — on older ones every install would fall back to compiling it.
+
+## Licence
+
+Proprietary — see `LICENSE`. You may install and run it to author, test, and
+deploy extensions to instances you are authorised to access, including on your
+own CI runners. Redistribution and reverse engineering are not permitted.