fix(tools): handle Windows drive paths in FS and Writer - #1325
Open
Yuang-Deng wants to merge 1 commit into
Open
Yuang-Deng wants to merge 1 commit into
Yuang-Deng wants to merge 1 commit into
Conversation
Yuang-Deng
requested a deployment
to
protected
September 17, 2026 12:11 — with 
GitHub Actions
Waiting
GitHub Actions
Waiting
This branch is waiting to be deployed
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.
Windows drive paths such as
C:/skills/visible/SKILL.mdwere interpreted as filesystem protocols, preventing skill discovery through FS. Writer image collection also rejected native Windows absolute paths as unsupported URI schemes.Treat drive paths as local in FS routing and accept native absolute image paths in Writer. Existing cloud protocol and HTTP(S) behavior is preserved.
Validation: 8 FS routing and Writer multimodal tests passed in the existing Linux container; LazyMind's related algorithm suite passed (3052 tests). Native Windows validation will run with LazyMind PR #710.