toolkit-contribute

To prepare customized files for upstream submission, identify changes with generic value and evaluate them against a 10-point generalizability gate. The toolkit then validates these changes with the full test suite before generating submission instructions.

The 10-point generalizability gate is a checklist used to evaluate customized files and ensure the improvements are generic enough for upstream toolkit inclusion. It filters out project-specific changes before preparing patches.

Generate patch or PR submission instructions for downstream maintainers by running the contribution workflow after your customized files pass the generalizability gate and the full toolkit test suite executes successfully.

Yes, the upstream contribution workflow is fully configurable through toolkit.toml and deliberately avoids project-specific paths or defaults. This ensures the submission process remains generic and portable across different environments.

Yes, the upstream contribution workflow supports both fork and direct-push workflows. You can configure your preferred submission method using toolkit.toml to match your repository's access model.

Running the full toolkit test suite before submitting an upstream patch ensures your generic improvements do not break existing functionality. It validates the customized files and guarantees the changes are safe for downstream maintainers to integrate.