refactor: rename workspace targets to TDD Workspace with tdd- prefix

- Rename "Issue Workspace" category to "TDD Workspace" in help output
- Add tdd- prefix to all workspace-related targets:
  - start-issue → tdd-start
  - add-test → tdd-add-test
  - workspace-status → tdd-status
  - finish-issue → tdd-finish
- Update .PHONY declarations for new target names
- Update all CLI output messages to reference new target names
- Maintain backward compatibility in CLI functionality

This provides clearer naming that emphasizes the TDD focus and avoids
confusion with general issue management targets.

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

Co-Authored-By: Claude <noreply@anthropic.com>

Makefile

@@ -1,7 +1,7 @@
 # MarkiTect - Advanced Markdown Engine
 # Makefile for common development tasks
 
-.PHONY: help setup install test build clean update status dev lint format check-deps venv-status update-digest add-diary-entry list-issues show-issue list-open-issues test-from-issue start-issue add-test finish-issue workspace-status
+.PHONY: help setup install test build clean update status dev lint format check-deps venv-status update-digest add-diary-entry list-issues show-issue list-open-issues test-from-issue tdd-start tdd-add-test tdd-finish tdd-status
 
 # Default target
 help:
@@ -41,11 +41,11 @@ help:
 	@echo "Test-Driven Development:"
 	@echo "  test-from-issue NUM=X - Generate test skeleton from issue (requires Claude Code)"
 	@echo ""
-	@echo "Issue Workspace:"
-	@echo "  start-issue NUM=X     - Start working on issue (creates workspace)"
-	@echo "  add-test              - Add test to current issue workspace"
-	@echo "  workspace-status      - Show current workspace state"
-	@echo "  finish-issue          - Complete issue work (moves tests to main)"
+	@echo "TDD Workspace:"
+	@echo "  tdd-start NUM=X       - Start working on issue (creates workspace)"
+	@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)"
 
 # Python and virtual environment setup
 PYTHON := python3
@@ -268,21 +268,21 @@ test-from-issue:
 	@curl -s "$(ISSUES_API)/$(NUM)" | jq -r 'if .title then "✅ 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 #$(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_$(NUM)_*.py\n   - Include docstring referencing issue #$(NUM)\n   - Test should initially fail (red state)\n\n💡 After generation, run '"'"'make test'"'"' to verify test fails initially" else "❌ Issue #$(NUM) not found or API error\n   Use '"'"'make list-open-issues'"'"' to see available issues" end' 2>/dev/null || echo "❌ Issue #$(NUM) not found or API error"
 
 # Start working on an issue (creates workspace)
-start-issue: $(VENV)/bin/activate
+tdd-start: $(VENV)/bin/activate
 	@if [ -z "$(NUM)" ]; then \
-		echo "❌ Please specify issue number: make start-issue NUM=1"; \
+		echo "❌ Please specify issue number: make tdd-start NUM=1"; \
 		exit 1; \
 	fi
 	@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py start-issue $(NUM)
 
 # Add test to current issue workspace
-add-test: $(VENV)/bin/activate
+tdd-add-test: $(VENV)/bin/activate
 	@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py add-test
 
 # Show current workspace status
-workspace-status: $(VENV)/bin/activate
+tdd-status: $(VENV)/bin/activate
 	@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py workspace-status
 
 # Complete issue work (move tests to main and cleanup)
-finish-issue: $(VENV)/bin/activate
+tdd-finish: $(VENV)/bin/activate
 	@PYTHONPATH=. $(VENV_PYTHON) tddai_cli.py finish-issue