Tracking issue for v0.1 completion. Closes the gap between proposal claims and shipped behavior. ## P0 — Make it run / core innovation - [ ] #8 Fix packaging & lazy imports (`code2test --help` currently fails) - [ ] #9 Bounded verify→repair self-healing loop (generator only diagnoses once today) ## P1 — Core / quality - [ ] #10 Shared auto-patch path for `verify --fix` + generation loop - [ ] #11 Intent vector store + similarity, or amend proposal (SQLite vs ChromaDB) - [ ] #12 Real pytest suite for code2test itself - [ ] #13 GitHub Actions CI (install + lint + test matrix) ## P2 — Validation / polish - [ ] #14 Code2TestBench harness + validate headline metrics - [ ] #15 Behavioral-coverage & diagnostic-accuracy in reporting - [ ] #16 Validate & harden Java/JS adapters end-to-end - [ ] #17 Docs: fix install + honest feature status ## Suggested order #8 → #9/#10 → #12/#13 → #11 → #14/#15/#16 → #17
Tracking issue for v0.1 completion. Closes the gap between proposal claims and shipped behavior.
P0 — Make it run / core innovation
code2testruns #8 Fix packaging & lazy imports (code2test --helpcurrently fails)P1 — Core / quality
verify --fixand generation loop #10 Shared auto-patch path forverify --fix+ generation loopP2 — Validation / polish
Suggested order
#8 → #9/#10 → #12/#13 → #11 → #14/#15/#16 → #17