rbrooks/Quest-Board
Watch
1
0
Fork
You've already forked Quest-Board
 0
Code Issues 58 Pull requests 7 Projects Releases 76 Packages Wiki Activity Actions

feat(feedback): the readout says who has rated, and what (#1257) #1322

Closed
claude-bot wants to merge 0 commits from feat/1257-who-rated into main
pull from: feat/1257-who-rated
merge into: rbrooks:main
Conversation 1 Commits - Files changed -
claude-bot commented 2026-11-02 23:09:20 +00:00
Collaborator
Copy link

The owner asked for this on 2 Nov. With "3 raters" on the names readout they couldn't tell whether those were all them or someone else, or what each person had reviewed.

On the feedback site's admin readout, Name sampler tab:

  • "Who has rated": one row per rater, newest first. It shows:

    • the name they gave;
    • which link saved it (group or external, the existing badge);
    • how many marks;
    • the styles they marked, with counts, and "+ note" where they left one;
    • when they last saved.

    Two rows with the same name show plainly as one person on two devices or browsers.

  • "Rated by": a line on each style panel, naming who marked it and how many marks each.

This changes only static/admin.html, with no server change. It's already live on the dev feedback site (data backed up first).

Checked:

  • the script parses (node --check);
  • a render against a throwaway copy of the site, with three made-up raters (two named "Ryan" on the group link, one "Sam" on the external link), shows the table and "Rated by" correctly, with no console errors.

🤖 Generated with Claude Code

The owner asked for this on 2 Nov. With "3 raters" on the names readout they couldn't tell whether those were all them or someone else, or what each person had reviewed. On the feedback site's admin readout, Name sampler tab: - **"Who has rated":** one row per rater, newest first. It shows: - the name they gave; - which link saved it (`group` or `external`, the existing badge); - how many marks; - the styles they marked, with counts, and "+ note" where they left one; - when they last saved. Two rows with the same name show plainly as one person on two devices or browsers. - **"Rated by":** a line on each style panel, naming who marked it and how many marks each. This changes only `static/admin.html`, with no server change. It's already live on the dev feedback site (data backed up first). **Checked:** - the script parses (`node --check`); - a render against a throwaway copy of the site, with three made-up raters (two named "Ryan" on the group link, one "Sam" on the external link), shows the table and "Rated by" correctly, with no console errors. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(feedback): the readout says who has rated, and what (#1257)
All checks were successful
CI / Backend lint (ruff) (pull_request) Successful in 31s
Details
CI / Feedback site tests (pull_request) Successful in 48s
Details
CI / Does this change touch the recording path? (pull_request) Successful in 18s
Details
CI / Which journeys does this change need? (pull_request) Successful in 18s
Details
CI / Synthetic session harness (no GPU, no LLM) (pull_request) Has been skipped
Details
CI / Bot/backend version sync (pull_request) Successful in 27s
Details
CI / Docker image build (pull_request) Successful in 27s
Details
CI / End-to-end journeys (desktop) (pull_request) Has been skipped
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 1m59s
Details
CI / Bot tests and audit (pull_request) Successful in 2m7s
Details
CI / Frontend (shard 2/2) (pull_request) Successful in 15m44s
Details
CI / Frontend (shard 1/2) (pull_request) Successful in 17m46s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 1h9m13s
Details
36bc3e6d5e 
Asked for on 2 Nov: with three raters the owner could not tell whether
they were all one person. A table of raters (the name they gave, the
link that saved it, marks, the styles marked with notes, last saved),
and a "Rated by" line on each style.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude-bot commented 2026-11-03 19:29:04 +00:00
Author
Collaborator
Copy link

This PR's commit is in main through #1329, which was built on this branch and merged on 2026-11-03 at the owner's request. Forgejo refuses a second merge (405), so I'm closing this one as landed. The "Who has rated" readout is live and on main.

This PR's commit is in main through #1329, which was built on this branch and merged on 2026-11-03 at the owner's request. Forgejo refuses a second merge (405), so I'm closing this one as landed. The "Who has rated" readout is live and on main.
claude-bot closed this pull request 2026-11-03 19:29:19 +00:00
All checks were successful
CI / Backend lint (ruff) (pull_request) Successful in 31s
Required
Details
CI / Feedback site tests (pull_request) Successful in 48s
Required
Details
CI / Does this change touch the recording path? (pull_request) Successful in 18s
Required
Details
CI / Which journeys does this change need? (pull_request) Successful in 18s
Required
Details
CI / Synthetic session harness (no GPU, no LLM) (pull_request) Has been skipped
Required
Details
CI / Bot/backend version sync (pull_request) Successful in 27s
Required
Details
CI / Docker image build (pull_request) Successful in 27s
Required
Details
CI / End-to-end journeys (desktop) (pull_request) Has been skipped
Required
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 1m59s
Required
Details
CI / Bot tests and audit (pull_request) Successful in 2m7s
Required
Details
CI / Frontend (shard 2/2) (pull_request) Successful in 15m44s
Required
Details
CI / Frontend (shard 1/2) (pull_request) Successful in 17m46s
Required
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 1h9m13s
Required
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
backend
Issue related to the backend

  
bot
Issue related to the bot

  
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
frontend
Issue related to the frontend

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
recording
Issue related to the recording system

  
security
Security hardening / vulnerability work

  
wontfix
This won't be fixed

No labels
backend
bot
bug
duplicate
enhancement
frontend
help wanted
invalid
question
recording
security
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/Quest-Board!1322
No description provided.