prreviewbuddy 0.57.0 → 0.59.50

package/CHANGELOG.md

@@ -1,5 +1,171 @@
 # Changelog
 
+## 0.59.50
+
+**A click on the Architecture background clears the selection.** Clicking empty space in the
+drawing was meant to deselect the part or arrow you had chosen, and never did; it now does, and the
+panel beside the drawing goes back to its prompt. Dragging the background to pan still leaves your
+selection as it was.
+
+## 0.59.49
+
+**A new Architecture map opens in the middle of its frame.** A picture smaller than the frame sat
+in the top-left corner; it is now centred. Zoomed in past the frame, it scrolls and drags as before.
+
+**Buddy AI's tab no longer covers the expand button.** With a section expanded, the **Buddy AI**
+tab on the right edge sat on top of that section's collapse button. It now sits just below it.
+
+## 0.59.48
+
+**An Architecture run keeps your layout.** With the diagrams expanded, starting a map, stopping one,
+or one finishing reloaded the page back to the normal layout. It now comes back expanded, or with
+Buddy AI expanded beside it, as you left it.
+
+## 0.59.47
+
+**A retried review is timed from the retry.** "Last review in this repository took …" counted a
+retry from when the review was first asked for, so a retry made later looked far slower than it
+was. It now counts from when the retry started.
+
+## 0.59.46
+
+**A resumed analysis no longer skews "Last analysis took".** An analysis picked up again after an
+interruption recorded the whole time between the attempts as its duration. It now records no
+duration, so the estimate comes only from runs timed from start to finish.
+
+## 0.59.45
+
+**An updated review says when the update ran.** **How this review was made** named the new commit
+after an update but kept the time of the first analysis, for example "3 days ago". It now gives the
+time of the update. Reviews updated before this keep the old time until their next update or
+reanalysis.
+
+## 0.59.44
+
+**No visible change.** An update now records how long the update itself took, rather than the time
+since the review was first analysed.
+
+## 0.59.43
+
+**No visible change.** A test of the Architecture tab now waits for the map to be drawn, so a run
+whose tests all passed can no longer exit as a failure.
+
+## 0.59.42
+
+**Waiting says how long it took last time.** Once something has succeeded before, the page says how
+long it took.
+
+- **Architecture map:** beside **Remap repository**, and while a remap runs, for example "Last map
+  took 3m 12s".
+- **Review in progress:** for example "Last review in this repository took 3m 10s".
+- **Reanalysis:** for example "Last analysis of this review took 2m 05s".
+- **Update or KISS run:** the same kind of line.
+
+With one earlier run the page states it exactly. With several it summarises, for example "Usually
+takes about 3 minutes" or "Recent maps took 3–4 minutes". Only runs that succeeded count, and KISS
+and standard reviews are never compared with each other. Before anything has succeeded, the page
+says what it said before. The history is kept on your machine in `~/.prreviewbuddy/runtimes.json`.
+
+## 0.59.41
+
+**No visible change.** A review still records which version of your coding agent made it, asked
+of the agent exactly as before. The tests now supply that version themselves instead of running
+whichever agents happen to be installed, so their results no longer depend on the machine.
+
+## 0.59.40
+
+**No visible change.** While the workspace is waiting to save your place in a page's history, it
+now marks the page as saving, and clears the mark once it has. The browser tests wait on that mark
+instead of sleeping past it, which takes them from about two minutes to about one.
+
+## 0.59.39
+
+**Mapping says its stage on a line of its own.** While a part is being mapped in depth or the
+repository is remapped, the notice above the map put its title and the current stage side by side,
+which read as two headings. The stage now sits under the title, as it already did for a first map,
+and the same goes for the line under **Remapping failed** and **Architecture may be out of date**.
+
+**Long links in PR messages wrap.** A comment holding a long URL or hash with no spaces in it ran
+out of its card on the PR messages tab. It now breaks onto the next line, and so does a long file
+path above a thread. Code blocks still scroll sideways as before.
+
+**A part's buttons on the Architecture tab get room.** Once a part was mapped in depth,
+**Remap this part** sat flush against **Open … in depth** below it. The way in now comes first,
+the remap button after it, and every button on the panel has its own line with space around it.
+
+## 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