riverbankcms 0.2.0 → 0.4.0

package/dist/cli/init-docs/content/workflow-remote-setup.md

@@ -1,6 +1,9 @@
 # Remote Site, Key, and User Access Setup
 
-This SDK project can sync content once it has a site ID, dashboard URL, and site-scoped management key. Creating the remote site, issuing keys, and granting dashboard user access are admin operations.
+This SDK project can sync content once it has a site ID, dashboard URL, and
+site-scoped management key. The authenticated Riverbank CLI can create a site
+and link project credentials for the signed-in account. Additional user access
+remains a dashboard operation.
 
 ## Check the Plan
 
@@ -18,18 +21,50 @@ riverbankcms setup plan --env=remote --json
 
 ## Authority Model
 
-- Dashboard/admin users can create sites, issue site-scoped management keys, and grant dashboard access.
-- Approved CMS repo scripts can do the same when run with service-role/admin credentials.
-- SDK management keys can verify access and sync content/config for one site. They cannot create sites, issue new keys, or grant user access.
+- The authenticated Riverbank CLI can create sites and issue project
+  credentials for the signed-in account through `sites create`, `link`, and
+  `init`.
+- Dashboard administrators can manage sites, issue credentials, and grant
+  access to additional users.
+- SDK management keys can verify access and sync content/config for one site.
+  They cannot create sites or grant other users access.
 
-Do not put platform-admin, service-role, or user-session credentials in an SDK site repository.
+The CLI stores its refresh session in the OS credential store when available.
+It never puts account sessions, platform-admin credentials, or service-role
+credentials in an SDK site repository.
+
+Production account OAuth is deliberately rollout-disabled. Use the staging (or
+local) account environment while that rollout is disabled; replace
+`<account-environment>` with `production` only after production account access
+has been explicitly enabled.
 
 ## Remote Setup Lifecycle
 
-1. Create or choose the remote site from the dashboard/admin surface.
-2. Generate a management key for that site.
-3. Grant the site owner or editor dashboard access from the dashboard/admin surface.
-4. Add the remote SDK variables to `.env.local`:
+1. Sign in to the account environment:
+
+```bash
+riverbankcms login --account-env=<account-environment>
+```
+
+2. Create a site or choose one visible to the signed-in account:
+
+```bash
+riverbankcms sites list --account-env=<account-environment>
+riverbankcms sites create --account-env=<account-environment> --name "My Site" --yes
+```
+
+3. Link the project. `--preview` includes preview routes and a preview
+   credential; use `--no-preview` to omit them:
+
+```bash
+riverbankcms link --project . --account-env=<account-environment> --site <site-id> --preview
+```
+
+For a new directory, use `riverbankcms init` instead; it scaffolds, links,
+initializes docs, and builds the complete project.
+
+4. Add the remote SDK variables to `.env.local` when linking an existing
+   project manually:
 
 ```bash
 RIVERBANK_REMOTE_SITE_ID=your-site-id
@@ -48,4 +83,25 @@ riverbankcms push --env=remote --dry-run
 
 ## Existing Sites and Users
 
-For an existing remote site, copy its site ID and create a fresh site-scoped management key if the old one is missing or should be rotated. Associate existing users with the site through the dashboard/admin surface. If the user does not exist yet, invite or create them through that approved flow rather than through the Riverbank CLI.
+For an existing remote site, use `riverbankcms link` so the CLI issues the
+needed site-scoped credentials and writes only ignored project env files.
+Associate additional users with the site through the dashboard/admin surface.
+If local work fails after the site is created, keep the site and resume with
+the reported `riverbankcms init --resume <directory>` command after fixing the
+local error.
+
+## Post-deployment revalidation
+
+`init` scaffolds `/api/revalidate` but does not register a webhook or write a
+webhook secret. Once the deployed site has a public HTTPS origin, activate
+revalidation explicitly:
+
+```bash
+riverbankcms webhooks setup \
+  --env=remote \
+  --url=https://www.example.com/api/revalidate \
+  --yes
+```
+
+Until then, the generated site’s ISR interval is the freshness fallback. Keep
+the one-time webhook secret in the deployment environment, not source control.

package/dist/{eventUpsertInputSchema-BUeXa6jk.mjs → eventUpsertInputSchema-Dg60PKJI.mjs}

@@ -1,5 +1,6 @@
 #!/usr/bin/env node
-import { a as classifySdkEventPricing, i as classifySdkEventSchedule, o as classifySdkEventPaymentTerms, r as sdkEventUpsertOptionalFieldSchemas } from "./sdk-event-upsert-CTqsrhFT.mjs";
+import { c as EVENT_PRESET_VALUES } from "./src-BRAF1Dee.mjs";
+import { a as classifySdkEventPricing, i as classifySdkEventSchedule, o as classifySdkEventPaymentTerms, r as sdkEventUpsertOptionalFieldSchemas } from "./sdk-event-upsert-C6zsxDcf.mjs";
 import { z } from "zod";
 
 //#region ../blocks/src/lib/typeGuards.ts
@@ -2044,21 +2045,21 @@ const EVENT_CONTENT_TYPE_SCHEMA = {
 		{
 			id: "summary",
 			type: "textarea",
-			label: "Summary",
-			description: "Short teaser shown in listings.",
+			label: "Short introduction",
+			description: "Write one or two sentences that help people quickly understand what this is. It appears wherever the event is listed and near the top of its page.",
 			rows: 3
 		},
 		{
 			id: "image",
 			type: "media",
-			label: "Listing image",
-			description: "Optional image used for event cards and previews."
+			label: "Event image",
+			description: "Choose the main image people will see wherever the event is listed and on its page."
 		},
 		{
 			id: "body",
 			type: "richText",
-			label: "Details",
-			description: "Full event details and agenda."
+			label: "About this event",
+			description: "Add the main information people need before booking—what to expect, who it’s for, what’s included, and anything they should bring or know."
 		}
 	],
 	routing: {
@@ -2070,6 +2071,10 @@ const EVENT_CONTENT_TYPE_SCHEMA = {
 			kind: "event-occurrence",
 			segmentType: "uuid-or-date",
 			precedence: "subroute-first"
+		}, {
+			kind: "event-run",
+			segmentType: "slug",
+			precedence: "content-first"
 		}]
 	},
 	labels: {
@@ -4913,14 +4918,7 @@ const eventUpsertInputSchema = z.object({
 	slug: z.string().min(1).optional(),
 	content: z.record(z.string(), z.unknown()).optional(),
 	blocks: sdkEntrySlotBlocksInputSchema.optional(),
-	preset: z.enum([
-		"event",
-		"class",
-		"course",
-		"workshop",
-		"retreat",
-		"performance"
-	]),
+	preset: z.enum(EVENT_PRESET_VALUES),
 	runRefs: z.tuple([z.string().min(1)], z.string().min(1)),
 	runs: z.tuple([eventRunInputSchema], eventRunInputSchema)
 }).superRefine((input, ctx) => input.runs.forEach((run, index) => {

package/dist/{load-config-CJUwrGHA.mjs → load-config-Co37ncZD.mjs}

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { n as assertCompatibleSdkPeer } from "./sdk-peer-D9FHJ54i.mjs";
+import { n as assertCompatibleSdkPeer } from "./sdk-peer-DZNUBvf5.mjs";
 import { dirname, resolve } from "path";
 import { createJiti } from "jiti";
 import { existsSync } from "fs";

package/dist/load-config-Dz8ygC-Z.mjs

@@ -0,0 +1,5 @@
+#!/usr/bin/env node
+import "./sdk-peer-DZNUBvf5.mjs";
+import { t as loadConfigFile } from "./load-config-Co37ncZD.mjs";
+
+export { loadConfigFile };