Fix scoped TS/JS call evidence and release Context 0.3.3 - #17
Merged
Merged
Conversation
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.
TS/JS scanning could link a shadowed call such as
invoke(target) { target() }to an unrelated file-level function. Version 0.3.3 resolves supported direct calls through scoped compiler bindings over selected source trees, excludes nested-callable attribution, rejects type-only/ambiguous exports and distinguishes same-named static/instance methods. The compiler host cannot load extra files or configuration; analysis makes no model calls.The release also records the deterministic language roadmap, OpenCode qualification and better-developer-outcome gates. Matching core/tools versions, notices and installation examples are updated. Full project resolution and default-export expression assignments remain unsupported.
Validation: 420 tests, independent installed-package smoke, both unchanged benchmark gates (required-source recall 1.0), navigation stdio smoke, 22 scale tests and the 10k postings correctness probe. Independent implementation review findings were repaired and rechecked; local Markdown links and diff checks pass.
Ship matching GitHub tarballs and checksums after CI/merge. npm authentication currently returns HTTP 401, so registry publication remains blocked. No new client/consumer acceptance or measured subscription/cash saving is claimed.