showpane 0.4.22 → 0.4.23

package/bundle/meta/scaffold-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-04-12T09:23:46.426Z",
+  "generatedAt": "2026-04-12T11:40:53.513Z",
   "scaffoldVersion": "0.2.7",
   "files": {
     ".env.example": "ed105f2bdcd1888a98181d55e3c9f7d6eff3ae9c3e2366c2e777a12e3caddfa7",

package/bundle/toolchain/CLI_VERSION

@@ -1 +1 @@
-0.4.22
+0.4.23

package/bundle/toolchain/VERSION

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

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

@@ -141,6 +141,8 @@ 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:
 

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

@@ -46,6 +46,8 @@ 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:
 

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

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

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

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

package/package.json

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