siteplane 0.1.41 → 0.1.43

package/README.md

@@ -9,7 +9,8 @@ Copy the setup prompt in Siteplane, then run its exact one-time command in the
 website repository:
 
 ```bash
-npx -y siteplane@0.1.41 init --setup-token <one-time-setup-grant>
+npx -y siteplane@<exact-version> setup preflight
+npx -y siteplane@<exact-version> init --setup-token <one-time-setup-grant>
 npx siteplane setup context
 ```
 
@@ -18,6 +19,34 @@ stores it only in the ignored `.siteplane/credentials.json`. No browser approval
 is required. The same connection resumes the open setup and review corrections
 until the owner completes or revokes the setup.
 
+`setup context` returns the single `siteplane.setup-task.v2` task: exact packages, current run,
+authorized modules/scopes, separate unchanged user instructions, environment provenance and one next action.
+An initial instruction such as `Only prices` does not start a correction workflow. The agent integrates
+Siteplane's existing CMS editing layer, preserving the website; it does not build a separate CMS.
+
+Report observed work with `siteplane setup activity --phase inspecting` (also integrating, deploying,
+verifying or repairing). Reports are limited to one per 30 seconds; context polling is not activity.
+Optional Analytics preparation uses this same connection with explicit authorization. It grants no
+activation, import, reporting, booking or publishing rights. Standalone bootstrap cannot replace an open task.
+
+`setup prepare` installs the task's exact packages and creates the narrow official runtime integration.
+The agent chooses and instruments content, then persists a separate, bounded summary:
+
+```bash
+siteplane setup apply --definition editor-definition.json --selection-summary-file selection.txt
+siteplane setup deploy --wait
+```
+
+Commit only intended source before deploy. The CLI securely transfers its Production environment, adopts or
+starts one matching deployment and verifies the actual build and signed runtime. Unchanged resume creates no
+new deployment. A saved 15-minute provider deadline and operation identity prevent blind retries after response
+loss. Uploads use committed source in a temporary checkout; local credentials are never copied into it.
+
+For a lost connection, the owner chooses **Replace local connection** in the same open setup. Its new grant
+preserves the Site, Run, runtime key, revalidation generation, selected fields and provider admin-session secret.
+Completed setup credentials remain closed. Known package/workspace/provider conflicts are diagnosed before
+writes; support ranges do not trigger automatic framework or package-manager upgrades.
+
 ## Approved fields
 
 Run the exact command from Siteplane's compact apply prompt. It authenticates