hCaptcha isn't available on the beta cluster, because of sensitivity around how hCaptcha enterprise's risk scores need to be handled. So unless you want to use integration test keys on wikidata beta (https://docs.hcaptcha.com/#integration-testing-test-keys), I would just skip that step.

Thanks!

Moving to in refinement until @ROdonoghue-WMF has a chance to review and sign off on the changes.

In T437659#12371578, @Tsevener wrote:

Note these aren't page edits, so I'm not sure if they should be prioritized for hCaptcha. But here's more that Claude dug up:

Which version are you on?

In T438934#12357201, @Dreamy_Jazz wrote:

Retrieve the feed, to be able to see revisions that are not considered handled (and allow for fetching the feed with parameters for "include handled revisions" and "include false positives", support pagination of responses, etc)

Could users not just use the revisions or recentchanges APIs with tag filters for this?

In T438050#12363302, @Dreamy_Jazz wrote:

Perhaps we could consider deleting the notifications from the DB once handled, and then re-creating them if the verdict is removed?

In T438235#12346382, @ROdonoghue-WMF wrote:

Proposed design for the recent-edits filter.

I’ve given this its own “Recent edits” section in the filter panel rather than grouping it under “Show additional items”, since it controls the age of revisions shown rather than their review status.

For the vandalism inbox, “Include recent edits (last 10 minutes)” would be unchecked by default, meaning edits made within the last 10 minutes are hidden to reduce churn from revisions that may be quickly reverted through existing workflows. Users can enable the option if they want to see those edits as well.

The helper text explains why recent edits are hidden. We should also make the active default visible outside the filter panel so users understand that the queue is intentionally excluding the newest revisions.

See example in Figma under 'ready for dev': https://www.figma.com/design/l8xYc2kynkR0t7CHwXAHyt/DE4.1-Content-Policy-Review?node-id=2073-4721&t=0d2chZRCLVweK2tW-1

We no longer need this task, because we switched from the table diff to inline diff format. Sorry for not closing this out earlier, and thanks for the patch.

This was implemented in another task/patch.

This task is pending T437493: UX testing for AbuseReview

Removing from the sprint and epic until we've figured out the mobile view, which will follow after the UX research.

Assigning to @ROdonoghue-WMF for now, to propose a design

Linking T401808: Allow Client Hints data to be used to prevent the save of edits to this one

@ROdonoghue-WMF would you be able to propose a design for this please?