showpane 0.4.25 → 0.4.27

package/bundle/meta/scaffold-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-04-13T22:00:52.340Z",
+  "generatedAt": "2026-04-13T22:57:26.230Z",
   "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.25
+0.4.27

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
 
@@ -168,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)
 
@@ -284,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)
@@ -335,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

@@ -73,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)
 
@@ -189,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)
@@ -240,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
 
@@ -154,20 +154,12 @@ If a checkpoint exists:
 
 ### Phase 1: Orientation
 
-Start with a compact welcome:
-
-```
- ╔══════════════════════════════════════════╗
- ║  SHOWPANE — First Portal Wizard         ║
- ╚══════════════════════════════════════════╝
-```
-
-Then use one short, friendly paragraph. Keep it concise and informal.
+Start with one short setup confirmation and one sharp ask. Keep it concise and informal.
 
 Suggested shape:
 
-- "Let's get your first portal started."
-- "Who's it for, and what's the context? If you've got a call transcript, paste it in and I'll use that too."
+- "Everything's set up. Let's make your first portal."
+- "Who’s it for? Paste a call transcript or meeting notes, or give me a short brief on the client and what you want the portal to do."
 
 Keep the opening focused on the user's first portal. This skill is the first-run default, so the top of the flow should feel fast, calm, and immediately useful.
 
@@ -222,7 +214,7 @@ Start with one short source question, not a menu.
 
 Recommended opening:
 
-- "Who's it for, and what's the context? If you've got a call transcript, paste it in and I'll use that too."
+- "Who’s it for? Paste a call transcript or meeting notes, or give me a short brief on the client and what you want the portal to do."
 
 Only branch after the user answers:
 
@@ -278,6 +270,7 @@ 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
@@ -329,25 +322,30 @@ If no dev server is running, start it using the `portal-dev` instructions first.
 If the create step already generated local credentials, show them before opening
 the preview link. Keep it simple:
 
+- preview URL
 - username
 - password
-- one sentence saying these are for local preview right now
 
 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.
+After that, open the local preview immediately.
 
-Tell the user exactly what to inspect:
+Once the preview is open, keep the handoff short and decision-oriented. Tell the
+user exactly what to inspect:
 
 - does the overall story feel right?
-- are next steps clear?
-- are obvious documents or dates missing?
+- anything factually wrong?
 
 If the user requests a small content fix after preview, make it and preview again.
 Keep this loop tight. Do not let it become an open-ended editing session.
 
+Bias the next step toward publish:
+
+- `If it looks right, say publish.`
+- `If not, tell me what to change.`
+- `If it looks right, I can publish it to Showpane Cloud so you get a hosted link and built-in analytics without having to self-host. Free for 7 days, then $29/mo.`
+
 Save checkpoint with phase `previewed`.
 
 ### Phase 7: Access setup
@@ -380,6 +378,7 @@ 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.
@@ -414,27 +413,32 @@ Save checkpoint with phase `published` once the hosted URL is live or clearly ac
 
 ### Phase 9: Final summary
 
-Show a compact final reference card:
+Show a compact final handoff card. At this point, prioritize the hosted link,
+the active access credentials, and one or two clear next actions.
 
 ```
 ════════════════════════════════════════
-  First portal complete
+  First portal live
 
   Portal: <slug> (<company>)
-  Local:  http://localhost:3000/client/<slug>
-  Cloud:  <hosted-url-or-publishing-status>
-  Access: <hosted login / hosted share link / both>
+  Cloud:  <hosted login URL or share URL>
+  Login:  <username if login is the active access mode>
+  Pass:   <password if login is the active access mode>
 
-  Next: /portal-update <slug>
-  Help: /portal-list, /portal-status
+  Next:   /portal-update <slug>
+          /portal-share <slug>   (if a direct hosted link would help)
 ════════════════════════════════════════
 ```
 
 Rules:
 
-- never include the password in the final summary
-- include the hosted share URL only if it exists and the user explicitly asked for it after publish
+- if login is the active access mode, include the username and password here so the user does not have to scroll back
+- if a hosted share URL exists because the user asked for one after publish, show that as the primary cloud link
+- otherwise show the hosted login URL as the cloud link
+- keep the summary short; avoid extra explanation once the portal is live
 - if publish is still finalizing, say so plainly instead of pretending it is live
+  In that case, show the local preview link and point the user to `/portal-status`
+  instead of pretending the hosted link is ready.
 
 After the final summary, delete the checkpoint:
 

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

@@ -61,20 +61,12 @@ If a checkpoint exists:
 
 ### Phase 1: Orientation
 
-Start with a compact welcome:
-
-```
- ╔══════════════════════════════════════════╗
- ║  SHOWPANE — First Portal Wizard         ║
- ╚══════════════════════════════════════════╝
-```
-
-Then use one short, friendly paragraph. Keep it concise and informal.
+Start with one short setup confirmation and one sharp ask. Keep it concise and informal.
 
 Suggested shape:
 
-- "Let's get your first portal started."
-- "Who's it for, and what's the context? If you've got a call transcript, paste it in and I'll use that too."
+- "Everything's set up. Let's make your first portal."
+- "Who’s it for? Paste a call transcript or meeting notes, or give me a short brief on the client and what you want the portal to do."
 
 Keep the opening focused on the user's first portal. This skill is the first-run default, so the top of the flow should feel fast, calm, and immediately useful.
 
@@ -129,7 +121,7 @@ Start with one short source question, not a menu.
 
 Recommended opening:
 
-- "Who's it for, and what's the context? If you've got a call transcript, paste it in and I'll use that too."
+- "Who’s it for? Paste a call transcript or meeting notes, or give me a short brief on the client and what you want the portal to do."
 
 Only branch after the user answers:
 
@@ -185,6 +177,7 @@ 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
@@ -236,25 +229,30 @@ If no dev server is running, start it using the `portal-dev` instructions first.
 If the create step already generated local credentials, show them before opening
 the preview link. Keep it simple:
 
+- preview URL
 - username
 - password
-- one sentence saying these are for local preview right now
 
 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.
+After that, open the local preview immediately.
 
-Tell the user exactly what to inspect:
+Once the preview is open, keep the handoff short and decision-oriented. Tell the
+user exactly what to inspect:
 
 - does the overall story feel right?
-- are next steps clear?
-- are obvious documents or dates missing?
+- anything factually wrong?
 
 If the user requests a small content fix after preview, make it and preview again.
 Keep this loop tight. Do not let it become an open-ended editing session.
 
+Bias the next step toward publish:
+
+- `If it looks right, say publish.`
+- `If not, tell me what to change.`
+- `If it looks right, I can publish it to Showpane Cloud so you get a hosted link and built-in analytics without having to self-host. Free for 7 days, then $29/mo.`
+
 Save checkpoint with phase `previewed`.
 
 ### Phase 7: Access setup
@@ -287,6 +285,7 @@ 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.
@@ -321,27 +320,32 @@ Save checkpoint with phase `published` once the hosted URL is live or clearly ac
 
 ### Phase 9: Final summary
 
-Show a compact final reference card:
+Show a compact final handoff card. At this point, prioritize the hosted link,
+the active access credentials, and one or two clear next actions.
 
 ```
 ════════════════════════════════════════
-  First portal complete
+  First portal live
 
   Portal: <slug> (<company>)
-  Local:  http://localhost:3000/client/<slug>
-  Cloud:  <hosted-url-or-publishing-status>
-  Access: <hosted login / hosted share link / both>
+  Cloud:  <hosted login URL or share URL>
+  Login:  <username if login is the active access mode>
+  Pass:   <password if login is the active access mode>
 
-  Next: /portal-update <slug>
-  Help: /portal-list, /portal-status
+  Next:   /portal-update <slug>
+          /portal-share <slug>   (if a direct hosted link would help)
 ════════════════════════════════════════
 ```
 
 Rules:
 
-- never include the password in the final summary
-- include the hosted share URL only if it exists and the user explicitly asked for it after publish
+- if login is the active access mode, include the username and password here so the user does not have to scroll back
+- if a hosted share URL exists because the user asked for one after publish, show that as the primary cloud link
+- otherwise show the hosted login URL as the cloud link
+- keep the summary short; avoid extra explanation once the portal is live
 - if publish is still finalizing, say so plainly instead of pretending it is live
+  In that case, show the local preview link and point the user to `/portal-status`
+  instead of pretending the hosted link is ready.
 
 After the final summary, delete the checkpoint:
 

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
 
@@ -183,12 +183,15 @@ Run this in a single Bash tool call so the browser opens immediately.
 After opening, display:
 
 ```
-Opened portal for <slug> in browser
-URL: http://localhost:3000/client/<slug>
+Preview ready
+
+  URL:   http://localhost:3000/client/<slug>
+  Login: /portal-credentials <slug>
 ```
 
-If the portal has credentials set up, remind the user:
-"Login with the credentials from /portal-credentials <slug>. For external access, publish first with /portal-deploy."
+Then add one short next step:
+
+- `If it looks right, publish it with /portal-deploy.`
 
 If the portal is the example portal (slug is "example"), no credentials are needed -- it is publicly accessible by design.
 

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

@@ -88,12 +88,15 @@ Run this in a single Bash tool call so the browser opens immediately.
 After opening, display:
 
 ```
-Opened portal for <slug> in browser
-URL: http://localhost:3000/client/<slug>
+Preview ready
+
+  URL:   http://localhost:3000/client/<slug>
+  Login: /portal-credentials <slug>
 ```
 
-If the portal has credentials set up, remind the user:
-"Login with the credentials from /portal-credentials <slug>. For external access, publish first with /portal-deploy."
+Then add one short next step:
+
+- `If it looks right, publish it with /portal-deploy.`
 
 If the portal is the example portal (slug is "example"), no credentials are needed -- it is publicly accessible by design.
 

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
 
@@ -269,21 +269,17 @@ Replace the placeholder values with the actual values collected. Use `chmod 600`
 
 ### Step 10: Print success summary
 
-Display a clear summary:
+Display a short success handoff:
 
 ```
 Showpane setup complete!
 
-  App path:     /path/to/showpane-project
-  Deploy mode:  local
-  Organization: Acme Consulting (acme-consulting)
-  Brand color:  #2563eb
-  Telemetry:    anonymous
+  App:  /path/to/showpane-project
+  Org:  Acme Consulting (acme-consulting)
 
-Next steps:
-  1. Recommended first run:    /portal-onboard
-  2. Fast repeat-user path:    /portal-create <slug>
-  3. View the example portal:  open http://localhost:3000/client/example
+Next:
+  /portal-onboard
+  /portal-create <slug>
 ```
 
 ### Step 11: Record learning (optional)

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

@@ -186,21 +186,17 @@ Replace the placeholder values with the actual values collected. Use `chmod 600`
 
 ### Step 10: Print success summary
 
-Display a clear summary:
+Display a short success handoff:
 
 ```
 Showpane setup complete!
 
-  App path:     /path/to/showpane-project
-  Deploy mode:  local
-  Organization: Acme Consulting (acme-consulting)
-  Brand color:  #2563eb
-  Telemetry:    anonymous
+  App:  /path/to/showpane-project
+  Org:  Acme Consulting (acme-consulting)
 
-Next steps:
-  1. Recommended first run:    /portal-onboard
-  2. Fast repeat-user path:    /portal-create <slug>
-  3. View the example portal:  open http://localhost:3000/client/example
+Next:
+  /portal-onboard
+  /portal-create <slug>
 ```
 
 ### Step 11: Record learning (optional)

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
 
@@ -153,17 +153,16 @@ Present the link in a clear, copy-friendly ASCII box:
 
 ```
 ════════════════════════════════════════
-  Share link for: whzan
-  https://portal.example.com/client/whzan/s/eyJ...
-  Expires: never (until credentials rotate)
+  Share link: https://portal.example.com/client/whzan/s/eyJ...
+  Revoke: rotate credentials or deactivate the portal
 ════════════════════════════════════════
 ```
 
 ### Step 4: Provide usage guidance
 
-After displaying the link, add this note:
+After displaying the link, add one short note:
 
-"This link is meant for the hosted portal. The link stays valid until the portal credentials are rotated or the portal is deactivated."
+`This is for the hosted portal. It stays valid until credentials rotate or the portal is deactivated.`
 
 If the user has previously generated share links (check learnings for patterns), you can skip the explanation and just show the link.
 

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

@@ -58,17 +58,16 @@ Present the link in a clear, copy-friendly ASCII box:
 
 ```
 ════════════════════════════════════════
-  Share link for: whzan
-  https://portal.example.com/client/whzan/s/eyJ...
-  Expires: never (until credentials rotate)
+  Share link: https://portal.example.com/client/whzan/s/eyJ...
+  Revoke: rotate credentials or deactivate the portal
 ════════════════════════════════════════
 ```
 
 ### Step 4: Provide usage guidance
 
-After displaying the link, add this note:
+After displaying the link, add one short note:
 
-"This link is meant for the hosted portal. The link stays valid until the portal credentials are rotated or the portal is deactivated."
+`This is for the hosted portal. It stays valid until credentials rotate or the portal is deactivated.`
 
 If the user has previously generated share links (check learnings for patterns), you can skip the explanation and just show the link.
 

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.25",
+  "version": "0.4.27",
   "description": "CLI for Showpane — AI-generated client portals",
   "type": "module",
   "bin": {