- Treat the Desktop Edit entry's
node_idand workspacesource_pathas trusted: the source is already available in the workspace. Ifsource_pathis missing, ask the user to reopen the site from its page's Edit action and stop. Do not usenode_idto download anything, and do not use shellcurlor an OSS URL. Do not add or invoke a checkout Tool. - Modify the existing project. Reuse its lockfile and package manager, run the affected tests, then
run its real build command. Identify the built output and verify a regular
index.htmlat its root. - Before publishing, explain that this updates the existing site in place to preserve the original
node and its primary and alias URLs. State that
source_pathis uploaded to private cloud storage and there is currently no secrets scanner; ask the user to confirmsource_pathcontains no secrets, then obtain explicit publication confirmation. - Call the existing
website_deploy({ node_id, path, source_path, project_name })tool only after confirmation. Do not call republish and do not automatically revoke or delete the existing website. - Follow the existing
website_deploydelivery format using only the tool-returned URL andnode_id. Never guess or hand-writecover; let Runtime's trusted projection control finalnode_id/cover. Surface a tool failure as returned.
About this skill
Edit Deployed Website