@biznetgio/neo-app 0.4.67 → 0.4.68

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@biznetgio/neo-app",
-  "version": "0.4.67",
+  "version": "0.4.68",
   "description": "NEO App CLI — one-command agent onboarding, MCP server, and project ops for coding agents (Codex, Claude Code).",
   "type": "module",
   "bin": {

package/src/mcp/tools.js

@@ -510,6 +510,15 @@ export const TOOLS = [
       return result(status, data);
     },
   },
+  {
+    name: 'neo_get_webhook',
+    description: 'Push-to-deploy (auto-deploy) integration status for a service (JNG #142). "Auto-deploy enabled" is NOT the same as "webhook active": this returns `status` = active (a delivery has been received) or **pending_setup** (NEO has never heard from the git provider — the webhook was likely never installed), plus `lastDeliveryAt` and the `setupUrl` to add to the repo. If pending_setup, add `setupUrl` as a push webhook (content-type application/json) in the repo\'s Settings → Webhooks; manual neo_deploy always works meanwhile.',
+    mutating: false,
+    schema: { type: 'object', properties: { appId: str('Service/app id') }, required: ['appId'] },
+    async call(api, args) {
+      return (await api.get(`/api/v1/apps/${args.appId}/webhook`)).data;
+    },
+  },
   {
     name: 'neo_get_domain_status',
     description: 'Check a custom domain\'s readiness to a TERMINAL state (JNG #112 §8.6): whether it is attached, whether DNS resolves to the expected CNAME target (with an expected-vs-observed diagnostic), whether managed TLS has been issued, and whether HTTPS actually serves a valid certificate for the host. Poll this after neo_add_service_domain + redeploy until ready:true — do NOT assume "attach accepted" means live. Returns {attached, expectedTarget, dns:{pointed,observed,diagnostic}, tls:{issued}, https:{ok,statusCode,certHostnameValid}, ready}.',