@kindgi/cli 0.1.7-rc.0 → 0.1.8-rc.0

package/dist/templates/scala/AGENTS.md

@@ -27,12 +27,41 @@ make it a `val`. The config is `kindgi.config.json`.
   `"openrouter"`) to `kindgi.config.json`: `kindgi dev` then registers it on
   every boot, in every worktree.
 
+## Skills
+
+`.claude/skills/` and `.agents/skills/` hold the same Kindgi skills for
+Scala packs: getting started, tools, guardrails, agents and flows in Scala
+(`kindgi-scala-*`), model providers, MCP servers, framework feedback, and
+guiding the person in using what you built (`kindgi-using`). Claude Code
+loads `.claude/skills/` on its own; Codex and Gemini CLI look in
+`.agents/skills/`; any other coding agent can read either.
+`./kindgiw skills sync` refreshes both.
+
 When you diagnose a framework bug (something in Kindgi itself, not in this
 pack's code), append an entry to `FEEDBACK.md` at the pack root with
 `./kindgiw feedback write`.
 
 When the person asks how to use what you built (where something is in
 Kindgi's console, what an agent did, what it cost, who has access), answer
-from `./kindgiw`'s read-only commands and give the console link beside it: see
-`.claude/skills/kindgi-using/SKILL.md`. Deciding approvals, erasing, adding
-people and rating answers stay with the person.
+from `./kindgiw`'s read-only commands and give the console link beside it:
+see the `kindgi-using` skill. Deciding approvals, erasing, adding people
+and rating answers stay with the person.
+
+## Commands for the person's own terminal
+
+Two commands are always the person's to run, in their own terminal, since
+they ask for a secret: `./kindgiw secrets set` and
+`./kindgiw auth registry`. Others need what a coding agent's sandbox often
+blocks: `./kindgiw dev` and any dev server (they keep running), and
+`./kindgiw build` or anything else that needs Docker. When your sandbox
+blocks a command (a process it can't start, `spawn EPERM`; Docker's socket
+denied; `localhost` refused; a folder it keeps read-only, as Codex's keeps
+`.agents/`, which `./kindgiw skills sync` writes), don't work around it:
+don't turn your sandbox off, and don't start the command in the background.
+Give the person the exact command, the folder to run it in and what they'll
+see, then wait for them. Once they say `./kindgiw dev` is running, starting
+it yourself exits 3 and says where theirs runs: use that one.
+
+A tool's own `EPERM` while it runs under `./kindgiw dev` is something else:
+Kindgi's dev sandbox, which the tools skill covers. Never turn that one off
+either.

package/dist/templates/scala/README.md.tmpl

@@ -6,7 +6,7 @@ Two tools (`echo`, `greet`), one guardrail (`response-not-empty`), one agent
 that uses both tools and the guardrail, and one flow that runs the echo tool.
 
 Java and Scala support is in preview: tested and supported, but the API may
-still change in 0.1.6 without the usual deprecation period.
+still change in a later release without the usual deprecation period.
 
 ## Layout
 

package/dist/templates/woocommerce/AGENTS.md

@@ -10,12 +10,12 @@ Agents answer through a model provider. `kindgi dev` gives a new pack
 `dev-echo`, a fallback that isn't a model: it calls the first tool and
 replies "Tool responded: …" after a warning line, while no other provider
 fits. For a real model, put one LLM provider's key in `.env`
-(`ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, `GEMINI_API_KEY`, `GROQ_API_KEY` or
-`OPENROUTER_API_KEY`) and declare its preset (`{ preset: 'anthropic' }`,
-`'openai'`, `'gemini-api'`, `'groq'` or `'openrouter'`) in
-`kindgi.config.ts`'s `providers`: `kindgi dev` then registers it on every
-boot, in every worktree. Other providers and per-agent model choice:
-`.claude/skills/kindgi-authoring-providers/SKILL.md`.
+(`ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, `GEMINI_API_KEY`, `GROQ_API_KEY`
+or `OPENROUTER_API_KEY`) and declare its preset
+(`{ preset: 'anthropic' }`, `'openai'`, `'gemini-api'`, `'groq'` or
+`'openrouter'`) in `kindgi.config.ts`'s `providers`: `kindgi dev` then
+registers it on every boot, in every worktree. Other providers and
+per-agent model choice: the `kindgi-authoring-providers` skill.
 
 ## This pack: a WooCommerce store
 
@@ -39,11 +39,36 @@ README.md explains the whole design; keep it true when you change the pack.
 - **The store's password is a secret** (`WOO_APP_PASSWORD`, set with
   `kindgi secrets set`): never write it in a file, a test or the chat.
 
-## For Claude Code sessions
+## Skills
 
-When you diagnose a framework bug (something in Kindgi itself, not in
-this pack's code), append an entry to `FEEDBACK.md` at the pack root
-via `kindgi feedback write` — see
-`.claude/skills/kindgi-framework-feedback/SKILL.md`. Mark items fixed
-by adding a `> **Fixed:** <note>` line right after their header; the
-file is a plain markdown list you edit directly.
+`.claude/skills/` and `.agents/skills/` hold the same Kindgi skills: getting
+started, tools, guardrails, agents and flows, model providers, MCP servers,
+framework feedback, and guiding the person in using what you built
+(`kindgi-using`). Claude Code loads `.claude/skills/` on its own; Codex and
+Gemini CLI look in `.agents/skills/`; any other coding agent can read
+either. `kindgi skills sync` refreshes both.
+
+When you diagnose a framework bug (something in Kindgi itself, not in this
+pack's code), append an entry to `FEEDBACK.md` at the pack root via
+`kindgi feedback write` — see the `kindgi-framework-feedback` skill. Mark
+items fixed by adding a `> **Fixed:** <note>` line right after their
+header; the file is a plain markdown list you edit directly.
+
+## Commands for the person's own terminal
+
+Two commands are always the person's to run, in their own terminal, since
+they ask for a secret: `kindgi secrets set` and `kindgi auth registry`.
+Others need what a coding agent's sandbox often blocks: `kindgi dev` and any
+dev server (they keep running), and `kindgi build` or anything else that
+needs Docker. When your sandbox blocks a command (a process it can't start,
+`spawn EPERM`; Docker's socket denied; `localhost` refused; a folder it
+keeps read-only, as Codex's keeps `.agents/`, which `kindgi skills sync`
+writes), don't work around it: don't turn your sandbox off, and don't start
+the command in the background. Give the person the exact command, the folder
+to run it in and what they'll see, then wait for them. Once they say
+`kindgi dev` is running, starting it yourself exits 3 and says where theirs
+runs: use that one.
+
+A tool's own `EPERM` while it runs under `kindgi dev` is something else:
+Kindgi's dev sandbox, which the tools skill covers. Never turn that one off
+either.

package/dist/templates/woocommerce/README.md.tmpl

@@ -158,8 +158,7 @@ calls the first tool. For Claude, with `kindgi dev` running:
 {{KINDGI}} providers register --preset=anthropic
 ```
 
-`.claude/skills/kindgi-authoring-providers/SKILL.md` has the other
-providers.
+The `kindgi-authoring-providers` skill has the other providers.
 
 Ask the store agent something:
 
@@ -167,6 +166,32 @@ Ask the store agent something:
 {{KINDGI}} runs start --agent={{PACK_ID}}.store-agent --input='{"userMessage": "Refund 40 on order 1043: the jacket arrived torn."}'
 ```
 
+## One project and one pack per client
+
+This pack is one client's: every id in it starts with `{{PACK_ID}}.`. For
+another client, make another copy, so its ids start with that client's
+name:
+
+```sh
+{{KINDGI}} init <client> --template=woocommerce
+```
+
+Deploy each copy into its client's project (its id or its slug):
+
+```sh
+{{KINDGI}} deploy --project <client project>
+```
+
+The agents and tools are registered in that project. Give it the store's
+credentials there too, apart from your other clients':
+
+```sh
+{{KINDGI}} secrets set WOO_APP_PASSWORD --env=<env> --scope=project:<client project id>
+```
+
+Deploying this same pack into a second project is refused with a `409`,
+since its ids already belong to the first.
+
 ## Review each new order
 
 `{{PACK_ID}}.order-review` is a flow with two steps:
@@ -221,7 +246,7 @@ delivery, and Kindgi checks the signature before it starts a run:
 
 ```sh
 {{KINDGI}} webhooks register --flow={{PACK_ID}}.order-review --flow-version={{PACK_VERSION}} \
-  --preset=woocommerce --generate-secret --secret=WOO_WEBHOOK_SECRET --env=local \
+  --preset=woocommerce --generate-secret --secret=WOO_WEBHOOK_SECRET \
   --label="WooCommerce orders"
 ```
 

package/dist/templates/woocommerce/kindgi.config.ts.tmpl

@@ -13,28 +13,32 @@ const config = {
     flows: 'flows/**/*.ts',
   },
   // ---------------------------------------------------------------
-  // Environments — one entry per deploy target. `kindgi build`
-  // reads `.build`, `.registry`, `.signingKey`, `.tenantId` for the
-  // chosen env; `kindgi deploy` reads `.endpoint`.
+  // Environments: one entry per place you deploy to, picked with
+  // `--env <name>` (default `staging`). `kindgi build` reads `build`,
+  // `registry`, `signingKey` and `tenantId`; `kindgi deploy` reads
+  // `endpoint`. Local `kindgi dev` doesn't read this block.
   //
-  // Fill these in when you're ready to push a build. Local
-  // `kindgi dev` does NOT read this block.
+  // Your API key goes only to the address you signed in to
+  // (`kindgi auth login --url <url>`), so an `endpoint` here must be
+  // that address. Builds are signed with a key of yours: make it with
+  // `kindgi key create <id>`, and let the runtime trust it with
+  // `kindgi key trust <id>` (once).
   // ---------------------------------------------------------------
   environments: {
-    staging: {
-      endpoint: 'https://api.staging.example.com',
-      build: 'http://localhost:8787', // your Kindgi build server
-      registry: 'ghcr.io/your-org',
-      signingKey: '~/.kindgi/keys/staging.pem',
-      tenantId: 'tenant-your-org-staging',
-    },
-    production: {
-      endpoint: 'https://api.example.com',
-      build: 'https://build.example.com',
-      registry: 'ghcr.io/your-org',
-      signingKey: '~/.kindgi/keys/production.pem',
-      tenantId: 'tenant-your-org-production',
-    },
+    // Kindgi Cloud: `kindgi deploy --env=prod` builds there and deploys.
+    // prod: {
+    //   build: 'hosted',
+    //   signingKey: '~/.kindgi/keys/<id>.pem',
+    // },
+    //
+    // A runtime of your own:
+    // production: {
+    //   endpoint: 'https://kindgi.your-company.example', // the address you signed in to
+    //   build: 'https://build.your-company.example', // your Kindgi build server
+    //   registry: 'ghcr.io/your-org',
+    //   signingKey: '~/.kindgi/keys/<id>.pem',
+    //   tenantId: '<your tenant id>',
+    // },
   },
 } as const;
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kindgi/cli",
-  "version": "0.1.7-rc.0",
+  "version": "0.1.8-rc.0",
   "description": "Command-line interface for Kindgi™. Create a pack, run it on your machine (`kindgi dev`), build, sign and deploy it, and work with a running Kindgi API from the terminal.",
   "license": "Apache-2.0",
   "repository": {
@@ -37,18 +37,18 @@
     "provenance": true
   },
   "dependencies": {
-    "@kindgi/agents": "0.1.7-rc.0",
-    "@kindgi/client": "0.1.7-rc.0",
-    "@kindgi/dotenv-file": "0.1.7-rc.0",
-    "@kindgi/crypto": "0.1.7-rc.0",
-    "@kindgi/env-schema": "0.1.7-rc.0",
-    "@kindgi/flow": "0.1.7-rc.0",
-    "@kindgi/handler-runtime": "0.1.7-rc.0",
-    "@kindgi/log": "0.1.7-rc.0",
-    "@kindgi/secrets-dotenv": "0.1.7-rc.0",
-    "@kindgi/platform": "0.1.7-rc.0",
-    "@kindgi/sdk": "0.1.7-rc.0",
-    "@kindgi/types": "0.1.7-rc.0",
+    "@kindgi/agents": "0.1.8-rc.0",
+    "@kindgi/client": "0.1.8-rc.0",
+    "@kindgi/dotenv-file": "0.1.8-rc.0",
+    "@kindgi/crypto": "0.1.8-rc.0",
+    "@kindgi/env-schema": "0.1.8-rc.0",
+    "@kindgi/flow": "0.1.8-rc.0",
+    "@kindgi/handler-runtime": "0.1.8-rc.0",
+    "@kindgi/log": "0.1.8-rc.0",
+    "@kindgi/secrets-dotenv": "0.1.8-rc.0",
+    "@kindgi/platform": "0.1.8-rc.0",
+    "@kindgi/sdk": "0.1.8-rc.0",
+    "@kindgi/types": "0.1.8-rc.0",
     "esbuild": "^0.24.0",
     "semver": "^7.8.5",
     "smol-toml": "^1.9.0",