showpane 0.4.20 → 0.4.23

package/bundle/meta/scaffold-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-04-12T08:47:16.973Z",
+  "generatedAt": "2026-04-12T11:40:53.513Z",
   "scaffoldVersion": "0.2.7",
   "files": {
     ".env.example": "ed105f2bdcd1888a98181d55e3c9f7d6eff3ae9c3e2366c2e777a12e3caddfa7",
@@ -12,7 +12,7 @@
     "postcss.config.js": "fa650b380adfabb151a0b352f7135e107e6352345f899060f1c5c231228f94bf",
     "prisma.config.ts": "36f56fd74eae70632e484443e38d08665158d72d5c978dc456651d8d5e1a636e",
     "prisma/schema.local.prisma": "f5d6f3cb17d6d229f46ef82eef7c0ff4261596924f0173fef075ac394f423073",
-    "prisma/seed.ts": "98f7d5fd97ce2ff66bdf060ccb6695416d18ac983672b256d5d95d315ccee6e5",
+    "prisma/seed.ts": "01b4295296676ab415ab2b30b4e39e13c3fdd30c3bab2b22a7cca672d1c2ea90",
     "public/example-avatar.svg": "0edeb0d3fbefa89cc27ffe6564d20e3ee0fd073cb6d9f2a025248ef3b3f277fd",
     "public/example-logo.svg": "bc5cd933aff2a17698dee66a7b4ea940ad12238e9d813474d643b459b1e8d6da",
     "public/robots.txt": "331ea9090db0c9f6f597bd9840fd5b171830f6e0b3ba1cb24dfa91f0c95aedc1",

package/bundle/scaffold/prisma/seed.ts

@@ -30,11 +30,15 @@ async function main() {
 
   const organizationSlug =
     process.env.SHOWPANE_ORG_SLUG?.trim() || normalizeSlug(organizationName);
-  const contactName = process.env.SHOWPANE_CONTACT_NAME?.trim() || null;
-  const contactEmail = process.env.SHOWPANE_CONTACT_EMAIL?.trim() || null;
+  const contactName = process.env.SHOWPANE_CONTACT_NAME?.trim() || organizationName;
+  const contactEmail = process.env.SHOWPANE_CONTACT_EMAIL?.trim() || "";
   const websiteUrl = normalizeWebsiteUrl(process.env.SHOWPANE_WEBSITE_URL);
   const contactTitle = "Point of contact";
 
+  if (!contactEmail) {
+    throw new Error("SHOWPANE_CONTACT_EMAIL is required to seed the local organization");
+  }
+
   const org = await prisma.organization.upsert({
     where: { slug: organizationSlug },
     update: {},

package/bundle/toolchain/CLI_VERSION

@@ -1 +1 @@
-0.4.20
+0.4.23

package/bundle/toolchain/VERSION

@@ -1 +1 @@
-1.1.7 (requires app >= 0.2.7)
+1.1.8 (requires app >= 0.2.7)

package/bundle/toolchain/bin/get-org.ts

@@ -28,7 +28,22 @@ async function main() {
   try {
     const org = await prisma.organization.findUnique({
       where: { slug },
-      select: { id: true, slug: true, name: true },
+      select: {
+        id: true,
+        slug: true,
+        name: true,
+        logoUrl: true,
+        primaryColor: true,
+        portalLabel: true,
+        websiteUrl: true,
+        contactName: true,
+        contactTitle: true,
+        contactEmail: true,
+        contactPhone: true,
+        contactAvatar: true,
+        supportEmail: true,
+        customDomain: true,
+      },
     });
 
     if (!org) {

package/bundle/toolchain/skills/portal-create/SKILL.md

@@ -128,6 +128,12 @@ Store:
 
 - `ORG_ID`
 - `ORG_NAME`
+- `ORG_CONTACT_NAME`
+- `ORG_CONTACT_TITLE`
+- `ORG_CONTACT_EMAIL`
+- `ORG_CONTACT_AVATAR`
+- `ORG_SUPPORT_EMAIL`
+- `ORG_WEBSITE_URL`
 
 If the helper fails, stop and tell the user to run `/portal-setup` again instead
 of guessing with ad-hoc SQL.
@@ -135,11 +141,14 @@ of guessing with ad-hoc SQL.
 Do not probe `showpane --help`, `package.json`, `scripts/`, `prisma/`, or template
 directories just to understand the project. Do not call `check-slug.ts` with
 anything except `--org-id`.
+Do not re-read config, Prisma, or SQLite to rediscover org fields that were already
+returned by `get-org.ts`.
 
 The canonical references for this skill are:
 
 - the configured `APP_PATH`
 - the configured `ORG_SLUG`
+- the org fields returned by `get-org.ts`
 - this skill file
 - `$SKILL_DIR/templates/<chosen-template>/...`
 - `$APP_PATH/src/app/(portal)/client/example/example-client.tsx`
@@ -277,13 +286,13 @@ import { PortalShell } from "@/components/portal-shell";
 - The exported component returns `<PortalShell>` with all required props
 
 **PortalShell props (all required):**
-- `companyName` — the org's company name (from config/DB)
+- `companyName` — the org's company name (from `ORG_NAME`)
 - `companyLogo` — a `<span>` with the first letter of the company name, white text
 - `clientName` — the client's company name (from transcript or user input)
 - `clientLogoSrc` — if client domain was provided: use `getLogoUrl(domain)` from `app/src/lib/branding.ts`. If not: use `getInitialLogo(clientName)` to generate an SVG data URI. Store the chosen URL in the ClientPortal record's `logoUrl` field
 - `clientLogoAlt` — the client company name
 - `lastUpdated` — today's date formatted as "7 April 2026"
-- `contact` — object with `name`, `title`, `avatarSrc`, `email` (from org config)
+- `contact` — object with `name`, `title`, `avatarSrc`, `email` (from the `get-org.ts` result, not from ad-hoc config or DB probing)
 - `tabs` — array of tab objects with `id`, `label`, `icon`, `content`, and optional `badge`
 - `hideFooterOnTab` — set to `"overview"` (hides the contact footer on the first tab since it typically has contact info inline)
 

package/bundle/toolchain/skills/portal-create/SKILL.md.tmpl

@@ -33,6 +33,12 @@ Store:
 
 - `ORG_ID`
 - `ORG_NAME`
+- `ORG_CONTACT_NAME`
+- `ORG_CONTACT_TITLE`
+- `ORG_CONTACT_EMAIL`
+- `ORG_CONTACT_AVATAR`
+- `ORG_SUPPORT_EMAIL`
+- `ORG_WEBSITE_URL`
 
 If the helper fails, stop and tell the user to run `/portal-setup` again instead
 of guessing with ad-hoc SQL.
@@ -40,11 +46,14 @@ of guessing with ad-hoc SQL.
 Do not probe `showpane --help`, `package.json`, `scripts/`, `prisma/`, or template
 directories just to understand the project. Do not call `check-slug.ts` with
 anything except `--org-id`.
+Do not re-read config, Prisma, or SQLite to rediscover org fields that were already
+returned by `get-org.ts`.
 
 The canonical references for this skill are:
 
 - the configured `APP_PATH`
 - the configured `ORG_SLUG`
+- the org fields returned by `get-org.ts`
 - this skill file
 - `$SKILL_DIR/templates/<chosen-template>/...`
 - `$APP_PATH/src/app/(portal)/client/example/example-client.tsx`
@@ -182,13 +191,13 @@ import { PortalShell } from "@/components/portal-shell";
 - The exported component returns `<PortalShell>` with all required props
 
 **PortalShell props (all required):**
-- `companyName` — the org's company name (from config/DB)
+- `companyName` — the org's company name (from `ORG_NAME`)
 - `companyLogo` — a `<span>` with the first letter of the company name, white text
 - `clientName` — the client's company name (from transcript or user input)
 - `clientLogoSrc` — if client domain was provided: use `getLogoUrl(domain)` from `app/src/lib/branding.ts`. If not: use `getInitialLogo(clientName)` to generate an SVG data URI. Store the chosen URL in the ClientPortal record's `logoUrl` field
 - `clientLogoAlt` — the client company name
 - `lastUpdated` — today's date formatted as "7 April 2026"
-- `contact` — object with `name`, `title`, `avatarSrc`, `email` (from org config)
+- `contact` — object with `name`, `title`, `avatarSrc`, `email` (from the `get-org.ts` result, not from ad-hoc config or DB probing)
 - `tabs` — array of tab objects with `id`, `label`, `icon`, `content`, and optional `badge`
 - `hideFooterOnTab` — set to `"overview"` (hides the contact footer on the first tab since it typically has contact info inline)
 

package/bundle/toolchain/skills/portal-deploy/SKILL.md

@@ -131,10 +131,9 @@ fi
 If the token is missing, stop and tell the user:
 
 - `showpane login` is the right next step
-- it opens browser auth for Showpane Cloud automatically
-- if they need an account first:
-  - sign up: `https://app.showpane.com/sign-up`
-  - sign in: `https://app.showpane.com/sign-in`
+- it owns the whole browser flow now: sign up or sign in if needed, start checkout,
+  then return to CLI authorization automatically
+- do not manually steer the user through separate sign-up, sign-in, or checkout steps
 
 If they are already inside Claude Code, explicitly suggest:
 
@@ -536,7 +535,7 @@ If the health endpoint returns non-200 after deploy:
 If the Showpane Cloud API returns 401/403 during pre-flight or publish:
 - **401 Unauthorized**: The access token is expired or revoked. Run `showpane login` to re-authenticate.
 - **403 Forbidden**: The token does not belong to an org that can publish. Re-authenticate or finish cloud onboarding.
-- **409 organization_required**: The user authenticated but has no org yet. Send them to Showpane Cloud checkout to start the trial, then re-run `showpane login`.
+- **409 organization_required**: Tell the user to run `showpane login` again and let that browser flow continue. Do not manually redirect them into separate checkout steps from this skill.
 - **409 organization_not_ready**: The org exists, but billing or provisioning is not publish-ready. Surface the returned `reason`, `nextAction`, and settings/checkout URL directly instead of collapsing it into a generic deploy failure.
 
 ### Cloud: Artifact upload failure

package/bundle/toolchain/skills/portal-deploy/SKILL.md.tmpl

@@ -36,10 +36,9 @@ fi
 If the token is missing, stop and tell the user:
 
 - `showpane login` is the right next step
-- it opens browser auth for Showpane Cloud automatically
-- if they need an account first:
-  - sign up: `https://app.showpane.com/sign-up`
-  - sign in: `https://app.showpane.com/sign-in`
+- it owns the whole browser flow now: sign up or sign in if needed, start checkout,
+  then return to CLI authorization automatically
+- do not manually steer the user through separate sign-up, sign-in, or checkout steps
 
 If they are already inside Claude Code, explicitly suggest:
 
@@ -441,7 +440,7 @@ If the health endpoint returns non-200 after deploy:
 If the Showpane Cloud API returns 401/403 during pre-flight or publish:
 - **401 Unauthorized**: The access token is expired or revoked. Run `showpane login` to re-authenticate.
 - **403 Forbidden**: The token does not belong to an org that can publish. Re-authenticate or finish cloud onboarding.
-- **409 organization_required**: The user authenticated but has no org yet. Send them to Showpane Cloud checkout to start the trial, then re-run `showpane login`.
+- **409 organization_required**: Tell the user to run `showpane login` again and let that browser flow continue. Do not manually redirect them into separate checkout steps from this skill.
 - **409 organization_not_ready**: The org exists, but billing or provisioning is not publish-ready. Surface the returned `reason`, `nextAction`, and settings/checkout URL directly instead of collapsing it into a generic deploy failure.
 
 ### Cloud: Artifact upload failure

package/bundle/toolchain/skills/portal-onboard/SKILL.md

@@ -290,9 +290,17 @@ Save checkpoint with:
 
 ### Phase 5: Practical refinements
 
-Do not ask the user to invent a whole redesign. Ask for one or two high-signal refinements only.
+This phase is optional.
 
-Recommended refinement prompts:
+Default behavior: do not stop to ask for refinements right after the draft is created.
+Move straight to preview unless one of these is true:
+
+- the user explicitly asked to polish before preview
+- there is an obvious missing practical element that would make the preview misleading
+
+If you do need a refinement prompt, keep it to one short, high-signal question.
+
+Recommended options:
 
 - `Do you want the portal to feel more concise, more sales-focused, or more delivery-focused?`
 - `Should we add anything practical before preview — timeline, documents, or sharper next steps?`
@@ -300,12 +308,18 @@ Recommended refinement prompts:
 Apply the requested refinement inline, using the same patterns as `/portal-update`
 without forcing the user to switch skills.
 
-If the user is happy with the first draft, move on immediately.
+If no refinement is needed, skip this phase entirely.
 
 Save checkpoint with phase `draft-refined`.
 
 ### Phase 6: Local preview
 
+The default path is:
+
+1. create the draft
+2. show local credentials if they were generated
+3. open the preview immediately
+
 Run the `portal-preview` flow inline.
 
 If no dev server is running, start it using the `portal-dev` instructions first.
@@ -320,6 +334,9 @@ the preview link. Keep it simple:
 Do this before opening the browser so the user is not dropped onto a login screen
 without the credentials they need.
 
+After that, open the local preview immediately. Do not ask a separate
+"do you want refinements first?" question unless the user already asked for that.
+
 Tell the user exactly what to inspect:
 
 - does the overall story feel right?

package/bundle/toolchain/skills/portal-onboard/SKILL.md.tmpl

@@ -197,9 +197,17 @@ Save checkpoint with:
 
 ### Phase 5: Practical refinements
 
-Do not ask the user to invent a whole redesign. Ask for one or two high-signal refinements only.
+This phase is optional.
 
-Recommended refinement prompts:
+Default behavior: do not stop to ask for refinements right after the draft is created.
+Move straight to preview unless one of these is true:
+
+- the user explicitly asked to polish before preview
+- there is an obvious missing practical element that would make the preview misleading
+
+If you do need a refinement prompt, keep it to one short, high-signal question.
+
+Recommended options:
 
 - `Do you want the portal to feel more concise, more sales-focused, or more delivery-focused?`
 - `Should we add anything practical before preview — timeline, documents, or sharper next steps?`
@@ -207,12 +215,18 @@ Recommended refinement prompts:
 Apply the requested refinement inline, using the same patterns as `/portal-update`
 without forcing the user to switch skills.
 
-If the user is happy with the first draft, move on immediately.
+If no refinement is needed, skip this phase entirely.
 
 Save checkpoint with phase `draft-refined`.
 
 ### Phase 6: Local preview
 
+The default path is:
+
+1. create the draft
+2. show local credentials if they were generated
+3. open the preview immediately
+
 Run the `portal-preview` flow inline.
 
 If no dev server is running, start it using the `portal-dev` instructions first.
@@ -227,6 +241,9 @@ the preview link. Keep it simple:
 Do this before opening the browser so the user is not dropped onto a login screen
 without the credentials they need.
 
+After that, open the local preview immediately. Do not ask a separate
+"do you want refinements first?" question unless the user already asked for that.
+
 Tell the user exactly what to inspect:
 
 - does the overall story feel right?

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "showpane",
-  "version": "0.4.20",
+  "version": "0.4.23",
   "description": "CLI for Showpane — AI-generated client portals",
   "type": "module",
   "bin": {