7e841ad90ee16a6464b842e3c3723e463e26f0d4
Bug fixes are red-then-green: write a failing test that pins the symptom, make the smallest change that turns it green, keep the test as a permanent regression. No fix without a test. Bug fixes do not need orchestrator permission — when a bug is unambiguous (build broken, fixture crashes, refcount underflow, observable wrong output), the fix is autonomous orchestrator work. The user directs features and priorities; bug fixes are mechanical work that ships when the bug is found.
Description
No description provided
Languages
Rust
91.6%
Python
4.6%
C
1.8%
LLVM
1.6%
Shell
0.4%