Tier 1.5-1.6: Multi-Tracker Support + Context Purity

[kanfil]

Summary

Epic issue for Tier 1 Async Task Context Delivery - Part 3

Sub-items

Tier 1.5 - Multi-Tracker Issue Creation

• ⚠️ Extended /taskstoissues: Template exists but currently only supports GitHub. Needs extension for Jira, Linear, GitLab
• ❌ Dynamic Tracker Detection: Auto-detect configured issue tracker from .mcp.json configuration
• ❌ Tracker-Specific MCP Tools: Invoke correct platform-specific MCP tool per tracker type
• ❌ URL Validation: Handle different URL formats (GitHub SSH/HTTPS, Jira REST, Linear API, GitLab REST)
• ❌ Task-to-Issue Linking: Establish bidirectional links between tasks.md and created issues for traceability

Tier 1.6 - Context Purity Enforcement (From Claude Code article insights)

• ❌ Full Artifact Delivery: Remote agents receive complete spec.md/plan.md/research.md (not summaries)
• ❌ Compression Thresholds: Only compress when artifacts exceed 150K tokens (configurable in config.json)
• ❌ Attention Mechanism Preservation: Ensure agents can perform pair-wise reasoning across context via full document loading
• ❌ Token Cost Visibility: Log context size and token costs in delegation prompts for transparency

Priority

Critical - Multi-tracker and quality features

Labels

epic, async, multi-tracker