@manudota/artist-mcp 2.3.0 → 2.3.1-staging.114

package/dist/notes.js

@@ -81,11 +81,21 @@ export const htmlToText = (html) => html
     .replace(/<(script|style)[\s\S]*?<\/\1>/gi, '')
     .replace(/<br\s*\/?>/gi, '\n')
     .replace(/<\/(p|div|li|h[1-6]|tr)>/gi, '\n')
-    // A to-do tag is an attribute on the paragraph, so it dies with the tag
-    // strip below unless it is turned into text first. Above the <li> rule
-    // too: that rule rewrites the opening tag, attribute and all.
-    .replace(/<(p|li)[^>]*data-tag="[^"]*\bto-do:completed\b[^"]*"[^>]*>/gi, '$&[x] ')
-    .replace(/<(p|li)[^>]*data-tag="[^"]*\bto-do\b(?!:)[^"]*"[^>]*>/gi, '$&[ ] ')
+    // A to-do tag is an attribute on the element, so it dies with the tag strip
+    // below unless it is turned into text first. Above the <li> rule too: that
+    // rule rewrites the opening tag, attribute and all.
+    //
+    // `span` is here because OneNote moves the tag there. A cell written as
+    // `<td><p data-tag="to-do">…</p></td>` comes back as
+    // `<td><span data-tag="to-do">…</span></td>` — the paragraph is gone and
+    // the tag is on the span. Matching only p and li meant every task inside a
+    // table read as untagged, so a page whose tasks live in an Aufgaben table
+    // reported none of them done however many were ticked. Found by writing
+    // twelve tags, reading the page back, and concluding from clean text that
+    // the write had failed; the tags were there and the reader could not see
+    // them.
+    .replace(/<(p|li|span)[^>]*data-tag="[^"]*\bto-do:completed\b[^"]*"[^>]*>/gi, '$&[x] ')
+    .replace(/<(p|li|span)[^>]*data-tag="[^"]*\bto-do\b(?!:)[^"]*"[^>]*>/gi, '$&[ ] ')
     .replace(/<li[^>]*>/gi, '- ')
     .replace(/<[^>]+>/g, '')
     // Numeric entities first: OneNote emits these for accented characters, so

package/dist/onenote-patch.js

@@ -513,10 +513,46 @@ export const inherit = (targetHtml, contentHtml) => {
         // And the cells, which carry their own border in what OneNote hands back.
         // Only when the replacement specifies none anywhere: a caller that styled
         // one cell has decided about all of them.
-        const cellStyle = /<t[dh]\b[^>]*\bstyle="([^"]*)"/i.exec(target.inner)?.[1];
-        if (cellStyle !== undefined && !/<t[dh]\b[^>]*\bstyle="/i.test(inner)) {
-            inner = inner.replace(/<(t[dh])(\b[^>]*?)?>/gi, `<$1$2 style="${cellStyle}">`);
-            carried = true;
+        //
+        // Cell by cell, in order. This used to take the FIRST cell's style and put
+        // it on every cell of the replacement, which is correct only for a table
+        // whose cells all look alike. On a table with a shaded header row the first
+        // cell IS the header, so replacing a twelve-row task table in place painted
+        // the header's `background-color:#EFEFEF` onto all 52 cells and the whole
+        // table came back grey. Nothing said so: the preview reported "keeping the
+        // style of the table it replaces", which was true and read as reassurance.
+        //
+        // Positional only when the shapes agree. A replacement with a different
+        // number of cells is a different table, and carrying styles across by index
+        // there would put a header's shading on whatever happened to land in that
+        // slot — the same bug with extra steps. The fallback is the style most of
+        // the target's cells carry, which is the body's, because being wrong about
+        // the header row is a great deal cheaper than being wrong about all of it.
+        if (!/<t[dh]\b[^>]*\bstyle="/i.test(inner)) {
+            const targetCells = target.inner.match(/<t[dh]\b[^>]*>/gi) ?? [];
+            const styles = targetCells.map((cell) => /\bstyle="([^"]*)"/i.exec(cell)?.[1]);
+            const replacementCells = inner.match(/<t[dh]\b[^>]*>/gi) ?? [];
+            if (styles.some((style) => style !== undefined)) {
+                const byIndex = replacementCells.length === targetCells.length;
+                const commonest = [...styles.filter((s) => s !== undefined)]
+                    .sort((a, b) => styles.filter((s) => s === b).length - styles.filter((s) => s === a).length)[0];
+                let seen = -1;
+                inner = inner.replace(/<(t[dh])(\b[^>]*?)?>/gi, (whole, tag, rest) => {
+                    seen += 1;
+                    const style = byIndex ? styles[seen] : commonest;
+                    return style === undefined ? whole : `<${tag}${rest ?? ''} style="${style}">`;
+                });
+                carried = true;
+                // Said separately from the borders, and said in terms of cells.
+                // "Keeping the style of the table it replaces" is what the preview
+                // reported while it was shading every cell, and it is accurate enough
+                // to be read as a promise that nothing changed. A note that names what
+                // is being copied onto what can at least be disagreed with.
+                notes.push(byIndex
+                    ? 'each cell keeps the styling of the cell it replaces, in order'
+                    : 'every cell takes the styling most of the replaced cells carried, ' +
+                        'because the replacement has a different number of them');
+            }
         }
         if (carried)
             notes.push('the borders of the table it replaces');

package/dist/server.js

@@ -176,7 +176,7 @@ const renderChangedSections = (chosen, notebook, since) => {
  * the only way OneNote allows a cell to change.
  */
 const INDEX_ENTRIES = 12;
-const serverVersion = '2.3.0'; // x-release-please-version
+const serverVersion = '2.3.1-staging.114'; // 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 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@manudota/artist-mcp",
-  "version": "2.3.0",
+  "version": "2.3.1-staging.114",
   "description": "MCP server that reads your OneNote notes in Claude Desktop or Codex, with optional Gmail and Calendar as supporting evidence. Signs in on your own machine; writes are opt-in per install.",
   "keywords": [
     "mcp",