showpane 0.4.24 → 0.4.26

package/bundle/meta/scaffold-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-04-13T21:26:42.638Z",
+  "generatedAt": "2026-04-13T22:42:22.971Z",
   "scaffoldVersion": "0.2.7",
   "files": {
     ".env.example": "ed105f2bdcd1888a98181d55e3c9f7d6eff3ae9c3e2366c2e777a12e3caddfa7",
@@ -11,7 +11,7 @@
     "package.json": "b095e17e7fc181c630e87fe9f473c5a4ef969afcd4b110f9f9c6d6a6d93f1c0b",
     "postcss.config.js": "fa650b380adfabb151a0b352f7135e107e6352345f899060f1c5c231228f94bf",
     "prisma.config.ts": "36f56fd74eae70632e484443e38d08665158d72d5c978dc456651d8d5e1a636e",
-    "prisma/schema.local.prisma": "f5d6f3cb17d6d229f46ef82eef7c0ff4261596924f0173fef075ac394f423073",
+    "prisma/schema.local.prisma": "90b9bc60e31a968137a574f156ad83ed5e46a45a8d6080b40126118806b9cd34",
     "prisma/seed.ts": "01b4295296676ab415ab2b30b4e39e13c3fdd30c3bab2b22a7cca672d1c2ea90",
     "public/example-avatar.svg": "0edeb0d3fbefa89cc27ffe6564d20e3ee0fd073cb6d9f2a025248ef3b3f277fd",
     "public/example-logo.svg": "bc5cd933aff2a17698dee66a7b4ea940ad12238e9d813474d643b459b1e8d6da",
@@ -19,6 +19,7 @@
     "scripts/prisma-db-push.mjs": "76ac85fe65b5dc3d9cc7432e44618fcc84b7443574c8d88198d01f13ac23c040",
     "scripts/prisma-generate.mjs": "d371e63388fa39f963b7c3c7cb8f87e0d9cd43cbf69d254b999108e29b8738c8",
     "scripts/prisma-schema.mjs": "0a86cc1b5f84120948aed8f97a84f2d5b173f91a43ea34ad6767441894121d83",
+    "src/__tests__/branding.test.ts": "dffbb3744705bc378ad91b9d7b8868004ffeaa45623f4748e1fed951096b9e3f",
     "src/__tests__/client-portals.test.ts": "9c3236bf0f7190b7d5ba9082287dcb29bc00d28dd63782a89505125ead06c624",
     "src/__tests__/deploy-bundle.test.ts": "abd3216170f306c09df6abb0d2afad966a5741e8859f25a310a0a09693d37609",
     "src/__tests__/portal-contracts.test.ts": "a3ecf29c460a14f22ef48449fc9de5b945ce5f03423f12380d05e01159d1e3b4",
@@ -27,7 +28,7 @@
     "src/app/(portal)/client/example/example-client.tsx": "ed32b111acea861f448d865338f8841d47c6ca7c2f87ed30d85bb0804940d4ec",
     "src/app/(portal)/client/example/page.tsx": "f330864f63c9feea76c8a62c3eba3ce57578627e0d4abd929fd7fefdfc7af058",
     "src/app/(portal)/client/layout.tsx": "4f43871510408a81da229d48ae316ec1d1c1beda93121922246300a2c8fd0999",
-    "src/app/(portal)/client/page.tsx": "7efe97c047e9ad8f5d9034fe616c0c915277a9cb92fa4ce57fe35af672c80320",
+    "src/app/(portal)/client/page.tsx": "cf0d1b0517aadf1bfbfc91552d0c13201a140c31d2df9e08e1c62a5d48e59189",
     "src/app/api/client-auth/route.ts": "ce1858559b1e944d5b1dc719d1f03bebf66286671700b1b5397382109f0f1e0d",
     "src/app/api/client-auth/share/route.ts": "ed82414212dcd26af8c6c0f2bd44d9d79a727ed35cfedbac8c4077a6220aad14",
     "src/app/api/client-events/route.ts": "13d545537b7e8ce421e6169d25c105adf2a2de3d978ae0a2c6751ff5f7d2eb33",
@@ -43,7 +44,7 @@
     "src/components/portal-login.tsx": "8b0d91bb28674e1102fd2e5b5ddcc3a93755dd806fbd3d1b2dbea2646cffca5e",
     "src/components/portal-shell.tsx": "f46a0f753a4a0318f06c8b4e46295febb84b03ea082c95057a6da50c737b4e21",
     "src/lib/abuse-controls.ts": "d79d58d93267aca48ad0b7b9b91f753c9a3c27263e4e98daf768a950c44a6fc6",
-    "src/lib/branding.ts": "cc55f40e02bc3e486b227988f95739ca1cda8012c97b591295995eb4465efd57",
+    "src/lib/branding.ts": "f0fa242c285610105c27fcaf76828f1892c8051fc2db5c36bdbe92ea916aa4bd",
     "src/lib/client-auth.ts": "b9bdfe77dbe5d6ec6c6a930627fc43d3253f0d76fd8fc4093af5a75742bebe42",
     "src/lib/client-portals.ts": "9b531f9a9ea459b4ab85257b9dd282874fa1422838fe89d511940e417114216a",
     "src/lib/control-plane.ts": "e0cf39f28ec7de715fd5cfbb5f4240773fcd3d775cd1677588dd749fff740a0e",
@@ -51,7 +52,7 @@
     "src/lib/deploy-bundle.ts": "e9675cccb2c802e408639481986c6b629737541853e1c93f322c08a5b9dfc5f9",
     "src/lib/files.ts": "24fd8d1d53c180d62441019395fb140ba3baa28311918ac488284adcdda8eb9a",
     "src/lib/load-app-env.ts": "78b80e17d896885f0d72315ee9a6cf7a0a8c6c08171f26e3d599bb9b2e8afeee",
-    "src/lib/portal-contracts.ts": "e3521b117239d0b0f9bc86a08607c6bb26f93dc1c47cd2dcf0485c2ca7358835",
+    "src/lib/portal-contracts.ts": "927695c64d4f7b56be9e7c0bc37fac105d37558404df8eac09c6f0d1a8f27669",
     "src/lib/prisma-client.ts": "28cd100129a0178a6c8fdfe49e6997b19983fcc427b9fa7caee3ac26226e5eb3",
     "src/lib/runtime-state.ts": "3d30de7dfeaaa48d8b6fd5d29976ecd001408172100c95b063d5d804fdce0a2e",
     "src/lib/storage.ts": "ae3b85fc6cccd39d4174a391dcbe6e91fb9460eb407ec9dbfedd63594a441d08",

package/bundle/scaffold/prisma/schema.local.prisma

@@ -69,6 +69,7 @@ model ClientPortal {
   organizationId    String
   slug              String
   companyName       String
+  websiteUrl        String?
   logoUrl           String?
 
   // Auth

package/bundle/scaffold/src/__tests__/branding.test.ts

@@ -0,0 +1,43 @@
+import { describe, expect, it } from "vitest";
+
+import {
+  getBrandLogoUrl,
+  getDomainFromWebsite,
+  getLogoUrl,
+  normalizeWebsiteUrl,
+} from "@/lib/branding";
+
+describe("branding helpers", () => {
+  it("normalizes bare domains into https URLs", () => {
+    expect(normalizeWebsiteUrl("bidgen.io")).toBe("https://bidgen.io/");
+    expect(normalizeWebsiteUrl("https://bidgen.io")).toBe("https://bidgen.io/");
+  });
+
+  it("extracts hostnames from bare domains and full URLs", () => {
+    expect(getDomainFromWebsite("bidgen.io")).toBe("bidgen.io");
+    expect(getDomainFromWebsite("https://www.bidgen.io/path")).toBe("www.bidgen.io");
+  });
+
+  it("prefers a stored logo URL, then website-derived logos, then initials", () => {
+    expect(
+      getBrandLogoUrl({
+        logoUrl: "https://cdn.example/logo.png",
+        websiteUrl: "bidgen.io",
+        fallbackName: "Bidgen",
+      }),
+    ).toBe("https://cdn.example/logo.png");
+
+    expect(
+      getBrandLogoUrl({
+        websiteUrl: "bidgen.io",
+        fallbackName: "Bidgen",
+      }),
+    ).toBe(getLogoUrl("bidgen.io", "Bidgen"));
+
+    expect(
+      getBrandLogoUrl({
+        fallbackName: "Bidgen",
+      }),
+    ).toBe(getLogoUrl("", "Bidgen"));
+  });
+});

package/bundle/scaffold/src/app/(portal)/client/page.tsx

@@ -1,5 +1,5 @@
 import { PortalLogin } from "@/components/portal-login";
-import { getInitialLogo } from "@/lib/branding";
+import { getBrandLogoUrl } from "@/lib/branding";
 import { prisma } from "@/lib/db";
 import { resolveDefaultOrganizationId } from "@/lib/client-portals";
 import { getRuntimePortalBySlug, getRuntimeState, isRuntimeSnapshotMode } from "@/lib/runtime-state";
@@ -12,12 +12,13 @@ export default async function ClientLogin({
   const params = (await searchParams) ?? {};
   const portalSlug = params.portal?.trim() || null;
 
-  let companyName = "Your Portal";
+  let companyName = "Showpane";
   let companyUrl = "https://showpane.com";
   let supportEmail = "support@showpane.com";
   let portalLabel = "Client Portal";
   let description = "Private portal access. Sign in with the credentials you were sent.";
-  let companyInitial = "P";
+  let companyLogoSrc: string | null = null;
+  let companyLogoAlt = companyName;
 
   if (portalSlug) {
     try {
@@ -25,10 +26,16 @@ export default async function ClientLogin({
         const state = await getRuntimeState();
         const portal = await getRuntimePortalBySlug(portalSlug);
         if (portal) {
-          companyName = portal.companyName;
-          portalLabel = `${portal.companyName} Portal`;
-          description = `Private portal for ${portal.companyName}. Sign in with the credentials you were sent.`;
-          companyInitial = portal.companyName[0]?.toUpperCase() || "P";
+          const orgName = state?.organization?.name || companyName;
+          companyName = orgName;
+          companyLogoAlt = orgName;
+          portalLabel = state?.organization?.portalLabel || `${orgName} Portal`;
+          description = `Private portal created by ${orgName} for ${portal.companyName}. Sign in with the credentials you were sent.`;
+          companyLogoSrc = getBrandLogoUrl({
+            logoUrl: state?.organization?.logoUrl,
+            websiteUrl: state?.organization?.websiteUrl,
+            fallbackName: orgName,
+          });
           if (state?.organization?.websiteUrl) {
             companyUrl = state.organization.websiteUrl;
           }
@@ -45,11 +52,15 @@ export default async function ClientLogin({
               slug: portalSlug,
               isActive: true,
             },
-            select: { companyName: true },
+            select: {
+              companyName: true,
+            },
           });
           const organization = await prisma.organization.findUnique({
             where: { id: organizationId },
             select: {
+              name: true,
+              logoUrl: true,
               websiteUrl: true,
               supportEmail: true,
               portalLabel: true,
@@ -57,10 +68,16 @@ export default async function ClientLogin({
           });
 
           if (portal) {
-            companyName = portal.companyName;
-            portalLabel = organization?.portalLabel || `${portal.companyName} Portal`;
-            description = `Private portal for ${portal.companyName}. Sign in with the credentials you were sent.`;
-            companyInitial = portal.companyName[0]?.toUpperCase() || "P";
+            const orgName = organization?.name || companyName;
+            companyName = orgName;
+            companyLogoAlt = orgName;
+            portalLabel = organization?.portalLabel || `${orgName} Portal`;
+            description = `Private portal created by ${orgName} for ${portal.companyName}. Sign in with the credentials you were sent.`;
+            companyLogoSrc = getBrandLogoUrl({
+              logoUrl: organization?.logoUrl,
+              websiteUrl: organization?.websiteUrl,
+              fallbackName: orgName,
+            });
           }
           if (organization?.websiteUrl) {
             companyUrl = organization.websiteUrl;
@@ -79,9 +96,19 @@ export default async function ClientLogin({
     <PortalLogin
       companyName={companyName}
       companyLogo={
-        <div className="flex h-7 w-7 items-center justify-center rounded-lg bg-gray-900">
-          <span className="text-xs font-bold text-white">{companyInitial}</span>
-        </div>
+        companyLogoSrc ? (
+          <img
+            src={companyLogoSrc}
+            alt={companyLogoAlt}
+            className="h-7 w-7 rounded-lg object-cover"
+          />
+        ) : (
+          <div className="flex h-7 w-7 items-center justify-center rounded-lg bg-gray-900">
+            <span className="text-xs font-bold text-white">
+              {companyName[0]?.toUpperCase() || "S"}
+            </span>
+          </div>
+        )
       }
       companyUrl={companyUrl}
       supportEmail={supportEmail}

package/bundle/scaffold/src/lib/branding.ts

@@ -4,6 +4,36 @@
  * All functions return sensible defaults on failure.
  */
 
+/**
+ * Normalize a website or bare domain into an https URL.
+ */
+export function normalizeWebsiteUrl(value?: string | null): string | null {
+  if (!value) return null;
+  const trimmed = value.trim();
+  if (!trimmed) return null;
+
+  const candidate = /^https?:\/\//i.test(trimmed) ? trimmed : `https://${trimmed}`;
+  try {
+    return new URL(candidate).toString();
+  } catch {
+    return null;
+  }
+}
+
+/**
+ * Extract a hostname from a website URL or bare domain.
+ */
+export function getDomainFromWebsite(value?: string | null): string | null {
+  const normalized = normalizeWebsiteUrl(value);
+  if (!normalized) return null;
+
+  try {
+    return new URL(normalized).hostname;
+  } catch {
+    return null;
+  }
+}
+
 /**
  * Fetch a company logo URL from a domain.
  * Uses Clearbit Logo API (free, no key required).
@@ -19,6 +49,23 @@ export function getLogoUrl(domain: string, fallbackName?: string): string {
   return `https://ui-avatars.com/api/?name=${initial}&background=111827&color=fff&size=128&bold=true`;
 }
 
+/**
+ * Resolve the best available logo source for a brand.
+ * Prefers a stored logo URL, then a website-derived domain, then initials.
+ */
+export function getBrandLogoUrl(options: {
+  logoUrl?: string | null;
+  websiteUrl?: string | null;
+  fallbackName: string;
+}): string {
+  if (options.logoUrl) {
+    return options.logoUrl;
+  }
+
+  const domain = getDomainFromWebsite(options.websiteUrl);
+  return getLogoUrl(domain ?? "", options.fallbackName);
+}
+
 /**
  * Fetch a Gravatar URL for an email address.
  * Falls back to UI Avatars if no Gravatar exists.

package/bundle/scaffold/src/lib/portal-contracts.ts

@@ -87,6 +87,7 @@ export interface PortalFileSyncManifestPayload {
 export interface RuntimePortalSnapshot {
   slug: string;
   companyName: string;
+  websiteUrl?: string | null;
   logoUrl?: string | null;
   username: string;
   passwordHash: string;

package/bundle/toolchain/CLI_VERSION

@@ -1 +1 @@
-0.4.24
+0.4.26

package/bundle/toolchain/bin/create-portal.ts

@@ -1,4 +1,5 @@
 import { PrismaClient } from "@/lib/prisma-client";
+import { getBrandLogoUrl, normalizeWebsiteUrl } from "@/lib/branding";
 import bcrypt from "bcryptjs";
 import crypto from "node:crypto";
 
@@ -16,7 +17,7 @@ async function main() {
   const args = process.argv.slice(2);
 
   if (args.includes("--help")) {
-    console.log("Usage: create-portal --slug <slug> --company <name> --org-id <orgId>");
+    console.log("Usage: create-portal --slug <slug> --company <name> --org-id <orgId> [--website <domain-or-url>]");
     console.log("Creates a new client portal with auto-generated credentials.");
     process.exit(0);
   }
@@ -25,6 +26,7 @@ async function main() {
   const slug = getArg("--slug");
   const company = getArg("--company");
   const orgId = getArg("--org-id");
+  const website = getArg("--website");
 
   if (!slug || !company || !orgId) fail("Missing --slug, --company, or --org-id");
 
@@ -37,6 +39,11 @@ async function main() {
   const username = slug;
   const password = crypto.randomBytes(16).toString("base64url");
   const passwordHash = await bcrypt.hash(password, 10);
+  const websiteUrl = normalizeWebsiteUrl(website);
+  const logoUrl = getBrandLogoUrl({
+    websiteUrl,
+    fallbackName: company,
+  });
 
   const prisma = new PrismaClient();
   try {
@@ -46,19 +53,51 @@ async function main() {
     });
     if (existing) fail(`Slug "${slug}" already exists`);
 
-    const portal = await prisma.clientPortal.create({
-      data: {
-        organizationId: orgId,
-        slug,
-        companyName: company,
-        username,
-        passwordHash,
-      },
-    });
+    const createData: Record<string, unknown> = {
+      organizationId: orgId,
+      slug,
+      companyName: company,
+      logoUrl,
+      username,
+      passwordHash,
+    };
+
+    // Older scaffolded apps may not have the ClientPortal.websiteUrl column yet.
+    if (websiteUrl) {
+      createData.websiteUrl = websiteUrl;
+    }
+
+    let portal;
+    try {
+      portal = await prisma.clientPortal.create({
+        data: createData,
+      });
+    } catch (error) {
+      const message = error instanceof Error ? error.message : String(error);
+      if (
+        websiteUrl &&
+        (message.includes("Unknown arg `websiteUrl`") ||
+          message.includes("Unknown argument `websiteUrl`"))
+      ) {
+        delete createData.websiteUrl;
+        portal = await prisma.clientPortal.create({
+          data: createData,
+        });
+      } else {
+        throw error;
+      }
+    }
 
     console.log(JSON.stringify({
       ok: true,
-      portal: { id: portal.id, slug: portal.slug, username, password },
+      portal: {
+        id: portal.id,
+        slug: portal.slug,
+        username,
+        password,
+        websiteUrl: portal.websiteUrl,
+        logoUrl: portal.logoUrl,
+      },
     }));
   } finally {
     await prisma.$disconnect();

package/bundle/toolchain/bin/export-runtime-state.ts

@@ -51,6 +51,7 @@ async function main() {
       select: {
         slug: true,
         companyName: true,
+        websiteUrl: true,
         logoUrl: true,
         username: true,
         passwordHash: true,

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

@@ -99,9 +99,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Overview
 

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

@@ -104,9 +104,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Steps
 
@@ -138,13 +138,8 @@ Store:
 If the helper fails, stop and tell the user to run `/portal-setup` again instead
 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:
+Once `get-org.ts` succeeds, extra project probing rarely improves the draft.
+Use that result plus the selected template/example as the canonical references:
 
 - the configured `APP_PATH`
 - the configured `ORG_SLUG`
@@ -153,6 +148,9 @@ The canonical references for this skill are:
 - `$SKILL_DIR/templates/<chosen-template>/...`
 - `$APP_PATH/src/app/(portal)/client/example/example-client.tsx`
 
+For slug checks, use `check-slug.ts` with `--org-id`. Re-reading config, Prisma,
+or SQLite usually just burns time without changing the correct org context.
+
 ### Step 2: Determine the portal slug
 
 If the user provided a slug (e.g., `/portal-create acme-health`), use it. Otherwise, infer from context — the company name mentioned in conversation, a meeting transcript, or ask the user directly.
@@ -170,9 +168,15 @@ The script returns `{"valid":true}` or `{"valid":false,"reason":"...","message":
 
 If invalid, explain the issue and ask for a different slug.
 
-Also ask for the client's website domain (e.g., "acme-health.com"). This is optional but enables auto-branding:
-- If provided, the client logo will be fetched via `getLogoUrl(domain)` and stored in `ClientPortal.logoUrl`
-- If not provided, an initial-based logo is generated via `getInitialLogo(companyName)` and stored as a data URI
+Also determine the client's website domain. This enables auto-branding and is worth a quick best-effort pass:
+- if the domain is explicit in the transcript or user prompt, use it
+- otherwise make one quick best-effort lookup for the official site
+- if one clear candidate stands out, suggest it briefly: `I found <domain> — I'll use that for the logo unless you want a different one`
+- if confidence is low, ask directly
+
+Store the confirmed value in `ClientPortal.websiteUrl`.
+Use it to derive `ClientPortal.logoUrl` via `getBrandLogoUrl(...)`.
+If no domain is confirmed, fall back to an initial-based logo.
 
 ### Step 3: Granola MCP integration (optional)
 
@@ -215,10 +219,10 @@ Always also read the example portal as your quality and style reference:
 cat "$APP_PATH/src/app/(portal)/client/example/example-client.tsx"
 ```
 
-The template provides content structure. The example provides quality and styling. Match the example's patterns: card styles, typography, spacing, responsive breakpoints. Templates are inspiration, not rigid scaffolds. Adapt the structure to fit the actual content.
-
-Do not search the repo for templates or ask the filesystem where templates live.
-Use the selected template and the exact `SKILL_DIR` path above.
+The template provides structure. The example provides quality and styling.
+Read those directly from the known paths above, then match the example's card
+styles, typography, spacing, and responsive breakpoints. Templates are
+inspiration, not rigid scaffolds.
 
 ### Step 5: Analyze transcript (if available)
 
@@ -286,10 +290,10 @@ 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 `ORG_NAME`)
-- `companyLogo` — a `<span>` with the first letter of the company name, white text
+- `companyName` — the org's company name (from `get-org.ts`)
+- `companyLogo` — prefer the org logo via `getBrandLogoUrl({ logoUrl: ORG.logoUrl, websiteUrl: ORG.websiteUrl, fallbackName: ORG.name })`; fall back to initials only if no better source exists
 - `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
+- `clientLogoSrc` — use `getBrandLogoUrl({ websiteUrl: <confirmed client website>, fallbackName: clientName })`; store the chosen URL in the `ClientPortal.logoUrl` field
 - `clientLogoAlt` — the client company name
 - `lastUpdated` — today's date formatted as "7 April 2026"
 - `contact` — object with `name`, `title`, `avatarSrc`, `email` (from the `get-org.ts` result, not from ad-hoc config or DB probing)
@@ -337,12 +341,12 @@ Import only the icons you need from `lucide-react`. Common choices:
 Run the create-portal script to register the portal in the database:
 
 ```bash
-cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PATH/tsconfig.json" "$SKILL_DIR/bin/create-portal.ts" --slug <slug> --company "<client_company_name>" --org-id "$ORG_ID"
+cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PATH/tsconfig.json" "$SKILL_DIR/bin/create-portal.ts" --slug <slug> --company "<client_company_name>" --org-id "$ORG_ID" --website "<confirmed_client_website_if_any>"
 ```
 
 This creates the `ClientPortal` record with the slug and company name, links it to
-the Organization, and currently auto-generates initial credentials. The script
-returns `username` and `password`.
+the Organization, stores the confirmed client website/logo if available, and
+currently auto-generates initial credentials. The script returns `username` and `password`.
 
 Do not dump those credentials into the middle of the flow unless the user asked.
 For onboarding, carry them forward quietly and show them at the access phase.

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

@@ -43,13 +43,8 @@ Store:
 If the helper fails, stop and tell the user to run `/portal-setup` again instead
 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:
+Once `get-org.ts` succeeds, extra project probing rarely improves the draft.
+Use that result plus the selected template/example as the canonical references:
 
 - the configured `APP_PATH`
 - the configured `ORG_SLUG`
@@ -58,6 +53,9 @@ The canonical references for this skill are:
 - `$SKILL_DIR/templates/<chosen-template>/...`
 - `$APP_PATH/src/app/(portal)/client/example/example-client.tsx`
 
+For slug checks, use `check-slug.ts` with `--org-id`. Re-reading config, Prisma,
+or SQLite usually just burns time without changing the correct org context.
+
 ### Step 2: Determine the portal slug
 
 If the user provided a slug (e.g., `/portal-create acme-health`), use it. Otherwise, infer from context — the company name mentioned in conversation, a meeting transcript, or ask the user directly.
@@ -75,9 +73,15 @@ The script returns `{"valid":true}` or `{"valid":false,"reason":"...","message":
 
 If invalid, explain the issue and ask for a different slug.
 
-Also ask for the client's website domain (e.g., "acme-health.com"). This is optional but enables auto-branding:
-- If provided, the client logo will be fetched via `getLogoUrl(domain)` and stored in `ClientPortal.logoUrl`
-- If not provided, an initial-based logo is generated via `getInitialLogo(companyName)` and stored as a data URI
+Also determine the client's website domain. This enables auto-branding and is worth a quick best-effort pass:
+- if the domain is explicit in the transcript or user prompt, use it
+- otherwise make one quick best-effort lookup for the official site
+- if one clear candidate stands out, suggest it briefly: `I found <domain> — I'll use that for the logo unless you want a different one`
+- if confidence is low, ask directly
+
+Store the confirmed value in `ClientPortal.websiteUrl`.
+Use it to derive `ClientPortal.logoUrl` via `getBrandLogoUrl(...)`.
+If no domain is confirmed, fall back to an initial-based logo.
 
 ### Step 3: Granola MCP integration (optional)
 
@@ -120,10 +124,10 @@ Always also read the example portal as your quality and style reference:
 cat "$APP_PATH/src/app/(portal)/client/example/example-client.tsx"
 ```
 
-The template provides content structure. The example provides quality and styling. Match the example's patterns: card styles, typography, spacing, responsive breakpoints. Templates are inspiration, not rigid scaffolds. Adapt the structure to fit the actual content.
-
-Do not search the repo for templates or ask the filesystem where templates live.
-Use the selected template and the exact `SKILL_DIR` path above.
+The template provides structure. The example provides quality and styling.
+Read those directly from the known paths above, then match the example's card
+styles, typography, spacing, and responsive breakpoints. Templates are
+inspiration, not rigid scaffolds.
 
 ### Step 5: Analyze transcript (if available)
 
@@ -191,10 +195,10 @@ 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 `ORG_NAME`)
-- `companyLogo` — a `<span>` with the first letter of the company name, white text
+- `companyName` — the org's company name (from `get-org.ts`)
+- `companyLogo` — prefer the org logo via `getBrandLogoUrl({ logoUrl: ORG.logoUrl, websiteUrl: ORG.websiteUrl, fallbackName: ORG.name })`; fall back to initials only if no better source exists
 - `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
+- `clientLogoSrc` — use `getBrandLogoUrl({ websiteUrl: <confirmed client website>, fallbackName: clientName })`; store the chosen URL in the `ClientPortal.logoUrl` field
 - `clientLogoAlt` — the client company name
 - `lastUpdated` — today's date formatted as "7 April 2026"
 - `contact` — object with `name`, `title`, `avatarSrc`, `email` (from the `get-org.ts` result, not from ad-hoc config or DB probing)
@@ -242,12 +246,12 @@ Import only the icons you need from `lucide-react`. Common choices:
 Run the create-portal script to register the portal in the database:
 
 ```bash
-cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PATH/tsconfig.json" "$SKILL_DIR/bin/create-portal.ts" --slug <slug> --company "<client_company_name>" --org-id "$ORG_ID"
+cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PATH/tsconfig.json" "$SKILL_DIR/bin/create-portal.ts" --slug <slug> --company "<client_company_name>" --org-id "$ORG_ID" --website "<confirmed_client_website_if_any>"
 ```
 
 This creates the `ClientPortal` record with the slug and company name, links it to
-the Organization, and currently auto-generates initial credentials. The script
-returns `username` and `password`.
+the Organization, stores the confirmed client website/logo if available, and
+currently auto-generates initial credentials. The script returns `username` and `password`.
 
 Do not dump those credentials into the middle of the flow unless the user asked.
 For onboarding, carry them forward quietly and show them at the access phase.

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

@@ -109,9 +109,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Steps
 

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

@@ -109,9 +109,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Safety Guard
 

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

@@ -102,9 +102,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Steps
 
@@ -168,12 +168,15 @@ Run list-portals and warn about portals missing credentials. This is a warning,
 ### Cloud Step 2: Run the canonical deploy command
 
 Use the built-in deploy command instead of reimplementing the staged cloud protocol in shell.
+Run it directly so progress lines stay visible while the build and publish are in flight.
 
 ```bash
-DEPLOY_JSON=$(cd "$APP_PATH" && SHOWPANE_APP_PATH="$APP_PATH" NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$SKILL_DIR/bin/tsconfig.json" "$SKILL_DIR/bin/deploy-to-cloud.ts" --app-path "$APP_PATH" --wait --json)
+DEPLOY_JSON=$(cd "$APP_PATH" && SHOWPANE_APP_PATH="$APP_PATH" "$SHOWPANE_BIN/showpane" deploy --wait --json)
 echo "$DEPLOY_JSON"
 ```
 
+Do not wrap this command in `tail` or another truncating pipe. If you need a shorter summary later, capture the output after the command finishes or read from a temp log separately.
+
 That command already owns:
 - type check
 - project-link bootstrap

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

@@ -73,12 +73,15 @@ Run list-portals and warn about portals missing credentials. This is a warning,
 ### Cloud Step 2: Run the canonical deploy command
 
 Use the built-in deploy command instead of reimplementing the staged cloud protocol in shell.
+Run it directly so progress lines stay visible while the build and publish are in flight.
 
 ```bash
-DEPLOY_JSON=$(cd "$APP_PATH" && SHOWPANE_APP_PATH="$APP_PATH" NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$SKILL_DIR/bin/tsconfig.json" "$SKILL_DIR/bin/deploy-to-cloud.ts" --app-path "$APP_PATH" --wait --json)
+DEPLOY_JSON=$(cd "$APP_PATH" && SHOWPANE_APP_PATH="$APP_PATH" "$SHOWPANE_BIN/showpane" deploy --wait --json)
 echo "$DEPLOY_JSON"
 ```
 
+Do not wrap this command in `tail` or another truncating pipe. If you need a shorter summary later, capture the output after the command finishes or read from a temp log separately.
+
 That command already owns:
 - type check
 - project-link bootstrap

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

@@ -99,9 +99,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Steps
 

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

@@ -99,9 +99,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Overview
 

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

@@ -99,9 +99,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Overview
 
@@ -262,9 +262,8 @@ cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PA
 Use the returned `org.id` as the canonical org id for the rest of the create flow.
 Do not guess schema fields or discover the org via ad-hoc SQLite queries if this helper succeeds.
 
-Also: do not probe `showpane --help`, `package.json`, `scripts/`, `prisma/`, or
-template directories just to reorient yourself. At this point the canonical inputs
-are already known:
+At this point, extra repo reorientation rarely changes the first draft. Use the
+known inputs below and spend the time shaping the portal instead:
 
 - workspace app path
 - org slug
@@ -272,10 +271,14 @@ are already known:
 - selected template
 - optional transcript source
 
+If you need structure or style, read only the selected template and the example
+portal. Other portal skills are for later phases and usually just add latency here.
+
 During this phase:
 
 - suggest a slug if needed
 - prefer a real company/client name in the portal
+- if the client website is not already obvious, do one quick best-effort domain lookup and suggest the result briefly before drafting
 - prefer useful structure over completeness
 - aim for a credible first draft, not a perfect final artifact
 - do not re-ask for the company name or template if the user already chose them
@@ -378,14 +381,17 @@ Save checkpoint with phase `access-ready` and `accessMode`.
 ### Phase 8: Publish to Showpane Cloud
 
 Run the `portal-deploy` flow inline.
+Let the deploy command stream its own progress. Do not wrap the long-running publish step in `tail`.
 
 This phase is part of onboarding by default. Do not treat publish as an optional
 afterthought unless the user explicitly says they want to stop at local preview.
 
 If cloud auth is missing:
 
-- tell the user to run `showpane login`
-- after login completes, resume from the checkpoint
+- run `showpane login` inline via Bash in the current session
+- if you need to hand control to the user, tell them to run `! showpane login`
+- let it handle sign-in, sign-up, and checkout if needed
+- then resume publish from the checkpoint
 
 If deploy returns `organization_required`:
 

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

@@ -169,9 +169,8 @@ cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PA
 Use the returned `org.id` as the canonical org id for the rest of the create flow.
 Do not guess schema fields or discover the org via ad-hoc SQLite queries if this helper succeeds.
 
-Also: do not probe `showpane --help`, `package.json`, `scripts/`, `prisma/`, or
-template directories just to reorient yourself. At this point the canonical inputs
-are already known:
+At this point, extra repo reorientation rarely changes the first draft. Use the
+known inputs below and spend the time shaping the portal instead:
 
 - workspace app path
 - org slug
@@ -179,10 +178,14 @@ are already known:
 - selected template
 - optional transcript source
 
+If you need structure or style, read only the selected template and the example
+portal. Other portal skills are for later phases and usually just add latency here.
+
 During this phase:
 
 - suggest a slug if needed
 - prefer a real company/client name in the portal
+- if the client website is not already obvious, do one quick best-effort domain lookup and suggest the result briefly before drafting
 - prefer useful structure over completeness
 - aim for a credible first draft, not a perfect final artifact
 - do not re-ask for the company name or template if the user already chose them
@@ -285,14 +288,17 @@ Save checkpoint with phase `access-ready` and `accessMode`.
 ### Phase 8: Publish to Showpane Cloud
 
 Run the `portal-deploy` flow inline.
+Let the deploy command stream its own progress. Do not wrap the long-running publish step in `tail`.
 
 This phase is part of onboarding by default. Do not treat publish as an optional
 afterthought unless the user explicitly says they want to stop at local preview.
 
 If cloud auth is missing:
 
-- tell the user to run `showpane login`
-- after login completes, resume from the checkpoint
+- run `showpane login` inline via Bash in the current session
+- if you need to hand control to the user, tell them to run `! showpane login`
+- let it handle sign-in, sign-up, and checkout if needed
+- then resume publish from the checkpoint
 
 If deploy returns `organization_required`:
 

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

@@ -99,9 +99,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Overview
 

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

@@ -93,9 +93,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Steps
 

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

@@ -102,9 +102,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Overview
 

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

@@ -99,9 +99,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Overview
 

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

@@ -99,9 +99,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Steps
 

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

@@ -99,9 +99,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Overview
 

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

@@ -99,9 +99,9 @@ If `RECENT_SKILLS` is shown, suggest the likely next skill:
 
 If `RECENT_LEARNINGS` is shown, review them before proceeding. Apply them where relevant but do not mention them unless they materially affect the current task.
 
-Read `skills/shared/runtime-principles.md` once near the start of the skill and apply the relevant product defaults.
+Read `skills/shared/runtime-principles.md` directly from that exact path near the start of the skill and apply the relevant product defaults.
 
-If `skills/shared/platform-constraints.md` exists, read it once near the start of the skill and apply only the relevant limits.
+If `skills/shared/platform-constraints.md` exists, read it directly from that exact path near the start of the skill and apply only the relevant limits. No directory listing is needed first.
 
 ## Steps
 

package/dist/index.js

@@ -671,8 +671,12 @@ async function syncCloudProjectLink(projectRoot, accessToken) {
   writeCloudProjectLink(projectRoot, projectLink);
 }
 function removePath(targetPath) {
-  if (!existsSync(targetPath)) return;
-  const stat = lstatSync(targetPath);
+  let stat;
+  try {
+    stat = lstatSync(targetPath);
+  } catch {
+    return;
+  }
   if (stat.isSymbolicLink() || stat.isFile()) {
     unlinkSync(targetPath);
     return;

package/package.json

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