HISE Transformation to the new age

[Christoph Hart]

Alright guys, I've been working on the automated workflow for handling issues. The idea is to give you a fixed set of guidelines that can classify issues / PRs into "contributor fixable" and "requires maintainer review".

Here's a nice summary of the proposed event flow:

https://gist.github.com/christoph-hart/394f9db01f97864e4c6ecd886c5e18ca

This will become part of the MCP server so if you're running a AI agent, you can simply launch the /contribute tool and it will guide you through the process. On the other side of the process it's me sitting around getting a nicely formatted PR that I can review quick and merge or reject with a comment or close altoghether.

I've tested this with a few real issues / PRs:

• one that I created myself, let the agent analyse and fix and then automerge: https://github.com/christophhart/HISE/pull/880 - the entire process from bug analysis to merge is handled by the MCP tool
• one that Dave created yesterday which went through the analysis without flagging concerns and thus got merged after a quick glance over the AI assessment: https://github.com/christophhart/HISE/pull/879
• one from David that the analysis (correctly) flagged as big fat no because it does affect the handling of script files in general: https://github.com/christophhart/HISE/pull/871

The response for the last one feels super icky because the AI starts talking to David like as if it would be a human, but I think if we iterate on this process it should streamline this entire procedure and vastly increase my PR merge speed.