Add quality standards and team command design patterns documentation

- Introduced a new quality standards document outlining assessment criteria for team command .md files, including completeness, pattern compliance, integration, and consistency dimensions.
- Established quality gates and issue classification for errors, warnings, and informational notes.
- Created a comprehensive team command design patterns document detailing infrastructure and collaboration patterns, including message bus integration, YAML front matter requirements, task lifecycle, five-phase execution structure, and error handling.
- Included a pattern selection guide for collaboration scenarios to enhance team interaction models.

.codex/agents/issue-plan-agent.md

@@ -226,13 +226,13 @@ function decomposeTasks(issue, exploration) {
     scope: inferScope(group),              // Module path
     action: inferAction(group),            // Create | Update | Implement | ...
     description: group.description,
-    modification_points: mapModificationPoints(group),
+    files: mapFiles(group),                // [{path, target, change, action?, conflict_risk?}]
     implementation: generateSteps(group),  // Step-by-step guide
     test: {
       unit: generateUnitTests(group),
       commands: ['npm test']
     },
-    acceptance: {
+    convergence: {
       criteria: generateCriteria(group),   // Quantified checklist
       verification: generateVerification(group)
     },
@@ -242,7 +242,7 @@ function decomposeTasks(issue, exploration) {
       message_template: generateCommitMsg(group)
     },
     depends_on: inferDependencies(group, tasks),
-    priority: calculatePriority(group)     // 1-5 (1=highest)
+    priority: calculatePriorityEnum(group) // "critical"|"high"|"medium"|"low"
   }));
 
   // GitHub Reply Task: Add final task if issue has github_url
@@ -254,20 +254,20 @@ function decomposeTasks(issue, exploration) {
       scope: 'github',
       action: 'Notify',
       description: `Comment on GitHub issue to report completion status`,
-      modification_points: [],
+      files: [],
       implementation: [
         `Generate completion summary (tasks completed, files changed)`,
         `Post comment via: gh issue comment ${issue.github_number || extractNumber(issue.github_url)} --body "..."`,
         `Include: solution approach, key changes, verification results`
       ],
       test: { unit: [], commands: [] },
-      acceptance: {
+      convergence: {
         criteria: ['GitHub comment posted successfully', 'Comment includes completion summary'],
         verification: ['Check GitHub issue for new comment']
       },
       commit: null,  // No commit for notification task
       depends_on: lastTaskId ? [lastTaskId] : [],  // Depends on last implementation task
-      priority: 5    // Lowest priority (run last)
+      priority: "low"    // Lowest priority (run last)
     });
   }
 
@@ -370,10 +370,10 @@ Each line is a solution JSON containing tasks. Schema: `cat ~/.ccw/workflows/cli
 ### 3.2 Validation Checklist
 
 - [ ] ACE search performed for each issue
-- [ ] All modification_points verified against codebase
+- [ ] All files[] paths verified against codebase
 - [ ] Tasks have 2+ implementation steps
 - [ ] All 5 lifecycle phases present
-- [ ] Quantified acceptance criteria with verification
+- [ ] Quantified convergence criteria with verification
 - [ ] Dependencies form valid DAG
 - [ ] Commit follows conventional commits
 
@@ -389,7 +389,7 @@ Each line is a solution JSON containing tasks. Schema: `cat ~/.ccw/workflows/cli
 4. Fetch issue details via `ccw issue status <id> --json`
 5. **Analyze failure history**: Check `issue.feedback` for type='failure', stage='execute'
 6. **For replanning**: Reference previous failures in `solution.approach`, add prevention steps
-7. Quantify acceptance.criteria with testable conditions
+7. Quantify convergence.criteria with testable conditions
 8. Validate DAG before output
 9. Evaluate each solution with `analysis` and `score`
 10. Write solutions to `.workflow/issues/solutions/{issue-id}.jsonl` (append mode)