@percepta/create 3.4.1 → 3.4.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@percepta/create",
-  "version": "3.4.1",
+  "version": "3.4.2",
   "description": "Scaffold a new Mosaic package",
   "keywords": [
     "cli",

package/templates/webapp/agent-skills/deploy.md

@@ -2,7 +2,7 @@
 
 This guide deploys __APP_TITLE__ to `https://__APP_NAME__.percepta-test.aitco.dev` using Ryvn. Tell Claude "deploy this app to percepta-test" and it should run the direct deploy helper below.
 
-This is the existing-environment deploy motion: `percepta-test` already owns the shared platform services, and this app is wired into them. Fresh-environment platform bootstrap is separate and should use a Ryvn blueprint or environment-specific platform rollout before app deploys run.
+This is the existing-environment deploy motion: `percepta-test` already owns the shared platform services, and this app is wired into them. Fresh-environment platform bootstrap is separate and should use a Ryvn blueprint or environment-specific platform rollout before app deploys run. The `pnpm deploy:percepta-test` script delegates to the versioned `@percepta/deploy` CLI; this app owns only its Ryvn YAML and generated secrets env file.
 
 ## What's Already Scaffolded
 

package/templates/webapp/deploy/README.md

@@ -18,7 +18,7 @@ These files deploy to `https://__APP_NAME__.percepta-test.aitco.dev`.
 
 The default deploy helper performs the existing-environment deploy motion: it assumes the target Ryvn environment already has the shared platform services installed, then wires this app into them. For `percepta-test`, that means shared Postgres, Inngest, the OTEL collector, the LGTM stack, and Langfuse must already exist before app deploy starts. Fresh-environment platform bootstrap is a separate motion and should be handled by a Ryvn blueprint or environment-specific platform rollout.
 
-The helper talks directly to Ryvn: it preflights the existing platform services, creates/updates the services, runs the GitHub Actions release workflows, creates the schema installation, approves the schema Terraform plan, creates or updates app-scoped Ryvn secrets, creates the web installation, waits for health, and verifies the health and app routes.
+The `pnpm deploy:percepta-test` script delegates to the versioned `@percepta/deploy` CLI. The app owns only the Ryvn service/installation YAML and secrets env file. The helper talks directly to Ryvn: it preflights the existing platform services, creates/updates the services, runs the GitHub Actions release workflows, creates the schema installation, approves the schema Terraform plan, creates or updates app-scoped Ryvn secrets, creates the web installation, waits for health, and verifies the health and app routes.
 
 ## Deploying
 

package/templates/webapp/package.json.template

@@ -24,8 +24,8 @@
     "db:setup-readonly": "tsx ./scripts/setup-readonly-user.ts",
     "db:studio": "pnpm db:setup-and-migrate && drizzle-kit studio",
     "db:seed": "tsx ./scripts/seed.ts",
-    "deploy:percepta-test": "tsx ./scripts/deploy-percepta-test.ts",
-    "deploy:percepta-test:pr": "tsx ./scripts/open-ryvn-deploy-pr.ts",
+    "deploy:percepta-test": "percepta-deploy percepta-test --app __APP_NAME__ --repo __REPO_NAME__",
+    "deploy:percepta-test:pr": "percepta-deploy percepta-test pr --app __APP_NAME__ --database-schema __APP_NAME_SNAKE__",
     "test": "vitest run",
     "test:e2e": "pnpm run setup && playwright test",
     "test:e2e:install": "playwright install chromium",
@@ -109,6 +109,7 @@
     "@next/eslint-plugin-next": "^15.3.5",
     "@playwright/test": "^1.58.2",
     "@percepta/build": "0.4.0",
+    "@percepta/deploy": "0.1.0",
     "@tailwindcss/postcss": "^4.1.11",
     "@types/formidable": "^3.4.5",
     "@types/he": "^1.2.3",