duclaw-cli 1.7.4 → 1.7.5

package/skills/.skills_store_lock.json

@@ -1,11 +0,0 @@
-{
-  "version": 1,
-  "skills": {
-    "github-api": {
-      "name": "GitHub",
-      "zip_url": "https://lightmake.site/api/v1/download?slug=github-api",
-      "source": "skillhub",
-      "version": "1.0.3"
-    }
-  }
-}

package/skills/duclaw-saas-release/SKILL.md

@@ -1,161 +0,0 @@
----
-name: duclaw-saas-release
-description: |
-  Release and roll out Duclaw Core updates to the SaaS layer without coupling Core back to SaaS.
-  Use this skill when updating tenant images, publishing Core versions, building tenant images from local source or npm, updating TENANT_IMAGE, or rolling out already-running tenants to a new image tag.
----
-
-# Duclaw SaaS Release
-
-Use this skill for the release/update chain between Core and SaaS.
-
-Boundary rule:
-
-- Core may evolve to support SaaS
-- SaaS may orchestrate Core
-- Core must not depend on SaaS internals
-
-This skill assumes:
-
-- Core = `src/` + `web/`
-- SaaS = `control-plane/` + `portal/`
-- Tenant runtime is updated by **image tag + container recreate**
-- `Restart` alone does **not** switch image versions
-
-## Pick The Right Flow
-
-Use **Local Source Flow** when:
-
-- You changed Core code locally
-- You want a local SaaS environment to use the latest Core immediately
-
-Use **Published npm Flow** when:
-
-- SaaS is deployed on another machine
-- That machine can access npm, but not your local source tree
-
-## Local Source Flow
-
-1. Build or refresh base images if needed:
-
-```bash
-pnpm tenant:base:build
-```
-
-Only needed when base images are missing, or `docker/Dockerfile.base` changed.
-
-2. Build the tenant image from the current local Core source:
-
-```bash
-pnpm tenant:image:build
-```
-
-This flow uses:
-
-- `build:all`
-- `core:pack`
-- Docker build from the packed Core artifact
-
-3. Roll out existing tenants to the new image:
-
-Dry run first:
-
-```bash
-pnpm --filter @duclaw/control-plane rollout:image --image duclaw:latest --dry-run --all
-```
-
-Then real rollout:
-
-```bash
-pnpm --filter @duclaw/control-plane rollout:image --image duclaw:latest --all
-```
-
-Target only one tenant when safer:
-
-```bash
-pnpm --filter @duclaw/control-plane rollout:image --image duclaw:latest --tenant <tenantId>
-```
-
-## Published npm Flow
-
-1. Publish a Core version to npm, for example `duclaw-cli@1.8.0`
-
-2. On the SaaS machine, build a tenant image from npm:
-
-```bash
-pnpm tenant:base:build
-IMAGE_REPO=registry/duclaw-runtime pnpm tenant:image:build:npm --version 1.8.0
-```
-
-If base images already exist, skip `tenant:base:build`.
-
-If `--version` is omitted, the command resolves npm `latest`.
-
-3. Update `TENANT_IMAGE` in `control-plane/.env`
-
-Example:
-
-```env
-TENANT_IMAGE="registry/duclaw-runtime:1.8.0"
-```
-
-Important:
-
-- `TENANT_IMAGE` affects **future new tenants**
-- existing tenants keep their own `imageTag` until rollout
-
-4. Restart control-plane so the new default takes effect
-
-5. Roll out existing tenants:
-
-Dry run:
-
-```bash
-pnpm --filter @duclaw/control-plane rollout:image --image registry/duclaw-runtime:1.8.0 --dry-run --all
-```
-
-Real rollout:
-
-```bash
-pnpm --filter @duclaw/control-plane rollout:image --image registry/duclaw-runtime:1.8.0 --all
-```
-
-Scope the rollout if needed:
-
-```bash
-pnpm --filter @duclaw/control-plane rollout:image --image registry/duclaw-runtime:1.8.0 --tenant <tenantId>
-pnpm --filter @duclaw/control-plane rollout:image --image registry/duclaw-runtime:1.8.0 --user <userId>
-pnpm --filter @duclaw/control-plane rollout:image --image registry/duclaw-runtime:1.8.0 --limit 10 --all
-```
-
-## Rollback
-
-Rollback uses the same rollout mechanism with an older image tag.
-
-1. Set `TENANT_IMAGE` back to the old stable tag
-2. Restart control-plane
-3. Roll out existing tenants to the old tag
-
-Example:
-
-```bash
-pnpm --filter @duclaw/control-plane rollout:image --image registry/duclaw-runtime:1.7.9 --all
-```
-
-## Operational Rules
-
-- Prefer immutable version tags in production, not `latest`
-- Use `--dry-run` before large rollouts
-- Roll out one tenant first when risk is non-trivial
-- Treat image build and tenant rollout as separate steps
-- Never assume `restart` updates running tenants to a new Core version
-
-## Canonical Files
-
-Read these only when you need deeper context:
-
-- `docs/CORE-SAAS-BOUNDARY.md`
-- `docs/SAAS-QUICKSTART.md`
-- `docker/Dockerfile.npm`
-- `scripts/buildTenantImageFromNpm.js`
-- `control-plane/scripts/rolloutImage.ts`

package/skills/github-api/LICENSE.txt

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2026 Maton
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.