feat(publish): Coolify deploy webhook field for host: coolify

[vianmora]

Fork side of webstudio-self-host#23 (publisher side: webstudio-publisher#37).

When Hosting = "Coolify (remote)" is selected in the Advanced settings disclosure, the Publish panel shows:

• a required Coolify deploy webhook URL input
• an optional Bearer token input (password field)
• a "Host with Coolify" link to the self-host docs

Publish is blocked (button disabled + tooltip) until the webhook URL is filled.

The webhook + token are persisted per-project in localStorage (publish:coolifyWebhook:<id> / …Token:<id>) and forwarded to the publisher on each publish (coolifyWebhookUrl / coolifyWebhookToken) — never stored server-side or in Build.deployment (no bundle-schema change, no migration).

Threaded through: publishInput (trpc-interface), the domain.publish procedure, publishProject, and the REST publish.create input (metadata regenerated).

🤖 Generated with Claude Code

https://claude.ai/code/session_017rF3HMB1Z7V3LLsYaUrELs

[github-actions]

🧪 Test images for this PR

Role	Image	Status
builder	ghcr.io/webstudio-community/builder:feat-publish-coolify-webhook	✅ built
publisher	ghcr.io/webstudio-community/webstudio-publisher:builder-feat-publish-coolify-webhook	✅ built (run)

Point BUILDER_IMAGE / PUBLISHER_IMAGE on the Coolify test stack at these two tags — they are built from the same fork commit and must be deployed together.

_{Updated for e9b1050dd342c54a76770b220df54580c44d0b96 · 2026-09-08 20:28 UTC}