relic-mcp 0.3.2 → 0.3.3

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
     {
       "name": "relic",
       "description": "Publish a file from your machine as an encrypted, shareable link. The agent encrypts locally, uploads only ciphertext, and hands back a URL whose fragment holds the key, so the service stores something it cannot read.",
-      "version": "0.3.2",
+      "version": "0.3.3",
       "source": "./",
       "author": {
         "name": "The Bushido Collective",
@@ -21,6 +21,6 @@
     }
   ],
   "metadata": {
-    "version": "0.3.2"
+    "version": "0.3.3"
   }
 }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "relic",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "Publish a file from your machine as an encrypted, shareable link. The agent encrypts locally, uploads only ciphertext, and hands back a URL whose fragment holds the key, so the service stores something it cannot read.",
   "mcpServers": "./mcp-servers.json",
   "author": {

package/dist/relic-mcp.js

@@ -1163,10 +1163,11 @@ var DESCRIBE_TOOL_NAME = "relic_describe_client";
 var REPUBLISH_TOOL_NAME = "relic_republish";
 var LOOKUP_TOOL_NAME = "relic_lookup_source";
 var MAX_TTL_DAYS = 3650;
+var VERSION_HISTORY_DISCLOSURE = "Anyone holding a relic's link can fetch every version it has ever held, " + "so republishing does not withdraw earlier content.";
 var TOOL_DEFINITION = {
   name: TOOL_NAME,
   title: "Publish a relic",
-  description: "Encrypt a file on this machine and publish it as a new relic, returning " + "a shareable URL. Publishing an update this way costs a second URL that " + "nobody holding the first one will ever see; use relic_republish instead " + "so the existing URL keeps working. The encryption key is generated " + "locally and never sent to the service. Takes a filesystem path, never " + "inline content.",
+  description: "Encrypt a file on this machine and publish it as a new relic, returning " + "a shareable URL. Publishing an update this way costs a second URL that " + "nobody holding the first one will ever see; use relic_republish instead " + "so the existing URL keeps working. " + VERSION_HISTORY_DISCLOSURE + " The encryption key is generated locally and never sent to the service. " + "Takes a filesystem path, never " + "inline content.",
   inputSchema: {
     type: "object",
     properties: {
@@ -1227,7 +1228,7 @@ var TOOL_DEFINITION = {
 var REPUBLISH_TOOL_DEFINITION = {
   name: REPUBLISH_TOOL_NAME,
   title: "Republish a relic",
-  description: "Publish a new version of a relic this machine originally published, " + "encrypting under the same key so the existing share URL keeps working. " + "Only possible from the machine that holds the relic's key and publish " + "token; a relic that was taken down can never be revived.",
+  description: "Publish a new version of a relic this machine originally published, " + "encrypting under the same key so the existing share URL keeps working. " + VERSION_HISTORY_DISCLOSURE + " Only possible from the machine that holds the relic's key and publish " + "token; a relic that was taken down can never be revived.",
   inputSchema: {
     type: "object",
     properties: {
@@ -1346,7 +1347,7 @@ var DESCRIBE_TOOL_DEFINITION = {
     additionalProperties: false
   }
 };
-var SERVER_VERSION = "0.3.2";
+var SERVER_VERSION = "0.3.3";
 var SERVER_INFO = {
   name: "relic",
   title: "Relic",
@@ -1359,7 +1360,7 @@ Five things that change how you should act:
 
 1. The link is the credential. Anyone holding it, fragment included, can read the file. Do not paste it into a tracker, a log, or a public channel.
 2. Publishing puts the key in this transcript. That is structural rather than a defect, and worth saying plainly when you hand the link over.
-3. If a source was published before, use relic_republish so its URL keeps working. Publishing it as new costs a second URL that nobody holding the first one will ever see. relic_publish refuses by default, relic_lookup_source recovers the id, and force_new is only for a deliberate second link.
+3. Check existing sources with relic_lookup_source. Use relic_republish when found; relic_publish otherwise costs a second URL. ${VERSION_HISTORY_DISCLOSURE}
 4. A relic can be republished only from the machine that published it, which is where its key and publish token are stored. Anywhere else it refuses, and no retry changes that.
 5. Rendered HTML and JSX run in an isolated frame with no network access. Inline the styles, scripts, fonts, and images a page needs, because a CDN reference renders as nothing. Decide that before you write the file.`;
 async function handleMessage(message, deps) {
@@ -1486,7 +1487,8 @@ async function callTool(id2, params, deps) {
 
 ` + (result.relic_expires_at === null ? "It does not expire; it is kept until it is deleted. " : `Expires ${result.relic_expires_at}. `) + "Anyone with this link, " + "including its fragment, can read the file. The key is in the " + "fragment and it is now in this transcript. This machine can " + `republish it later; the link will not change.
 ` + isolationNote(result.renderer_class) + `What Relic knows: ${result.disclosure_url}`
-          }
+          },
+          { type: "text", text: VERSION_HISTORY_DISCLOSURE }
         ],
         structuredContent: result,
         isError: false
@@ -1564,7 +1566,8 @@ async function callRepublish(id2, params, deps) {
 
 ` + (result.relic_expires_at === null ? "The relic does not expire; it is kept until it is deleted." : `Expires ${result.relic_expires_at}.`) + `
 ` + `What Relic knows: ${result.disclosure_url}`
-          }
+          },
+          { type: "text", text: VERSION_HISTORY_DISCLOSURE }
         ],
         structuredContent: result,
         isError: false

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "relic-mcp",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "Publish a file as an encrypted relic. The key is generated on your machine and never sent to the service.",
   "license": "MIT",
   "type": "module",

package/skills/relic/SKILL.md

@@ -39,6 +39,11 @@ Do not publish an update as a new relic. That costs a second URL that nobody
 holding the first one will ever see. `relic_publish` enforces this: when local
 state matches the source, it refuses and points to `relic_republish`.
 
+Anyone holding a relic's link can fetch every version it has ever held, so
+republishing does not withdraw earlier content. Republishing moves the artifact
+forward without retracting what came before. Deleting the relic still removes
+every version.
+
 Optional arguments worth knowing:
 
 - `filename` overrides the display name shown to the recipient.

package/src/server.ts

@@ -105,6 +105,10 @@ export const LOOKUP_TOOL_NAME = 'relic_lookup_source';
  */
 const MAX_TTL_DAYS = 3650;
 
+const VERSION_HISTORY_DISCLOSURE =
+  "Anyone holding a relic's link can fetch every version it has ever held, " +
+  'so republishing does not withdraw earlier content.';
+
 export const TOOL_DEFINITION = {
   name: TOOL_NAME,
   title: 'Publish a relic',
@@ -112,8 +116,10 @@ export const TOOL_DEFINITION = {
     'Encrypt a file on this machine and publish it as a new relic, returning ' +
     'a shareable URL. Publishing an update this way costs a second URL that ' +
     'nobody holding the first one will ever see; use relic_republish instead ' +
-    'so the existing URL keeps working. The encryption key is generated ' +
-    'locally and never sent to the service. Takes a filesystem path, never ' +
+    'so the existing URL keeps working. ' +
+    VERSION_HISTORY_DISCLOSURE +
+    ' The encryption key is generated locally and never sent to the service. ' +
+    'Takes a filesystem path, never ' +
     'inline content.',
   inputSchema: {
     type: 'object',
@@ -187,7 +193,8 @@ export const REPUBLISH_TOOL_DEFINITION = {
   description:
     'Publish a new version of a relic this machine originally published, ' +
     'encrypting under the same key so the existing share URL keeps working. ' +
-    "Only possible from the machine that holds the relic's key and publish " +
+    VERSION_HISTORY_DISCLOSURE +
+    " Only possible from the machine that holds the relic's key and publish " +
     'token; a relic that was taken down can never be revived.',
   inputSchema: {
     type: 'object',
@@ -369,10 +376,9 @@ Five things that change how you should act:
 the file. Do not paste it into a tracker, a log, or a public channel.
 2. Publishing puts the key in this transcript. That is structural rather than \
 a defect, and worth saying plainly when you hand the link over.
-3. If a source was published before, use relic_republish so its URL keeps \
-working. Publishing it as new costs a second URL that nobody holding the first \
-one will ever see. relic_publish refuses by default, relic_lookup_source \
-recovers the id, and force_new is only for a deliberate second link.
+3. Check existing sources with relic_lookup_source. Use relic_republish when \
+found; relic_publish otherwise costs a second URL. \
+${VERSION_HISTORY_DISCLOSURE}
 4. A relic can be republished only from the machine that published it, which \
 is where its key and publish token are stored. Anywhere else it refuses, and \
 no retry changes that.
@@ -601,6 +607,7 @@ async function callTool(
               isolationNote(result.renderer_class) +
               `What Relic knows: ${result.disclosure_url}`,
           },
+          { type: 'text', text: VERSION_HISTORY_DISCLOSURE },
         ],
         structuredContent: result,
         isError: false,
@@ -732,6 +739,7 @@ async function callRepublish(
               '\n' +
               `What Relic knows: ${result.disclosure_url}`,
           },
+          { type: 'text', text: VERSION_HISTORY_DISCLOSURE },
         ],
         structuredContent: result,
         isError: false,