viber-channel 0.8.13 → 0.8.15
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/package.json +1 -1
- package/viber-channel.ts +9 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "viber-channel",
|
|
3
|
-
"version": "0.8.
|
|
3
|
+
"version": "0.8.15",
|
|
4
4
|
"description": "Voice + text MCP channel between a Claude Code session and the Viber UI (https://viber.dgypx.dev). Push transcripts to Claude; send_message tool delivers text back to the UI.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
package/viber-channel.ts
CHANGED
|
@@ -2,6 +2,15 @@
|
|
|
2
2
|
/**
|
|
3
3
|
* viber-channel MCP channel server (#217, #232)
|
|
4
4
|
*
|
|
5
|
+
* This package's `version` in package.json is what vibe-master's spawn-time probe reads
|
|
6
|
+
* from the npm registry to decide whether a machine's global install has drifted (#503).
|
|
7
|
+
* It is therefore a PUBLISHED contract, not just a number: the `channel-v*` tag, the
|
|
8
|
+
* package version and vibe-master's `EXPECTED_VIBER_CHANNEL_VERSION` floor move together
|
|
9
|
+
* (#423). From vibe-master 0.7.7 on, that contract lets a version published here reach
|
|
10
|
+
* clients WITHOUT a vibe-master release: the floor only sets the minimum, the registry
|
|
11
|
+
* sets the target. Measured evidence belongs in the issue/plan that measures it — not in
|
|
12
|
+
* the package whose publication is what makes the measurement possible.
|
|
13
|
+
*
|
|
5
14
|
* Reads .viber/auth.json for authentication, then connects to
|
|
6
15
|
* /api/conversations/<id>/events SSE stream and pushes transcripts and
|
|
7
16
|
* messages as channel events.
|