This document tracks Claude Code issues that directly impact our development workflows for the MarkiTect project. Each issue section provides a clear problem description, affected workflows, related GitHub issues for monitoring, available workarounds, and resolution tracking information.
**Purpose:**
- Document blocking Claude Code issues affecting project development
- Provide centralized tracking of GitHub issues to monitor for fixes
- Maintain awareness of workarounds and their trade-offs
- Enable quick assessment of when normal workflows can resume
**Maintenance:**
- Update when new blocking issues are discovered
- Check GitHub issue status weekly and update resolution monitoring
- Remove resolved issues after confirming fixes work in our environment
When discussing project issues (not Claude Code issues), ALWAYS fetch from Gitea first. Gitea is the source of truth for all issue assessment, feasibility evaluation, and implementation planning. Local files are insufficient for decision-making about issues. See ISSUE_WORKFLOW_REMINDER.md for complete workflow.
Custom subagents defined in `.claude/agents/` directory were not being detected or made available as `subagent_type` options in the Task tool. This prevented the intended workflow of using specialized subagents for domain-specific tasks like project management, documentation, or Claude Code expertise.
This document should be reviewed weekly to check for issue resolution and update status. The agent-claude-documentation subagent is responsible for maintaining this tracking and updating the project team when workflows can resume normal operation.
