@kigo-dev/sindri 0.1.0 → 0.1.4

package/README.md

@@ -22,10 +22,17 @@ names, parameters and this document are English. The contract lives in
 | `list_apps` | – | The PM's apps, with local folder state. |
 | `versions` | `app` | Published versions, most recent first. |
 | `rollback` | `app`, `version` | `POST rollback`, then downloads that version's archive and replaces the local tree (keeps `node_modules`, `.sindri`, `.env.local`). Stops the preview first: PGlite allows one process per data dir. |
+| `update_template` | `app` | `POST /v1/apps/<app>/template`: Sindri replaces the files the app never customised with the current template (customised ones come back in `skipped`) and publishes «Plantilla actualizada». When `published`, downloads the new archive and replaces the local tree like `rollback` (stops the preview, re-migrates, rewrites `last-published.json`). Refuses with "Publica o descarta tus cambios antes de actualizar la plantilla" while the folder has unpublished edits. |
+| `rename_app` | `app`, `new_name?`, `display_name?` | At least one. `display_name`: writes `display_name:` in the app's `kigo-app.yaml` (line edit, no YAML library) and runs the `publish` flow with the message «Ahora se llama «<display_name>»». `new_name`: refuses with "Publica tus cambios antes de cambiar la dirección" while the folder has unpublished edits (same check as `status`), `POST /v1/apps/<app>/rename`, then stops the preview, moves `~/Sindri/<app>` to `~/Sindri/<new_name>` and `apps/<owner>/<app>` to `apps/<owner>/<new_name>`, rewrites `name:` in `kigo-app.yaml` exactly like the builder and rewrites `.sindri/last-published.json` so `status` is clean. Both together: visible name first (a publish under the old address), then the address. |
+| `delete_app` | `app`, `confirm` | `confirm` must equal `app` (the PM typed it; the instructions forbid Claude from filling it in). Stops the preview, `DELETE /v1/apps/<app>`, then moves `~/Sindri/<app>` to `~/Sindri/.papelera/<app>-<YYYYMMDD-HHmm>` (Mexico City time) instead of deleting. A 404 from the API with the folder present still moves the folder and says so. |
 | `share` | `app` | The Slack line. |
+| `help` | – | No network. `{ summary, space_url, logged_in, apps_dir }`: the Spanish introduction Claude gives on first contact (what Sindri is, what to ask for, limits, the Mi espacio link https://sindri.kigo.dev), whether credentials are stored on this computer (keychain or file, no API call) and where the apps live. |
+| `design_guide` | `app`, `topic?` | No network. Reads the `kigo-sindri-design` skill the template ships at `apps/<owner>/<app>/.claude/skills/kigo-sindri-design/`: without `topic`, `SKILL.md` plus `topics` (the file names under `references/` without `.md`); with `topic`, that reference file. `{ ok, summary, topic, topics, content }`, `content` verbatim markdown for Claude to follow (never pasted to the PM). `ok:false, code:"no_design_guide"` when the app predates the skill (Claude runs `update_template` once and retries); `code:"unknown_topic"` lists the valid topics. Also exposed as MCP resources `sindri://design-guide/<app>` and `sindri://design-guide/<app>/<topic>`. |
 
 Every result is `{ ok, summary, ...data }`. `needs_login: true` / `needs_setup: true` tell Claude
-which tool to run first. The server also ships `instructions` describing how to talk to the PM.
+which tool to run first. `list_apps` also returns `space_url`. The server also ships
+`instructions` describing how to talk to the PM (first contact via `help`, address vs visible
+name, typed confirmation before `delete_app`).
 
 ## Install
 
@@ -36,7 +43,7 @@ which tool to run first. The server also ships `instructions` describing how to
 **Claude Code:**
 
 ```
-claude mcp add sindri -- npx -y @kigo-dev/sindri
+claude mcp add sindri -- npx -y @kigo-dev/sindri@0.1.4
 ```
 
 **Manual check without an MCP client:**
@@ -82,12 +89,31 @@ archive ships it (`package.json`, `pnpm-workspace.yaml`, `pnpm-lock.yaml`, `tsco
 and cannot install standalone. `pnpm install` runs at that root; `preview`, `db:migrate`,
 `db:seed`, `tsc`, the tree hash, `.env.local`, `.sindri/last-published.json` and the `publish`
 tarball (paths relative to the app) all live at `apps/<owner>/<name>`. `replaceTree` swaps the
-whole root on `create_app`/`rollback` but keeps every `node_modules` and the app's `.sindri/`
+whole root on `create_app`/`rollback`/`update_template` but keeps every `node_modules` and the app's `.sindri/`
 and `.env*`. The owner is the single folder under `apps/`, else the `owner` from `GET /v1/me`
 (cached in `~/.sindri/me.json`).
 
+Claude Code loads project skills from the folder it is opened in, and a PM opens the root
+(`~/Sindri/<name>`), not the app dir. So after every operation that writes the tree
+(`create_app`, `rollback`, `update_template`, `rename_app`) the connector puts a relative symlink at
+`~/Sindri/<name>/.claude/skills/kigo-sindri-design` pointing to
+`apps/<owner>/<name>/.claude/skills/kigo-sindri-design` when that folder exists (`linkDesignGuide`
+in `layout.ts`). It is idempotent, skips silently when the app has no skill and never replaces a
+real directory at that place. The root is neither hashed nor packed, so the link changes nothing
+for `status` or `publish`; the app's own `.claude/` is part of the tree and travels to Sindri.
+
+`rename_app` with `new_name` moves the root and the app dir in place (nothing is downloaded) and
+then applies the one edit the builder made in its copy, `name:` in `kigo-app.yaml`, written as
+`name: "<new_name>"` (JSON-quoted, the shape `mcp` `renderManifest` uses). The tree hash the
+connector stores in `last-published.json` is over the same file set `publish` uploads (everything
+except `node_modules`, `.next`, `.sindri`, `dist`, `.turbo`, `.git`, `.env*`, `.DS_Store`), so a
+file the builder ignores but the connector hashes would make `status` report unpublished edits
+after a rename; `test/tools.test.ts` builds the builder's post-rename tree (old archive, moved,
+`name:` edited) and asserts both hashes are equal. Deleted apps are never removed from disk: they
+go to `~/Sindri/.papelera/`, which no tool scans (`.papelera` is not a valid app name).
+
 ## Local database
 
 The template runs on PGlite when `KIGO_ENV=local` and no `DATABASE_URL` is set; data lives in
 `<app>/.sindri/pglite/`. PGlite is single-process: the connector never runs migrations while a
-preview is up, and stops the preview before a rollback replaces the tree.
+preview is up, and stops the preview before a rollback or a template update replaces the tree.