The artifact picker gets a pinned tab and a p key to pin, if your server enables it.
What's wrong with this entry?
The artifact list gained a fourth filter tab for pinned artifacts, a p key whose label flips between pin and unpin, and sorting that puts pinned artifacts first. The switch is not a local flag: the list response carries a starsEnabled boolean, and when the server omits it the tab is dropped, the pin action disappears, and a selected pinned filter is rewritten back to "all".
- Per-artifact list data gained a pinned marker, an audience (owner, users, org, or public) and a last-viewed timestamp; ordering is pinned first, then most recently viewed, updated, or created.
- Pin state updates locally straight away and is reconciled against the server.
- The pinned tab is only offered once you actually have something pinned, or are already on it, and the empty state reads "Nothing pinned yet. Press p on an artifact to pin it."
- There is no environment variable or local flag to force it on; it stays invisible until the artifacts backend returns the field.
Nothing pinned yet. Press p on an artifact to pin it., starsEnabled
Strings lifted out of the shipped bundle, so the claim above can be checked against them.