Merged a ticket correcting this mistake.

Which validators need batch lookup support, besides UserDef? Is there a precedent for batch DB lookups? Moving to needs further discussion before considering a possible implementation.

It's unclear to me if this change can be made at this time. Moving to generate further discussion

Moving to bugs and chores with a low priority status. This task looks to be within the scope of our team.

This is likely to be an issue with pywikibot, which is outside of the scope of Interfaces. Moving to Radar to watch for updates in case it turns out to involve an issue with Action API.

Are we the current maintainers of pageDeletion, and is this a feature we can take on as a team? Tagging Ohana for further discussion about who is prepared to add features to pageDeletion.

With regard to T402952, Is this table associated with user_editcount? Since API:allusers can display editcount as an optional usprop, it seems that a user of the API could sort by editcount on their end. If API:allusers were to sort by edit count, why not by any other usprop available? Cautiously this feature seems like it would fundamentally change the allusers endpoint without solving any current problems. Triaging as low priority for now.

Not sure this task is a fit for Interfaces, but it's not obvious to me which team might be able to pick it up. Is there a particular team responsible for maintenance scripts?

I'm going to go through a second time, but I think I found the most obvious strings to update. I'm wondering if those that aren't in the specs should be updated/rewritten, as well.

Restricting to an array seems less disruptive than disallowing PARAM_ISMULTI entirely. What additional tests are needed?

Patches are proposed on each extension. There are unrelated test failures on Workflows, BlueSpiceExtendedSearch, Checklists, ContentStabilization and MenuEditor.

Made edits across wikis; given the range of wikis and variety of pages across languages needing changes, encouraging communities to make associated edits.

Made relevant changes on-wiki for those wikis I had access to; I didn't make changes on individual users' pages. @Krinkle

Taking a look, it seems like the necessary config change was made in 2022 in MainConfigSchema.php.

How do we know the review process is complete? Is there an established benchmark for improvement, or baseline criteria that need to be met, in order to begin endpoint implementation?

In an attempt to summarize the discussion in Code Mob today, on investigation, there are several options for returning the pages/namespace(s) blocked from a user as part of the BlockInfo endpoint. Potentially, we could:

Patch initializes service and adds edits/aggregate endpoint