Runner: Analyse-Skript und Datenschutz-Zusatzseite einsetzen

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

runner/src/jobs.js

@@ -7,6 +7,7 @@ import { join, dirname, sep } from 'node:path';
 import { buildRunArgs } from './docker.js';
 import { detectFromDir } from './detect.js';
 import { readMemAvailable } from './server.js';
+import { injectAnalytics } from './analytics-inject.js';
 
 const LOG_LINES = 300;
 const MAX_LINE = 2000;
@@ -254,6 +255,8 @@ export function createJobs({ config, docker, fs: fsOver = {}, git, mem = readMem
       await fs.mkdir(config.previewsRoot, { recursive: true });
       await fs.copyTree(fs, srcDir, fresh, { skipGit, skipNodeModules });
       await ensureIndexHtml(fs, fresh, job.displayName || job.sub, onLine);
+      // Analyse (optional): auf dem .new-Ordner vor dem Tausch; Fehler brechen die Veröffentlichung ab, die alte Preview bleibt (V4).
+      if (job.analytics) await injectAnalytics(fresh, job.analytics, { baseUrl: config.analyticsPublicBase || 'https://project.webklar.com/a/', onLine, fs });
       try { await fs.rename(target, old); } catch (e) { if (e.code !== 'ENOENT') throw e; hadOld = false; }
       try { await fs.rename(fresh, target); } catch (e) {
         if (hadOld) await fs.rename(old, target).catch((e2) => onLine?.(`Rollback fehlgeschlagen: ${e2.message}`));