mirror of
https://github.com/Heretek-AI/heretek-control-core.git
synced 2026-10-12 02:03:55 +00:00
Mian Shahzad RazaandClaude Opus 4.8
b6ffb0d459
CONTRIBUTING had drifted from the codebase and would have sent a new contributor down several dead ends: - required PHP 7.4 and WP 6.8, actually 8.1+ and 6.9+ - listed the MCP Adapter as a plugin to install, it has been bundled since 1.7.4 - treated Elementor as required, it has been optional since 3.0.0 - registered abilities with wp_register_ability(), 'category' => 'elementor-mcp', and a 'callback' key; the real API is emcp_tools_register_ability() with 'category' => 'emcp-tools' and 'execute_callback' - pointed at a tests/ layout and an architecture tree that no longer match - told contributors to hand-update tool counts, which are now generated - never mentioned the two-dispatcher integration pattern, which is how most new tools now get added Rewritten around what someone can actually contribute (report, docs, prompt, tool, integration), with the current setup, the real registration API, and the rules that are easy to get wrong: 'category' is required or the ability is silently dropped, never write _elementor_data directly, never guess a field name because a wrong one looks like it worked. Adds five issue forms (bug, feature, integration, idea, plus config) so reports arrive with the MCP client, the tool called, and the versions already filled in. Blank issues are disabled and the config routes docs, connection problems, Discord, security reports, and Pro support to the right place. Every link verified live. Dropped support.emcptools.com from the routing, the domain does not resolve yet. Co-Authored-By: Claude Opus 4.8 <[email protected]>