PRISM v4.5

• Start a new job from any job's page. Every job's detail view now has a
  + New job button, so you no longer have to go back to the list first. The
  form opens with that job's settings (usually only the PR id changes), and
  Cancel takes you back to the job you were on.
• Ctrl+Enter starts the review. Once the PR id, working folder, region and
  repository are filled in, press Ctrl+Enter instead of clicking
  Start Prisming. It does nothing while anything required is still missing.
• Fixed: the model list could stay empty forever. The engine sometimes
  can't answer for a few seconds after it starts, and PRISM gave up on the
  first failure, leaving "could not list models" and an endless "Loading
  models…". It now retries, remembers the last good list, keeps re-asking in
  the background, and says what it's doing.
• Fixed: reviews failing with Agent not found: "pr-reviewer" when PRISM
  was started from a different folder than the project, on opencode 2.x.

PRISM v4.4

• Stability fixes

PRISM v4.3

• A warning before merging a PR that was never reviewed. If a run skips the
  review (sync + merge only, or merge alone), PRISM now stops and asks before
  it merges: "Merge without a review?", with the option to abort. It asks every
  time, so a setting left over from an earlier run can no longer merge a PR
  unreviewed by accident. A background run, with nobody to ask, does not merge.

PRISM v4.2

• PRISM CLI integration

PRISM v4.1

No changelog entry yet for this release.

PRISM v3.9

• Faster, steadier reviews. A review no longer fails after a fixed 20
  minutes when the model is simply slow, and PRISM says it is still working
  while it waits. If a review does have to be stopped, you still get its
  findings, marked as a partial review.
• The reviewer no longer runs a PR's tests or installs packages. It reads
  the code only, which is faster and safer.

PRISM v3.8

• Stability and performance fixes.

PRISM v3.7

• Works with any branching setup. The reviewer's guidance and PRISM's
  messages about repeat reviews no longer assume particular branch names or a
  promotion order — a repeat can be the same PR, another PR or another branch.

PRISM v3.6

• Reviews stay consistent from develop to QA to staging. PRISM keeps a
  short-lived record (a temp file on this machine; nothing is ever written to
  your repositories) of what it concluded about each change, matched by the code
  that changed so it survives rebases and squashes, and gives the reviewer the
  earlier findings when the same change comes back in a later PR (or a Retry). A
  defect the earlier stages missed is flagged as a late find in the job log
  and the PR description, since a fix made that late hasn't been through the
  testing in between. Only a late Critical/High finding blocks the merge; a
  late Medium or lower is reported and approves with comments. Nothing changes
  if there is no earlier review of those changes.
• Reviewers look harder the first time. Every review now checks failure
  handling and edge cases, the impact on callers, and searches the repository
  for the same defect elsewhere: each finding lists the other places the pattern
  occurs (or says none were found), so one fix can cover them all. Findings can
  be longer as a result, and reviews use somewhat more tokens.
• Codegen tool integration (optional). In Help, tick Accept reviews from a
  code-generation tool and PRISM will review the pull requests a codegen tool
  opens, send "request changes" findings back to it, and merge once the PR is
  approved — repeating up to five rounds before it hands over to you. Off by
  default and local to your machine; a job from the tool is an ordinary job
  (marked via codegen) with every existing check, including the high-impact
  confirmation, still in force. Nothing changes if you never turn it on.
• The manual is updated for all of the above: how to read the new finding
  markers, the new safety notes and troubleshooting entries.

PRISM v3.5

• Fewer "could not parse a verdict" stops. The verdict is now found
  however the reviewer formats it, and a follow-up reply that doesn't repeat
  it no longer wipes out the verdict it already gave. If a verdict still
  can't be read, PRISM asks the reviewer once to restate it before stopping.
  "Approve — no blocking issues" is no longer mistaken for a Block.
• Custom instructions set before you start are now honoured. They are
  handed to the reviewer up front as a clearly marked block (and logged),
  instead of a trailing sentence it could skim past.
• Ask about a PR after its job has finished. The instruction box stays
  enabled on finished and stopped jobs and becomes a read-only follow-up
  question to the reviewer; unrelated requests are declined with a reason.
• PRISM AWS Alerts: deployment alerts are now cards like the merge alert,
  with a colour-coded SUCCEEDED (green) / FAILED (red) status. Redeploy
  prism-aws-alerts to pick this up.
• The jobs list is split into Running and Completed sections, so live
  work is always at the top.