Repository navigation
fix(e2e): fill the Kimi Code Scope script path in installed guidance - #2090
Merged
hidb4ai merged 1 commit intoOct 20, 2026
Merged
Conversation
oceanbase#2043 added a __POWERCONTEXT_SCOPE_SCRIPT_JSON__ placeholder to the Kimi Code skill that setup replaces with the installed scope.mjs path. The ON arm's installer, added in oceanbase#2038, only filled the Scope placeholder, so its guidance kept the raw marker and no longer matched setup.
Contributor
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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
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.
Which issue or RFC does this PR close?
Fixes the
validate(harness-check) failure that now shows up on PRs touchinge2e/, for example #2035.Rationale for this change
#2043 added a
__POWERCONTEXT_SCOPE_SCRIPT_JSON__placeholder to the Kimi Code skill guidance, andpowercontext setup kimi-codenow replaces it with the installedscripts/scope.mjspath. The ON arm's plugin installer from #2038 replaces only__POWERCONTEXT_SCOPE_JSON__. That leaves the raw marker in the installed SKILL.md, sotest_kimi_code_on_arm_installs_the_plugin_as_setup_doesfails. The two PRs merged 14 minutes apart, and each one passed CI against a base that did not include the other.What changes are included in this PR?
harbor_kimi_code.CONFIGURE_PLUGINalso replaces__POWERCONTEXT_SCOPE_SCRIPT_JSON__with the JSON-encoded path ofscripts/scope.mjsin the installed plugin, the same way setup does.Are there any user-facing changes?
No. This only changes the e2e harness and its test.
How was this change tested?
uv run --project e2e/bub python -m pytest e2e/bub/tests(271 passed)uv run ruff check e2e/bubanduv run ruff format --check e2e/bubAI usage statement
Claude Code (Claude Opus 5.5) found the cause in the CI log and drafted the fix and this description. I reviewed both.