prreviewbuddy 0.53.1 → 0.55.6

package/CHANGELOG.md

@@ -1,5 +1,140 @@
 # Changelog
 
+## 0.55.6
+
+**File paths are shown whole.** A deep directory above a file name was cut short with an ellipsis,
+and the full path appeared only in a browser tooltip on hover. The directory now wraps onto a
+second line where it needs one, so the whole path is always on screen, and the tooltips are gone.
+This covers file locations on issues and questions, related files, the Guide's file rows, the Files
+tab and KISS locations, in the workspace and the extension. The extension's file list, which had no
+tooltip, no longer hides the end of a long directory either. (Extension 0.25.4.)
+
+## 0.55.5
+
+**Why this change? says what is known, plainly.** Each state now has a label anyone can read and a
+colour that says how sure it is: **Author's reason** (green), the author's own words in the PR
+description; **Possible reason** (gold), "The PR description doesn't give a clear reason. Based on
+the change itself, this appears to…"; and **Reason unclear** (grey), "It isn't clear why this
+change is needed.", with **Ask the author** and the question to ask. Colour is only a thin rule
+beside the reason and the label's own colour; the text stays dark, and the label says it all
+without colour. Once that question is marked answered the section reads **Answer available**: "This
+question has been marked answered. Run the review again after adding the answer to the PR
+description."
+
+**A refused reason is never shown as nothing.** When the analysis says the author gave a reason but
+the words it quotes can't be confirmed in the PR description, the section used to show nothing at
+all. It now shows Reason unclear, asking the analysis's own question when it gave one, or "What
+problem does this change solve, or what goal does it serve?". That question has the same id on
+every analysis, so marking it answered survives a rerun, even when the analysis happens to ask it
+in the same words. The refused wording is still never shown, and the evidence the refused reason
+came with is not presented as a reason.
+
+**What the harness corrected moves into Analysis details.** The amber box above the review, which
+showed on every tab, is gone; its notes are now listed under Analysis details on the Overview. The
+note for a refused reason says only what the check found, since a quote also fails when it is two
+words or is the template's text. The refused quote (cut at 500 characters) and its evidence are
+kept in the review's audit record, or the extension's dev trace.
+
+The prompt asks for the author's words exactly as written, backticks and punctuation included, and
+treats a reason found only in commits, review comments or a linked issue as inferred. Under
+Possible reason, the kind of each piece of evidence ("Test", "Code") is now the size of the text
+beside it. (Extension 0.25.3.)
+
+## 0.55.4
+
+**Empty pages use the full width.** On the PR context page, the note saying no pull request
+discussion was brought in, and on Diagrams, the card offering to draw a change map or an
+implementation diagram, were held to a narrow column. They now fill the page's width like the
+rest of the workspace.
+
+## 0.55.3
+
+**Template comments stay hidden.** HTML comments in a PR description, such as a template's
+`<!-- Describe your change -->`, showed as literal text in Author's context, in both the full view
+and the preview. They are now hidden, as on GitHub. The same goes for comments in review comments
+on the PR context page. A comment inside a code block or written as inline code is still shown,
+since there it is code, and a code fence inside a comment no longer turns the rest of the
+description into code. The preview never shows part of a comment. Model output is unchanged:
+nothing it writes is hidden.
+
+## 0.55.2
+
+**A lighter Overview.** Author's context, Why this change? and What's changing no longer read as
+one block:
+
+- **Author's context** opens on a short preview of the first thing the author wrote, past any
+  template heading such as "Summary": a paragraph's first two sentences (or about 400 characters,
+  never cut mid-word), a list's first three items, or "Code block included" for a long code block.
+  **View full PR description** shows the whole description, as written. A description that fits
+  the preview is shown whole, with no button.
+- **Why this change?** shows the label and the motive. The author's quote behind a stated motive
+  is under **Author's words**, one click away, since the motive usually says the same thing.
+- **What's changing** is asked for in about 80 to 120 words, and says what the change does without
+  repeating why it exists or judging it. Analyses made before this version keep their summary.
+- More space between the three sections, and more again before the risk verdict and the
+  suggested review path.
+
+## 0.55.1
+
+**Load more on the Notifications page.** The list shows the newest fifteen, and Load more reveals
+fifteen more at a time, the same way each section of the Reviews page does. Mark all read still
+covers every notification, including the ones not yet shown.
+
+## 0.55.0
+
+Published with 0.54.0, which did not go to npm on its own: read both entries below.
+
+**Why this change?** The Overview now says why the change exists, between Author's context and
+What's changing, and how it knows:
+
+- **Stated by the author**, with a short quote from the description. The quote is checked
+  against the description the analysis read, and **From Author's context** takes you to it.
+- **Likely motivation**, when nothing states it but the change gives evidence: a test, an issue,
+  a commit message. The evidence is listed, with links to its files.
+- **Motivation unclear**, when knowing why would change how the change should be read. The
+  analysis asks the author one question, filed first on the Questions page under **Intent**, with
+  the same Mark answered control as every other question.
+
+Nothing is shown when the reason would not change the review, or for analyses made before this
+version. A claim that fails its check is never shown in the model's words: an unverified quote or
+an inference without evidence becomes "unclear" with a neutral sentence when the analysis asked a
+question, and is left out when it did not. The workspace says so under **What the harness
+corrected**.
+
+- The workspace's prompt now reads the pull request's description. A local branch's commit
+  subjects are labelled as commits rather than as a description.
+- Updating an analysis with new commits keeps its motivation, since commits show what changed
+  rather than why. The extension 0.25.0 shows the same Overview.
+- Once the Intent question is marked answered, the Overview says **Motivation was unclear when
+  analysed** and offers **Run review again**, since marking a question answered records no answer
+  for an update to use. A new analysis reads the description and conversation as they now stand.
+  The workspace page can now start that analysis itself, as `review --reanalyse` does.
+- Evidence follows one rule in both places. A changed file opens in the diff, and a real unchanged
+  file opens in the source view. A path the reviewed commit does not hold is removed and listed
+  under **What the harness corrected**. A path that cannot be checked, which is any path outside
+  the pull request in the extension, is shown as an unverified path rather than a link.
+- A quote counts as the author's only if it is in the text they wrote. A partly filled template's
+  comments, unticked checklist items and bare headings no longer count.
+- Tabbing into a closed Author's context preview opens it, so a focused link or Copy button is
+  never hidden under the fade.
+
+## 0.54.0
+
+**The Overview starts with the change, then gives the verdict.** The risk card used to come first,
+and its takeaway read like the pull request's description. The Overview now opens with
+**Author's context**, the pull request's description exactly as the author wrote it. Under it is
+**What's changing**, the analysis's summary of what the code does. The risk card, the counts and
+the suggested review path follow, as before.
+
+- Author's context appears only when the pull request has a description. A description that is
+  only an unfilled template counts as none, and so does a review of a local branch or commit.
+- Each analysis keeps the description it was made against. If the author edits it later, older
+  analyses still show what they read, and the next analysis reads the new text.
+- Long descriptions open as a preview with **Show full description**. All of it, checklists and
+  testing notes included, is one click away, and **Show less** folds it again.
+- The workspace now fetches the description in the same `gh pr view` call it already made. The
+  extension 0.24.0 shows the same Overview.
+
 ## 0.53.1
 
 **The running KISS review has its normal layout back.** While a KISS review ran, its progress