@m-kopa/launchpad-cli 0.57.0 → 0.61.0

package/skills/launchpad-identity/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: launchpad-identity
 description: Teach an app author how to use the signed-in user's identity inside a Launchpad app — read the gateway-forwarded X-Launchpad-User-Assertion in a Pages Function, VERIFY it with @m-kopa/platform-auth (fail-closed), and show who's logged in (sub/email/name). Use when someone says "who is logged in", "show the current user", "get the user's email in my app", "auth in my launchpad app", "read the user identity", "/launchpad-identity", or is wiring up an /api/me for a gateway-fronted app.
-version: 0.57.0
+version: 0.61.0
 ---
 
 <!-- BEGIN shell-contract (managed by scripts/sync-skill-contract.sh — edit skills/_partials/shell-contract.md) -->

package/skills/launchpad-onboard/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: launchpad-onboard
 description: One-time setup for the Launchpad CLI + Claude Code skill bundle. Verifies the `launchpad` CLI is installed and current, runs `launchpad whoami` to confirm the session is fresh, and checks the bundled skills are installed and in lock-step with the CLI. Idempotent — safe to re-run any time. Use when someone says "set me up for Launchpad", "I just got a new machine and want to use Launchpad", "/launchpad-onboard", or any of the other launchpad-* skills fails on a prereq check.
-version: 0.57.0
+version: 0.61.0
 ---
 
 <!-- BEGIN shell-contract (managed by scripts/sync-skill-contract.sh — edit skills/_partials/shell-contract.md) -->
@@ -211,3 +211,15 @@ Otherwise finish with:
 - Do **not** read `~/.launchpad/session.json` directly. Use
   `launchpad whoami`; the file is an internal artefact.
 - Do **not** retry indefinitely. One pass, one summary, done.
+
+
+## New app defaults
+
+`launchpad init` creates new static and React apps on Workers dispatch with gateway authentication.
+The generated v2 manifest preserves the detected build settings and the chosen access groups.
+Use the normal `launchpad deploy` flow; authors do not create Cloudflare projects or choose a gateway.
+The platform assigns new gateway-fronted apps to the configured gateway with the most free hostname slots, including pending reservations.
+Existing apps keep their assigned gateway, URL and access groups.
+React API starters remain on Pages, and existing manifests keep their current origin.
+An explicit `--origin pages` is available when required.
+Dispatch secret bindings are not supported yet, so do not promise that `launchpad secrets push` will work for those apps.

package/skills/launchpad-report/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: launchpad-report
 description: File a bug report or feature request to the Launchpad team's tracker from the CLI. Use when someone reports something broken, hits an error in a launchpad command, or wishes a feature existed — e.g. "this is broken", "report a bug", "can you file that", "I wish launchpad could…", "/launchpad-bug", "/launchpad-feature". Always confirm and show exactly what you'll send before filing; never file silently.
-version: 0.57.0
+version: 0.61.0
 ---
 
 <!-- BEGIN shell-contract (managed by scripts/sync-skill-contract.sh — edit skills/_partials/shell-contract.md) -->

package/skills/launchpad-status/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: launchpad-status
 description: Safely refresh a Launchpad clone, show manifest drift, or read the deployed manifest. Wraps bare `launchpad pull` for source sync, `launchpad pull --manifest` for deployed YAML, and `launchpad status` for drift. Use for "sync my clone", "what's deployed", "show drift", "/launchpad-status", "/launchpad-pull", or post-deploy verification.
-version: 0.57.0
+version: 0.61.0
 ---
 
 <!-- BEGIN shell-contract (managed by scripts/sync-skill-contract.sh — edit skills/_partials/shell-contract.md) -->
@@ -379,3 +379,12 @@ CI.
 ## Version
 
 This skill ships in launchpad-cli v0.56.0+.
+
+
+## Dispatch status in CLI 0.60.0
+
+New static and React apps use Workers dispatch and have no per-app Pages project.
+A missing Pages project is expected for `origin: dispatch`; do not treat it as a failed deployment or create a replacement.
+Use `launchpad status <slug> --json` to compare `deployedSha`, `headSha` and `deployment.liveDeployment.buildStatus`.
+A `live_drift_unknown` state can include a successful dispatch deployment while infrastructure drift is unavailable.
+If the CLI's first-deploy wait expires, keep checking the recorded submission instead of creating another app or claiming it is live.