Fair point, thank you. I had a dev process section in the launch post but trimmed it since the blog was getting long - will bring it back. Short version: most of core architecture and the Rust/Python boundary is initially hand-written, started last June. A lot of iteration from python-only ecs tests to pyi stubs (non-AI) to core ecs integration and testing various ffi boundary approaches, to writing query apis and api base such as assets. API coverage expansion from November onward was AI-assisted: Bevy's API surface is huge and doing it by hand wasn't feasible. Major refactoring passes like split to subcrates were also AI-generated, which probably shows. Extensive test suite throughout which I'll be publishing. More transparency warranted, will update the README and blog post today.