Testing Community Projects agains Regression

I was working on a complex form thing not long ago in late 2025 ([hokulea/pahu](https://github.com/hokulea/pahu), then used in [hokulea](https://github.com/hokulea/hokulea)). Types were as expected within the limits of glint, but correct and working. I have renovate running and for pahu it updated glint updates as they were coming, all good. For hokulea, the update fails on declarations: https://github.com/hokulea/hokulea/pull/608 Not because my types are wrong, but there was a regression missinterpreting my types as wrong. The naive way would be to extract a minimal example and submit it as test-case. This is quite a surgery. I have a suspicion, this is isolating only an incomplete piece. (And in my case would need to be able to copy types from across multiple projects). Hokulea is not the only complex project, there are others, too. So I'm asking for a CI step to run this against a selection of OSS community projects living at the limits of ember's type spectrum. What happens when a community project fails on CI? - Failing test is expected: Provide a patch with `// @ts-expect-error` comment - Failing test is unexpected: Regression detected OR: Allow the CI to fail, but inspect the results (which likely never gonna happen).