refactor: align with ReusableCapabilitiesArchitecture v0.1

Refactor issue-facade to conform to the new ReusableCapabilitiesArchitecture
specification, improving discoverability and establishing consistent patterns
for capability integration.

Architecture Changes:
- Rename .feedback/ → feedback/ (visible user interface)
- Rename CAPABILITY.yaml → CAPABILITY-issue-tracking.yaml (explicit family)
- Keep .capability/ hidden (evolving implementation infrastructure)

File Updates:
- Updated all documentation references (.feedback → feedback)
- Updated .capability/feedback script paths
- Updated Makefile, README.md, CLAUDE.md, examples
- Fixed CAPABILITY.yaml → CAPABILITY-issue-tracking.yaml references

New Tools:
- Created .capability/detach script for clean capability removal
- Supports git submodule and directory-based integrations
- Generates detachment manifest for re-integration guidance

Rationale:
- feedback/ is visible: encourages user participation, shows capability identity
- .capability/ is hidden: implementation details that will evolve
- CAPABILITY-<family>.yaml: explicit family declaration, supports multiple capabilities per repo
- Underscore prefix pattern: flatter hierarchy, clear signal of integration

This aligns with the principle that capabilities are conceptual units
designed for natural language integration by devhumans and devagents,
not just technical libraries.

See ReusableCapabilitiesArchitecture.md for complete specification.

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

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

examples/feedback-example.md

@@ -52,8 +52,8 @@ EOF
 ### Method 2: Direct File Drop (No CLI Required)
 
 ```bash
-# Just create a markdown file directly in .feedback/inbound/
-cat > .feedback/inbound/$(date +%Y%m%d-%H%M%S)-performance.md << 'EOF'
+# Just create a markdown file directly in feedback/inbound/
+cat > feedback/inbound/$(date +%Y%m%d-%H%M%S)-performance.md << 'EOF'
 ## Quick Note
 
 The JSON output format for `issue list` is fantastic for scripting!
@@ -92,7 +92,7 @@ EOF
 
 # Copy to capability's feedback directory
 cp feedback-for-issue-facade.md \
-   capabilities/issue-facade/.feedback/inbound/$(date +%Y%m%d)-github-backend.md
+   capabilities/issue-facade/feedback/inbound/$(date +%Y%m%d)-github-backend.md
 ```
 
 ## Feedback Categories
@@ -237,7 +237,7 @@ Thank you!
 
 ## What Happens to Your Feedback
 
-1. **Submission**: Your feedback lands in `.feedback/inbound/`
+1. **Submission**: Your feedback lands in `feedback/inbound/`
 2. **Review**: Maintainers review it (usually within a week)
 3. **Action**:
    - Create issue if it needs tracking
@@ -259,10 +259,10 @@ If you're curious whether your feedback was addressed:
 
 ```bash
 # Check if it's still in inbound (pending review)
-ls .feedback/inbound/ | grep <keyword>
+ls feedback/inbound/ | grep <keyword>
 
 # Check if it's been reviewed
-ls .feedback/reviewed/ | grep <keyword>
+ls feedback/reviewed/ | grep <keyword>
 
 # Check if an issue was created
 issue list --label=feedback --search="<your topic>"
@@ -274,7 +274,7 @@ If you maintain this capability, see the maintainer guide:
 - **Review workflow**: `.capability/feedback list` and `review`
 - **Creating issues**: `.capability/feedback review <id> --create-issue`
 - **Statistics**: `.capability/feedback stats`
-- **Full docs**: `.feedback/README.md`
+- **Full docs**: `feedback/README.md`
 
 ## Questions?