prreviewbuddy 0.56.0 → 0.59.38

package/CHANGELOG.md

@@ -1,5 +1,109 @@
 # Changelog
 
+## 0.59.38
+
+**Map a repository from its Architecture tab.** A review whose repository has no map now offers
+**Map this repository** on the Architecture tab. Your configured coding agent maps it in the
+background, and you can keep reviewing meanwhile. The tab says what each stage is doing, **Stop**
+ends a run you no longer want, and a notification says **Map ready** or **Mapping failed** when it
+finishes. Every linked worktree of one repository shares the same map. **How this map was made**
+says which agent made it, from which commit, and how many of the places it quotes can still be found.
+When enough of them cannot, the tab says **Architecture may be out of date** and offers **Remap
+repository**.
+
+**Map one part in depth, and see what a change touches.** Selecting a part that owns files offers
+**Map this part in depth**, which draws that part on its own with a trail back to the repository's
+map. If a later remap moves files into or out of the part, its map in depth says so and offers
+**Remap this part**. Above the drawing, **Affected by this change** names the parts the review's
+files belong to, and counts the changed files no part owns. The drawing opens fitted to the frame,
+and every part and arrow can be reached with Tab and selected with Enter or Space.
+
+**Cancel a review or an update while it runs.** A review in progress now has **Cancel review**
+beside its running time, whether it was started from the terminal or from the page. The agent is
+stopped, and the review shows as stopped with **Carry on**, which picks up where it left off. An
+update in progress has **Cancel update**: the agent is stopped and the review is left exactly as it
+was before the update began, including the pull request conversation. A cancel that arrives once
+the result is already being saved says it was too late, and the page then shows the finished
+result.
+
+**Opening a review marks its notifications read.** Any unread notification about a review is marked
+read when you open that review, however you got there: from Notifications, the Reviews list, a
+link or a reload. The notifications stay in the list; only the unread count changes. Opening one
+review leaves the notifications about other reviews as they were.
+
+**Restart is more careful.** A restart onto a new port, after changing it in Settings, keeps the old
+server answering until the new one is up, and the page follows it there. If the new server never
+starts, the old one carries on where it was. A restart now also waits for a KISS review started
+from the browser, or for a Buddy AI answer or drawing, as well as for a review or a map.
+
+**Fixes.**
+
+- A pull request whose clone has a `main` with unpushed commits can be reviewed again. The default
+  base is checked only when the pull request names no base of its own.
+- A KISS review started from the browser asks for the model the review was made with, when it uses
+  the review's agent.
+- Updating a review clears a pull request description the author has since emptied, instead of
+  carrying the deleted words into the reassessment. When the description was edited, a motive the
+  review had quoted from it is checked again, and asked about if the quote has gone.
+- A KISS answer that lost recommendations on the way reads as incomplete, not as proportionate.
+- A JSON example in the prose before an agent's reply is no longer mistaken for the reply.
+- Files, Architecture, Change map and Implementation take the same full width in focus mode.
+- The line between open and resolved findings, and similar section lines on Files, KISS, Reviews and
+  Notifications, have gone; space separates them instead.
+- The unused native desktop notification code has been removed, along with the
+  `PRB_DESKTOP_NOTIFICATIONS` setting that switched it on. Notifications in the workspace, and the
+  toasts that announce them, are unchanged.
+
+## 0.58.0
+
+**Architecture: the important parts of a repository and how they relate.** A repository with an
+architecture gets a third tab in Diagrams, before Change map and Implementation. It shows the
+repository's main parts and the relationships between them, the same for every review of that
+repository. A part that contains others opens to show them, with a trail back to where you started.
+Selecting a part or an arrow shows what it is, the relationships it takes part in, and the code each
+claim rests on, quoted, with a link that opens your editor at that code.
+
+**The evidence follows the code.** Every claim cites a short quote from a file, not just a line
+number. Each time the page loads, the quote is looked for again in the code as it is now, so a link
+still lands on the right code after lines above it were added or removed. A claim whose code can no
+longer be found keeps its quote and note but loses its link, and the tab says how many citations
+still stand.
+
+Nothing in the workspace makes an architecture yet. A repository without one shows no Architecture
+tab, so for now nothing changes unless a model has been imported with the developer command
+described in `docs/architecture/README.md`.
+
+## 0.57.0
+
+**Reviews you marked reviewed now find out when their pull request merges.** Until now the
+workspace server only checked the pull requests of reviews that were queued, saved, Waiting, Done or
+not yet marked reviewed. A review you finished while its pull request was still open stopped being
+checked, so if the pull request merged later, its card kept saying nothing. The server now keeps
+checking those in the background too, for whether each pull request is open, closed or merged and
+nothing else. The checks run every hour and take a limited number of pull requests each time, so
+with many reviews, or a pull request GitHub keeps failing to answer for, it can take a few hours to
+come round to a particular one. A card that had already missed a merge picks it up the same way, and
+shows **Merged** with the time it was found, so it may read "Merged just now" for a pull request that
+merged days ago. A merged pull request is never checked again. One closed without merging keeps
+being checked, since it can be reopened. These background checks never send a notification, and
+never take a turn from the checks of reviews you are still working on.
+
+**Check for updates asks GitHub too.** Pressing **Check for updates** on a review page now also asks
+GitHub whether its pull request is open, closed or merged, and the label beside the pull request
+number updates at once. It does not wait for any background check that happens to be running. It works on any review, including one marked **Done**, and leaves the review
+where it is: still Done, not queued, not checked any more often than before. The checks the page makes
+by itself, every minute and when you come back to the tab, still never contact GitHub.
+
+**A deleted checkout no longer stops other pull requests being checked.** If a review's folder had
+been moved or deleted, the server took the failure to mean the GitHub CLI was missing, and skipped
+every other pull request on GitHub for the rest of that check. Now only that one review's check
+fails, and everything else is checked as normal.
+
+**Done reviews no longer notify when their pull request merges or closes.** A Done review is still
+checked, so its card still says **Changed since done** after a push, a merge, a close or a reopen, and
+a push still sends **PR updated**. A merge, close or reopen is now recorded without a **PR merged** or
+**PR closed** notification. Reviews that are not Done notify as before.
+
 ## 0.56.0
 
 **Work in one focused tab, with Back and Forward that know where you were.** The workspace now has