v0.3.4 — Concrete gaps and one finding per place

Azure DevOps PR Review for OpenCode — 0.3.4

This release changes what reviewers report. Concrete gaps the change leaves,
such as an untested change or a document that now contradicts the code, become
findings, and a mistake repeated in several places is reported at each place
that needs its own fix. Settings, commands, comment previews, adjustments and
publication work as in 0.3.3, and the tested host stays OpenCode 2.2.4.

What changed

• Concrete gaps are findings. Reviewers file, usually as low: a changed or
  added behavior that no test would catch where the project already tests
  comparable code (naming the missing case and the tests it belongs with), a
  test that cannot fail or checks the wrong thing, a comment, document,
  example, schema or configuration that now contradicts the code, and
  duplicated, dead, misleading or inconsistent code the change introduces.
  These used to appear only as advice in the report. Design trade-offs and
  general advice without a specific defect or location still go to the report
  and the summary's improvement suggestions.
• One finding per place that needs its own fix. When the same mistake is
  written separately in several functions, files or routes, for example three
  routes that each build a URL from the internal request origin, each place is
  its own finding at its own lines, with the sibling places in its evidence.
  Reviewers check their other assigned files for the same mistake. One wrong
  piece of shared code is still one finding at that code.
• Identical copies count once per reviewer. A template, example, document
  or vendored file repeated with identical content in several directories is
  one place among one reviewer's assigned files: one finding at one copy that
  lists the other copies. A large PR is reviewed in shards cut by path, so
  copies in different shards can each produce a finding. Files whose content
  differs, such as each package's own manifest, stay separate places.

Publication is unchanged: inline comments go to high and medium findings, and
low findings stay in the summary index. A review therefore shows more low
findings in the summary and, for a repeated high or medium mistake, one inline
comment at each place. /pr-review, /pr-deep and /pr-quick share these
rules.

Measured effect

Before release, the new instructions were compared with 0.3.3 on the public
ReviewBench test set, served to
OpenCode 2.2.4 through a local fixture of the Azure DevOps API and scored with
the benchmark's matcher and classifier rubric by Claude Opus subagents rather
than its official judge. The comparison shows the direction of the change, not
a leaderboard result:

• With /pr-deep and gpt-6.1-sol, reviews matched more of the high- and
  medium-severity reference issues, including high ones. A mistake repeated in
  several routes was reported, and matched, at each route.
• Reviews produce more findings, mostly low, which stay in the summary index,
  and take somewhat longer; the share of findings judged valid stayed about the
  same.
• With /pr-review and gpt-6-luna, reviews matched slightly more, within the
  variation between runs.

The
validation record
describes the method and its limits.

Installation

opencode plugin add opencode-azure-devops-pr-review@0.3.4

Alternatively, install the same release from Git:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.3.4'

Add only one of them. Follow the
quickstart
for a private PAT file, /pr-setup, a service restart and the first review.

Upgrading AZPR

For an entry that opencode plugin add created, add 0.3.4 and remove the
previous version only when the download succeeded. Replace PREVIOUS_VERSION
with the version in your plugins entry, such as 0.3.3:

opencode plugin add opencode-azure-devops-pr-review@0.3.4 &&
  opencode plugin remove opencode-azure-devops-pr-review@PREVIOUS_VERSION

Run them when no AZPR command is running: OpenCode 2.2.4 switches the running
service to 0.3.4 within seconds, without a restart, and
opencode plugin list should then show a single azpr row with 0.3.4. Running
only the first command leaves the previous version running. For an entry with
options, change only its package value; the OpenCode service then downloads
0.3.4 with its own network settings. See
upgrading
for the details. External settings, the PAT file and review records remain in
place, and this release adds no settings or required migration.

For a source installation, extract the new archive and run its installer with
--replace to retain settings:

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

Compatibility and validation

The tested target is OpenCode CLI 2.2.4 (V2 plugin API), Node.js
22.23.3, Ubuntu 22.04.5 under WSL2, and Azure DevOps Services REST API
7.1. OpenCode 1.x and Azure DevOps Server are not supported; other operating
systems remain unvalidated.

The runtime code is that of 0.3.3; only the reviewer instructions changed. The
validation record
lists the offline and real-host checks with fake services and the comparison
above. Live runs with openai/gpt-6-luna on the 1-file test PR, in a service on
OpenCode 2.2.4, completed without publishing comments: /pr-review confirmed
the PR's three known defects, and /pr-quick reported the same three.

The npm package, Git package and source archive contain the same runtime, with
no npm dependencies or install scripts; the source archive also contains the
documentation, installers and settings example. The release source artifact is
opencode-azure-devops-pr-review-v2-0.3.4.tar.gz, with checksums in SHA256SUMS.