feat: Establish PM and Azure systems as complementary solutions

[rafeekpro]

• Create comprehensive coexistence strategy documentation
• Add system selection guide for choosing between PM/Azure/Both
• Update COMMAND_MAPPING.md to clarify complementary roles
• Implement missing high-priority Azure commands:
  • task-analyze: Deep task metrics and pattern analysis
  • feature-show: Detailed feature information display
• Document migration paths between systems
• Add decision criteria and practical scenarios

Both systems now clearly coexist:

• PM System: Local, offline, universal git support
• Azure System: Enterprise, team collaboration, metrics
• Use both for maximum flexibility

🤖 Generated with Claude Code

[Copilot]

Pull Request Overview

This PR establishes a comprehensive coexistence strategy between the PM system and Azure DevOps system, clarifying them as complementary rather than competing solutions. It provides detailed guidance on when to use each system, how they work together, and migration paths between them.

• Create documentation defining PM and Azure systems as complementary solutions
• Add comprehensive system selection guide with decision trees and practical scenarios
• Implement two missing high-priority Azure commands for task analysis and feature display

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
SYSTEM-SELECTION-GUIDE.md	New comprehensive guide with decision trees, scenarios, and migration strategies
PM-AZURE-COEXISTENCE.md	New detailed coexistence strategy documentation explaining how both systems work together
task-analyze.md	New Azure command for deep task metrics and pattern analysis
feature-show.md	New Azure command for detailed feature information display
COMMAND_MAPPING.md	Updated to clarify complementary roles and current implementation status

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The performance comparison table lacks context about what influences the Azure system timing ranges. Consider adding a note explaining that Azure timings depend on network latency, API throttling, and data volume.

Suggested change

	> **Note:** Azure system timings are approximate and can vary significantly depending on network latency, API throttling, and the volume of data being processed.

[Copilot]

The cycle time calculation assumes dates are in the expected format and doesn't handle potential null values or parsing errors. Consider adding error handling for malformed dates.

[Copilot]

The progress bar uses magic numbers (20 segments, multiplication by 5). Consider defining these as variables with descriptive names like PROGRESS_BAR_WIDTH=20 and SEGMENT_PERCENTAGE=5 for better maintainability.

[Copilot]

The string interpolation mixing shell variables with jq expressions is complex and error-prone. Consider simplifying by extracting the jq output to variables first, then constructing the display string.

Suggested change

	echo " 🎯 Parent: $(echo "$parent_info" | jq -r '"\(.Type) #'$parent_id': \(.Title)"')"
	parent_type=$(echo "$parent_info" | jq -r '.Type')
	parent_title=$(echo "$parent_info" | jq -r '.Title')
	echo " 🎯 Parent: $parent_type #$parent_id: $parent_title"