feat(submission): add Titan Edge MCP Server submission

[jackhu24-ship-it]

Summary

This pull request submits Titan Edge MCP Server (\ itan-edge-mcp) for the X-Agent AI MCP Hackathon.

Capability

• Name: Titan Edge MCP Server
• Slug: \ itan-edge-mcp\
• Description: Autonomous ASIL-D compliant edge MCP server providing real-time dual-core redundant finite-state-machine (FSM) fault diagnosis, bus telemetry analysis, and sub-5ms self-healing transitions for industrial and automotive edge AI agents.

Live Endpoints & Verification

• API Base URL: https://commander-jackhu24.netlify.app/api
• Health Check URL: https://commander-jackhu24.netlify.app/api/health
• Deployment Proof: https://commander-jackhu24.netlify.app/.well-known/xagent-verification.json
• Source Review Commit: \422f0aeb5520a3506b08b05cfefcb76c6cb786c0\

Validation

• Local preflight:
  pm run validate:submission -- --dir submissions/mcp-hackathon/titan-edge-mcp\ passed.
• Online preflight:
  pm run validate:submission -- --dir submissions/mcp-hackathon/titan-edge-mcp --online\ passed with all 6 checks verified.

[github-actions]

Submission received — #47

Thank you for submitting to the current X-Agent MCP Hackathon. We have received your pull request.

This is a receipt only. It does not confirm eligibility, completeness, technical approval, a judging result, or an award. Passing automated checks or merging code for archival purposes does not, by itself, mean the entry has passed review or won a prize.

Please include the complete source for the submitted capability in this repository under submissions/mcp-hackathon/<slug>/source/, with dependency files, configuration examples, and reproducible setup/build instructions. An external repository link alone is not sufficient. The official copy is intended to remain available if the original repository later becomes unavailable. Do not include secrets, credentials, or private user data; clearly disclose external and private-service dependencies.

The automated checks report technical checks separately. A workflow failure is not a judging decision. Keep updates in this PR while submissions remain open, and keep the documented source version and deployment evidence consistent.

See the submission instructions. Final review results and awards will be announced separately through the official event channels.