You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Rene Cannao 80ecaa2c5d docs(plans): Step 4 — merge 4.C/4.D/4.E (construction-site dependency) ... The original plan claimed the 5 "stateless" tool handlers could move in 4.C ahead of the listener moving in 4.E. Implementation analysis showed that 4 of those 5 (Admin/Cache/Config/Stats — only Observe is orphan) are constructed directly in lib/ProxySQL_MCP_Server.cpp at L84-131 with `new Admin_Tool_Handler(handler)` etc., so moving their .cpp files out of lib/ while leaving ProxySQL_MCP_Server.cpp behind breaks the lib/libproxysql.a → src/proxysql link. The transitional forwarding-header escape hatch the plan proposed addresses includes, not symbols, so it doesn't help. This commit revises the sub-step table: 4.D and 4.E are now merged into a revised 4.C — one atomic move of the entire MCP surface (8 tool handlers + base + MCP_Endpoint + MCP_Thread + ProxySQL_MCP_Server) plus the Query/MySQL backend rewires plus the GloMCPH lifecycle takeover. 4.F (register_command dispatch) and 4.G (register_table) remain separate and follow the merged 4.C. Adds a new section "4.C / 4.D / 4.E merge (revision)" that documents the construction-site dependency, the temporary admin-SQL surface gap between merged-4.C and 4.F (intentional, called out in commit messages), and the AI/RAG handlers' continued residence in lib/ (they're Steps 5/6 scope). No code changes in this commit — pure plan revision.		2 months ago
..
superpowers	docs(plans): Step 4 — merge 4.C/4.D/4.E (construction-site dependency)	2 months ago
pgsql_servers_ssl_params.md	fix: support one-sided TLS version ranges and warn on malformed input	2 months ago