Merge upstream NVIDIA/SkillSpector v2.3.11 (up to c2d09df)#269
Closed
will-exaforce wants to merge 18 commits into
Closed
Merge upstream NVIDIA/SkillSpector v2.3.11 (up to c2d09df)#269will-exaforce wants to merge 18 commits into
will-exaforce wants to merge 18 commits into
Conversation
Sync upstream OSS release snapshots into main
Standalone uv project that runs SkillSpector over a labeled corpus, persists scan results to DuckDB, and ships SQL queries for metrics (recall, false positives/negatives, threshold sweeps, timing).
feat(benchmark): add SkillSpector benchmark harness
Sync upstream NVIDIA/SkillSpector (2.2.3 → 2.3.7)
…tten. This is to improve llm request/response time and reduce timeout frequency.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Pruning moves to the fork-only exaforce runtime patch (subsequent tasks).
Runtime now matches PR #8. The two reverted upstream test files assert the un-pruned schema and fail by design (see docs/superpowers/EXPECTED_TEST_FAILURES.md).
These were process/design docs, not product deliverables. The functional EXPECTED_TEST_FAILURES.md is kept (referenced by the PR description).
refactor(exaforce): isolate schema pruning as runtime monkeypatch
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.
Summary
4cf0cb9 chore(release): bump version to 2.3.11), stopping at merge commitc2d09dfas requested.--no-ffmerge (fa7d15d), matching the prior sync pattern (d3fac00).Details
pyproject.tomlversion now reads2.3.11.contrib/multilingual/batch scanner (PR feat: add multilingual batch scanner with parallel execution and LLM gap-fill #100), plus doc reorganization, SPDX headers, and Windows/CJK stdout fixes.c2d09df; the 6 upstream commits after it (PRs docs: correct MCP fixture expectations #262, fix(mcp): prove stdio initialize compatibility (#199) #248, Improve batch scan visibility: add README usage guide and rename contrib/multilingual → contrib/batch_scan #258, …) are not included.benchmark/WIP (report module + generated artifacts) is stashed locally and intentionally excluded from this PR. Untracked.claude/anddocs/superpowers/artifacts are likewise excluded, consistent with5c17e2a.Warning
Verification gap: the ExaForce schema-pruning monkeypatch (
e6ac14c,a2f6d97) targets upstream LLM/prompt code that this sync touched. The merge was textually clean but the patch's compatibility against the new upstream was not run locally. Please rely on CI + review, or run the exaforce pruning tests (cb631d8) before merging.