relic-mcp 0.12.0 → 0.12.1

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.12.0",
+      "version": "0.12.1",
       "source": "./",
       "author": {
         "name": "The Bushido Collective",
@@ -21,6 +21,6 @@
     }
   ],
   "metadata": {
-    "version": "0.12.0"
+    "version": "0.12.1"
   }
 }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "relic",
-  "version": "0.12.0",
+  "version": "0.12.1",
   "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/README.md

@@ -180,10 +180,10 @@ relic plaintext leaves the machine during rendering.
 | `relic_lookup_source` | `path` | Reads local state to find whether this machine already published that file, and returns the exact `relic_republish` call. Calls no server. |
 | `relic_list` | optional `limit`, `include_expired`, `verify`, `refresh` | Every relic this machine published, newest first. The only tool that enumerates: lookup answers only from the file a relic came from. A name this machine never recorded is recovered by decrypting the relic's own envelope in one 64 KB range request, or comes back `null` with the reason. A relic the service will not serve is listed with which of removed, expired, exhausted, or unreachable it is. Each row carries the share URL, fragment included, so each row is a credential. Reaching the service spends one of a relic's finite opens; recovered names are cached, so a repeat listing spends none. |
 | `relic_show` | `relic_id`, optional `include_content` | One relic in detail, including how many versions the service holds against how many this machine recorded, and with `include_content` the current decrypted content. Read it before republishing anything you did not just write: republish replaces what the link serves, so without the read-back the edit is blind. Content that is not valid UTF-8 is reported as size and type rather than mangled text. |
-| `relic_republish` | `relic_id`, `path`, optional `filename`, `title`, `cover`, `ttl_days`, `addresses`, `notify` | Publishes a new version under the same key, so the share URL is unchanged. Replaces the plaintext title (defaults to the new filename; pass `""` to remove it). Replaces the cover image with a newly rendered cover, or clears it if `cover: false` is passed. Sends a change notice email to everyone following the relic unless `notify: false` is passed. Works only on the machine holding that relic's key and publish token; a taken-down relic can never be revived. |
-| `relic_share` | `relic_id`, `emails` | Send a relic this machine published to named people. Registers up to 20 email addresses with the service for change notices on future versions, and returns a composed share email and mailto link to draft in the sharer's own mailbox. Addresses are stored in the clear by the service, linked to the relic id. Relic never sends the share email. Readers holding the link can also share from the viewer once this client version has published or republished the relic. |
+| `relic_republish` | `relic_id`, `path`, optional `filename`, `title`, `cover`, `ttl_days`, `addresses`, `notify` | Publishes a new version under the same key, so the share URL is unchanged. Replaces the plaintext title (defaults to the new filename; pass `""` to remove it). Replaces the cover image with a newly rendered cover, or clears it if `cover: false` is passed. Sends a change notice email to everyone following the relic unless `notify: false` is passed. At most one email per person per relic per 10 minutes is sent, and one stop link stops every email about that relic. Works only on the machine holding that relic's key and publish token; a taken-down relic can never be revived. |
+| `relic_share` | `relic_id`, `emails` | Send a relic this machine published to named people. Registers up to 20 email addresses with the service for change and comment notices, and returns a composed share email and mailto link to draft in the sharer's own mailbox. Addresses are stored in the clear by the service, linked to the relic id. A new comment emails everyone on the list except the author, naming the commenter's address (or 'The publisher'). At most one email per person per relic per 10 minutes, and one stop link stops every email about that relic. Relic never sends the share email. Readers holding the link can also share from the viewer once this client version has published or republished the relic. |
 | `relic_read_comments` | `relic_id` | Returns the relic's comments oldest first, decrypted locally, with the author and a count of any that would not decrypt. Works only on the machine that published. |
-| `relic_comment` | `relic_id`, `body`, optional `display_name` | Leaves a comment, encrypted on this machine, authorized by the publish token and attributed as `publisher`. Body caps at 4096 bytes of UTF-8. |
+| `relic_comment` | `relic_id`, `body`, optional `display_name` | Leaves a comment, encrypted on this machine, authorized by the publish token and attributed as `publisher`. Warning: posting emails everyone following the relic, naming 'The publisher'. At most one email per person per relic per 10 minutes, and one stop link stops every email about that relic. Body caps at 4096 bytes of UTF-8. |
 | `relic_describe_client` | none | Explains the encryption path. Reads nothing, sends nothing. |
 
 ## Environment

package/dist/relic-mcp.js

@@ -26295,7 +26295,7 @@ async function shareVerifierFor(proof) {
 function composeShareEmail(p) {
   const thing = p.title === null ? "a file" : `"${p.title}"`;
   const subject = p.title === null ? "A file shared with you on Relic" : `Shared with you: ${p.title}`;
-  const next = p.sender === "publisher" ? "When I publish a new version" : "When a new version is published";
+  const next = p.sender === "publisher" ? "When someone comments or I publish a new version" : "When someone comments or a new version is published";
   const text = [
     `I've shared ${thing} with you on Relic. Open it here:`,
     "",
@@ -26303,7 +26303,7 @@ function composeShareEmail(p) {
     "",
     "Anyone with this whole link can read it, including the part after the #, which is the key that decrypts it. Relic never receives that part.",
     "",
-    `${next}, Relic will email you that it changed. That email never contains the key, and it has a link to stop those emails. Relic keeps your address for that.`
+    `${next}, Relic will email you. That email never contains the key, and it has a link to stop those emails. Relic keeps your address for that.`
   ].join(`
 `);
   return { to: [...p.to], subject, text };
@@ -31389,7 +31389,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. " + 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. " + "By default a picture of the first screen is rendered locally and " + "uploaded unencrypted for link previews; pass cover: false to withhold " + "it." + REPUBLISH_DISCIPLINE_DISCLOSURE + " Each new version emails a change notice, naming the title and version and never the key, to everyone who commented and every address added with relic_share; pass notify: false to skip it.",
+  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. " + "By default a picture of the first screen is rendered locally and " + "uploaded unencrypted for link previews; pass cover: false to withhold " + "it." + REPUBLISH_DISCIPLINE_DISCLOSURE + " Each new version emails a change notice, naming the title and version and never the key, to each verified commenter and each address added with relic_share, minus any that stopped emails; pass notify: false to skip it. At most one email per person per relic per 10 minutes, and one stop link stops every email about that relic.",
   inputSchema: {
     type: "object",
     properties: {
@@ -31442,7 +31442,7 @@ var REPUBLISH_TOOL_DEFINITION = {
       notify: {
         type: "boolean",
         default: true,
-        description: "Optional. Email a change notice for this version to everyone following the relic: each verified address that commented on it and each address added with relic_share, except any that stopped those emails. Defaults to true. The notice names the title and version and never carries the key. Pass false for a change not worth an email, such as a typo fix."
+        description: "Optional. Email a change notice for this version to each verified address that commented on the relic and each address added with relic_share, except any that stopped those emails. Defaults to true. The notice names the title and version and never carries the key. At most one email per person per relic per 10 minutes, and one stop link stops every email about that relic. Pass false for a change not worth an email, such as a typo fix."
       }
     },
     required: ["relic_id", "path"],
@@ -31505,7 +31505,7 @@ var REPUBLISH_TOOL_DEFINITION = {
 var SHARE_TOOL_DEFINITION = {
   name: SHARE_TOOL_NAME,
   title: "Share a relic with people",
-  description: "Send a relic this machine published to named people. Registers their email addresses with the service so each gets a change notice when you republish, and returns a ready share email carrying the full link, plus a mailto link that opens it as a draft. Relic never sends the share email, because it carries the key: draft it in the sharer’s own mailbox, from their own address, and let them send it. The service stores the addresses in the clear, linked to the relic. A change notice names the title and version, never the key, and carries a link to stop them. Only works on the machine that published the relic: the link needs its key and registering needs its publish token. Takes the relic id, never the share URL. Up to 20 addresses per call and 50 per relic.",
+  description: 'Send a relic this machine published to named people. Registers their email addresses with the service so each gets an email notice when someone comments and when you republish, and returns a ready share email carrying the full link, plus a mailto link that opens it as a draft. Relic never sends the share email, because it carries the key: draft it in the sharer’s own mailbox, from their own address, and let them send it. The service stores the addresses in the clear, linked to the relic. A change notice names the title and version, never the key. A new comment emails everyone on the list except the author, naming the commenter’s address (or "The publisher"). At most one email per person per relic per 10 minutes, and one stop link stops every email about that relic. Only works on the machine that published the relic: the link needs its key and registering needs its publish token. Takes the relic id, never the share URL. Up to 20 addresses per call and 50 per relic.',
   inputSchema: {
     type: "object",
     properties: {
@@ -31518,7 +31518,7 @@ var SHARE_TOOL_DEFINITION = {
         items: { type: "string" },
         minItems: 1,
         maxItems: 20,
-        description: "Up to 20 email addresses to register for change notices."
+        description: "Up to 20 email addresses to register for comment and change notices."
       }
     },
     required: ["relic_id", "emails"],
@@ -32055,7 +32055,7 @@ var READ_COMMENTS_TOOL_DEFINITION = {
 var COMMENT_TOOL_DEFINITION = {
   name: COMMENT_TOOL_NAME,
   title: "Comment on a relic",
-  description: "Leave a comment on a relic this machine published, encrypted here so " + "the service stores ciphertext it cannot read. Everyone holding the " + "link sees it. Attribution is the publish token, so the comment is " + 'attributed to "publisher" rather than to an email address: an agent has ' + "no mailbox and cannot verify one. That is attribution and not " + "authorization. " + "Comments can be anchored to an exact location: a text quote, a stage " + "pin, an artifact region, a moment or span in audio or video, or a page " + "in a document. Passing an anchor attaches your reply at that location, " + "so the reader sees what you are answering; omitting it leaves a remark " + "about the whole relic. " + COMMENT_MACHINE_BOUNDARY + " Takes the relic id, never the share URL.",
+  description: "Leave a comment on a relic this machine published, encrypted here so " + "the service stores ciphertext it cannot read. Everyone holding the " + "link sees it. Warning: posting emails everyone following the relic " + "(each verified commenter, each address added with relic_share, and " + "the owner address, minus any that used the stop link). " + "Attribution is the publish token, so the comment is attributed to " + '"publisher" rather than to an email address: an agent has no mailbox ' + 'and cannot verify one, and the email names "The publisher". At most ' + "one email per person per relic per 10 minutes, and one stop link stops " + "every email about that relic. That is attribution and not " + "authorization. " + "Comments can be anchored to an exact location: a text quote, a stage " + "pin, an artifact region, a moment or span in audio or video, or a page " + "in a document. Passing an anchor attaches your reply at that location, " + "so the reader sees what you are answering; omitting it leaves a remark " + "about the whole relic. " + COMMENT_MACHINE_BOUNDARY + " Takes the relic id, never the share URL.",
   inputSchema: {
     type: "object",
     properties: {
@@ -32265,7 +32265,7 @@ var DESCRIBE_TOOL_DEFINITION = {
     additionalProperties: false
   }
 };
-var SERVER_VERSION = "0.12.0";
+var SERVER_VERSION = "0.12.1";
 var SERVER_INFO = {
   name: "relic",
   title: "Relic",
@@ -32281,9 +32281,9 @@ Nine things that change how you should act:
 4. Check sources with relic_lookup_source; relic_republish keeps the URL where relic_publish costs a second URL. ${VERSION_HISTORY_DISCLOSURE}
 5. A relic can be republished only from the machine that published it: the key and publish token live nowhere else.
 6. HTML and JSX render in an isolated frame with no network access, so inline styles, scripts, fonts, and images: a CDN reference renders as nothing.
-7. People can comment on a relic. Read with relic_read_comments before changing reviewed content, answer with relic_comment. relic_edit_comment rewrites one, relic_resolve_comment settles one, and settled counts as handled. All take the relic id and attribute you as publisher.
+7. People can comment on a relic. Read with relic_read_comments before changing reviewed content, answer with relic_comment. relic_edit_comment rewrites one, relic_resolve_comment settles one, and settled counts as handled. All take the relic id and attribute you as publisher. A new comment emails everyone on the relic's list except the author (naming the address, or "The publisher" for relic_comment; at most once per 10 minutes). One stop link stops every email about that relic.
 8. By default relic_publish and relic_republish upload a picture of the file's first screen, unencrypted, for link previews: the service and anyone holding the link without the key can see it. Pass cover: false for anything you would not show in a chat preview.
-9. relic_republish emails a change notice, naming the title and version but never the key, to everyone who commented and every address added with relic_share; pass notify: false to skip it. relic_share hands back a share email with the full link for you to draft in the sharer's own mailbox: Relic never sends it, so the key never reaches the service. Readers holding the link can also share from the viewer once this client version has published or republished the relic.`;
+9. relic_republish emails a change notice, naming the title and version but never the key, to everyone following the relic; pass notify: false to skip it. relic_share hands back a share email with the full link for you to draft in the sharer's own mailbox: Relic never sends it, so the key never reaches the service. Readers holding the link can also share from the viewer once this client version has published or republished the relic.`;
 async function handleMessage(message, deps) {
   if (message.id === undefined)
     return;
@@ -32369,9 +32369,10 @@ async function callTool(id2, params, deps) {
           ciphertext_destination: "object storage, via a signed URL",
           local_publish_state: "relic id, source identity, key, and publish token per relic, " + "written 0600 under the user config directory; key and token " + "are never printed or sent",
           comment_encryption: "AES-128-GCM under a key derived from the relic key with a " + "distinct HKDF label, so comment bodies reach the service as " + "ciphertext and the URL fragment is unchanged",
-          comment_attribution: 'the publish token, reported by the service as "publisher"; the ' + "operator learns which identity commented on which relic and when",
-          change_notices: "on every republish unless notify: false, the service emails every " + "verified address that commented on the relic and every address " + "added with relic_share, minus any that used the stop link; the " + "email names the title and version and never carries the key",
-          sharing: "relic_share sends the service email addresses and nothing else; " + "it stores them in the clear, linked to the relic id; the share " + "email carrying the full link is composed here for you to send " + "from your own mailbox, so the key never reaches the service; " + "readers holding the link can also share from the viewer once a " + "relic was published or republished by this client version",
+          comment_attribution: 'the publish token, reported by the service as "publisher"; the ' + "operator learns which identity commented on which relic and when; " + 'posting with relic_comment emails everyone following the relic, naming "The publisher"',
+          comment_notices: "a new comment on a relic emails everyone on its list (commenters, " + "shared addresses, the owner address) except the author, naming the " + 'commenter’s address or "The publisher"; at most one email per person ' + "per relic per 10 minutes, and one stop link stops every email about that relic",
+          change_notices: "on every republish unless notify: false, the service emails every " + "verified address that commented on the relic and every address " + "added with relic_share, minus any that used " + "the stop link; the email names the title and version and never carries the key; " + "at most one email per person per relic per 10 minutes, and one stop link stops every email about that relic",
+          sharing: "relic_share sends the service email addresses and nothing else; " + "it stores them in the clear, linked to the relic id so they receive " + "comment and change notices; the share email carrying the full link " + "is composed here for you to send from your own mailbox, so the key " + "never reaches the service; readers holding the link can also share " + "from the viewer once a relic was published or republished by this client version",
           service_origin: deps.serviceOrigin
         },
         isError: false
@@ -32692,7 +32693,7 @@ async function callRepublish(id2, params, deps) {
 
 ` + "The share URL is unchanged: everyone holding the existing " + "link, including its fragment, now sees this content. There " + `is no new link to hand out.
 
-` + `${result.notify ? `Relic sends a change notice for version ${result.version} to everyone following this relic, meaning each address that commented on it or was added with relic_share, except any that stopped those emails. It names the title and version and never carries the key.` : "No change notice goes out for this version, as asked."}
+` + `${result.notify ? `Relic sends a change notice for version ${result.version} to each address that commented on this relic or was added with relic_share, except any that stopped those emails. It names the title and version and never carries the key (at most one email per recipient per relic per 10 minutes; one stop link stops every email about that relic).` : "No change notice goes out for this version, as asked."}
 
 ` + `Key phrase: ${result.key_phrase}
 ` + `${KEY_PHRASE_DISCLOSURE}
@@ -32734,7 +32735,7 @@ async function callShare(id2, params, deps) {
       relic_id: relicId,
       emails: rawEmails
     }, deps);
-    const text = `Registered ${result.registered.length} address(es) on relic ${result.relic_id} ` + `for change notices (${result.added} new; ${result.shared_count} of ${result.share_limit} on its list). ` + `Relic has emailed nobody.
+    const text = `Registered ${result.registered.length} address(es) on relic ${result.relic_id} ` + `for comment and change notices (${result.added} new; ${result.shared_count} of ${result.share_limit} on its list). ` + `Relic has emailed nobody.
 
 ` + "Draft the email below in the sharer's own mailbox, from their own address, " + "and let them send it. Do not send it through Relic or any other service, and " + `do not paste the link anywhere else: it carries the key, which is now in this transcript.
 
@@ -32837,7 +32838,7 @@ async function callComment(id2, params, deps) {
           {
             type: "text",
             text: `Commented on relic ${result.relic_id} as ${result.author}.
-` + "Everyone holding the link sees it. The service stored " + "ciphertext it cannot read, and it knows that this address " + "commented on this relic at this time."
+` + "Everyone holding the link sees it. The service stored " + "ciphertext it cannot read, and it knows that this address " + "commented on this relic at this time. Relic emails everyone " + 'following this relic, naming "The publisher" (at most one ' + "email per recipient per relic per 10 minutes; one stop link " + "stops every email about that relic)."
           }
         ],
         structuredContent: result,
@@ -33101,18 +33102,23 @@ writes is attributed to the publisher rather than an email address, because
 an agent has no mailbox to verify. What the operator does learn is who
 commented on which relic and when: for a person that is a verified email
 address, and that association is a real cost the content's encryption does
-not cover.
+not cover. A new comment emails everyone on the relic's list (commenters,
+shared addresses, and the owner address) except the author, naming the
+commenter's address or "The publisher" for comments this client posts.
+At most one email per person per relic per 10 minutes, and one stop link
+stops every email about that relic.
 
 What happens with change notices and sharing: on every republish unless
 notify: false, the service emails every verified address that commented on
 the relic and every address added with relic_share, minus any that used the
-stop link. The email names the title and version and never carries the key.
-relic_share sends the service email addresses and nothing else: it stores
-them in the clear, linked to the relic id. The share email carrying the
-full link is composed here on this machine for you to send from your own
-mailbox, so the key never reaches the service. Readers holding the link
-can also share from the viewer once the relic was published or republished
-by this client version.
+stop link. The email names the title and version and
+never carries the key. At most one email per person per relic per 10 minutes,
+and one stop link stops every email about that relic. relic_share sends the
+service email addresses and nothing else: it stores them in the clear, linked
+to the relic id. The share email carrying the full link is composed here on
+this machine for you to send from your own mailbox, so the key never reaches
+the service. Readers holding the link can also share from the viewer once the
+relic was published or republished by this client version.
 
 What this does NOT protect against: the key is returned to your agent in the
 URL, so it enters the model's context and your session transcript. That is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "relic-mcp",
-  "version": "0.12.0",
+  "version": "0.12.1",
   "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

@@ -153,18 +153,23 @@ Call `relic_share` with the relic id and up to 20 email addresses:
 relic_share(relic_id: "0a2c...", emails: ["ada@example.com", "grace@example.com"])
 ```
 
-`relic_share` registers the addresses with the service so each recipient receives an email notice whenever a new version is republished. It composes a ready-to-send share email containing the full URL and key, and returns both the email text and a `mailto:` link.
+`relic_share` registers the addresses with the service so each recipient receives an email notice whenever someone comments or a new version is republished. It composes a ready-to-send share email containing the full URL and key, and returns both the email text and a `mailto:` link.
 
 Draft the email in the user's own mailbox (or hand over the `mailto:` link if there is no mail tool available) and let them send it. Relic never sends the share email, because the share link carries the key in its fragment, and the service must never receive the key.
 
-Addresses are stored by the service in the clear, linked to the relic id. When you republish, the service automatically sends a change notice to everyone who commented and every address added with `relic_share`, unless you pass `notify: false`.
+Addresses are stored by the service in the clear, linked to the relic id. When you republish, the service automatically sends a change notice to each commenter and shared address, unless you pass `notify: false`. When a new comment is posted, the service emails everyone on the relic's list (commenters, shared addresses, and the owner address) except the comment's author, naming the commenter's address (or "The publisher"). Relic sends at most one email per person per relic per 10 minutes, and one stop link stops every email about that relic.
 
 Readers holding the link can also share from the viewer once a relic was published or republished by this client version.
 
 ## Comments
 
 People can comment on a relic, and that is the only way a reader can answer
-back. Nothing tells you a comment arrived, so read them.
+back. A new comment on a relic emails everyone on its list (verified commenters,
+shared addresses, and the owner address) except the author, naming the
+commenter's address (or "The publisher"). At most one email per person per
+relic per 10 minutes is sent, and one stop link stops every email about that
+relic. You have no mailbox, so none of those emails reach you: read them.
+
 ```
 relic_read_comments(relic_id: "0a2c...")
 ```
@@ -180,6 +185,9 @@ Answer with:
 relic_comment(relic_id: "0a2c...", body: "Fixed the chart, republished as version 3.")
 ```
 
+Posting a comment with `relic_comment` emails everyone following the relic,
+naming "The publisher".
+
 Four things to know:
 
 - **Both work only on the machine that published the relic.** The comment key
@@ -192,7 +200,8 @@ Four things to know:
 - **Your comment is attributed to the publisher, not to a person.** A human
   commenter verifies an email address through a magic link and that address is
   their identity. You have no mailbox, so the publish token stands in and the
-  comment reads as `publisher`. Optional `display_name` puts a label beside it;
+  comment reads as `publisher`. Posting emails everyone following the relic,
+  naming "The publisher". Optional `display_name` puts a label beside it;
   it decorates the attribution and never replaces it.
 - **A comment that will not decrypt comes back marked unreadable**, with a
   count. That is not noise to filter out: it means part of the conversation is

package/src/server.ts

@@ -383,7 +383,7 @@ export const REPUBLISH_TOOL_DEFINITION = {
     'uploaded unencrypted for link previews; pass cover: false to withhold ' +
     'it.' +
     REPUBLISH_DISCIPLINE_DISCLOSURE +
-    ' Each new version emails a change notice, naming the title and version and never the key, to everyone who commented and every address added with relic_share; pass notify: false to skip it.',
+    ' Each new version emails a change notice, naming the title and version and never the key, to each verified commenter and each address added with relic_share, minus any that stopped emails; pass notify: false to skip it. At most one email per person per relic per 10 minutes, and one stop link stops every email about that relic.',
   inputSchema: {
     type: 'object',
     properties: {
@@ -451,7 +451,7 @@ export const REPUBLISH_TOOL_DEFINITION = {
         type: 'boolean',
         default: true,
         description:
-          'Optional. Email a change notice for this version to everyone following the relic: each verified address that commented on it and each address added with relic_share, except any that stopped those emails. Defaults to true. The notice names the title and version and never carries the key. Pass false for a change not worth an email, such as a typo fix.',
+          'Optional. Email a change notice for this version to each verified address that commented on the relic and each address added with relic_share, except any that stopped those emails. Defaults to true. The notice names the title and version and never carries the key. At most one email per person per relic per 10 minutes, and one stop link stops every email about that relic. Pass false for a change not worth an email, such as a typo fix.',
       },
     },
     required: ['relic_id', 'path'],
@@ -516,7 +516,7 @@ export const SHARE_TOOL_DEFINITION = {
   name: SHARE_TOOL_NAME,
   title: 'Share a relic with people',
   description:
-    'Send a relic this machine published to named people. Registers their email addresses with the service so each gets a change notice when you republish, and returns a ready share email carrying the full link, plus a mailto link that opens it as a draft. Relic never sends the share email, because it carries the key: draft it in the sharer\u2019s own mailbox, from their own address, and let them send it. The service stores the addresses in the clear, linked to the relic. A change notice names the title and version, never the key, and carries a link to stop them. Only works on the machine that published the relic: the link needs its key and registering needs its publish token. Takes the relic id, never the share URL. Up to 20 addresses per call and 50 per relic.',
+    'Send a relic this machine published to named people. Registers their email addresses with the service so each gets an email notice when someone comments and when you republish, and returns a ready share email carrying the full link, plus a mailto link that opens it as a draft. Relic never sends the share email, because it carries the key: draft it in the sharer\u2019s own mailbox, from their own address, and let them send it. The service stores the addresses in the clear, linked to the relic. A change notice names the title and version, never the key. A new comment emails everyone on the list except the author, naming the commenter\u2019s address (or "The publisher"). At most one email per person per relic per 10 minutes, and one stop link stops every email about that relic. Only works on the machine that published the relic: the link needs its key and registering needs its publish token. Takes the relic id, never the share URL. Up to 20 addresses per call and 50 per relic.',
   inputSchema: {
     type: 'object',
     properties: {
@@ -529,7 +529,8 @@ export const SHARE_TOOL_DEFINITION = {
         items: { type: 'string' },
         minItems: 1,
         maxItems: 20,
-        description: 'Up to 20 email addresses to register for change notices.',
+        description:
+          'Up to 20 email addresses to register for comment and change notices.',
       },
     },
     required: ['relic_id', 'emails'],
@@ -1210,9 +1211,14 @@ export const COMMENT_TOOL_DEFINITION = {
   description:
     'Leave a comment on a relic this machine published, encrypted here so ' +
     'the service stores ciphertext it cannot read. Everyone holding the ' +
-    'link sees it. Attribution is the publish token, so the comment is ' +
-    'attributed to "publisher" rather than to an email address: an agent has ' +
-    'no mailbox and cannot verify one. That is attribution and not ' +
+    'link sees it. Warning: posting emails everyone following the relic ' +
+    '(each verified commenter, each address added with relic_share, and ' +
+    'the owner address, minus any that used the stop link). ' +
+    'Attribution is the publish token, so the comment is attributed to ' +
+    '"publisher" rather than to an email address: an agent has no mailbox ' +
+    'and cannot verify one, and the email names "The publisher". At most ' +
+    'one email per person per relic per 10 minutes, and one stop link stops ' +
+    'every email about that relic. That is attribution and not ' +
     'authorization. ' +
     'Comments can be anchored to an exact location: a text quote, a stage ' +
     'pin, an artifact region, a moment or span in audio or video, or a page ' +
@@ -1558,18 +1564,20 @@ styles, scripts, fonts, and images: a CDN reference renders as nothing.
 7. People can comment on a relic. Read with relic_read_comments before \
 changing reviewed content, answer with relic_comment. relic_edit_comment \
 rewrites one, relic_resolve_comment settles one, and settled counts as \
-handled. All take the relic id and attribute you as publisher.
+handled. All take the relic id and attribute you as publisher. A new \
+comment emails everyone on the relic's list except the author (naming \
+the address, or "The publisher" for relic_comment; at most once per 10 \
+minutes). One stop link stops every email about that relic.
 8. By default relic_publish and relic_republish upload a picture of the file's \
 first screen, unencrypted, for link previews: the service and anyone holding \
 the link without the key can see it. Pass cover: false for anything you would \
 not show in a chat preview.
 9. relic_republish emails a change notice, naming the title and version but \
-never the key, to everyone who commented and every address added with \
-relic_share; pass notify: false to skip it. relic_share hands back a share \
-email with the full link for you to draft in the sharer's own mailbox: Relic \
-never sends it, so the key never reaches the service. Readers holding the \
-link can also share from the viewer once this client version has published \
-or republished the relic.`;
+never the key, to everyone following the relic; pass notify: false to skip \
+it. relic_share hands back a share email with the full link for you to draft \
+in the sharer's own mailbox: Relic never sends it, so the key never reaches \
+the service. Readers holding the link can also share from the viewer once this \
+client version has published or republished the relic.`;
 
 /**
  * Handle one JSON-RPC message.
@@ -1715,19 +1723,26 @@ async function callTool(
             'ciphertext and the URL fragment is unchanged',
           comment_attribution:
             'the publish token, reported by the service as "publisher"; the ' +
-            'operator learns which identity commented on which relic and when',
+            'operator learns which identity commented on which relic and when; ' +
+            'posting with relic_comment emails everyone following the relic, naming "The publisher"',
+          comment_notices:
+            'a new comment on a relic emails everyone on its list (commenters, ' +
+            'shared addresses, the owner address) except the author, naming the ' +
+            'commenter\u2019s address or "The publisher"; at most one email per person ' +
+            'per relic per 10 minutes, and one stop link stops every email about that relic',
           change_notices:
             'on every republish unless notify: false, the service emails every ' +
             'verified address that commented on the relic and every address ' +
-            'added with relic_share, minus any that used the stop link; the ' +
-            'email names the title and version and never carries the key',
+            'added with relic_share, minus any that used ' +
+            'the stop link; the email names the title and version and never carries the key; ' +
+            'at most one email per person per relic per 10 minutes, and one stop link stops every email about that relic',
           sharing:
             'relic_share sends the service email addresses and nothing else; ' +
-            'it stores them in the clear, linked to the relic id; the share ' +
-            'email carrying the full link is composed here for you to send ' +
-            'from your own mailbox, so the key never reaches the service; ' +
-            'readers holding the link can also share from the viewer once a ' +
-            'relic was published or republished by this client version',
+            'it stores them in the clear, linked to the relic id so they receive ' +
+            'comment and change notices; the share email carrying the full link ' +
+            'is composed here for you to send from your own mailbox, so the key ' +
+            'never reaches the service; readers holding the link can also share ' +
+            'from the viewer once a relic was published or republished by this client version',
           service_origin: deps.serviceOrigin,
         },
         isError: false,
@@ -2303,7 +2318,7 @@ async function callRepublish(
               'is no new link to hand out.\n\n' +
               `${
                 result.notify
-                  ? `Relic sends a change notice for version ${result.version} to everyone following this relic, meaning each address that commented on it or was added with relic_share, except any that stopped those emails. It names the title and version and never carries the key.`
+                  ? `Relic sends a change notice for version ${result.version} to each address that commented on this relic or was added with relic_share, except any that stopped those emails. It names the title and version and never carries the key (at most one email per recipient per relic per 10 minutes; one stop link stops every email about that relic).`
                   : 'No change notice goes out for this version, as asked.'
               }\n\n` +
               `Key phrase: ${result.key_phrase}\n` +
@@ -2375,7 +2390,7 @@ async function callShare(
 
     const text =
       `Registered ${result.registered.length} address(es) on relic ${result.relic_id} ` +
-      `for change notices (${result.added} new; ${result.shared_count} of ${result.share_limit} on its list). ` +
+      `for comment and change notices (${result.added} new; ${result.shared_count} of ${result.share_limit} on its list). ` +
       'Relic has emailed nobody.\n\n' +
       "Draft the email below in the sharer's own mailbox, from their own address, " +
       'and let them send it. Do not send it through Relic or any other service, and ' +
@@ -2546,7 +2561,10 @@ async function callComment(
               `Commented on relic ${result.relic_id} as ${result.author}.\n` +
               'Everyone holding the link sees it. The service stored ' +
               'ciphertext it cannot read, and it knows that this address ' +
-              'commented on this relic at this time.',
+              'commented on this relic at this time. Relic emails everyone ' +
+              'following this relic, naming "The publisher" (at most one ' +
+              'email per recipient per relic per 10 minutes; one stop link ' +
+              'stops every email about that relic).',
           },
         ],
         structuredContent: result,
@@ -2984,18 +3002,23 @@ writes is attributed to the publisher rather than an email address, because
 an agent has no mailbox to verify. What the operator does learn is who
 commented on which relic and when: for a person that is a verified email
 address, and that association is a real cost the content's encryption does
-not cover.
+not cover. A new comment emails everyone on the relic's list (commenters,
+shared addresses, and the owner address) except the author, naming the
+commenter's address or "The publisher" for comments this client posts.
+At most one email per person per relic per 10 minutes, and one stop link
+stops every email about that relic.
 
 What happens with change notices and sharing: on every republish unless
 notify: false, the service emails every verified address that commented on
 the relic and every address added with relic_share, minus any that used the
-stop link. The email names the title and version and never carries the key.
-relic_share sends the service email addresses and nothing else: it stores
-them in the clear, linked to the relic id. The share email carrying the
-full link is composed here on this machine for you to send from your own
-mailbox, so the key never reaches the service. Readers holding the link
-can also share from the viewer once the relic was published or republished
-by this client version.
+stop link. The email names the title and version and
+never carries the key. At most one email per person per relic per 10 minutes,
+and one stop link stops every email about that relic. relic_share sends the
+service email addresses and nothing else: it stores them in the clear, linked
+to the relic id. The share email carrying the full link is composed here on
+this machine for you to send from your own mailbox, so the key never reaches
+the service. Readers holding the link can also share from the viewer once the
+relic was published or republished by this client version.
 
 What this does NOT protect against: the key is returned to your agent in the
 URL, so it enters the model's context and your session transcript. That is