You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(webapp): drop what the profile never rendered
`PracticeTrendPanel` had no caller outside its own story and test: the detail
page shows `PracticeTrendChip` and nothing else. Its 214 lines went, and with
them `formatTrendGap` and `formatTrendCoverage`, which nothing else called, and
the `barClassName` and `trendPolarity` fields its stacked bar was the only
reader of. `isVerdictStanding` and `ringClass` were exported and never read.
`ReviewRunTimeline` also carried an empty state its only caller made
unreachable — and a worse one: it said "matches these filters" whether or not a
filter was set, while the caller already tells the two apart. The rule moves
into a comment, and the case the deleted test named is now asserted where the
decision is actually made.
The trend provenance sentence counts "pieces of reviewed work" rather than
"work items", which is what `practice-feedback-language.md` calls the unit.
Also fixes the operator note on the practice-standing changeset, which told
callers to replace `/practice-groups` with `/practice-groups`. The retired path
is `/practice-areas`.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MAQxdMw579siMh1wXKEEh4
Copy file name to clipboardExpand all lines: .changeset/practice-standing-feedback-api.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,4 +4,4 @@
4
4
5
5
The application API can now answer where a developer stands in each practice group: the current standing and its guidance, how the group has developed across recently reviewed work, which kinds of work contributed feedback, a filterable observation history, and the complete review runs behind it. An undecided observation remains visible in that history without being presented as a verdict. Developers can also replace or delete their response to delivered feedback, recording whether it was helpful, how they handled it, and an optional explanation. Every endpoint answers only for the signed-in developer.
6
6
7
-
**Operators:** direct API callers must replace `/practice-groups` with `/practice-groups`, use the corresponding group schema and field names, replace `/practices/developer` with `/practices/reviewed`, and move from the older reaction endpoint to the combined response endpoint. Existing response history is preserved; `MIGRATION.md` lists the contract changes. The generated Hephaestus web client is updated in the same release.
7
+
**Operators:** direct API callers must replace `/practice-areas` with `/practice-groups`, use the corresponding group schema and field names, replace `/practices/developer` with `/practices/reviewed`, and move from the older reaction endpoint to the combined response endpoint. Existing response history is preserved; `MIGRATION.md` lists the contract changes. The generated Hephaestus web client is updated in the same release.
0 commit comments