feat: implement reusable feedback capability for continuous improvement

Add comprehensive feedback system that enables lightweight, unstructured feedback
collection from users of the issue-facade capability, establishing a continuous
improvement loop grounded in real-world usage.

Core Components:
- .feedback/ directory structure (inbound, reviewed, archived)
- Standalone CLI tool (.capability/feedback) for submission and management
- Comprehensive documentation (.feedback/README.md)
- Integration examples and usage guides

Key Features:
- Multiple submission methods (CLI, Makefile, direct file drop)
- No structure imposement - accepts any text/markdown format
- Automatic metadata capture (timestamp, git context, version)
- Maintainer workflow (list, review, archive, create issues)
- Colored terminal output for better UX
- Future-ready for API endpoint evolution

Integration:
- Updated CAPABILITY.yaml with feedback section
- Enhanced CLAUDE.md with comprehensive integration guide
- Added Makefile commands (feedback, feedback-list, feedback-stats, etc.)
- Created detailed usage examples (examples/feedback-example.md)

Design Philosophy:
- Capability-agnostic pattern (reusable across all markitect capabilities)
- Decentralized (each capability owns its feedback)
- Flexible (no required formats or fields)
- Durable (plain markdown files, git-tracked)
- Actionable (feedback lives where maintainers work)
- Scalable (works for 1 user or 1000 users)

Feedback Submission Examples:
  ./.capability/feedback submit "Your feedback"
  make feedback MSG="Your feedback"
  echo "Feedback" > .feedback/inbound/$(date +%Y%m%d)-feedback.md

Maintainer Workflow:
  make feedback-list                    # List pending
  make feedback-stats                   # Show statistics
  make feedback-review-issue FILE=xxx   # Review and create issue

This establishes a robust continuous improvement loop:
User Experience → Feedback → Review → Action → Improved Capability

The pattern is designed to be copied to any capability in the markitect
project, providing consistent feedback collection across all capabilities.

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

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

CAPABILITY.yaml

@@ -158,12 +158,52 @@ agent_guidance:
       exit 1
     fi
 
+# Feedback and continuous improvement
+feedback:
+  enabled: true
+  method: feedback-capability
+  description: >
+    This capability integrates the feedback pattern for continuous improvement
+    based on real-world usage from master projects.
+
+  submission:
+    cli: ".capability/feedback submit 'Your feedback here'"
+    file: ".capability/feedback submit path/to/feedback.md"
+    directory: ".feedback/inbound/"
+
+  organization:
+    inbound: "New feedback awaiting review"
+    reviewed: "Feedback that's been reviewed by maintainers"
+    archived: "Resolved or outdated feedback"
+
+  for_users: |
+    Submit feedback about issue-facade:
+      ./.capability/feedback submit "Feedback text"
+      ./.capability/feedback submit detailed-feedback.md
+
+    Or drop a file directly:
+      echo "Feedback..." > .feedback/inbound/$(date +%Y%m%d)-feedback.md
+
+  for_maintainers: |
+    Review feedback:
+      ./.capability/feedback list
+      ./.capability/feedback show <filename>
+      ./.capability/feedback review <filename> --create-issue
+      ./.capability/feedback stats
+
+  integration_notes:
+    - "Feedback capability is reusable across all markitect capabilities"
+    - "No structure imposement - accepts any text/markdown format"
+    - "Capability owns feedback organization and prioritization"
+    - "Can evolve to API endpoint when capability becomes a service"
+
 # Documentation references
 documentation:
   integration: "AGENT_INTEGRATION.md"
   development: "CLAUDE.md"
   roadmap: "ROADMAP.md"
   examples: "examples/agents/"
+  feedback: ".feedback/README.md"
 
 # Dependencies and requirements
 requirements: