feat(project): define project structure #72
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/kronai!72
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/0004-define-project-structure"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Define the project directory layout, Python module structure, and dependency files for the KronAI project.
Why
Establishes the foundational project structure needed for all subsequent Phase 1 tasks.
Testing
Breaking Changes
None.
Notes
Sets up
src/kronai/package with core module stubs (type hints + docstrings),tests/unit/andtests/integration/directories, and dependency files.Closes #0001
Closes #0002
Closes #0003
Closes #0004
Automated Review — PR #72
Result: COMMENT (no blocking issues found; suggestions and questions below)
Suggestions
src/kronai/mcp.py:24,40— Docstring format inconsistency.RaisesandReturnssection headers missing trailing colon. Rest of codebase usesRaises:/Returns:(numpy-style). Ruff D416 will flag this.src/kronai/llm.py:38—**kwargs: floattoo restrictive. OpenAI-compatible clients pass non-float params likestop(list[str]),top_p, etc. Suggest**kwargs: Anyor a TypedDict.src/kronai/mcp.py:39—get_toolsreturn typelist[dict[str, str]]likely too narrow. MCP tool definitions include nestedinputSchemadicts. Considerlist[dict[str, Any]].pyproject.toml—fail_under = 0.5is functionally a waiver. Fine for scaffold, but add a TODO to raise once implementation starts.Questions
.forgejo/workflows/ci.yml—upload-artifact@v4for coverage HTML was removed. Intentional?Yes coverage was removed so that CI would pass until actual code was in there to be able to enforce the requirement.
Correcting my review — no blocking issues, so this is an approval. Suggestions from previous review still stand (docstring format, kwargs type, mcp return type, fail_under TODO).