Megamenu: rail display for page trees, cache tags, editorial promo boxes

- Page-tree entries get a "Page tree display" field (columns | rail |
  rail-compact), emitted as display + cardSize: Markets and Solutions
  show their main pages as a list and the sub-pages as image cards on
  hover. Page-tree items carry image (page media) and teaser (abstract)
  from stage 2. Additive; front ends ignoring display render columns.
- vitec:attach-page-media gains --depth=2 and falls back to the page's
  hero background before the grey placeholder; the 39 sub-solution
  pages got their hero image as page media.
- MegamenuJsonRenderer tags every page carrying the menu with the menu
  tables and tt_content_<uid>, so saving menu records refreshes all
  pages instead of waiting for a full flush.
- Products catalog: drop catalog.news; both promo boxes ("Product
  highlight", "Product news") are the entry's editorial teaser cards.
  ProvideInsightsSpotlight back to its previous state.
- Spec v1.29 and v1.30 (header version corrected), README.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

packages/evo_megamenu_json/README.md

@@ -125,7 +125,15 @@ page, its children as the items. Hidden or nav-hidden pages leave the menu
 with the next cache flush. Curated columns are ignored; teasers and the
 featured slot stay editorial. From stage 2 a child page with media gets its
 first image as `image` on the column - attach images in the page
-properties and the panel turns visual by itself.
+properties and the panel turns visual by itself. From stage 2 the items
+carry `image` (first page media or `null`) and, when set, the page
+`abstract` as `teaser`.
+
+The entry field *Page tree display* picks the presentation and travels as
+`display`: `columns` (default, columns side by side) or `rail` (the columns
+as a list on the left, the hovered column's items as image cards on the
+right) plus `cardSize` (`regular` | `compact`) for `rail`. A front end that
+ignores `display` keeps rendering columns.
 
 ### Layout `spotlight`
 
@@ -163,5 +171,9 @@ The VITEC site package ships `ProvideInsightsSpotlight`, which supplies
   entry.
 * The renderer never throws: a broken menu returns an empty value rather than
   taking the page payload down.
+* Caching: every page carrying the menu is tagged with the menu tables and
+  `tt_content_<uid>` of the menu element, so saving any menu record refreshes
+  all of them. Panels built from the page tree (`pagetree`, `catalog`,
+  `spotlight`) pick up page changes with the next cache flush.
 * Without `friendsoftypo3/headless` the element has no JSON envelope to render
   into — the extension is built for headless installations.