@teqfw/di switches to an LLM-first workflow
About a week ago I changed the development of @teqfw/di to a new workflow: I now write not only code and my own rules, but first of all documentation for an LLM agent, which then applies those rules across large numbers of small files.
This shift affected not only the way I work, but also the package architecture itself. Version
@teqfw/di 2.0.0
is incompatible with the 1.2.0 line because the dependency declaration concept changes there.
A detailed explanation of why I made this move, how the Codex agent rewrote the library, and how the rules for people and agents are changing is collected on a separate library page: Declaration of (Non)Dependencies for ESM .
In short, a person now defines the boundaries, and the agent fills them with working code. For small, repeatable changes, that is already more practical than trying to keep the whole project in manual mode.