refactor: remove obsolete issue management system in favor of issue-facade

Complete cleanup of the legacy TDD AI and issue management system, establishing clear separation of concerns as requested. All issue handling is now provided by the standalone issue-facade system.

Removed components:
- TDD AI framework (tddai/ directory and tddai_cli.py)
- Legacy issue management CLI commands and services
- Issue-related Makefile targets and helper commands
- Obsolete tests and infrastructure dependencies
- Finance modules that depended on the old issue system

Updated:
- Makefile: Removed issue-*, tdd-*, and test-from-issue commands
- CLI framework: Simplified to core functionality only
- Documentation: Added deprecation notice for old config system

The issue-facade now serves as the universal CLI for issue tracking,
providing backend-agnostic interface to GitHub, GitLab, Gitea, and
local SQLite storage as documented in issue-facade/README.md.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
tegwick 2025-10-24 21:25:04 +02:00
parent cb94c92fc0
commit a8e5b4b044
58 changed files with 11 additions and 14628 deletions

260
Makefile
View file

@ -1,7 +1,7 @@
# MarkiTect - Advanced Markdown Engine
# Makefile for common development tasks
.PHONY: help setup install-dev install-home install-home-venv install-deps install-deps-force install-deps-venv install-system list-deps setup-dev test build clean update status lint format check-deps venv-status update-digest add-diary-entry issue-list issue-show issue-list-open issue-create issue-close issue-close-enhanced issue-close-batch issue-get issue-csv issue-json issue-high test-from-issue tdd-start tdd-add-test tdd-finish tdd-status test-status test-new test-coverage test-arch test-foundation test-infrastructure test-integration test-domain test-service test-application test-presentation test-quick test-layers test-random test-random-seed test-random-repeat test-install-randomly test-clean test-tdd test-changed test-module test-cache-clean test-efficient cli-help release-status release-validate release-prepare release-build release-publish release-dry-run chaos-validate chaos-matrix chaos-inject chaos-report cost-help cost-note-issue
.PHONY: help setup install-dev install-home install-home-venv install-deps install-deps-force install-deps-venv install-system list-deps setup-dev test build clean update status lint format check-deps venv-status update-digest add-diary-entry test-status test-new test-coverage test-arch test-foundation test-infrastructure test-integration test-domain test-service test-application test-presentation test-quick test-layers test-random test-random-seed test-random-repeat test-install-randomly test-clean test-tdd test-changed test-module test-cache-clean test-efficient cli-help release-status release-validate release-prepare release-build release-publish release-dry-run chaos-validate chaos-matrix chaos-inject chaos-report cost-help
# Default target
help:
@ -28,7 +28,7 @@ help:
@echo " test - Run all tests"
@echo " test-status - Show test status summary without re-running"
@echo " test-new - Create new test file template"
@echo " test-coverage ISSUE=X - Analyze test coverage for issue"
@echo " test-coverage - Analyze test coverage"
@echo " build - Build the package"
@echo " lint - Run code linting"
@echo " format - Format code"
@ -49,7 +49,6 @@ help:
@echo ""
@echo "Cost Tracking:"
@echo " cost-help - Show cost tracking commands and usage"
@echo " cost-note-issue ISSUE=X INPUT_TOKENS=N OUTPUT_TOKENS=M - Generate cost note for issue"
@echo ""
@echo "Architectural Testing:"
@echo " test-arch - Run all tests in architectural order"
@ -87,27 +86,6 @@ help:
@echo " update-digest - Update ProjectStatusDigest.md (requires Claude Code)"
@echo " add-diary-entry - Add new entry to ProjectDiary.md (requires Claude Code)"
@echo ""
@echo "Issue Management:"
@echo " issue-list - Show all gitea issues with status and priority"
@echo " issue-list-open - Show only open issues (active backlog)"
@echo " issue-create TITLE='...' BODY='...' - Create a new issue (or BODY_FILE='/path/to/file.md')"
@echo " issue-show ISSUE=X (or NUM=X) - Show detailed view of specific issue"
@echo " issue-close ISSUE=X [COMMENT='reason'] - Close an issue and mark as completed"
@echo " issue-close-enhanced ISSUE=X [WORK='description'] - Close issue with enhanced functionality"
@echo " issue-close-batch NUMS='X Y Z' [COMMENT='reason'] - Close multiple issues at once"
@echo " issue-get - Export compact issue index to ISSUES.index"
@echo " issue-csv - Export issues as CSV for spreadsheet processing"
@echo " issue-json - Export issues as JSON for programmatic processing"
@echo " issue-high - Export only high/critical priority issues"
@echo ""
@echo "Test-Driven Development:"
@echo " test-from-issue ISSUE=X - Generate test skeleton from issue (requires Claude Code)"
@echo ""
@echo "TDD Workspace:"
@echo " tdd-start ISSUE=X - Start working on issue (with requirements validation)"
@echo " tdd-add-test - Add test to current issue workspace"
@echo " tdd-status - Show current workspace state"
@echo " tdd-finish - Complete issue work (moves tests to main)"
@echo ""
@echo "Requirements Engineering:"
@echo " validate-requirements - Analyze foundations before development"
@ -569,202 +547,7 @@ add-diary-entry:
# Git repository and API configuration
GITEA_URL := http://92.205.130.254:32166
REPO_OWNER := coulomb
REPO_NAME := markitect_project
ISSUES_API := $(GITEA_URL)/api/v1/repos/$(REPO_OWNER)/$(REPO_NAME)/issues
# Issue workspace configuration
WORKSPACE_DIR := .markitect_workspace
CURRENT_ISSUE_FILE := $(WORKSPACE_DIR)/current_issue.json
# List all gitea issues
issue-list: $(VENV)/bin/activate
@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py list-issues
# Show detailed view of a specific issue
issue-show: $(VENV)/bin/activate
@ISSUE_NUM=""; \
if [ -n "$(ISSUE)" ]; then \
ISSUE_NUM="$(ISSUE)"; \
elif [ -n "$(NUM)" ]; then \
ISSUE_NUM="$(NUM)"; \
fi; \
if [ -z "$$ISSUE_NUM" ]; then \
echo "❌ Please specify issue number: make issue-show ISSUE=5 (or NUM=5)"; \
exit 1; \
fi; \
PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py show-issue $$ISSUE_NUM
# List only open issues (active backlog)
issue-list-open: $(VENV)/bin/activate
@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py list-open-issues
# Create a new issue
issue-create:
@if [ -z "$(TITLE)" ]; then \
echo "❌ Please specify issue title: make issue-create TITLE='Fix bug' BODY='Description'"; \
echo "❌ Or use: make issue-create TITLE='Fix bug' BODY_FILE='/path/to/body.md'"; \
exit 1; \
fi
@if [ -z "$(BODY)" ] && [ -z "$(BODY_FILE)" ]; then \
echo "❌ Please specify either BODY='...' or BODY_FILE='/path/to/file.md'"; \
exit 1; \
fi
@echo "📋 Creating new issue..."
@echo "📋 Title: $(TITLE)"
@if [ -n "$(BODY_FILE)" ]; then \
tea issue create --title "$(TITLE)" --description "$$(cat $(BODY_FILE))"; \
else \
tea issue create --title "$(TITLE)" --description "$(BODY)"; \
fi
# Close an issue and mark as completed
issue-close: $(VENV)/bin/activate
@ISSUE_NUM=""; \
if [ -n "$(ISSUE)" ]; then \
ISSUE_NUM="$(ISSUE)"; \
elif [ -n "$(NUM)" ]; then \
ISSUE_NUM="$(NUM)"; \
fi; \
if [ -z "$$ISSUE_NUM" ]; then \
echo "❌ Please specify issue number: make issue-close ISSUE=5 (or NUM=5)"; \
exit 1; \
fi; \
if [ -n "$(COMMENT)" ]; then \
echo "🔄 Closing issue #$$ISSUE_NUM with comment..."; \
PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py close-issue $$ISSUE_NUM --comment "$(COMMENT)"; \
else \
echo "🔄 Closing issue #$$ISSUE_NUM..."; \
PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py close-issue $$ISSUE_NUM; \
fi; \
echo "✅ Issue #$$ISSUE_NUM closed successfully!"
# Close issue using dedicated issue_closer.py script (enhanced functionality)
issue-close-enhanced: $(VENV)/bin/activate
@ISSUE_NUM=""; \
if [ -n "$(ISSUE)" ]; then \
ISSUE_NUM="$(ISSUE)"; \
elif [ -n "$(NUM)" ]; then \
ISSUE_NUM="$(NUM)"; \
fi; \
if [ -z "$$ISSUE_NUM" ]; then \
echo "❌ Please specify issue number: make issue-close-enhanced ISSUE=5 (or NUM=5)"; \
exit 1; \
fi; \
if [ -n "$(WORK)" ]; then \
echo "🔄 Closing issue #$$ISSUE_NUM with completion message..."; \
PYTHONPATH=. $(VENV_PYTHON) tddai/issue_closer.py $$ISSUE_NUM --work-completed "$(WORK)"; \
elif [ -n "$(COMMENT)" ]; then \
echo "🔄 Closing issue #$$ISSUE_NUM with comment..."; \
PYTHONPATH=. $(VENV_PYTHON) tddai/issue_closer.py $$ISSUE_NUM --comment "$(COMMENT)"; \
else \
echo "🔄 Closing issue #$$ISSUE_NUM..."; \
PYTHONPATH=. $(VENV_PYTHON) tddai/issue_closer.py $$ISSUE_NUM; \
fi
# Close multiple issues at once using issue_closer.py
issue-close-batch: $(VENV)/bin/activate
@if [ -z "$(NUMS)" ]; then \
echo "❌ Please specify issue numbers: make issue-close-batch NUMS='42 43 44'"; \
exit 1; \
fi
@if [ -n "$(COMMENT)" ]; then \
echo "🔄 Closing issues $(NUMS) with comment..."; \
PYTHONPATH=. $(VENV_PYTHON) tddai/issue_closer.py $(NUMS) --comment "$(COMMENT)"; \
else \
echo "🔄 Closing issues $(NUMS)..."; \
PYTHONPATH=. $(VENV_PYTHON) tddai/issue_closer.py $(NUMS); \
fi
# Export compact issue index to ISSUES.index file (TSV format)
issue-get: $(VENV)/bin/activate
@echo "📋 Fetching issue index from gitea..."
@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py issue-index --format tsv --sort number > ISSUES.index
@echo "✅ Issue index exported to ISSUES.index (TSV format)"
@echo "📄 File contents:"
@cat ISSUES.index
# Export issues as CSV for spreadsheet processing
issue-csv: $(VENV)/bin/activate
@echo "📊 Exporting issues as CSV..."
@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py issue-index --format csv --sort priority --include-state > ISSUES.csv
@echo "✅ Issues exported to ISSUES.csv"
@wc -l ISSUES.csv | awk '{print "📄 Total entries:", $$1-1, "(excluding header)"}'
# Export issues as JSON for programmatic processing
issue-json: $(VENV)/bin/activate
@echo "🔧 Exporting issues as JSON..."
@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py issue-index --format json --sort priority > ISSUES.json
@echo "✅ Issues exported to ISSUES.json"
@echo "📄 Sample entry:"
@head -20 ISSUES.json
# Export only high and critical priority issues
issue-high: $(VENV)/bin/activate
@echo "🚨 Exporting high priority issues..."
@echo "High priority issues:" > ISSUES.high.txt
@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py issue-index --format tsv --filter-priority high --sort number >> ISSUES.high.txt
@echo "" >> ISSUES.high.txt
@echo "Critical priority issues:" >> ISSUES.high.txt
@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py issue-index --format tsv --filter-priority critical --sort number >> ISSUES.high.txt
@echo "✅ High priority issues exported to ISSUES.high.txt"
@cat ISSUES.high.txt
# Generate test skeleton from gitea issue (requires Claude Code)
test-from-issue:
@ISSUE_NUM=""; \
if [ -n "$(ISSUE)" ]; then \
ISSUE_NUM="$(ISSUE)"; \
elif [ -n "$(NUM)" ]; then \
ISSUE_NUM="$(NUM)"; \
fi; \
if [ -z "$$ISSUE_NUM" ]; then \
echo "❌ Please specify issue number: make test-from-issue ISSUE=1 (or NUM=1)"; \
exit 1; \
fi
@echo "🔍 Checking for Claude Code availability..."
@if ! command -v claude >/dev/null 2>&1; then \
echo "❌ Claude Code not found in PATH"; \
echo " This target requires Claude Code CLI to be installed"; \
echo " Visit: https://claude.ai/code for installation instructions"; \
exit 1; \
fi
@echo "✅ Claude Code found"
@echo "🔍 Checking for curl..."
@if ! command -v curl >/dev/null 2>&1; then \
echo "❌ curl not found - required for API access"; \
exit 1; \
fi
@echo "✅ curl found"
@echo "📋 Fetching issue #$$ISSUE_NUM details..."
@curl -s "$(ISSUES_API)/$$ISSUE_NUM" | jq -r 'if .title then "✅ Issue #'"$$ISSUE_NUM"': " + .title + "\n\n🧪 Generating test skeleton...\n Please ask Claude Code to generate a test for this issue:\n\n Command: '"'"'Generate a test skeleton for issue #'"$$ISSUE_NUM"''"'"'\n\n📋 Issue Details:\n Title: " + .title + "\n Description: " + .body + "\n\n📝 Test Requirements:\n - Follow TDD principles (test first, then implementation)\n - Use pytest framework (existing project convention)\n - Place test in tests/ directory\n - Name test file: test_issue_'"$$ISSUE_NUM"'_*.py\n - Include docstring referencing issue #'"$$ISSUE_NUM"'\n - Test should initially fail (red state)\n\n💡 After generation, run '"'"'make test'"'"' to verify test fails initially" else "❌ Issue #'"$$ISSUE_NUM"' not found or API error\n Use '"'"'make list-open-issues'"'"' to see available issues" end' 2>/dev/null || echo "❌ Issue #$$ISSUE_NUM not found or API error"
# Start working on an issue (creates workspace with requirements validation)
tdd-start: validate-requirements $(VENV)/bin/activate
@ISSUE_NUM=""; \
if [ -n "$(ISSUE)" ]; then \
ISSUE_NUM="$(ISSUE)"; \
elif [ -n "$(NUM)" ]; then \
ISSUE_NUM="$(NUM)"; \
fi; \
if [ -z "$$ISSUE_NUM" ]; then \
echo "❌ Please specify issue number: make tdd-start ISSUE=1 (or NUM=1)"; \
exit 1; \
fi; \
echo "🚀 Starting TDD workflow with requirements validation..."; \
PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py start-issue $$ISSUE_NUM
# Add test to current issue workspace
tdd-add-test: $(VENV)/bin/activate
@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py add-test
# Show current workspace status
tdd-status: $(VENV)/bin/activate
@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py workspace-status
# Complete issue work (move tests to main and cleanup)
tdd-finish: $(VENV)/bin/activate
@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py finish-issue
# Show test status summary without re-running tests
test-status: $(VENV)/bin/activate
@ -876,19 +659,11 @@ test-new: $(VENV)/bin/activate
echo " 3. Implement the actual functionality"; \
echo " 4. Run tests again to verify (TDD cycle)"
# Analyze test coverage for a specific issue
# Analyze test coverage
test-coverage: $(VENV)/bin/activate
@ISSUE_NUM=""; \
if [ -n "$(ISSUE)" ]; then \
ISSUE_NUM="$(ISSUE)"; \
elif [ -n "$(NUM)" ]; then \
ISSUE_NUM="$(NUM)"; \
fi; \
if [ -z "$$ISSUE_NUM" ]; then \
echo "❌ Please specify issue number: make test-coverage ISSUE=5 (or NUM=5)"; \
exit 1; \
fi; \
PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py analyze-coverage $$ISSUE_NUM
@echo "📊 Analyzing test coverage..."
@pytest --cov=markitect --cov-report=html --cov-report=term-missing tests/
@echo "✅ Coverage report generated in htmlcov/"
# ============================================================================
# Architectural Testing Targets
@ -1473,26 +1248,3 @@ cost-help:
@echo "💰 Currency: Costs calculated in USD and EUR"
@echo "🤖 Model: Default claude-sonnet-4 pricing"
# Generate cost note for an issue (requires ISSUE, INPUT_TOKENS, OUTPUT_TOKENS)
cost-note-issue: $(VENV)/bin/activate
@if [ -z "$(ISSUE)" ]; then \
echo "❌ Please specify issue number: make cost-note-issue ISSUE=136 INPUT_TOKENS=45000 OUTPUT_TOKENS=28000"; \
exit 1; \
fi
@if [ -z "$(INPUT_TOKENS)" ]; then \
echo "❌ Please specify input tokens: make cost-note-issue ISSUE=$(ISSUE) INPUT_TOKENS=45000 OUTPUT_TOKENS=28000"; \
exit 1; \
fi
@if [ -z "$(OUTPUT_TOKENS)" ]; then \
echo "❌ Please specify output tokens: make cost-note-issue ISSUE=$(ISSUE) INPUT_TOKENS=$(INPUT_TOKENS) OUTPUT_TOKENS=28000"; \
exit 1; \
fi
@echo "💰 Generating cost note for Issue #$(ISSUE)..."
@$(VENV_PYTHON) -c "import sys; sys.path.append('.'); from tddai.issue_fetcher import IssueFetcher; fetcher = IssueFetcher(); issue = fetcher.fetch_issue($(ISSUE)); print(f'📋 Issue: {issue[\"title\"]}')"
@ISSUE_TITLE=$$($(VENV_PYTHON) -c "import sys; sys.path.append('.'); from tddai.issue_fetcher import IssueFetcher; fetcher = IssueFetcher(); issue = fetcher.fetch_issue($(ISSUE)); print(issue['title'])"); \
markitect cost session track $(ISSUE) "$$ISSUE_TITLE" \
--input-tokens $(INPUT_TOKENS) \
--output-tokens $(OUTPUT_TOKENS) \
--summary "$(if $(SUMMARY),$(SUMMARY),Implementation completed using TDD8 methodology)"
@echo "✅ Cost note generated successfully!"
@echo "📁 Check cost_notes/issue_$(ISSUE)_cost_$$(date +%Y-%m-%d).md"