>Have 2 repositories, stable and unstable. The unstable repo would be used the same way the current singular one is. Constantly updated without attention paid to changelogging or version compatibility.
We are currently in middle of some things in development so immediately creating a stable version doesn't make sense at the moment - but eventually, we can maybe distribute kokonotsuba in a zip file on github.io homepage.
Those who benefit from the repo being on github are those who are familiar with using git, who are already likely advanced enough to deal with a rolling release software.

>The stable repo could also consider removing some of Heyuri's cultural footprint on the software to make it more generalized for a wider audience. Many board admins could view the default inclusion of heyuri fortunes, emotes, etc as them using HEYURI's software rather than using kokonotsuba. This is disadvantageous
That's fair. Currently it's just a few things in static/ that has Heyuri print and could be changed. We mostly didn't have alternatives for certain stuff, but if Kokonotsuba itself had some personality (like a mascot or icon), it could have Kokonotsuba-default fullbanners. I think 300x100 banners already have a boring placeholder, we can just go with stuff like that too.

>I do not support removing credits to heyuri however
There already isn't a lot of credit to heyuri besides hijacks in source codes of js files
The credit goes to kokonotsuba's home page, and Heyuri is mentioned there.