chore: give agents a language server and a type check they can read - #62
Merged
Conversation
basedpyright is wired up as a checked-in plugin, so a clone gets code navigation instead of grepping for a name and hoping it is unique. Its config carries the import roots every stacklet bootstraps at runtime, without which most of the tree reads as unresolved. The tree is not clean and is not meant to be a gate, so CONTRIBUTING and the engineer guide cover reading it: a baseline for agents without LSP tools, so they see the error they just wrote rather than the couple of hundred already there.
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.
Wires up basedpyright as a checked-in plugin, so a clone gets code navigation instead of grepping for a name and hoping it is unique. The config carries the import roots each stacklet bootstraps at runtime, without which most of the tree reads as unresolved.
The tree is not clean and this is not a gate. CONTRIBUTING and the engineer guide cover reading it, including a baseline for agents without LSP tools so they see the error they just wrote rather than the couple of hundred already there.
testsis analysed but silenced viaignore, which is what lets find-references reach test callers without their fixture noise burying the findings about shipped code.