Should be a 1 character fix:

https://github.com/wikimedia/mediawiki-extensions-WikibaseLexeme/blob/fbf443600c872e75ef16bb00bda8e61f3fdc31c7/src/WikibaseLexemeHooks.php#L60

Change 437461 had a related patch set uploaded (by Tarrow; owner: Tarrow):
[mediawiki/extensions/WikibaseLexeme@master] Make Lexeme_talk namespace have lowercase T

https://gerrit.wikimedia.org/r/437461

Unlikely to be a real-world problem but worthwhile mentioning that this will break (user) CSS that is based on the classes derived from that (e.g. .page-Lexeme_talk_L42).

Change 437461 merged by jenkins-bot:
[mediawiki/extensions/WikibaseLexeme@master] Make Lexeme_talk namespace have lowercase T

https://gerrit.wikimedia.org/r/437461

@Pablo-WMDE: Is there some policy we need to meet (e.g. the stable interface or similar). Or do we need to get the change announced somewhere?

At this point this should be fine without any announcement. We've made it clear that things are going to change and no-one should rely on Lexeme UI or API being stable.

@Tarrow @Lydia_Pintscher Cool. I suppose there is no harm in pointing such changes out and Lydia and Léa decide what kind of communication it warrants.

I think this can be resolved now or do we wait until it hits production?

+1 with Lydia, we don't have a stable policy for Lexemes yet. However, I like to be informed of the changes, so I can go to the person who asked for it and say "look, we did the thing" :)

FYI, in the MoM board we have a column "needs announcement" between "PM review" and "done", that's an example of process to make sure that things are announced. I let you think on how you would like to do :)

Is there anything left to do here or can this be closed?