Building server-key-injection by specialization

server-key-injection is an SSH certificate issuer. A user connects with ssh -A, authenticates, and receives a new, short-lived keypair and certificate in their existing ssh-agent. Production hosts trust the user CA and make their authorization decision locally. It is also an experiment in software development with a language model. No line of code outside /developer was written by a human. The source tree, tests, configuration, installer, and documentation were generated by an LLM in a code-generation harness. I wrote, reviewed, and repeatedly revised the requirements and their specialised derivatives. That was the whole point of the exercise: The project is as much a proof of concept for SSH key injection as it is a test of a development process. More precisely, I wanted to answer three questions: Can I develop a systematic vibecoding workflow, rather than merely have a sequence of lucky chat sessions? What code quality does that workflow actually produce? What teachable rules and…