Repository navigation
chore: resolve project check decisions - #375
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
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.
Canonical mise task references now dispatch aggregate tests and tooling uses
test:python:integration --project tools/python. Shared wheel/contracts preparation and one Rust archive extraction finish before concurrent consumers start. A repository-scoped native mise task lock preserves the ordinary one-task default for standalone commands. Every real lane exit is retained; final collection fails for failed or missing results.Keep the criterion evidence and GUI testing namespaces through their deliberate barrel policy. Move both artifact scratch ownership stories and license-file containment to integration tests through existing public entry points, preserving every assertion. Remove the unused unit-build include of shared I/O support. The report comparison retains byte and decode assertions without ad hoc timing; existing system report benchmarks own saved-report measurements. README product claims are unchanged; contributor task documentation is updated.
The 178 private-access lines remain explicitly unresolved under the instruction to leave changes needing a public contract that the findings file does not settle. No new testing facade, production visibility expansion, assertion weakening, deadline increase or suppression was introduced. No pending OpenSpec feature was started.
Validation at
9e541ec1629f2495a34d757344057db828d3cd70:mise run lint:rust: exit 0. Clippy reports an unreachable disallowed-method path fortokio::process::Command::new; no suppression was added.stkr project check: exit 1, 192 finding lines (195 total output lines).scan-diff.sh: exit 0,CLEAN.Compiler tasks use
CARGO_BUILD_JOBS=8; no allocation reduction was needed. No full product lanes or CI simulations ran. Hosted PR CI was started and was not awaited.Exact Remaining Project Check Output