@manudota/artist-mcp 1.8.2-staging.87 → 1.8.2

package/agent-pack/AGENTS.md

@@ -13,12 +13,18 @@ Load them before working on the musician's notes:
 - Without the server, read `.artist/policies/` directly. Every file there
   applies to this work whether or not anyone loaded it.
 
-OneNote is never written, no message is ever sent, and nothing is ever booked:
-drafts, plans, audits and page patches are handed to the musician, who applies
-them or does not. What an install may change beyond that is not fixed, and this
-file does not say — `list_agent_workflows` states it in full at the top of every
-briefing, because it depends on what the user granted at install time. Assuming
-either answer is how this file drifted before.
+No message is ever sent. That one is unconditional — a scope commitment, not a
+grant — and it is the only absolute this file is entitled to state. Otherwise
+the shape of the work is that it is handed over rather than applied: drafts,
+plans, audits and page patches go to the musician, who uses them or does not.
+
+What an install may actually change is not fixed, and this file does not say —
+`list_agent_workflows` states it in full at the top of every briefing, because
+it depends on what the user granted at install time. Assuming either answer is
+how this file drifted before, and this paragraph did it again: it claimed
+OneNote was never written and nothing was ever booked, two sentences above the
+warning against exactly that, and both had been false since the first write
+grant shipped.
 
 ## Why this file says so little
 

package/dist/server.js

@@ -164,7 +164,7 @@ const renderChangedSections = (chosen, notebook, since) => {
         caveats.join("\n\n"),
     ].join("\n\n");
 };
-const serverVersion = '1.8.2-staging.87'; // x-release-please-version
+const serverVersion = '1.8.2'; // x-release-please-version
 const errorResult = (err) => {
     const message = err instanceof GraphError ? err.message : `Unexpected error: ${err}`;
     return { content: [{ type: "text", text: message }], isError: true };
@@ -311,6 +311,23 @@ const renderWorkflowBriefing = async (entries, load, writes = []) => {
  * Derived, never restated. An install with no grant says so too — that line is
  * the one that keeps a read-only install describing itself correctly.
  */
+/**
+ * The sentence that puts the playbooks in force on a client that never sees the
+ * handshake.
+ *
+ * Claude Desktop does not deliver the `instructions` field to the model at all,
+ * so on the one client `init` configures a tool description is the only thing
+ * that reaches a session before it answers. It opens every note-reading tool's
+ * description: a client may clip the tool list to one line, and the opening is
+ * what is read most often.
+ *
+ * One constant, not three literals. Three copies of a rule is how `AGENTS.md`
+ * drifted from the pack it restated. See #99.
+ */
+const PLAYBOOK_GATE = "Call `list_agent_workflows` first if you have not already this session — " +
+    "the playbooks it returns govern how pages are surveyed, what is stated " +
+    "and how firmly, and how anything is handed over. Without them no policy " +
+    "is in force. ";
 const capabilityLine = (writes) => {
     if (writes.length === 0) {
         return (" This install can only read. It cannot create, change or delete " +
@@ -345,6 +362,18 @@ const createServer = async (call, grants = []) => {
     // alone with no policy in force. That is the "a rule in a role is not in
     // force" failure one level up: the briefing was correct and never arrived.
     //
+    // Kept, but do not mistake it for the channel that binds. Claude Desktop —
+    // the client `init` configures — does not deliver this field to the model at
+    // all: a live Desktop session, asked to quote it back, reported the tool list
+    // and no preamble of any kind. Claude Code does deliver it verbatim, and a
+    // Code session called `list_agent_workflows` unprompted, which is why this
+    // stays. The rule a Desktop session actually reads is the one on `list_notes`
+    // and `read_note`, and #99 is why it is there as well as here.
+    //
+    // The capability line below is subject to the same limit. A Desktop session
+    // that described its writes correctly did so from its own tool list, since
+    // write tools are registered only when granted — not from this sentence.
+    //
     // It deliberately carries no rules of its own. `AGENTS.md` restated the pack
     // for repository clients and drifted from it — it still announces three
     // always-loaded policies, and still uses the winner-picking phrasing that
@@ -410,7 +439,18 @@ const createServer = async (call, grants = []) => {
             return errorResult(err);
         }
     });
-    server.tool("list_notes", "List the user's OneNote pages, with title, notebook, section and last " +
+    server.tool("list_notes", 
+    // The playbook gate lives here, not only in the handshake. Claude Desktop
+    // does not deliver the `instructions` field to the model at all — verified
+    // against a live session, which reported the tool list and no preamble —
+    // so on the one client `init` configures, the handshake reaches nothing.
+    // A description does reach it: `preview_calendar_event`'s refusal clause
+    // sits ~650 characters in and a Desktop session acted on it. See #99.
+    //
+    // It opens the description because a client may render the listing clipped
+    // to one line, and because the first paragraph is what is read most often.
+    PLAYBOOK_GATE +
+        "List the user's OneNote pages, with title, notebook, section and last " +
         "date. Takes an optional notebook name. When the account holds " +
         "more than one notebook and none is given, this returns the list of " +
         "notebooks instead of any pages, so the user can say which one to work " +
@@ -523,7 +563,12 @@ const createServer = async (call, grants = []) => {
             return errorResult(err);
         }
     });
-    server.tool("map_notes", "Sketch every page in one notebook without reading them, so a notebook can " +
+    server.tool("map_notes", 
+    // A third entry point, and often the first: a session may triage a notebook
+    // before it lists anything, so gating list_notes alone leaves the survey
+    // itself running with no policy in force. See #99.
+    PLAYBOOK_GATE +
+        "Sketch every page in one notebook without reading them, so a notebook can " +
         "be triaged before any page is read in full. Returns the opening of each " +
         "page — for a well-kept page that is its headline facts. Use it to decide " +
         "which pages are worth read_note. What it returns is the TOP of a page, " +
@@ -651,7 +696,11 @@ const createServer = async (call, grants = []) => {
             return errorResult(err);
         }
     });
-    server.tool("read_note", "Read the text content of one OneNote page. Takes the id from list_notes. " +
+    server.tool("read_note", 
+    // Both entry points carry it: an id can be remembered from earlier in a
+    // session, so read_note is not always reached through list_notes. See #99.
+    PLAYBOOK_GATE +
+        "Read the text content of one OneNote page. Takes the id from list_notes. " +
         "A page too long for one answer comes back in parts, and the answer says " +
         "so and how to continue — a page is never truncated silently.", {
         note_id: z.string().describe("The id of the note, as returned by list_notes"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@manudota/artist-mcp",
-  "version": "1.8.2-staging.87",
+  "version": "1.8.2",
   "description": "MCP server that reads your OneNote notes, with optional Gmail and Calendar as supporting evidence, via a hosted connection.",
   "repository": {
     "type": "git",