Deepen GaugeGap into an eight-experiment science library

[slavazeph-coder]

What this adds

Expands the GaugeGap science arcade from four to eight genuinely different interactive systems.

New live experiments

5. Gravity Forge — launch planets into a Newtonian n-body sandbox, load solar/binary/slingshot presets, and score orbital stability.
6. Flock Mind — tune alignment/cohesion/separation and influence a Reynolds-boids flock as either predator or beacon.
7. Outbreak Zero — choose patient zero, spend a limited vaccine budget, and contain an SIR-style process on a contact graph.
8. Chaos Twins — race two near-identical double pendulums and measure when deterministic trajectories visibly diverge.

Product depth

• Eight distinct interaction verbs: tune, synchronize, explore, create, construct, influence, intervene and predict
• One mission and live score per new experiment
• Shareable URLs preserving experiment settings
• Model-underneath cards explaining the scientific mechanism
• New experiment cards and updated homepage positioning
• Responsive controls and canvas layouts
• Existing BrainSNN scanner, research workspace and first four labs remain intact

Validation requested

• TypeScript/noEmit
• deterministic tests
• production Vite/Express build
• MCP smoke test
• manual interaction pass for pointer/touch and responsive layouts

[gemini-code-assist]

Code Review

This pull request expands the GaugeGap science arcade from four to eight live experiments by adding four new interactive simulation labs: Gravity Forge (orbital mechanics), Flock Mind (collective intelligence), Outbreak Zero (network epidemiology), and Chaos Twins (deterministic chaos). It also introduces shared chrome components and utilities for these labs, along with corresponding styles. The review feedback highlights a critical coordinate-scaling issue present in the Flock Mind, Outbreak Zero, and Gravity Forge simulations. On smaller screens where the canvas is scaled down, raw pointer and click coordinates do not align with the internal simulation space, causing misaligned interactions. Actionable code suggestions are provided to scale these coordinates relative to the bounding rect dimensions.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

On screens where the canvas bounding rect is smaller than the minimum dimensions (320x360), the canvas is scaled down by the browser. However, the pointer coordinates are calculated using raw client coordinates relative to the bounding rect, which do not match the internal simulation coordinate space. This causes the pointer interaction to be misaligned with the visual elements on smaller screens.

To fix this, scale the pointer coordinates by the ratio of the simulation dimensions to the actual bounding rect dimensions.

    function pointer(event) {
      const rect = canvas.getBoundingClientRect();
      const x = (event.clientX - rect.left) * (width / (rect.width || 1));
      const y = (event.clientY - rect.top) * (height / (rect.height || 1));
      pointerRef.current = { x, y, active: true };
    }

[gemini-code-assist]

Similar to the flocking simulation, the click coordinates in the outbreak simulation are not scaled to the simulation coordinate space when the canvas bounding rect is smaller than the minimum dimensions (320x360). This makes it difficult or impossible to click nodes near the right or bottom edges on smaller screens.

Scale the click coordinates by the ratio of the simulation dimensions to the actual bounding rect dimensions to ensure accurate node selection.

Suggested change

	function onClick(event) {
	const rect = canvas.getBoundingClientRect();
	const x = event.clientX - rect.left;
	const y = event.clientY - rect.top;
	function onClick(event) {
	const rect = canvas.getBoundingClientRect();
	const x = (event.clientX - rect.left) * (width / (rect.width || 1));
	const y = (event.clientY - rect.top) * (height / (rect.height || 1));

[gemini-code-assist]

In the gravity simulation, the pointer coordinates used for launching planets are not scaled to the simulation coordinate space when the canvas bounding rect is smaller than the minimum dimensions (320x360). This causes planet launches to be misaligned and have incorrect velocities on smaller screens.

Scale the pointer coordinates by the ratio of the simulation dimensions to the actual bounding rect dimensions to ensure consistent launch behavior across all screen sizes.

    function pointerPosition(event) {
      const rect = canvas.getBoundingClientRect();
      return {
        x: (event.clientX - rect.left) * (width / (rect.width || 1)),
        y: (event.clientY - rect.top) * (height / (rect.height || 1)),
      };
    }

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4dfd2e41be

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve zero-valued flock controls from shared links

When a shared Flock Mind URL contains a valid zero for any slider that allows it, such as ?lab=flock&state=120,0,0,0,predator, these || fallbacks replace the shared values with the defaults. That means links copied from the minimum alignment/cohesion/separation settings do not reload the experiment state the sender actually shared; use nullish fallback so 0 survives parsing.

Useful? React with 👍 / 👎.