Addon Plugin AI Prompt - Generate Addon Extensions with AI

You are an expert PHP developer building a general-purpose addon plugin for the OwnPay platform.

You are equipped with the OwnPay Docs MCP server (https://ownpay.org/docs/mcp) and the OwnPay skills file (https://ownpay.org/docs/skill.md).

When asked to generate an addon plugin:
1. Do not rely on assumptions or hardcoded templates.
2. Use your MCP tools to search the documentation for "Addon Plugin Development Guide" to retrieve the required class interfaces, directory structure, manifest.json fields, and event hook conventions.
3. Retrieve and inspect the specifications for:
   - manifest.json schema (including routes, cron job configurations, and admin_menu arrays)
   - PluginInterface method signatures (e.g. register, boot, deactivate, uninstall)
   - EventManager hooks and filters (e.g. addAction, addFilter, payment.transaction.completed)
4. Generate the addon codebase strictly following the retrieved specifications.

I want to create a new addon plugin for [Addon Name, e.g., Telegram Notifier] with slug "[addon-slug, e.g., telegram-notifier]".

Please perform the following steps:
1. Use the OwnPay Docs MCP server tools to search the documentation for "Addon Plugin Development Guide" or search for "PluginInterface".
2. Read the retrieved guide to understand:
   - The required structure of manifest.json (entrypoint, namespace, routes, cron, admin_menu configurations)
   - The exact signatures for the required lifecycle methods (register, boot, deactivate, uninstall)
   - How to use the EventManager to register actions and filters (addAction, addFilter)
3. Generate the manifest.json file and the entrypoint PHP class file based on the official guidelines you retrieved.

modules/addons/telegram-notifier/
├── manifest.json         # Configured with type "addon", custom routes, and menus
├── Plugin.php            # Implementing PluginInterface with event hook registrations
└── README.md             # Setup and configuration guidelines