given this is impacting Minerva and Vector 2022, this sounds very much like an issue with the hook inside Flow. Looks like it's removing the menu item from p-namespaces BUT not p-associated-pages. Growth team, let me know if I can help.

Seems close enough to the criteria for issues we will work on in our "non maintained" projects, so moving this to current sprint.

I think the issue is this block of code:

	if ( isset( $links['namespaces']['topic_talk'] ) ) {
				// hide discussion page in Topic namespace(which is already discussion)
				unset( $links['namespaces']['topic_talk'] );
				// hide protection (topic protection is done via moderation)
				unset( $links['actions']['protect'] );
				// topic pages are also not movable
				unset( $links['actions']['move'] );
			}

It now also needs to apply to $links['associated-pages'] when Skin::supportsMenu('associated-pages') is truthy (but you can also do it unconditionally).

Change 886452 had a related patch set uploaded (by Mainframe98; author: Mainframe98):

[mediawiki/extensions/Flow@master] Hide non-existing Topic_talk namespace in associated-pages portlet

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

I created a Patch demo for the supplied patch with a test topic: https://patchdemo.wmflabs.org/wikis/0af35a07c6/wiki/Topic:Xbzfeyhzxgxx3yq9?useskin=minerva.

Change 886452 merged by jenkins-bot:

[mediawiki/extensions/Flow@master] Hide non-existing Topic_talk namespace in associated-pages portlet

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