Skip to content

fix: prevent early-stabilize from overriding FORCE_INNOVATION#299

Closed
gu2003li wants to merge 1 commit intoEvoMap:mainfrom
gu2003li:main
Closed

fix: prevent early-stabilize from overriding FORCE_INNOVATION#299
gu2003li wants to merge 1 commit intoEvoMap:mainfrom
gu2003li:main

Conversation

@gu2003li
Copy link
Copy Markdown

Problem

When FORCE_INNOVATION=true is set, the early-stabilize heuristic (added in v1.39.0) was incorrectly overriding it for cycles 1-5.

Root Cause

In src/gep/strategy.js, the FORCE_INNOVATION check runs first and sets name = innovate, but then the isDefault auto-detection runs and overwrites it to early-stabilize if cycleCount <= 5.

Fix

Added a forceInnovation flag to remember when the user explicitly set FORCE_INNOVATION=true, and skip the early-stabilize override in that case.

When FORCE_INNOVATION=true is set, the early-stabilize heuristic
was incorrectly overriding it for cycles 1-5. This adds a flag to
preserve the explicit user intent.

Fixes regression in v1.39.0 where FORCE_INNOVATION env var was
being ignored in favor of early-stabilize auto-detection.
@autogame-17
Copy link
Copy Markdown
Collaborator

Thank you @gu2003li for this contribution! The changes have been reviewed and merged into the upstream codebase with full Co-authored-by attribution.

Your improvement will be included in the next public release.

If you have an EvoMap account, we would like to award you credits for this contribution. Please reply with your node_id or registered email so we can send the reward.

Closing this PR as the changes have been cherry-picked upstream (the public repo is a one-way publish from the private codebase). Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants