Severity: medium | Category: docs | Phase: P2.22
Problem
Verified: a 9,569-line test_output.log and 393KB coverage.json are tracked and ship in the sdist; OpenAPI declares MIT while the package is AGPL-3.0; events_v2 docstring falsely claims auth is missing; module-level print() dumps CORS config; PRD.md describes the abandoned v1 multi-agent product with a broken SPRINTS.md link; AGENTS.md is ~2 phases stale and references a deleted server/ dir; README documents a nonexistent cf tui (actual: cf dashboard).
Evidence
test_output.log:1, coverage.json, codeframe/ui/server.py:596 (MIT vs AGPL), :640 (print), codeframe/ui/routers/events_v2.py:6 (stale auth TODO), PRD.md:10, AGENTS.md:5, README.md:275 (cf tui)
Acceptance criteria
Tracked scratch artifacts removed + gitignored; license_info set to AGPL-3.0; stale events_v2 TODO deleted; CORS print → logger; PRD.md/AGENTS.md refreshed or pointed at CLAUDE.md; README cf tui → cf dashboard.
Dependencies
None
Filed from the SaaS launch-readiness audit. Atomic: one developer, one session. Work order: strictly P0.1 → P3.12 (no forward dependencies).
Severity: medium | Category: docs | Phase: P2.22
Problem
Verified: a 9,569-line
test_output.logand 393KBcoverage.jsonare tracked and ship in the sdist; OpenAPI declares MIT while the package is AGPL-3.0;events_v2docstring falsely claims auth is missing; module-levelprint()dumps CORS config;PRD.mddescribes the abandoned v1 multi-agent product with a brokenSPRINTS.mdlink;AGENTS.mdis ~2 phases stale and references a deletedserver/dir; README documents a nonexistentcf tui(actual:cf dashboard).Evidence
test_output.log:1,coverage.json,codeframe/ui/server.py:596(MIT vs AGPL),:640(print),codeframe/ui/routers/events_v2.py:6(stale auth TODO),PRD.md:10,AGENTS.md:5,README.md:275(cf tui)Acceptance criteria
Tracked scratch artifacts removed + gitignored;
license_infoset to AGPL-3.0; staleevents_v2TODO deleted; CORSprint→logger; PRD.md/AGENTS.md refreshed or pointed at CLAUDE.md; READMEcf tui→cf dashboard.Dependencies
None
Filed from the SaaS launch-readiness audit. Atomic: one developer, one session. Work order: strictly P0.1 → P3.12 (no forward dependencies).