mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-08-23 23:55:50 +00:00
3a1f86d805
Some checks are pending
E2E Tests / E2E Test (Linux) - sandbox:docker - shard 1/3 (push) Waiting to run
E2E Tests / E2E Test (Linux) - sandbox:docker - shard 2/3 (push) Waiting to run
E2E Tests / E2E Test (Linux) - sandbox:docker - shard 3/3 (push) Waiting to run
E2E Tests / E2E Test (Linux) - sandbox:none - shard 1/3 (push) Waiting to run
E2E Tests / E2E Test (Linux) - sandbox:none - shard 2/3 (push) Waiting to run
E2E Tests / E2E Test (Linux) - sandbox:none - shard 3/3 (push) Waiting to run
E2E Tests / web-shell Browser Regression (push) Waiting to run
E2E Tests / E2E Test - macOS - shard 1/2 (push) Waiting to run
E2E Tests / E2E Test - macOS - shard 2/2 (push) Waiting to run
E2E Tests / channel-plugin E2E (nightly) (push) Waiting to run
E2E Tests / cron-interactive E2E (nightly) (push) Waiting to run
npm cache producer / Save npm cache (push) Waiting to run
SDK Java / ubuntu-latest / Java 11 (push) Waiting to run
SDK Java / ubuntu-latest / Java 17 (push) Waiting to run
SDK Java / macos-latest / Java 21 (push) Waiting to run
SDK Java / ubuntu-latest / Java 21 (push) Waiting to run
SDK Java / windows-latest / Java 21 (push) Waiting to run
SDK Java / Real daemon E2E / Java 11 (push) Waiting to run
Security Checks / Dependency CVE audit (push) Waiting to run
Security Checks / Secret scan (TruffleHog) (push) Waiting to run
* feat(review): give verifiers a do-not-refute list and a constructible rejection bar Step 4's verifier brief already floors uncertain Criticals at low confidence instead of rejection, but it never names the states in which "too speculative / depends on runtime state" is not a valid rejection. The finder side carries the recall rule (do not silently drop a candidate); the verifier side lacked its counterpart, so real-but-uncertain findings could die in Step 4 on a plausibility vote instead of surfacing under "Needs Human Review". Close the same leak on the verifier side: - Rejection is now defined as direct counter-evidence constructible from the code — one of four shapes: factually wrong (quote the misread line), provably impossible (type/constant/invariant, shown), already handled in this diff (cite the guard and show it covers the trigger), or pure style / an Exclusion Criterion. A rejection constructing none of them downgrades to confirmed (low confidence) instead of dropping. - A third masquerading state joins "I could not verify it" and "its evidence is somewhere I did not look": "it is too speculative". A finding whose failure scenario names a realistic state the code does not exclude is PLAUSIBLE by default — concurrency races, nil/undefined on a rare-but-reachable path, falsy zeros treated as missing, off-by-one on a boundary the code does not exclude, retry storms and partial failures, patterns that lost an anchor. SKILL.md's Step 4 summary and the user-facing code-review docs are synced to the new semantics. The pinning test asserts every shape, every ground, and the downgrade consequence — a mutation flipping the consequence into "reject" survived the subject-only assertion, so the consequence clause is pinned too. Fixes #9789 * fix(review): sync the rejection-bar summaries with the brief's four grounds (#9799) * fix(review): sync the plausible-by-default wording and re-head the probe option (#9799) --------- Co-authored-by: qwen-code-dev-bot <qwen-code-dev-bot@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| acp-bridge | ||
| audio-capture | ||
| channels | ||
| chrome-extension | ||
| cli | ||
| core | ||
| cua-driver | ||
| desktop | ||
| desktop-shell | ||
| mobile-mcp | ||
| node-repl | ||
| sdk-java | ||
| sdk-python | ||
| sdk-typescript | ||
| vscode-ide-companion | ||
| web-shell | ||
| web-templates | ||
| webui | ||
| zed-extension | ||