feat(demo): the seed data ships with the extension, and screenshots need no ddev

Three things were tangled together, and untangling them is what this is.

THE SEED WAS TIED TO ONE LOCAL TOOL. It lived under .ddev/ as two MySQL dumps
plus a raw-PDO script hard-wired to host `db`, database `v14` and root/root.
Nothing else could use it: not the functional suite, which runs on SQLite, and
not a documentation screenshot run, which needs the same rows to exist
somewhere it can serve TYPO3 from. The data now lives in
Resources/Private/Demo/DemoData.php and `nrllm:demo:seed` writes it through the
ConnectionPool, so the DBMS is whatever the instance uses.

Relations are named by IDENTIFIER. The SQL resolved them through MySQL session
variables that looked up "whatever is default right now", so the graph depended
on insert order and on flags it did not set itself.

THE NUMBERS ARE REAL AND REPRODUCIBLE. Every value in the usage history is
derived from (seed, day, model) rather than drawn from a seeded global stream.
Two things break the global stream and both did: a value depends on how many
numbers were drawn before it, so the history changes when iteration order does
— and PHP-CS-Fixer rewrites mt_srand/mt_rand to srand/random_int, which is
cryptographically seeded and ignores the seed entirely. The reproducible
history would have been silently un-reproducible from the first `-s cgl` run.
Verified by checksum: cgl now leaves the file byte-identical.

The demo graph also gained a priced stream. The local Ollama models are free,
so every cost surface read $0.00 — the functional test caught exactly that, and
`cost_input`/`cost_output` are CENTS per 1M tokens, which the first formula had
wrong by five orders of magnitude.

SCREENSHOTS NO LONGER NEED DDEV, AND NO LONGER SHOW THE MENU.
Build/Scripts/screenshots.sh installs TYPO3 on SQLite, seeds it, serves it with
PHP's built-in server and drives Playwright at it. Every piece already existed;
the only local answer to "a running TYPO3" was E2E_BASE_URL pointing at a ddev
site, which is why taking a screenshot needed a tool meant for humans.

screenshots.spec.ts captures the module IFRAME, not the window. TYPO3 v14
renders module content in an iframe, so that element IS the module without the
menu. This is not cosmetic: all sixteen full-window PNGs went stale the day the
modules moved into the AI section, because each showed `Administration > LLM`
in the sidebar. A module-only shot cannot go stale that way.

Five things had to be fixed to make that pipeline run, each found by a failure
that named something else:

  - a router script, because handing index.php to `php -S` makes it the router
    for /_assets/* too and the backend renders with no stylesheet at all
  - trustedHostsPattern, because the container reaches the server by a name the
    install never saw and TYPO3 answers 500, which reads as "server not up"
  - loginRateLimit off and a fresh database each run, because eight logins from
    one address plus one early wrong password locks the rest out with a 403
  - PHP_CLI_SERVER_WORKERS, because the built-in server is single-threaded and
    parallel browser workers queue until the navigation times out
  - --workers=1, for the same reason

One upstream bug is worked around rather than fixed here:
netresearch/typo3-ci-workflows v1.6.0 uses ${IMAGE_PLAYWRIGHT} at line 715 and
assigns it nowhere, while every sibling IMAGE_* is set around line 540 — so
`-s e2e` feeds docker an empty image and dies with "invalid reference format".
It can never have started a container. screenshots.sh supplies the image,
pinned to the version package-lock.json resolves because the image ships
matching browsers. Reported separately.

Tests: Tests/Functional/Command/SeedDemoDataCommandTest.php, 5 tests / 23
assertions, on SQLite — which is itself the evidence that the seed left ddev.
It asserts the counts against the shipped data rather than repeating them, that
every relation resolves to a real uid, that a second run updates rather than
duplicates, and that the same --days produces identical totals twice.

Gates: unit 7318 / 24770, functional (sqlite) for the new class, cgl, phpstan
level 10 — all green on PHP 8.4. The screenshot pipeline ran end to end: 8
passed, all eight PNGs rewritten. Rector NOT run: pinned to 8.2, this .Build is
resolved at 8.4, platform_check fatals. CI covers it.

Assisted-by: claude-code:claude-opus-5
Agent-Session: https://claude.ai/code/session_01MNg1MysJVugv1xo2husknU
Agent-Host: 0493f0
Signed-off-by: Sebastian Mendel <sebastian.mendel@netresearch.de>

Author: CybotTM

.ddev/AGENTS.md

@@ -43,13 +43,12 @@ ddev describe   # print URLs and credentials
 | Task | Command |
 |------|---------|
 | Full setup (TYPO3 v14 + extension) | `ddev install-v14` (also `install-v13`, `install-all`, `setup`) |
-| Seed provider/model/config demo data | `ddev seed-ollama` |
-| Seed task demo data | `ddev seed-tasks` (also `seed-usage`; SQL in `.ddev/sql/`) |
+| Seed the demo graph and usage history | `ddev seed-demo [days]` |
 | Ollama status / models | `ddev ollama` |
 | Render RST docs | `ddev docs` |
 
 ### Demo data for screenshots and manual testing
-`ddev seed-ollama` creates 1 provider (Local Ollama), 3 models and 4 configurations; `ddev seed-tasks` creates 13 tasks across 4 categories. `ddev install-v14` auto-runs seed-ollama but NOT seed-tasks — run both before documentation screenshots so populated views are visible.
+`ddev seed-demo` delegates to the extension's own `nrllm:demo:seed`. The data lives in `Resources/Private/Demo/DemoData.php` and ships with the extension, so the functional suite and a screenshot run seed the same rows — the two MySQL dumps and the raw-PDO script that used to live under `.ddev/` could only ever reach ddev. `ddev install-v14` runs it, so a fresh install already has populated views.
 <!-- AGENTS-GENERATED:END commands -->
 
 <!-- AGENTS-GENERATED:START patterns -->

.ddev/commands/host/seed-demo

@@ -0,0 +1,14 @@
+#!/bin/bash
+## Description: Seed the demo record graph and usage history (delegates to nrllm:demo:seed)
+## Usage: seed-demo [days]
+## Example: ddev seed-demo
+## Example: ddev seed-demo 30
+
+# A wrapper, not an implementation. The seed used to live here as two MySQL
+# dumps plus a raw-PDO script hard-wired to host `db`, database `v14` and
+# root/root — which is why nothing but ddev could use it. It now ships with the
+# extension in Resources/Private/Demo/ and runs through the ConnectionPool, so
+# the functional suite and a screenshot run reach the same rows.
+DAYS="${1:-90}"
+
+ddev exec ./.Build/bin/typo3 nrllm:demo:seed --days="${DAYS}"

.ddev/commands/host/seed-ollama

@@ -95,14 +95,10 @@ vendor/bin/typo3 styleguide:generate || echo "Styleguide generation skipped"
 # Flush caches
 vendor/bin/typo3 cache:flush
 
-# Import Ollama seed data (provider, models, configurations)
-echo "Importing Ollama LLM seed data..."
-SQL_FILE="/var/www/nr_llm/.ddev/sql/seed-ollama.sql"
-if [ -f "$SQL_FILE" ]; then
-    mysql -h db -u root -proot "$VERSION" < "$SQL_FILE" && echo "   Seed data imported" || echo "   Seed import skipped"
-else
-    echo "   Seed file not found, skipping"
-fi
+# Seed the demo graph. Ships with the extension now, so this is the same
+# command the functional suite and a screenshot run use.
+echo "Seeding demo data..."
+./.Build/bin/typo3 nrllm:demo:seed --days=90 && echo "   Demo data seeded" || echo "   Seeding failed"
 
 echo ""
 echo "TYPO3 $VERSION installation complete!"

.ddev/commands/host/seed-tasks

@@ -96,14 +96,10 @@ vendor/bin/typo3 styleguide:generate || echo "⚠️ Styleguide generation skipp
 # Flush caches
 vendor/bin/typo3 cache:flush
 
-# Import Ollama seed data (provider, models, configurations)
-echo "🤖 Importing Ollama LLM seed data..."
-SQL_FILE="/var/www/nr_llm/.ddev/sql/seed-ollama.sql"
-if [ -f "$SQL_FILE" ]; then
-    mysql -h db -u root -proot "$VERSION" < "$SQL_FILE" && echo "   ✅ Seed data imported" || echo "   ⚠️ Seed import skipped"
-else
-    echo "   ⚠️ Seed file not found, skipping"
-fi
+# Seed the demo graph. Ships with the extension now, so this is the same
+# command the functional suite and a screenshot run use.
+echo "🤖 Seeding demo data..."
+./.Build/bin/typo3 nrllm:demo:seed --days=90 && echo "   ✅ Demo data seeded" || echo "   ⚠️ Seeding failed"
 
 echo ""
 echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"