chore(release): version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

hephaestus@0.75.0

Minor Changes

• Deciding whether to adopt a practice now starts with why the habit matters, not with the rule the reviewer follows. The rule is still there, under How it decides, next to what the practice reads and what it measures first — but it is written for the model that applies it, runs to several thousand characters, and is not what you need in order to choose.

  The library list carries each practice's reason too, so you can work through the catalog without opening every entry to find out what it is for.

• Workspace administrators now choose which practices their workspace reviews, instead of receiving a copy of the instance library at creation. Practice setup shows the library beside the practices you already have, so you can read a practice's full definition, the evidence it needs, and what it will look like in your workspace before you add it. Adding one gives you an independent copy you can edit; later library changes never rewrite it. A whole group can be added at once, and a group you removed earlier can be restored from the same place.

  Adding never starts sending feedback on its own. A practice Hephaestus can review starts at Review before sending, and a practice it cannot review stays Off until you connect what it reads.

  You can also add a whole area at once. Hephaestus shows every practice it would add, reuse, or skip first, and applies the result in one step or not at all. Adding is refused if the library or your workspace changed while you were reading the preview, so you always act on what you saw.

  Workspaces you already have keep everything in them, and a workspace that has never recorded a catalog installation still receives one at the next start, so nothing goes missing.

• Practice reviews deliver feedback again. A review measured a pull request, recorded what it found, and then stopped: the step that turns those findings into something a developer reads was never switched on, so every review ended with its results stored and nothing said. Reviews now compose feedback for each lane the occasion can reach — the note on the work, the developer's own practice pages, and an ongoing conversation — and issue reviews compose for the two longitudinal lanes, since an issue is not the work a note belongs on.

  Operators: feedback now appears where it previously did not, so a workspace with review switched on begins posting again. Nothing new is required of you, and the instance-wide Silent Mode brake still holds everything back while it is engaged — but if you upgraded during the window where reviews were silent, this is the change that ends it.

• The practice screens now read the way the decision is actually made, and they stop implying things that are not true.

  A practice leads with why the habit matters; what adding it will do sits at the bottom, next to the button that does it. Not independently validated is gone — it appeared on every practice, so it told you nothing while looking like a warning. In its place is a sentence saying nobody has measured how often the practice is right, which is why a new one starts by asking you to approve each piece of feedback.

  Provenance says what actually happens. A copy never tracks the catalog, whether you edited it or not, so the badges now say Same as the catalog, Catalog changed, yours did not, and No longer in the catalog — and the matching case is finally labelled instead of silent.

  Opening or dismissing a panel no longer moves the page behind it, panels slide rather than jump when you step back, and the whole thing respects a reduced-motion setting.

  Loading no longer means a spinner in an empty box: each screen draws the shape of what is coming, so nothing jumps when it arrives, and quick responses no longer flash a loading state at all.

  One word throughout: the set of practices this instance offers is the catalog.

• Removing a practice area now asks what should happen to the practices in it: keep them and move them to Unassigned, or delete them together with the area. Deleting them also deletes their observations, and the dialog says so before you choose. Previously the practices were always kept, with no way to remove an area and its practices in one step.

Patch Changes

• A review comment now stays as it was written. Where a later look at the same change used to rewrite the original comment in place — and quietly demote anything already answered on the diff — it now leaves a new comment beside the old one, the way a person would. The comment also stops repeating the notes that sit on the diff: those live on the lines they are about, and anything that could not be placed on a line falls back into the comment rather than disappearing between the two.

• Practice setup no longer sends you to another page to look at something on it. Selecting a practice — one of yours, or one the library is offering — opens it beside the tree you were reading, and selecting something inside that opens on top of it, so you can go two levels deep and step back one at a time with Escape, a press on the page, the browser's Back button, or a swipe. The page behind stays readable rather than blurred, and each panel leaves a column of the one beneath it showing.

  Your own practices now have a read-only view for the first time. Opening one used to mean opening the edit form, so "what does this practice say?" and "change this practice" were the same act; now reading is reading, and editing is one clearly marked step away. A practice looks the same whether you met it in the library or in your own tree, because both show the same definition.

  Writing a practice no longer takes over the page either — on Practice setup and in the instance catalog, Create and Edit open beside the tree the practice belongs to, so you can see where it is going while you write it. An editor closes the same four ways everything else does — Escape, a press on the page beside it, a swipe, or its own controls — and asks before discarding unsaved changes on any of them, so nothing is lost and nothing silently refuses to close. The old addresses still work and open the same editor.

  Adding a practice returns you to the library you were working through — the practice moves into your own tree and stops being offered — instead of dropping you into an edit form. Adding five practices is now five selections rather than five round trips. Everything is addressable: the URL you are looking at is the URL you can share, and it reopens exactly the panels you had open.

• Creating or editing a practice area now lets you pick its icon and colour, the same way the instance library does. Left alone, both still follow the area's name.

  A practice's "What to look for" is written in markdown — the editor says so — and the read view now renders it. Headings, lists, emphasis and inline code used to reach you as literal ## and - characters in one long paragraph of bold text.

• Pull request responses no longer require a URL when the upstream provider does not supply one.

• Fixes three faults in the sliding panels used across practice setup and the instance catalog. A panel now slides in from the edge instead of appearing fully formed. Opening a panel on top of another no longer makes the one behind jump back and re-animate when you step back out of it. And a covered panel keeps a readable column of its own content on screen rather than a bare strip of its margin, which is the whole reason these stack instead of replacing each other.

• A review whose evidence check fails on one observation now delivers the others. The check that refuses to show a developer a claim it cannot trace back to the code applied to the whole review at once: one practice that mis-quoted its source — by a stray character, in a file the reader never sees — withheld every other finding in that review, including correct, fully evidenced ones. The developer saw nothing at all. Only a quote that does not match its source is treated this way; a citation to evidence the review never gathered still stops the whole delivery, as before. What was withheld is logged with the reason, and a review in which no claim can be verified still fails rather than arriving empty.

• Notes prepared for the mentor now say where a point has already been put to the developer and whether anything has moved without help, so a conversation does not repeat feedback they have already had twice. Notes written before this carry no such record, which reads as nothing having been said rather than as nothing to say.

• When the library changes while you are reading an area's plan, the panel now stays open and shows you the refreshed plan, the same way a single practice already did. It used to close and leave you a message asking you to go and look at the area again.

• Screen readers now announce what every dropdown list is for. The status, timeframe, work-type,
  rows-per-page and model pickers each opened a list of options with no name attached, so the list
  itself was announced as unlabelled.

  Also fixed, all surfaced by a stricter type and lint gate across the whole codebase:

  • A review schedule saved with a time that had no minutes (9 rather than 09:00) stored no minute
    at all instead of falling back to the hour's start.
  • Audit-log entries and the curated-catalogue version panel printed [object Object] for any field
    whose value was not plain text.
  • A cookie-consent choice was read back from browser storage without checking it, so a corrupted
    entry could be treated as a decision.
  • A theme, a workspace role or a feature flag that the browser or server reported as something this
    build does not recognise is now ignored rather than trusted: the theme falls back to the default,
    the role is refused, and the flag reads as off.
  • GitLab sub-issue sync could delete parent links it had never looked at. When a page walk stopped
    early — an error, or a repository past the pagination ceiling — the cleanup step still ran against
    the partial result and cleared the parent of every issue whose link lived on a page it never
    fetched, then reported the sync as completed.
  • Server errors now keep their original stack trace. Fifty-two places caught an exception and threw a
    new one without attaching the cause, so the log recorded where the failure was reported rather than
    where it happened. Sign-in, token validation and Slack preference failures were all affected.
  • Scrollbars inside scrollable panels rendered 2px wide with no border instead of the intended 10px.
  • A checkbox or radio that is switched off now looks switched off: its label kept full contrast, and
    the control itself showed neither the dimming nor the blocked cursor.
  • The primary button gave no hover feedback. The style was written so that it only applied when the
    button was rendered as a link, so the most-used button in the app looked inert under the cursor.
  • A mentor attachment that failed to upload disappeared with no message, leaving the sender believing
    it was attached. The failure is now reported.
  • A disabled accordion section still opened when clicked.
  • Copying a mentor reply to the clipboard failed silently when the browser refused.
  • Countdowns now advance while the page is open: an Outline token's expiry, and the wait shown while a
    sync is rate-limited, previously only moved when something else on the page happened to redraw.
  • Screen readers no longer hear an orientation announced on grouped toggle buttons, which is not
    something a group can meaningfully have.
  • The achievements API described an unlock time as always present, even for an achievement nobody
    has earned. It is now reported as absent, which is what the server was already sending.

• A panel covered by another one now leaves noticeably more of itself showing, so the thing you opened from stays readable rather than reduced to a stripe of its margin.

• Tidies the practice and group editors. Their Save and Cancel buttons now sit on the panel's own bottom edge, spanning it, instead of floating in a bar that stopped short of both sides and left a strip of empty space beneath it. The fields fill the panel rather than stopping partway across, so the buttons line up with them. Panel headings no longer squeeze the practice name into a narrow column beside a badge — the badge moves under the name, which leaves the name room to read on a phone. The scrollable part of a panel can also be scrolled from the keyboard, including while a form is saving and every field in it is disabled.

• Editing a practice no longer costs you your place: opening the editor from a practice panel and saving or cancelling returns you to that panel, with the catalog still open where you left it.

  Rows that pair a label with a dropdown now stack on a narrow screen instead of squeezing the label into a sliver beside it.

• The practice screens say one thing one way. The set of practices an instance offers is the catalog everywhere, entries are included or excluded rather than offered, a practice with no group is Unassigned, and the grouping is called a group — or not named at all where its own name is already on screen.

  Filtering the practice list to nothing now says so and gives you a button to clear the filter, instead of leaving you with empty groups and a note about a filter you had no way to remove.

• Review comments no longer repeat their own issue count in the opening line, no longer run a strength and its next step together into one unpunctuated sentence, and no longer report how long the run took.

• A problem the review found by opening a file now arrives as a comment on the changed line, rather than as a paragraph at the bottom of the merge request.

• A review comment now leads with its most serious finding and the one edit that fixes it, instead of leading with whichever finding happened to have no line number attached. Each finding says what to do before it says why it matters, and the reasoning is one sentence rather than the same paragraph on every review that touches the practice.

• A review comment now opens with a sentence written about your change, instead of one of a handful of fixed lines that read the same on every review — including on reviews that opened with praise ahead of a serious problem. When the review has nothing worth opening on, it opens on its first finding.

• Review comments no longer append the workspace's own wording about a practice to each note. That paragraph was identical on every review that touched the practice, and it was about the practice rather than about the change in front of you. The practice still decides what gets raised; it just doesn't get quoted back.

• Rejects mentor chat requests missing a message and integration connection requests missing a provider kind.

• Fixes the "Uses Hephaestus default" notice in the instance practice catalogue running edge to edge while every field below it was indented. It now sits inside the panel like the rest of the content, and scrolls with it instead of holding a fixed strip at the top.

• Practice reviews now also start for practices that have no precompute script. Preparing the sandbox failed for those, so the review ended before it began.