Enable and implement planner agent #620

Summary

The planner workflow is currently disabled (if: false). Its purpose is to automatically add new issues and PRs to appropriate projects based on labels and metadata.

Problem

• Planner workflow disabled; script not implemented
• Issues/PRs not automatically assigned to projects on creation
• Manual project management creates friction and inconsistency
• Planning documentation not validated or enforced

Solution

Implement scripts/agents/planner.agent.js to:

1. Detect new issues/PRs lacking project assignment
2. Derive appropriate project from:
   • Issue labels (area:, type:, meta:*)
   • Issue description (if mentions project explicitly)
   • Project-issue type mapping rules
3. Add to appropriate project (or queue for manual review if ambiguous)
4. Log action in issue comment with reasoning
5. Create fallback queue for manual review if auto-assignment is uncertain

Enable workflow in .github/workflows/planner.yml and add concurrency management.

Implementation Details

• Effort: 4–5 hours
• Complexity: High
• Risk: Medium (relies on label stability and project schema)
• Related: Labeling system (.github/workflows/labeling.yml), project sync (.github/workflows/project-meta-sync.yml)
• Dependencies: GitHub API integration, label-to-project mapping rules

Acceptance Criteria

• Planner agent script implemented
• Workflow enabled (remove if: false)
• At least 80% of new issues auto-assigned to correct project
• Fallback queue handles ambiguous cases
• Logging includes reasoning for assignment
• Integration tests verify label → project mapping
• All tests pass; no project conflicts

Reference

See workflow standards audit: .github/reports/audits/workflow-standards-audit-2026-05-31.md