- Add start-issue NUM=X target to create structured issue workspaces
- Add add-test target for iterative test generation within workspace
- Add workspace-status target to monitor active workspace state
- Add finish-issue target to move tests to main and cleanup workspace
- Create workspace structure with requirements.md and test_plan.md templates
- Include .markitect_workspace/ in .gitignore for temporary development files
- Enable multiple test generation per issue with proper organization
- Provide guided workflow for issue breakdown and test planning
This replaces single test generation with comprehensive workspace approach
supporting complex issues requiring multiple test scenarios.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add test-from-issue NUM=X target to generate test skeletons from gitea issues
- Integrate Claude Code requirement checking and issue data fetching
- Provide comprehensive test generation guidance with TDD best practices
- Include issue details, test naming conventions, and pytest requirements
- Enable systematic conversion of issue backlog into test-driven development
- Support error handling for non-existent issues
This establishes the core infrastructure for issue-driven TDD workflow
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add list-issues target for comprehensive issue overview
- Add show-issue NUM=X target for detailed issue inspection
- Add list-open-issues target for active backlog filtering
- Configure gitea API endpoints with proper URL handling
- Include error handling and jq fallback support
- Enable command-line access to issue tracking and backlog
This establishes foundation for issue-driven TDD workflow
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Create ProjectDiary.md with reverse chronological milestone tracking
- Add make add-diary-entry target with Claude Code prerequisite check
- Include initial entry documenting today's infrastructure setup
- Track contributors, time estimates, and AI token usage
- Provide structured format for future development logging
- Guide users through diary entry creation process
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Create comprehensive project status digest documentation
- Add make update-digest target with Claude Code prerequisite check
- Include current architecture, features, and development approach
- Document repository structure and getting started guide
- Add digest update workflow for version releases
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add venv-status target to check current shell activation
- Detect if venv exists but not activated vs actively running
- Handle different venv active vs project venv scenarios
- Use realpath for robust path comparison across symlinks
- Clean output with --no-print-directory flag
- Integrate status check into help target
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>