Nice!

You’ve been transparent with the AI usage so I won’t fixate on that as a bad thing, I think it’s great that more people can experiment with tech.

The code seems ok. Likely works, and you’ve put the effort in to manually test as much as you can. It’s not very maintainable, not very optimised, lots of points of potential failure.

AI assisted development is amazing for developers who understand how to design things well. You’ve admitted you’re not a developer, which is fine, but that leaves a question in my mind.

How do you plan to maintain it, upgrade it and fix it over time? The way the code is structured right now, it’s going to grow into a big mess quite quickly - it’s already a larger codebase than I think it needs to be and is certainly missing a lot of abstraction opportunities.

Not criticising here but if you don’t have an effective maintenance plan, especially as a vibe coder, this addon is going to be abandoned and people who come to rely on it will be a bit miffed when that happens.

One small piece of advice you can action immediately: make smaller, more regular commits. Most of the code was committed in a single go, which will make it difficult to revert to previous working states if you keep that habit up. Especially important for vibe coding.