siteplane 0.1.51 → 0.1.53
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +25 -0
- package/dist/bin/siteplane.js +454 -203
- package/dist/index.js +254 -179
- package/dist/next.js +245 -177
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -10,6 +10,31 @@ policies and check real rendered images after the change. This preparation does
|
|
|
10
10
|
Public Siteplane CLI for connected-site setup, field synchronization, Analytics
|
|
11
11
|
instrumentation and Booking integration.
|
|
12
12
|
|
|
13
|
+
## Controlled guest review
|
|
14
|
+
|
|
15
|
+
After a controlled accountless setup reaches `ready_for_review`, run `siteplane setup review`
|
|
16
|
+
in the same website repository. Its protected local installation key opens access to that project's
|
|
17
|
+
saved review without creating another site or deployment. Give the one-time link to the user;
|
|
18
|
+
they choose **Open review** in their own browser. Do not consume the link on their behalf.
|
|
19
|
+
Issue a fresh link only when needed. The URL fragment is a short-lived credential, so do not
|
|
20
|
+
write it to source, documentation, analytics or shared logs. Guest review can organize and finish
|
|
21
|
+
the setup; activation and account ownership require the later claim step. This entry remains
|
|
22
|
+
controlled while Batch 3 is being completed.
|
|
23
|
+
|
|
24
|
+
### Controlled claim confirmation
|
|
25
|
+
|
|
26
|
+
When the signed-in review supplies a claim code, run `siteplane setup claim inspect --code <code>`
|
|
27
|
+
in the original repository. Show the returned account, workspace and website to the user. After
|
|
28
|
+
they explicitly approve that concrete request, run `siteplane setup claim confirm --code <code>
|
|
29
|
+
--request <requestId>`. Inspection never confirms automatically. A code alone cannot claim a website;
|
|
30
|
+
the command also requires the original local installation key.
|
|
31
|
+
|
|
32
|
+
Confirmation saves the receipt in the ignored local credentials file before acknowledging it to
|
|
33
|
+
the server. If the response is lost, retry the same code and request. Keep the existing project,
|
|
34
|
+
connection and deployment. Claim revokes guest access and preserves only the still-open setup rights;
|
|
35
|
+
it does not activate modules or reopen a finished setup. The browser Auth/claim flow is still under
|
|
36
|
+
development, and the general accountless entry remains closed.
|
|
37
|
+
|
|
13
38
|
## Initial setup
|
|
14
39
|
|
|
15
40
|
Copy the setup prompt in Siteplane, then run its exact one-time command in the
|