Product content check as page content (vitec_productcheck)

The product audit of public/product-check/ becomes data for the React frontend: new content element vitec_productcheck (plugin registration, wizard entry, TypoScript USER func) delivers under content.productcheck either the overview (every product with one {ok,count} check per field - hero, photos, og, video, teaser, subtitle, description, description2, highlights, capabilities, applications, features incl. icon count, resources, datasheets, solutions - plus per-field summary) or, with ?check=<uid>, the detail of one product (texts as stored HTML, images with original URL and 480px thumbnail, videos, feature cards with icons, resources, datasheets, solutions). ProductCheckService ports the PDO queries of the standalone page to Doctrine; the renderer is always USER_INT so the audit is never served from the page cache; check is excluded from the cHash. Migration adds the element to page 607 (/products/product-check). The standalone page stays untouched. Verified on DEV: overview 85 products in 0.13 s warm, detail 0.2-0.9 s, thumbnails resolve.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

packages/vitec/Configuration/Sets/Vitecset/setup.typoscript

@@ -100,6 +100,20 @@ tt_content {
         }
     }
 
+    # Product Content Check - the product audit table as data (page
+    # /products/product-check). Always USER_INT, see ProductCheckJsonRenderer.
+    vitec_productcheck < lib.contentElementWithHeader
+    vitec_productcheck {
+        fields {
+            content {
+                fields {
+                    productcheck = USER
+                    productcheck.userFunc = Evomedien\Vitec\UserFunc\ProductCheckJsonRenderer->render
+                }
+            }
+        }
+    }
+
     # EXT:solr search results as JSON - the search endpoint for the React frontend
     solr_pi_results < lib.contentElementWithHeader
     solr_pi_results {