BUG: Neos 9.0.x: Sitekickstarter generates SitePackage without required Neos.Demo reference

[labre-rdc]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The SiteKickstarter package seems to generate a SitePackage, which does miss a reference to Neos.Demo, since adding any NodeType leads to a rendering failure when following the (slightly outdated) install Docs and figuring out the valid install steps.

The error message is: The Fusion object "Neos.Demo:Content.Headline" cannot be rendered: Most likely… (full stacktrace at the end)

Expected Behavior

The NodeTypes should be rendered correctly.

Steps To Reproduce

I reproduced this in two environments, each with a Docker setup (see below).

1. Follow the install steps until just before the Neos site step.
2. ./flow site:kickstart Vendor.Testing
3. ./flow site:create vendor-testing Vendor.Testing Vendor.Testing:Document.Homepage (outdated in Docs)
4. Login to 127.0.0.1:8081/neos
5. Add a NodeType (i.e. Headline) within the default (main) Content Collection.
6. Results in the attached stacktrace.
   202509261400137d60af.txt

Environment

As outlined, this happens in two environments:

Environment 1:
Debian 12 Server with Caddy reverse proxy
- Flow:9.0.3
- Neos:9.0.6
- PHP:8.2

Environment 2:
Windows Local install with Docker Desktop on WSL2
- Flow:9.0.3
- Neos:9.0.6
- PHP:8.4

Anything else?

For reference I attach the Windows Docker files. The Debian environment is more complex due to the reverse proxy setup:

docker-compose.yml
Dockerfile.txt