You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
examples: address code-review findings (standards and spec)
Make the sandbox the accepted path. run_review defaults to the auto
runtime, which uses the container sandbox when Docker is available and
the local subprocess sandbox otherwise; in-process becomes an explicit
dev fast-path, and both the selftest and the agent tool run through the
sandbox. The standalone run_checks.py and pipeline/scanners.py are
reconciled to emit identical findings (aligned severity, confidence and
path normalization), enforced by a parity test, so the two paths cannot
drift.
Make failures visible. A missing scanner produces a needs-human-review
finding instead of a silent zero-finding report; the monitoring
tool-call count reflects the scanners that actually ran; and the
persisted review status is derived from the run (blocked, failed, or
completed) rather than always completed.
Correctness and deliverables. File-level findings key on the rule as
well as the category so distinct issues in one category are not
collapsed. The container path's post-processing is extracted into
build_container_result and unit-tested without Docker. The agent CLI
gains a dry-run flag that forces the fake model, the stale run_review
docstring is corrected, and the change adds the committed sample report
and a RULES.md documenting all six categories. yapf and the
trailing-newline fix leave the tree lint-clean.
Updates #92
RELEASE NOTES: NONE
0 commit comments