- New extension fe_comment (Evomedien, framework-agnostic): floating page

feedback widget served from /api/fe-comment/widget.js, note pad in
  localStorage, submissions mailed via /api/fe-comment/submit with
  recipients from the extension configuration; classic sites get the
  script injected via AssetCollector when the jsonOutput setting is off.
  An enabled master switch serves the widget EMPTY when off (no 404, no
  console errors) and rejects submissions - the go-live kill switch, no
  front-end build change needed
- URL swap finished: /_json prefix middleware, SPA fallback live with a
  dedicated root rule (REQUEST_FILENAME of / is a directory) and a
  query-string exception for the TYPO3 v14 install tool entry
  (?__typo3_install on the site root - the backend Settings/Environment
  modules depend on it); /api/ as a whole stays with TYPO3
- MailMessage::send() no longer exists in v14: fe_comment and the form
  EmailDelivery (latently broken since the core upgrade) now send through
  the Mailer service. Mail transport moved to SMTP against the local exim
  so delivery errors surface instead of bouncing into the blackhole -
  exim verifies the envelope sender, which therefore must be a routable
  existing address (transport config lives in the untracked settings.php)
- Related-product card texts editable on the product record (table rebuilt
  with uid/pid, TCA + inline field, one-time migration script); shared
  RteCompare for the module badge and the CLI comparison - batch dry-run
  now reports 0 writes instead of flagging every richtext field
- Workbook clarification cases executed: VisionIO-SD14, VisionSC-SD14 and
  both Diamond OG records imported (40 fields, live-verified); ArtioSign
  and ArtioView created hidden (uid 109/110) via
  create_artio_records.php - the product table has no sorting column;
  WallControl_10 mapping REVERTED and parked: the dry run revealed
  aetria-wallcontrol already carries its own agency workbook, which
  WallControl_10 would have overwritten. Manifest now 75 product /
  24 family / 1 open

packages/vitec/Classes/Service/RteCompare.php

@@ -0,0 +1,45 @@
+<?php
+
+declare(strict_types=1);
+
+namespace Evomedien\Vitec\Service;
+
+/**
+ * Equality check tolerant of TYPO3's RTE storage transform - THE shared
+ * comparator for "does the workbook differ from the database?", used by the
+ * import module's "differs" badge and the CLI's write/unchanged decision.
+ * One implementation on purpose: the two used to disagree, and the stricter
+ * one cried wolf on every richtext field.
+ *
+ * What the transform changes on save, and what is neutralized here:
+ *   - bare content gets wrapped in <p>...</p>       -> wrap simulation
+ *   - newlines are stripped, whitespace collapses    -> \s+ collapse
+ *   - whitespace BETWEEN tags is dropped
+ *     ("</p> <ul>" becomes "</p><ul>")               -> >\s+< join
+ *   - entities may be re-encoded ("&times;" vs "×")  -> entity decode
+ *
+ * Anything beyond that (real markup changes) still counts as different.
+ * The Phase-2 change watch compares workbook against imported_values instead
+ * of the database precisely because storage transforms exist - this class
+ * only keeps the LIVE comparison honest.
+ */
+final class RteCompare
+{
+    public static function equal(string $stored, string $incoming): bool
+    {
+        $storedNorm = self::normalize($stored);
+        if ($storedNorm === self::normalize($incoming)) {
+            return true;
+        }
+
+        return $storedNorm === self::normalize('<p>' . $incoming . '</p>');
+    }
+
+    private static function normalize(string $html): string
+    {
+        $s = html_entity_decode($html, ENT_QUOTES | ENT_HTML5, 'UTF-8');
+        $s = (string)preg_replace('/\s+/u', ' ', $s);
+        $s = (string)preg_replace('/>\s+</', '><', $s);
+        return trim($s);
+    }
+}