feat: Issue #46 Decomposition - Schema Generation Capability Outline

Complete breakdown of Issue #46 into 6 structured sub-issues:

Created Issues:
- Issue #50: Define metaschema for JSON schema structure (High priority)
- Issue #51: Add outline mode to schema generation (High priority)
- Issue #52: Capture actual heading text in schemas (Medium priority)
- Issue #54: Add content field instruction capabilities (Medium priority)
- Issue #55: Schema-based draft generation (Medium priority)
- Issue #56: Data-driven multiple draft generation (Low priority)

Documentation Added:
- ISSUE_WORKFLOW_REMINDER.md: Comprehensive workflow for issue management
  - Establishes Gitea as source of truth for all issue discussions
  - Documents working make targets for issue access
  - Prevents circular inefficiency in issue handling
- RelevantClaudeIssues.md: Added workflow reminder reference

Implementation Strategy:
- Foundation-first approach starting with metaschema (Issue #50)
- Clear dependency chain and parallel development opportunities
- Transforms MarkiTect from static analysis to dynamic generation pipeline

Active Gameplan:
Next step is to start with 'make tdd-start NUM=50' for metaschema work.

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

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

RelevantClaudeIssues.md

@@ -16,6 +16,9 @@ This document tracks Claude Code issues that directly impact our development wor
 - Remove resolved issues after confirming fixes work in our environment
 - Maintained by the claude-expert subagent as part of issue tracking responsibilities
 
+**🎯 CRITICAL WORKFLOW REMINDER:**
+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.
+
 ---
 
 ## Resolved Issues