Progress of tickets; new Typosauris system, be patient

You created a issue and received the good news a pull request was created? Well, its gone. Not in the merged way.

They were all made by the old bots. The old system was a project manager bot (the one that communicates in ticket) and that gave instructions to the Devplace Code CLI application. But the CLI application does not give enough output to work with. It was a black box.

There is a newer system, but that only triggrs when actuallly assigned to typosaurus in gitea. I will do this manually in batchies so i can optimize per ticket etc. Just letting a system build 19 tickets is no way to test.

Automating a system this way is really challengiing because I only allow the quality that it would have if i would write it myself using claude. This means, full compattibility with claude eco system (agents, commands, rules, workflows, md files) on global and local level. You can imagine, this takes some time and testing.

Old system: solo developer on your issue. New system: a team of developers with each their own speciality on your ticket. Ironically, the team of eevelopers seems to be cheaper. It will post the costs it makes. It`s cents, in a very bad case, ten cents. But thats all.

Important is ticket quality.