slidemind 0.3.5 → 0.3.12

package/src/pptx/tags.mjs

@@ -670,7 +670,56 @@ export function computeProjection(files, slidePathOverride) {
       fill: paint.fill,
       line: paint.line,
       mediaSha256: parseMediaSha(files, slidePath, raw.xml),
+      // Always null here — see the CHART HASH note below. The FIELD is mirrored
+      // so both implementations serialize the same key set (the parity fixtures
+      // are byte-compared); the VALUE is the one thing this mirror cannot
+      // reproduce.
+      chart: null,
     });
   }
   return { v: 1, shapes };
 }
+
+// ---------------------------------------------------------------------------
+// CHART HASH — the one non-parity field, deliberately
+// ---------------------------------------------------------------------------
+//
+// The add-in's `ProjectionShape.chart` is sha256 over the CANONICAL ChartSpec of
+// a chart graphic frame (`native-charts`, task 7.4). It is a SPEC hash, never a
+// hash of the chart part's XML, and that is not a detail: PowerPoint
+// re-serializes a chart part on every save and materializes its own defaults
+// into it, so an XML hash would report drift on a deck nobody touched. Only
+// `canonicalize(spec)` is stable across that round trip.
+//
+// Producing it therefore needs the whole chart READER (`c:` + `cx:` families,
+// ~3k lines of DOM code) plus the canonicaliser. This file is regex-only and
+// `src/pptx/` is deliberately dependency-free — no DOM parser ships here — so a
+// hand-port would be a second source of truth for chart semantics that WILL
+// drift from the add-in's. It is not written, on purpose.
+//
+// What that costs, stated plainly: this mirror cannot tell that a chart's data
+// or styling changed. Everything else about the slide — geometry, text, fill,
+// line, media — still compares exactly. The consumers below therefore drop the
+// field from BOTH sides before comparing, so a chart can never produce a FALSE
+// "someone edited this" refusal; the price is that a chart-ONLY edit is
+// invisible to the CLI's guard (the add-in's own drift check, which does have
+// the reader, still catches it on the next push).
+//
+// Closing it properly means giving this repo the reader as a GENERATED artifact
+// built from the add-in's TypeScript — never a hand-written copy.
+
+/**
+ * A projection with every `chart` hash dropped, for comparing an add-in-written
+ * baseline against a projection computed HERE. Both sides go through it, so the
+ * comparison stays symmetric.
+ */
+export function withoutChartHashes(projection) {
+  if (!projection?.shapes) return projection;
+  return {
+    ...projection,
+    shapes: projection.shapes.map((shape) => {
+      const { chart: _unreadableHere, ...rest } = shape;
+      return rest;
+    }),
+  };
+}