fix(vscode): fix pipeline test and lint failures - #13534
Merged
Merged
Conversation
marius-kilocode
enabled auto-merge
August 28, 2026 08:55
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (4 files)
Reviewed by grok-4.6 · Input: 60K · Output: 6.5K · Cached: 308.5K Review guidance: REVIEW.md from base branch |
WebReflection
approved these changes
Aug 28, 2026
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.
What Problem This Solves
The VS Code pipeline failed because a Happy DOM fixture did not expose IntersectionObserver, and the session context exceeded the enforced ESLint file-size limit.
Why This Change Was Made
The activity fixture now exposes the browser API used by the mounted UI. The session context value type is moved to a dedicated type module, and the source contract test follows the type declaration.
User Impact
No production behavior changes. The VS Code unit-test and production build checks can complete successfully.
Evidence