@minnovate/shadow-publisher 0.11.0 → 0.11.2

package/dist/claude/plugin/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "git-publisher",
   "displayName": "Git Publisher",
-  "version": "0.11.0",
+  "version": "0.11.2",
   "description": "Publish an app folder's Git history to the serverless Git publishing backend and keep it updated (\"publish my app\", \"update my app\", \"fetch the engineered version\").",
   "author": { "name": "git-publisher project" },
   "keywords": ["git", "publish", "deploy", "serverless"]

package/dist/claude/plugin/skills/publish-app/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: publish-app
 description: Publish or update the user's app (a folder) with the publisher. Use when the user says "publish my app", "update my app", "save my changes", "push my changes", "save this version online", or asks to resolve an interrupted publication. Handles first-time setup, every later update, interruption recovery and conflicts by running the `publisher` command; never uses git to commit or push.
-allowed-tools: Bash(publisher *), Bash(npm install -g @minnovate/shadow-publisher*), Bash(git status *), Bash(git diff *), Bash(git log *)
+allowed-tools: Bash(publisher *), Bash(mkdir -p *), Bash(npm install -g @minnovate/shadow-publisher*), Bash(git status *), Bash(git diff *), Bash(git log *)
 ---
 
 # Publish or update the user's app
@@ -101,16 +101,27 @@ have; when it is not null it is already phrased for them, so pass it on rather t
 If they name an environment ("publish to dev"), pass `--profile dev` on each command rather than
 changing their default.
 
-## 2. First publication of a folder
+## 2. A new app: make it before you write it
 
-There is no separate first step: run step 3 in the app folder, adding `--name "<app name>"` the
-first time. A folder that is not published yet gets its application and repository from that same
-`sync` (the portal makes the application first, in one request), and is then published.
+When the person asks for a NEW app, make it before you write a file. Do step 1 first, then:
+
+```bash
+mkdir -p <folder>
+publisher init <folder> --name "<app name>" --json
+```
+
+`init` makes the app and links the folder to it. It publishes nothing and starts no checks. While
+you write the app, the platform prepares its hosting, so the first publication goes live in
+seconds, not in a minute. The folder must exist, and it can be empty. Its output names the app
+under `appId`. Then write the app into that folder, and publish it with step 3, without `--name`.
+
+If the app is already written and was never published, `init` gains nothing. Run step 3 in the
+app folder and add `--name "<app name>"`: that one `sync` makes the app, and then publishes it.
 
 The first `sync` prepares the folder with an explicit file selection: it excludes `.git`,
 `node_modules`, build caches, `.env*`, keys/certificates and files larger than 50 MB, and it
-respects `.gitignore`. Show the user the `linked` result and the excluded files it reports so they
-know what was left out (the exclusion rules are a safety net, not a secret scanner).
+respects `.gitignore`. Show the user the excluded files it reports so they know what was left out
+(the exclusion rules are a safety net, not a secret scanner).
 
 ## 3. Every publish, the first one included
 
@@ -231,7 +242,7 @@ publisher list --json
 
 `apps[]` lists what they published, newest first, each with its `name` and a `checkout` command.
 Ask which one only if the name does not settle it, then run its `checkout` command and work in that
-folder. Never `sync` an empty new folder in its place: that makes a second app.
+folder. Never `init` or `sync` an empty new folder in its place: that makes a second app.
 
 ## If the service cannot be reached
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@minnovate/shadow-publisher",
-  "version": "0.11.0",
+  "version": "0.11.2",
   "description": "publisher: publish an app's Git history to the serverless Git backend",
   "license": "Apache-2.0",
   "type": "module",
@@ -19,6 +19,7 @@
   },
   "scripts": {
     "build": "tsc -b tsconfig.json && pnpm run bundle",
+    "typecheck": "tsc -p tsconfig.test.json",
     "test": "vitest run --project unit --root ../.. packages/cli/",
     "bundle": "esbuild src/main.ts --bundle --platform=node --target=node22 --format=cjs --outfile=dist/publisher.cjs --banner:js=\"#!/usr/bin/env node\" --log-level=warning && pnpm run skills",
     "skills": "rm -rf dist/claude && mkdir -p dist/claude && cp -R ../../integrations/claude/.claude-plugin ../../integrations/claude/plugin dist/claude/",