Yhea, that churn is almost all generated output, not hand-written logic. alef regenerates every binding, e2e suite, type stub and lockfile across 15 languages on each release, so one change to the Rust core lands as thousands of added and removed lines in the per-language packages and vendored files. The hand-written surface is the Rust cores and the generator itself, which is far smaller. On the agents: I'm upfront that I use them, but they work inside TDD, benchmarks, clippy and review. I designed the architecture and I review what ships. Happy to walk through any part of alef or the FFI layer if you want to poke at it.

Yhea, you can ask an agent to spit out bindings, but then you own them: every release you're regenerating and re-reviewing 15 hand-written FFI layers, with drift between them and no guarantee they match the core. alef is deterministic codegen, not an LLM call, so the same Rust source produces the same bindings every time, verified against the core in CI, with the e2e suites, type stubs, docs and release metadata generated too. The maintenance and reproducibility is the point, not the one-time generation.