Skip to content

fix(app-shell): render the envelope's producer-marked userMessage in the Studio package lookup #7960

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-sam merged 2 commits into from
Sep 6, 2026
Merged

fix(app-shell): render the envelope's producer-marked userMessage in the Studio package lookup #7960

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f9433eb
fix(app-shell): render the envelope's producer-marked userMessage in …
claude Sep 6, 2026
15c57f8
test(app-shell): mark the userMessage channel pin as green-either-way…
claude Sep 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions .changeset/tidy-buttons-repeat.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
'@object-ui/app-shell': patch
---

Studio package lookup now renders a producer-marked `error.userMessage` from the failure
envelope, preferring it over the diagnostic `error.message`.

`fetchFullPackage` — the `/api/v1/packages` read behind "Package info & settings" and the
managed-snapshot refresh — read only `error.message` and `error.code`. In the 5xx band the
platform withholds the producer's prose and substitutes the generic `Internal server error`
into `message`, while the marked `userMessage` rides through untouched, so an author met a
500/503 that carried a sentence written for them and was shown the generic one instead.
Per the envelope contract, presence of `userMessage` IS the producer's marking and a
consumer that sees it renders it verbatim; `error.code` still travels alongside, and an
unmarked refusal is unchanged.
Loading
Loading