- 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/ext_tables.sql

@@ -58,6 +58,7 @@ CREATE TABLE tx_vitec_domain_model_product (
     capabilities text,
     portfolio varchar(1024) DEFAULT '' NOT NULL,
     textrelatedproducts text,
+    related_texts int(11) DEFAULT '0' NOT NULL,
     solutions int(11) DEFAULT '0' NOT NULL,
     resources int(11) DEFAULT '0' NOT NULL,
     datasheets int(11) DEFAULT '0' NOT NULL,
@@ -377,12 +378,24 @@ CREATE TABLE tx_vitec_seo_research (
 -- (relation later removed) are simply never joined. No TCA on purpose -
 -- written by the product-text import module, read by ProductShowJsonRenderer.
 --
+#
+# Since 2026-09-28 a real TCA table (inline on the product, field
+# related_texts). Existing installations MUST run
+# migrations/rebuild_related_text_table.php BEFORE extension:setup -
+# MySQL cannot grow the auto_increment uid onto the old composite-key
+# table through the schema compare.
+#
 CREATE TABLE tx_vitec_product_related_text (
+    uid int(11) NOT NULL auto_increment,
+    pid int(11) DEFAULT '0' NOT NULL,
     product_uid int(11) DEFAULT '0' NOT NULL,
     related_uid int(11) DEFAULT '0' NOT NULL,
+    sorting int(11) DEFAULT '0' NOT NULL,
     cardtext text,
     tstamp int(11) DEFAULT '0' NOT NULL,
-    PRIMARY KEY (product_uid, related_uid)
+    crdate int(11) DEFAULT '0' NOT NULL,
+    PRIMARY KEY (uid),
+    UNIQUE KEY pair (product_uid, related_uid)
 );
 
 --