quarry: Artifact Description [ce3c86cb79]

Artifact ce3c86cb79ccad053fa2bd7196c4f4fb81f5a0b1e41ff15e56a8ae80524e7311:

File internal/api/praise_test.go
- 2026-08-24 19:59:53 — part of check-in [f1a6be9a77] on branch praise — Praise: vocabulary, storage, ops
  Any signed-in account may praise any repository it can SEE — no capability letter, because the read gate has already decided whether the repository exists for this caller and past that gate praising is not a privilege anyone needs granting.
  Per account, not per contributor: someone who has never authored an artifact can still say a repository is worth attention, which is why this cannot hang off the contributor pages.
  praise.list filters by the VIEWER, never the owner. Praise is public; the existence of a private repository is not, and this is where the two meet.
  UI deferred: the button belongs in the repo stats strip, which is on the unlanded clone-counts branch. (user: dmestas, size: 4515) [annotate] [blame] [check-ins using]
- 2026-08-24 20:26:30 — part of check-in [0cba46d4ed] on branch praise-ui — Praise UI: a button on the repo, a listing to reverse it
  Restores the backend the trunk merge dropped, and adds the two surfaces that get pressed.
  The button sits in the stats strip beside the clone count, drawn only when there is an account behind it. Pressed state rides on aria-pressed as well as colour.
  /praised is where praise is revisited and withdrawn. It exists apart from /people/{user} because that page lists CONTRIBUTORS derived from the DAG, and a praiser need never have authored anything. (user: dmestas, size: 4515) [annotate] [blame] [check-ins using]
- 2026-08-24 23:12:41 — part of check-in [411e60c2d5] on branch trunk — land praise-ui (user: dmestas, size: 4515) [annotate] [blame] [check-ins using]