@vitrinka/cli 3.6.0 → 3.7.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +34 -0
- package/README.md +12 -14
- package/package.json +8 -9
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,40 @@
|
|
|
3
3
|
`vitrinka update` prints the sections newer than your previous version after
|
|
4
4
|
updating — keep entries short and user-facing.
|
|
5
5
|
|
|
6
|
+
## 3.7.1
|
|
7
|
+
|
|
8
|
+
### Fixed
|
|
9
|
+
- **`vitrinka update` migrates a Codex marketplace registered under a legacy
|
|
10
|
+
name.** Codex refuses `marketplace upgrade` for a clone registered as
|
|
11
|
+
`lovinka` or `vitrinka` once the kit's manifest names it `kit`; update now
|
|
12
|
+
drops the stale registration, re-adds the kit and re-adds the plugin
|
|
13
|
+
instead of handing you the error.
|
|
14
|
+
|
|
15
|
+
## 3.7.0
|
|
16
|
+
|
|
17
|
+
One version, everywhere: the `vitrinka` agent plugin (Claude Code / Codex
|
|
18
|
+
marketplace `vitrinka@kit`) now carries the CLI's version, so `vitrinka
|
|
19
|
+
update` always brings the skills and the MCP vocabulary that match this
|
|
20
|
+
binary. The plugin jumps from 1.11.0 to 3.7.0 in one step.
|
|
21
|
+
|
|
22
|
+
### Added
|
|
23
|
+
- **File a task from a board card.** Right-click any card → *File a task
|
|
24
|
+
from this card*: the task lands in the project with the card as its
|
|
25
|
+
evidence, and (when you may accept intake) is projected straight back
|
|
26
|
+
onto the board as a task card. Cards wear a quiet `REN-12 · done ↗` link
|
|
27
|
+
to the tasks filed from them.
|
|
28
|
+
- **Pin a task on a board** from the task panel's menu; task cards link
|
|
29
|
+
back to their task.
|
|
30
|
+
- **`docs {family: element|board|artifact}`** narrows the docs index to one
|
|
31
|
+
layer (about a third of the tokens).
|
|
32
|
+
|
|
33
|
+
### Changed
|
|
34
|
+
- `scrape_board` and `list_sections` take `board` like every other board
|
|
35
|
+
tool (`slug` still works).
|
|
36
|
+
- `list_tasks` answers compact rows — label names, no bodies, no actor
|
|
37
|
+
objects, no timestamps; `get_task` has the full record.
|
|
38
|
+
- The docs index shows one sentence per topic.
|
|
39
|
+
|
|
6
40
|
## 3.6.0
|
|
7
41
|
|
|
8
42
|
### Added
|
package/README.md
CHANGED
|
@@ -37,32 +37,30 @@ failing as "command not found".
|
|
|
37
37
|
|
|
38
38
|
## MCP
|
|
39
39
|
|
|
40
|
-
The MCP
|
|
41
|
-
|
|
40
|
+
The MCP surface is served by the vitrinka server at `/mcp`; the registration
|
|
41
|
+
every client runs is the CLI's own stdio forwarder, `vitrinka mcp`. It resolves
|
|
42
|
+
the deployment origin, the token (OS keyring) and the operator at runtime, so
|
|
43
|
+
the registration itself carries no URL, no token, no headers — it is identical
|
|
44
|
+
on every machine and safe to commit. `vitrinka install` registers it for you;
|
|
45
|
+
manually:
|
|
42
46
|
|
|
43
47
|
```bash
|
|
44
|
-
claude mcp add --scope user --transport
|
|
45
|
-
--header "Authorization: Bearer $(vitrinka token)"
|
|
48
|
+
claude mcp add --scope user --transport stdio vitrinka -- vitrinka mcp
|
|
46
49
|
```
|
|
47
50
|
|
|
48
|
-
For Claude Desktop or any other MCP client, add the equivalent
|
|
51
|
+
For Claude Desktop or any other MCP client, add the equivalent stdio entry:
|
|
49
52
|
|
|
50
53
|
```json
|
|
51
54
|
{
|
|
52
55
|
"mcpServers": {
|
|
53
|
-
"vitrinka": {
|
|
54
|
-
"type": "http",
|
|
55
|
-
"url": "https://app.vitrinka.ai/mcp",
|
|
56
|
-
"headers": { "Authorization": "Bearer …" }
|
|
57
|
-
}
|
|
56
|
+
"vitrinka": { "command": "vitrinka", "args": ["mcp"] }
|
|
58
57
|
}
|
|
59
58
|
}
|
|
60
59
|
```
|
|
61
60
|
|
|
62
|
-
> The
|
|
63
|
-
>
|
|
64
|
-
>
|
|
65
|
-
> `vitrinka install` and `vitrinka doctor --fix` will do it for you.
|
|
61
|
+
> The old **HTTP + `Authorization: Bearer …` registration is retired** — it
|
|
62
|
+
> baked a credential into client config. `vitrinka doctor` flags it and
|
|
63
|
+
> rewrites it to the stdio form above; `vitrinka install` does the same.
|
|
66
64
|
|
|
67
65
|
vitrinka is reachable over the WireGuard mesh — bring the VPN up (or point
|
|
68
66
|
`VITRINKA_BASE_URL` at any reachable host) before use.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vitrinka/cli",
|
|
3
|
-
"version": "3.
|
|
3
|
+
"version": "3.7.1",
|
|
4
4
|
"description": "vitrinka CLI \u2014 capture and publish artifact sets, drive the annotation-board work queue. Thin npm launcher for the single-binary Go CLI.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"vitrinka": "bin/vitrinka.js"
|
|
@@ -14,23 +14,22 @@
|
|
|
14
14
|
"node": ">=18"
|
|
15
15
|
},
|
|
16
16
|
"optionalDependencies": {
|
|
17
|
-
"@vitrinka/cli-darwin-arm64": "3.
|
|
18
|
-
"@vitrinka/cli-darwin-x64": "3.
|
|
19
|
-
"@vitrinka/cli-linux-arm64": "3.
|
|
20
|
-
"@vitrinka/cli-linux-x64": "3.
|
|
21
|
-
"@vitrinka/cli-win32-arm64": "3.
|
|
22
|
-
"@vitrinka/cli-win32-x64": "3.
|
|
17
|
+
"@vitrinka/cli-darwin-arm64": "3.7.1",
|
|
18
|
+
"@vitrinka/cli-darwin-x64": "3.7.1",
|
|
19
|
+
"@vitrinka/cli-linux-arm64": "3.7.1",
|
|
20
|
+
"@vitrinka/cli-linux-x64": "3.7.1",
|
|
21
|
+
"@vitrinka/cli-win32-arm64": "3.7.1",
|
|
22
|
+
"@vitrinka/cli-win32-x64": "3.7.1"
|
|
23
23
|
},
|
|
24
24
|
"keywords": [
|
|
25
25
|
"vitrinka",
|
|
26
|
-
"lovinka",
|
|
27
26
|
"cli",
|
|
28
27
|
"mcp",
|
|
29
28
|
"model-context-protocol",
|
|
30
29
|
"screenshots",
|
|
31
30
|
"ai"
|
|
32
31
|
],
|
|
33
|
-
"author": "
|
|
32
|
+
"author": "FixIt Technologies",
|
|
34
33
|
"license": "MIT",
|
|
35
34
|
"repository": {
|
|
36
35
|
"type": "git",
|