Meikero MCP 1.1.1

- Fixed ChatGPT OAuth discovery returning HTTP 404 despite containing valid metadata.
- Moved OAuth discovery handling before WordPress routing and explicitly return HTTP 200 for valid metadata requests.
- Added HEAD support and correct method responses for discovery endpoints.
- Added a “Check ChatGPT discovery” button to the Connection page, with HTTP status and metadata validation.
- Preserved existing Claude connections, Elementor tools, permissions and licensing behavior.

CAUSE VERIFIED
On the affected ASKA installation, /.well-known/oauth-authorization-server and the protected-resource discovery URL returned valid JSON with HTTP 404. The previous handler ran at template_redirect and did not explicitly set the status, so WordPress's 404 status could survive. REST metadata endpoints returned 200.

VALIDATION
- Reproduced the old behavior in a PHP HTTP harness: valid metadata + HTTP 404.
- Patched code passes seven HTTP regression cases: authorization/resource/path-specific discovery GET, query-string handling, HEAD, POST rejection and unrelated-path 404 preservation.
- Existing 45 isolated OAuth/Elementor checks pass.
- Production PHP syntax checks and admin JavaScript syntax check pass.
- Plugin boot/inventory smoke test passes: 67 static tool definitions, no duplicates.
- HTTP harness uses WordPress function doubles; it is not a full WordPress installation.
- Updated ZIP has not been installed on ASKA by the assistant. Full ChatGPT sign-in and actual Elementor writes remain pending live verification.

INSTALL
1. Upload meikero-mcp-1.1.1.zip as an update and visit Meikero > Connection.
2. Clear host/CDN cache if previous 404 responses were cached.
3. Click Check ChatGPT discovery. Both metadata checks should show OK.
4. In ChatGPT, retry adding the server URL with OAuth. Refresh/reopen the add-server dialog if it retained the old discovery error. Use automatic registration once metadata is detected.
5. Authenticate in WordPress and approve the desired access. Test reading before editing.

No License Manager update, static files, .htaccess changes or permission changes are included in this fix.
