docs: AI_CAPABILITIES.md changelog for MCP v2.4.7

Made-with: Cursor

AI_CAPABILITIES.md

@@ -587,7 +587,7 @@ The MCP descriptor at `GET /api/mcp` reports a semver `version`. Tool names
 are append-only within a major version — agents can cache the tool list
 safely for the duration of a conversation but should re-fetch on 404.
 
-Current version: **2.4.6**.
+Current version: **2.4.7**.
 
 - **1.x** — session-cookie-only MCP, no tenant keys.
 - **2.0** — `vibn_sk_…` keys, workspace-scoped Gitea bot + Coolify project.
@@ -674,6 +674,16 @@ Current version: **2.4.6**.
     serving Traefik 503 or Mixed Content errors, or whenever a user
     rotates a custom domain. Params: `{ uuid, fqdn, publicAppName,
     port? }`. Returns `{ reachable, postDeploy: { steps }, probe }`.
+- **2.4.7** — `applyCoolifyPostDeployFixes` now schedules the
+  `coolify-proxy` restart (step 5) as a fire-and-forget background
+  job (`(sleep 3 && docker restart coolify-proxy) &`) instead of
+  blocking on it synchronously. The proxy restart kills any in-flight
+  TCP connection through the gateway — including the very request
+  that's running `apps.repair` / `apps.create` — so doing it inline
+  caused the agent to see a curl framing error (exit 16) right when
+  the work was in fact succeeding. Now the SSH command returns within
+  ~50ms, the HTTP response is delivered, and Traefik re-discovers
+  labels ~3s later.
 
 ---