feat: log enabled experimental flags#357
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 14149ff The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue
No linked issue; this change addresses the need to make active experimental flags visible in startup diagnostics.
Problem
Experimental flags are resolved from environment variables at process startup, but the diagnostic log did not provide a single summary of which flags were enabled. That made feature-gated behavior harder to confirm from logs.
What changed
Added resolver helpers to expose the full flag snapshot and enabled flag ids, reused that snapshot for the existing RPC response, and logged one
experimental flags enabledentry during core startup when at least one flag is active. The existingKIMI_CODE_EXPERIMENTAL_FLAGmaster switch remains the only all-flags environment variable.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.