generatesaas 1.23.1 → 2.0.1

package/dist/skill/content/SKILL.md

@@ -21,6 +21,7 @@ Step 0: Pre-flight safety checks
 Step 1: Fetch + stage + prepare update data (you run the CLI, then the script)
 Step 2: Present changelog to user
 Step 2.5: Review newly available options - adopt or keep default (re-stage if adopted)
+Step 2.6: Companion source flips (only when the user asks)
 Step 3: Classify files (script)
 Step 4: Analyze dependencies
 Step 5: Present update plan - user chooses interaction mode
@@ -198,6 +199,41 @@ but the user decides.
    before this point, so a re-stage never leaves a half-applied tree.
 4. If the user adopted nothing, continue to Step 3 directly.
 
+### Step 2.6: Companion Source Flips (only when the user asks)
+
+A companion-ON project records where its daemon comes from in `companionSource`
+("shared" points at an existing companion repo; "vendored" owns the daemon in this repo).
+Flipping it is a manifest edit + re-stage, exactly like option adoption in Step 2.5.
+**Never flip it unprompted** - only when the user explicitly asks to switch.
+
+**vendored -> shared** (abandons the in-repo daemon):
+
+1. Warn first and get explicit confirmation:
+
+   > Switching to a shared companion REMOVES `apps/companion` and `scripts/companion-export`
+   > from this project when the update is applied. Local customisations to the vendored daemon
+   > are abandoned (they survive only in git history), and your published companion repo stops
+   > receiving updates from this project. Continue?
+
+2. On confirmation, edit `.generatesaas/manifest.json`: set `"companionSource": "shared"`, add
+   `"companionRepoUrl"` (ask which repo; default `https://github.com/Duzbee/OpenCompanion`),
+   optionally `"companionLocalPath"`, and REMOVE `"companionName"`.
+3. Re-run `npx generatesaas@latest update` to re-stage (append `auto` in Automatic mode), then
+   continue the normal flow. The CLI removes the now-stale `.generatesaas/companion-release.json`
+   on shared-source updates.
+4. Remind the user: their end-users keep running the OLD published daemon until they install the
+   shared one; after apply + deploy, the Companions page renders the new install command.
+
+**shared -> vendored** (take ownership of a daemon):
+
+1. Edit `.generatesaas/manifest.json`: set `"companionSource": "vendored"`, add
+   `"companionName"` (ask; default: the title-cased project name + " Companion"), and REMOVE
+   `"companionRepoUrl"` / `"companionLocalPath"`.
+2. Re-run `npx generatesaas@latest update` to re-stage. Applying vendors `apps/companion` + the
+   export pipeline, branded from the name.
+3. Remind the user: the Companions page shows a publish-first state until they run
+   `pnpm companion:publish`.
+
 ### Step 3: Classify Files
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "generatesaas",
-  "version": "1.23.1",
+  "version": "2.0.1",
   "type": "module",
   "description": "CLI for scaffolding and managing GenerateSaaS projects",
   "license": "UNLICENSED",
@@ -21,7 +21,7 @@
   "devDependencies": {
     "@types/node": "^25.6.0",
     "tsup": "^8.5.1",
-    "typescript": "^6.0.2",
+    "typescript": "^6.0.3",
     "vitest": "^4.1.5",
     "@repo/tsconfig": "1.0.0"
   },