This works on Wikidata only, not on cilents.

In https://www.wikidata.org/wiki/Wikidata:Property_proposal/replacement_property, another use case is provided.

Note the interface (both JavaScript GUI and special page) currently does not support edit summary (T47224: [Story] Custom edit summaries).

See T87645: Existing pages without ability to reach and obviously wrong namespace.

As these should be solved together

See T87645: Existing pages without ability to reach and obviously wrong namespace.

Special:MergeItem or Special:MergeLexeme already check whether two entities are the same. Special:RedirectEntity does not.

Lower the priority, now I have fixed the specific lexeme. The issue can still be debugged at https://test.wikidata.org/wiki/Lexeme:L49

As it makes contributions impossible to view.

I have successfully created https://www.wikidata.org/wiki/Translations:MediaWiki:Search-nonefound. When this is created, https://www.wikidata.org/wiki/MediaWiki:Search-nonefound/zh is created too.

This is because the page MediaWiki:Linkshere is able for translation (with <translate> tag). It was removed in 2015 (see https://commons.wikimedia.org/wiki/MediaWiki_talk:Linkshere). Currently there's no translatable interface messages in Commons.

@Lydia_Pintscher Is this task still useful?

Enabling Structured Discussion on talk pages of Schema pages may be an idea if we want to track individual comments.

Is it a human-readable discussion? If yes why not use talk page?

Probably we can just use test.wikidata.org for this, if the Structured Wikiquote project will not replace existing Wikiquote and we also hold Structured Wikiquote data in Wikidata instead of a brand new project.

Still happens:

See T87645: Existing pages without ability to reach and obviously wrong namespace and T109238: Clean up broken namespace pages across Wikimedia sites.

These types of dumps should be considered:
Terms

1. Dump of all labels
2. Dump of all descriptions
3. Dump of all aliases
4. Dumps of all labels in a specific language
5. Dumps of all descriptions in a specific language
6. Dumps of all aliases in a specific language
7. Dump of all terms (optional)
8. Dumps of all terms in a specific language (optional)

We need the language input field - using the interface language is not enough. See T108907: Add a "language" field to Special:NewItem

This is still a bug...

API also returned (already passed) block status:

more:
https://codesearch.wmflabs.org/search/?q=defintion&i=fosho&files=(js|php|xml)%24&repos=
https://codesearch.wmflabs.org/search/?q=seperat&i=fosho&files=(js|php|xml)%24&repos=

As a long-term solution I propose to build a similar tool in MediaWiki, see T203557: Create a Edit group extension.

As each senses may have some statements, we may create a new special page Special:MergeSense to handle that.