feat(mcp): notify users website CDN deployment can take up to 5 minutes

[pcfreak30]

Guides the agent to tell users that after publishing or updating a website, the site can take up to 5 minutes to fully deploy to the CDN and may not resolve at its URL immediately.

Carried on all three publish_website domain branches (platform subdomain, explicit label, custom domain) and the update_website flow, plus the website onboarding/update prompt templates. Platform-domain validation remains instant — the notice covers CDN deployment only.

---

Summary

This PR updates the MCP (Model Context Protocol) agent guide and onboarding/update prompt templates to notify users that website CDN deployment can take up to 5 minutes after publishing or updating a site.

Changes

1. CDN deployment notice added to agent guide (internal/mcp/agent_guide.go)

A new cdnDeployNoticeClause was introduced and appended to all website publish paths (generic platform subdomain, explicit label, custom domain) and the website update flow. The notice instructs the agent to inform the user that a newly published or updated site can take up to 5 minutes to fully deploy to the CDN, so it may not be reachable at its URL immediately even though create/validation succeeded. This clarifies that CDN deployment is independent of validation (platform-domain validation is instant).

2. Notice added to prompt templates (internal/mcp/prompttemplates/website_onboarding.tmpl)

• Website onboarding completion step: Added guidance to let the user know the site can take up to 5 minutes to fully deploy to the CDN after the onboarding wizard returns "complete": true.
• Website update completion step: Added similar guidance to the update workflow completion template, informing users the site can take up to 5 minutes to fully deploy to the CDN after an update.

3. Test coverage (internal/mcp/agent_guide_test.go)

Added a new test (TestAgentGuideCDNDeployNotice) that verifies:

• Every website publish branch (generic, label, custom domain) across all platform profiles includes the CDN deploy notice (5 minutes to fully deploy)
• The update_website flow also carries the CDN deploy notice for all platform profiles

Purpose

This change sets user expectations appropriately: after publishing or updating a website, users should be aware that the site may not be immediately reachable at its URL due to CDN deployment lag (up to 5 minutes), even when creation or validation succeeds instantly. This prevents confusion when users try to access the site right after deployment.

[kody-ai]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​

[github-actions]

Code Coverage Report

Total Coverage: 50.1%

Generated from commit: cc2200f
Repository: LumeWeb/pinner-cli