@vitrinka/cli 3.8.0 → 3.8.1

package/CHANGELOG.md

@@ -3,6 +3,27 @@
 `vitrinka update` prints the sections newer than your previous version after
 updating — keep entries short and user-facing.
 
+## 3.8.1
+
+The public-beta surface: vitrinka is an authenticated service at
+`app.vitrinka.ai` — sign up, run `vitrinka auth login`, and every skill,
+message and manifest now says so. Author and repository moved to Henderson
+Tech (`github.com/henderson-tech/vitrinka-kit`).
+
+### Removed
+- **`vitrinka import pultik`** — the one-off Obsidian vault importer is gone;
+  `vitrinka import <file>` still forwards to `diagram import`.
+
+### Changed
+- Unreachable-host and `doctor` messages point at your network or
+  `VITRINKA_URL` for self-hosted deployments instead of a VPN.
+- Skills and MCP tool descriptions describe the authenticated service; Eve is
+  introduced as vitrinka's AI reviewer; example slugs are `acme`.
+- The npm launcher and platform packages are Elastic-2.0 and ship the LICENSE;
+  author Henderson Tech; issues and README link to the public kit repository.
+- Docs: the quickstart links sign-up; the report widget page describes the
+  served `report-widget-1.mjs` script.
+
 ## 3.8.0
 
 Personal todos and scheduled reminders live in vitrinka: a `todo` task type

package/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that organization.
+**control** means ownership of substantially all the assets of an entity, or the
+power to direct its management and policies by vote, contract, or otherwise.
+Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/README.md

@@ -1,6 +1,6 @@
 # @vitrinka/cli
 
-The [vitrinka](https://github.com/FixIt-Technologies/vitrinka) CLI — capture
+The [vitrinka](https://github.com/henderson-tech/vitrinka-kit) CLI — capture
 screenshots, publish artifact **sets**, scaffold interactive artifacts, and arm
 the annotation-board `watch` monitor that feeds work to a listening AI session.
 
@@ -37,18 +37,31 @@ failing as "command not found".
 
 ## MCP
 
-The MCP surface is served by the vitrinka server at `/mcp`; the registration
-every client runs is the CLI's own stdio forwarder, `vitrinka mcp`. It resolves
-the deployment origin, the token (OS keyring) and the operator at runtime, so
-the registration itself carries no URL, no token, no headers — it is identical
-on every machine and safe to commit. `vitrinka install` registers it for you;
-manually:
+The MCP surface is served by the vitrinka server at `/mcp` and per workspace
+at `/w/<workspace>/mcp`, with OAuth 2.1 built in. `vitrinka install` registers
+it for you. For Claude Code that is a **remote HTTP entry** — no local
+process per session; sign in once from inside Claude Code (`/mcp` → vitrinka
+→ authenticate):
 
 ```bash
-claude mcp add --scope user --transport stdio vitrinka -- vitrinka mcp
+claude mcp add --scope project --transport http vitrinka https://app.vitrinka.ai/w/<workspace>/mcp
 ```
 
-For Claude Desktop or any other MCP client, add the equivalent stdio entry:
+The same command renders the repo's committed `.vitrinka/project.json` into
+every other harness's project-level file — Cursor (`.cursor/mcp.json`),
+OpenCode (`opencode.json`), VS Code (`.vscode/mcp.json`), Gemini CLI
+(`.gemini/settings.json`) — as a plain remote URL the harness signs into with
+its own OAuth flow; `--harness <csv|all>` picks them (default: Claude Code
+plus whatever is detected), entries merge into existing files, and
+`vitrinka doctor` reports drift. Through a user-level entry (root `/mcp`)
+writes reach only projects that already exist; the bound repo's project file
+is what allows creating them.
+
+For Codex, headless machines (`vitrinka install --mcp-stdio`) and any MCP
+client without OAuth, the CLI's own stdio forwarder `vitrinka mcp` does the
+same job: it resolves the deployment origin, the workspace, the token (OS
+keyring) and the operator at runtime, so the entry carries no URL, no token,
+no headers:
 
 ```json
 {
@@ -60,17 +73,25 @@ For Claude Desktop or any other MCP client, add the equivalent stdio entry:
 
 > The old **HTTP + `Authorization: Bearer …` registration is retired** — it
 > baked a credential into client config. `vitrinka doctor` flags it and
-> rewrites it to the stdio form above; `vitrinka install` does the same.
+> `vitrinka install` rewrites it.
 
-vitrinka is reachable over the WireGuard mesh — bring the VPN up (or point
-`VITRINKA_BASE_URL` at any reachable host) before use.
+`vitrinka install` also links `~/.local/bin/vitrinka` straight to the Go
+binary this package ships (on npm and bun; pnpm gets a copy that `vitrinka
+update` refreshes) and puts it first on PATH, so long-running commands
+(`vitrinka mcp`, `vitrinka watch`) run without the Node launcher idling as
+their parent. Updates still flow through your package manager.
+
+vitrinka is an authenticated service at `https://app.vitrinka.ai` — sign up
+there (open beta), then `vitrinka auth login` signs the CLI in through the
+browser. Self-hosted deployments point the CLI at their own host with
+`VITRINKA_URL` (or `--base`).
 
 ## Configuration (env)
 
 | Var | Default | Purpose |
 |---|---|---|
 | `VITRINKA_URL` / `VITRINKA_BASE_URL` | `https://app.vitrinka.ai` | vitrinka server base URL. `VITRINKA_URL` wins, then `VITRINKA_BASE_URL`; the CLI's `--base` flag overrides both. |
-| `VITRINKA_TOKEN` | — | Bearer write token. Falls back to the OS keyring / `~/.config/vitrinka/`. Required only by the **mutating** calls; read calls work unauthenticated. |
+| `VITRINKA_TOKEN` | — | Bearer token. `vitrinka auth login` stores it in the OS keyring / `~/.config/vitrinka/`; set the variable explicitly for CI. |
 | `VITRINKA_OPERATOR` | — | Operator persona name. When set, write calls carry `X-Board-Actor: <name>` so the board credits the operator — agent-authored content keeps its explicit `claude` attribution. |
 
 ## Trustworthy project index
@@ -109,15 +130,11 @@ open boards in the app (pass `--browser` to force the browser), and
 
 ## Development
 
-The CLI source lives in the vitrinka repo — `cmd/vitrinka` + `internal/cli/`:
-
-```bash
-go build -o /tmp/vitrinka ./cmd/vitrinka
-go test ./internal/cli/...
-```
-
-This package carries no implementation; it is the npm front door only.
+This package carries no implementation; it is the npm front door only. The
+binaries are built and released from the vitrinka server repository; the
+public plugin, skills and issue tracker live in
+[vitrinka-kit](https://github.com/henderson-tech/vitrinka-kit).
 
 ## License
 
-MIT
+Elastic License 2.0 — see the [LICENSE](./LICENSE) file shipped in this package.

package/package.json

@@ -1,25 +1,26 @@
 {
   "name": "@vitrinka/cli",
-  "version": "3.8.0",
-  "description": "vitrinka CLI \u2014 capture and publish artifact sets, drive the annotation-board work queue. Thin npm launcher for the single-binary Go CLI.",
+  "version": "3.8.1",
+  "description": "vitrinka CLI — capture and publish artifact sets, drive the annotation-board work queue. Thin npm launcher for the single-binary Go CLI.",
   "bin": {
     "vitrinka": "bin/vitrinka.js"
   },
   "files": [
     "bin",
     "README.md",
-    "CHANGELOG.md"
+    "CHANGELOG.md",
+    "LICENSE"
   ],
   "engines": {
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@vitrinka/cli-darwin-arm64": "3.8.0",
-    "@vitrinka/cli-darwin-x64": "3.8.0",
-    "@vitrinka/cli-linux-arm64": "3.8.0",
-    "@vitrinka/cli-linux-x64": "3.8.0",
-    "@vitrinka/cli-win32-arm64": "3.8.0",
-    "@vitrinka/cli-win32-x64": "3.8.0"
+    "@vitrinka/cli-darwin-arm64": "3.8.1",
+    "@vitrinka/cli-darwin-x64": "3.8.1",
+    "@vitrinka/cli-linux-arm64": "3.8.1",
+    "@vitrinka/cli-linux-x64": "3.8.1",
+    "@vitrinka/cli-win32-arm64": "3.8.1",
+    "@vitrinka/cli-win32-x64": "3.8.1"
   },
   "keywords": [
     "vitrinka",
@@ -29,11 +30,14 @@
     "screenshots",
     "ai"
   ],
-  "author": "FixIt Technologies",
-  "license": "MIT",
+  "author": "Henderson Tech",
+  "license": "Elastic-2.0",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/FixIt-Technologies/vitrinka.git",
-    "directory": "npm/vitrinka"
+    "url": "git+https://github.com/henderson-tech/vitrinka-kit.git"
+  },
+  "homepage": "https://vitrinka.ai",
+  "bugs": {
+    "url": "https://github.com/henderson-tech/vitrinka-kit/issues"
   }
 }