I (author of the ticket) do not have stake in this and, I guess, neither has WMDE anymore. Maybe with the issue written down and linked to the blubber board this ticket has served its purpose (discoverability). I don't object to closing it.

rely on wikit tokens

It is not well reflected in T258046 but this feature, especially the section

Keep in mind that this is a universe in itself, with complexity only limited by imagination. The beauty of the topic is that it really lends itself to a generic solution. When we touched on this in wikit, design system / token support in storybook was still in its infancy (I was looking at this at the time), but there has been some movement since. Maybe you can find a ready-made building block which works well enough (and potentially contribute to it) to avoid having to create+own a custom one.

Something similar to what you seem to aim for is done when e.g. publishing the data-bridge storybook to https://doc.wikimedia.org/#Wikibase. The repo root is in control and delegates to different sub folders to build their individual documentations.

Not sure if I understand correctly, but sounds like module-alias could be for you.
This is also one of the reasons why we used lerna for the wikit monorepo back in the day.

A data point to prevent anchoring: the causality "only use the ES6 standard to implement new features, and thus we'll be dropping optimal support for IE11" (T178356's gist; @Sarai-WMDE is just the messenger) does not exist. It is only valid in a – somewhat artificial – universe where there is no way for a computer to help us (stern look at T199004).

Maybe it is obvious but everyone working on linting of termbox should be aware that, in addition to the "official" eslint-config-wikimedia, it uses eslint-config-wikimedia-typescript – interpreting the Wikimedia code conventions for the TypeScript language, which had no representation in eslint-config-wikimedia at the time (end of 2019). All changes done should be performed in the awareness that eslint-config-wikimedia-typescript was meant as a stop-gap (see) until eslint-config-wikimedia supports TypeScript; also see former T249304 comments. The situation today may allow for changes to land in central eslint-config-wikimedia instead of taking the indirect route via eslint-config-wikimedia-typescript – for the better of all TypeScript-based projects in Wikimedia land and to eventually eliminate this potentially unexpected aspect.

FWIW lerna-audit now (v1.3.1) does not show the problems anymore which we encountered earlier (e.g.) when using it to tend to monorepos.

The introduced changes are a good step in the right direction - they separate implementation from configuration for the tests and the dedicated library is a nice touch as it keeps this concern out of the individual products and allows for it to be centrally maintained.