Integrate Project Genie simulation via PM2

[Igor Holt (igor-holt)]

Integrates the simulated "Project Genie" live and continuous building of Yennefer into the PM2 ecosystem configuration. This is achieved by running the genesis.cjs script in a continuous loop with forced mutations enabled. In addition, hardcoded absolute paths in ecosystem.config.cjs were replaced with relative paths to ensure portability across different deployment environments.

---

PR created automatically by Jules for task 13198259164414231020 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	0849868	Commit Preview URL Branch Preview URL	Apr 09 2026, 07:40 AM

[gemini-code-assist]

Code Review

This pull request updates the ecosystem.config.cjs file by changing several script paths from absolute paths to relative paths. It also adds a new service configuration for 'project-genie'. The review comments consistently suggest that using direct relative paths can be fragile and recommend using Node.js's path module to construct absolute paths for better robustness.

[gemini-code-assist]

Using a relative path here can be fragile, as it depends on the directory where the pm2 command is executed. For better robustness, it's recommended to construct an absolute path relative to this config file using Node.js's path module.

This suggestion uses an inline require for convenience. A cleaner approach would be to add const path = require('path'); at the top of the file and then use path.resolve(...) here.

      script: require('path').resolve(__dirname, 'genesis-q-mem/qmcp_admin_panel.py'),

[gemini-code-assist]

Using a relative path here can be fragile, as it depends on the directory where the pm2 command is executed. For better robustness, it's recommended to construct an absolute path relative to this config file using Node.js's path module.

This suggestion uses an inline require for convenience. A cleaner approach would be to add const path = require('path'); at the top of the file and then use path.resolve(...) here.

      script: require('path').resolve(__dirname, 'genesis-q-mem/qmcp_diamond_watchdog.py'),

[gemini-code-assist]

Using a relative path here can be fragile, as it depends on the directory where the pm2 command is executed. For better robustness, it's recommended to construct an absolute path relative to this config file using Node.js's path module.

This suggestion uses an inline require for convenience. A cleaner approach would be to add const path = require('path'); at the top of the file and then use path.resolve(...) here.

      script: require('path').resolve(__dirname, 'genesis-q-mem/a2a_handoff_server.py'),

[gemini-code-assist]

Using a relative path here can be fragile, as it depends on the directory where the pm2 command is executed. For better robustness, it's recommended to construct an absolute path relative to this config file using Node.js's path module.

This suggestion uses an inline require for convenience. A cleaner approach would be to add const path = require('path'); at the top of the file and then use path.resolve(...) here.

      script: require('path').resolve(__dirname, 'scripts/qmcp_genesis_bridge.cjs'),

[gemini-code-assist]

Using a relative path here can be fragile, as it depends on the directory where the pm2 command is executed. For better robustness, it's recommended to construct an absolute path relative to this config file using Node.js's path module.

This suggestion uses an inline require for convenience. A cleaner approach would be to add const path = require('path'); at the top of the file and then use path.resolve(...) here.

      script: require('path').resolve(__dirname, 'scripts/eth_optimism_bridge.cjs'),

[gemini-code-assist]

Using a relative path here can be fragile, as it depends on the directory where the pm2 command is executed. For better robustness, it's recommended to construct an absolute path relative to this config file using Node.js's path module.

This suggestion uses an inline require for convenience. A cleaner approach would be to add const path = require('path'); at the top of the file and then use path.resolve(...) here.

      script: require('path').resolve(__dirname, 'scripts/genesis_deployer.cjs'),

[gemini-code-assist]

Using a relative path here can be fragile, as it depends on the directory where the pm2 command is executed. For better robustness, it's recommended to construct an absolute path relative to this config file using Node.js's path module.

This suggestion uses an inline require for convenience. A cleaner approach would be to add const path = require('path'); at the top of the file and then use path.resolve(...) here.

      script: require('path').resolve(__dirname, 'genesis-q-mem/qmcp_qflop_miner.py'),

[gemini-code-assist]

Using a relative path here can be fragile, as it depends on the directory where the pm2 command is executed. For better robustness, it's recommended to construct an absolute path relative to this config file using Node.js's path module.

This suggestion uses an inline require for convenience. A cleaner approach would be to add const path = require('path'); at the top of the file and then use path.resolve(...) here.

      script: require('path').resolve(__dirname, 'scripts/process_guardian.cjs'),

[gemini-code-assist]

Using a relative path here can be fragile, as it depends on the directory where the pm2 command is executed. For better robustness, it's recommended to construct an absolute path relative to this config file using Node.js's path module.

This suggestion uses an inline require for convenience. A cleaner approach would be to add const path = require('path'); at the top of the file and then use path.resolve(...) here.

      script: require('path').resolve(__dirname, 'scripts/genesis.cjs'),