PR-scoped workflow layer built on top of StrykerJS

Hi StrykerJS team, I’m building an open-source project called **Tautest**: https://github.com/canblmz1/tautest Tautest is a TypeScript CLI and GitHub Action that uses **StrykerJS as the mutation testing engine**, but focuses specifically on **pull request-scoped mutation quality gates**. The goal is not to replace StrykerJS. Tautest is intended to be a workflow layer around StrykerJS that makes mutation testing easier to adopt in everyday PR review workflows. It currently focuses on: - detecting changed source lines in a pull request - running focused mutation testing around affected code - generating Markdown, JSON, and HTML reports - producing GitHub Action summaries - creating PR annotations/comments - generating AI-ready fix prompts for surviving mutants - supporting incremental CI workflows I wanted to ask for your feedback on a few points: 1. Does this positioning make sense from the StrykerJS project’s perspective? 2. Are there any integration patterns you would recommend? 3. Are there any reporting conventions or APIs that Tautest should align with? 4. Would a PR-focused workflow layer like this be useful as an ecosystem tool around StrykerJS? I’m happy to adjust wording, attribution, or implementation details if anything feels misleading or incompatible with the StrykerJS ecosystem. Thanks for building StrykerJS — Tautest would not exist without it.