Integrate Project Genie Continuous Building

[Igor Holt (igor-holt)]

Integrates the simulated "Project Genie" continuous building capability by adding the project-genie process configuration into the main ecosystem.config.cjs file, allowing it to start automatically alongside the core services. Note: Google's Project Genie is an early research prototype without a public API; this integration leverages the local simulation present in scripts/genesis.cjs as designed by the current repository architecture.

---

PR created automatically by Jules for task 17953597322462118363 started by Igor Holt (@igor-holt)

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	yennefer	fce1ece	Commit Preview URL Branch Preview URL	Apr 03 2026, 07:38 AM

[genesis-code-assist]

Code Review

This pull request adds a new PM2 process configuration for 'project-genie' to the ecosystem configuration file. The feedback suggests increasing the memory limit for this process from 300M to at least 512M to prevent potential crash loops during memory-intensive operations.

[genesis-code-assist]

The memory limit of 300M is relatively low for a process performing 'continuous building' tasks. Node.js build processes (even simulated ones) often require significant heap memory for operations like file processing or AST manipulation. If the process exceeds this limit, PM2 will restart it, which could lead to a crash loop and instability. Consider increasing this to 512M or 1G to provide more headroom.

      max_memory_restart: '512M',

[gemini-code-assist]

Code Review

This pull request adds a new PM2 process configuration for 'project-genie' to the ecosystem configuration. Feedback suggests increasing the memory limit from 300M to 1G to prevent unexpected restarts during resource-intensive tasks and adding the 'COMPUTE_MODE' environment variable to maintain consistency with other services in the stack.

[gemini-code-assist]

The memory limit of 300M is quite restrictive for a process described as performing "continuous building". Node.js build toolchains and complex simulations can easily exceed this threshold, which would cause PM2 to restart the process unexpectedly. Increasing this to 1G (or at least 512M) would provide better stability for these types of workloads.

      max_memory_restart: '1G',

[gemini-code-assist]

To maintain consistency with the core services defined in this configuration (see line 107), the COMPUTE_MODE environment variable should be included. Since this is a "local simulation", setting it to local ensures that the project-genie process operates within the same environment context as the rest of the application stack.

      env: {
        COMPUTE_MODE: 'local',
        GENESIS_LOOP: 'true',
        FORCE_MUTATION: 'true',
        ALWAYS_ON: 'true'
      }