Add detailed diagnostics to Dokploy deployment workflow

docs/dokploy-deployment.md

@@ -116,10 +116,21 @@ the commit, upload it, and inspect deployment status. Gitea documents how
 runner labels select host versus Docker execution in the [runner
 documentation](https://gitea.com/gitea/runner/src/branch/main/README.md#labels).
 
-Every push to `master` triggers a deployment. The job suppresses API response
-bodies and infrastructure addresses in its logs, waits for Dokploy's deployment
-status, and fails if the upload or deployment fails. Build logs remain available
-in the Dokploy dashboard.
+Every push to `master` triggers a deployment. The job logs the pinned target,
+commit, curl/TLS runtime versions, DNS results, proxy configuration (without
+credentials), CA configuration status, and source archive size. Each request logs
+curl's exit code, HTTP status, connection IPs, certificate verification result,
+transfer sizes, and DNS/TCP/TLS/first-byte/total timings. Curl errors are preserved
+and common DNS, connection, proxy, timeout and certificate failures include hints.
+
+Failed responses include selected headers, JSON error/message fields, or an HTML
+page title. API keys and application IDs are redacted; cookies, source archives,
+deployment payloads and complete response bodies are not printed. The workflow
+does not enable shell tracing, disable TLS verification, follow authenticated
+redirects, or retry source uploads automatically. HTTP `000` means no HTTP
+response was received; inspect the curl exit code and error immediately above it.
+The job waits for Dokploy's deployment status and fails if the upload or deployment
+fails. Build logs remain available in the Dokploy dashboard.
 
 `git archive` sends tracked files from that commit only. It does not include
 `.git` metadata, local environment files, untracked files, or local caches. The