Here another example of this -- but note that this was back in March (there might have already been UX improvements since)

Yes, that's correct. This will be crucial to have in Q3/FY24/25 ( Q1 calendar year 2025), in order to be able to find the right Lexemes for a given Item (i.e. to go from Q144 to L1122). The only other option to do so would be through the SPARQL endpoint, which has its own set of issues.

This is now implemented on Wikifunctions, e.g. go to https://www.wikifunctions.org/wiki/Z10000 and click or tap on the ZID.

Just a few thoughts, can be ignored: adding an icon makes the UI more busy - but an icon that shows up on hover over the ID could help with discoverability of that feature. That wouldn't be helpful on mobile though.

My understanding is that the problem is indeed (as @cmassaro points out) with the Z17646/same reference function.

My explanation for this is (but it's just a theory): pages have been imported to Wikifunctions and Wikidata from other wikis including their edit history, and these had edits from before the launches, and get counted here.

I wonder if we can raise that ban again? I think the crawler in combination with T374241 was causing the site instability issue. I would suggest that we de-ban the bot, and see if it causes issues again, because I don't think that the crawling itself would cause the issues described here.

This should be resolved now. Please let us know if not. It was the same root cause as T374241

This should have stopped occurring. The issue was the following edit on Wikifunctions, which was reverted (here is the revert). That one triggered an infinite recursion during validation. Geno's patch above should make this not happen again, and for now the revert should stop the ongoing issues.

The composer.local.json file is not being set through the setup script. The content is given in the README file below as the following:

It would be good to improve error messages for all standard libraries which are disabled. or not working.

action=raw just displays whatever is stored. Whether we should be storing in normal or canonical (and whether it matters) is probably the underlying question that we should answer first.

Ah, it only works int he Edit mode. I defer this question to @AAlhazwani-WMF : should we change the label, keep everything as is, or change the functionality (i.e. turn it into an explorer on view). We can then triage this again, based on the decision.

The function explorer in fact allows you to check on other functions too, out of the widget. It is indeed meant as a widget to explore functions. If there are no more feedback on this, I would close this as invalid.