chore: remove outdated docs and planning files

[StuMason]

Summary

Remove 7,768 lines of obsolete documentation.

Deleted

• docs/features/*.md (14 files) - Old ADR planning docs from March 2025, all features implemented
• docs/mcp-example-clients.md - Copy-pasted MCP docs, not project-specific
• docs/mcp-js-readme.md - Copy-pasted MCP SDK readme, not needed

Kept

• docs/coolify-openapi.yaml - Coolify API reference
• docs/openapi-chunks/ - Used by OpenAPI drift detection workflow

🤖 Generated with Claude Code

[claude]

PR Review: chore: remove outdated docs and planning files

Summary

This PR removes 7,768 lines of obsolete documentation - specifically ADR planning documents from early development and copy-pasted MCP documentation that doesn't belong in this repository.

✅ Approval

This is a clean, well-scoped housekeeping PR. I recommend merging it.

What's Being Removed

Category	Files	Lines
ADR Planning Docs	docs/features/001-013*.md (14 files)	~1,026
Copy-pasted MCP Docs	docs/mcp-example-clients.md	6,255
Copy-pasted SDK Readme	docs/mcp-js-readme.md	487

What's Being Kept (Good Decisions)

• docs/coolify-openapi.yaml - Active Coolify API reference
• docs/openapi-chunks/ - Used by the OpenAPI drift detection workflow

Review Notes

1. ADR Documents: These served their purpose during initial development but are now outdated. All features described (001-011, 013) have been implemented. Keeping them would create confusion since they show incomplete checkboxes for completed work.

2. External Documentation Copies: The mcp-example-clients.md (6,255 lines) and mcp-js-readme.md (487 lines) are copies of upstream MCP documentation. These belong in the original repositories, not here. Users should reference the official MCP docs instead.

3. Empty File Cleanup: docs/features/012-backup-management.md was an empty placeholder - good to remove.

4. No Impact on Functionality: This is purely documentation cleanup with no code changes.

Suggestions for Future

• Consider adding a link to the official MCP documentation in the README if users need that reference
• The main README.md already has good documentation coverage

LGTM 👍