@jiggai/recipes 0.2.24 → 0.3.0

package/README.md

@@ -11,7 +11,7 @@ If you like durable workflows: ClawRecipes is built around a **file-first team w
 ## Quickstart
 ### 1) Install
 #### Option A (preferred): install from npm
-Once published:
+When published on npm:
 
 ```bash
 openclaw plugins install @jiggai/recipes
@@ -58,7 +58,8 @@ openclaw recipes dispatch \
 - `openclaw recipes list|show|status`
 - `openclaw recipes scaffold` (agent → `workspace-<agentId>` + writes workspace recipe `~/.openclaw/workspace/recipes/<agentId>.md` by default)
 - `openclaw recipes scaffold-team` (team → `workspace-<teamId>` + `roles/<role>/` + writes workspace recipe `~/.openclaw/workspace/recipes/<teamId>.md` by default)
-- `openclaw recipes install <idOrSlug> [--yes] [--global|--agent-id <id>|--team-id <id>]` (skills: global or scoped)
+- `openclaw recipes install-skill <idOrSlug> [--yes] [--global|--agent-id <id>|--team-id <id>]` (skills: global or scoped)
+- `openclaw recipes install <slug>` (marketplace recipe)
 - `openclaw recipes bind|unbind|bindings` (multi-agent routing)
 - `openclaw recipes dispatch ...` (request → inbox + ticket + assignment)
 - `openclaw recipes tickets|move-ticket|assign|take|handoff|complete` (file-first ticket workflow)
@@ -79,15 +80,26 @@ The plugin supports these config keys (with defaults):
 Config schema is defined in `openclaw.plugin.json`.
 
 ## Documentation
-Start here:
-- Installation: `docs/INSTALLATION.md`
-- Agents + skills: `docs/AGENTS_AND_SKILLS.md`
-- Tutorial (create a recipe): `docs/TUTORIAL_CREATE_RECIPE.md`
+**For users:**
+- [Installation](docs/INSTALLATION.md) — install the plugin
+- [Agents & skills](docs/AGENTS_AND_SKILLS.md) — mental model, tool policies
+- [Tutorial](docs/TUTORIAL_CREATE_RECIPE.md) — create your first recipe
+- [Commands](docs/COMMANDS.md) — full command reference
+- [Team workflow](docs/TEAM_WORKFLOW.md) — file-first workflow
+
+**For contributors:**
+- [Architecture](docs/ARCHITECTURE.md) — codebase structure
+- [Contributing](CONTRIBUTING.md) — setup, tests, PR workflow
 
 ## Development
 ### Unit tests (vitest)
 Run:
 - `npm test`
+- `npm run test:coverage` — coverage with CI thresholds (see `vitest.config.ts`)
+- `npm run smell-check` — quality checks (ESLint, jscpd, pattern grep)
+
+### Pre-commit hooks
+Husky runs on commit. Run `npm ci` first to install hooks.
 
 ### Scaffold smoke test (regression)
 A lightweight smoke check validates scaffold-team output contains the required testing workflow docs (ticket 0004).
@@ -98,6 +110,11 @@ Run:
 Notes:
 - Creates a temporary `workspace-smoke-<timestamp>-team` under `~/.openclaw/` and then deletes it.
 - Exits non-zero on mismatch.
+- Requires OpenClaw and workspace config.
+
+### For contributors
+- [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) — codebase structure
+- [CONTRIBUTING.md](CONTRIBUTING.md) — setup, commands, pre-commit, CI
 
 Reference:
 - Commands: `docs/COMMANDS.md`
@@ -139,8 +156,10 @@ Notes:
   - [Recipe format](https://github.com/JIGGAI/ClawRecipes/blob/main/docs/RECIPE_FORMAT.md): `docs/RECIPE_FORMAT.md`
   - [Team workflow](https://github.com/JIGGAI/ClawRecipes/blob/main/docs/TEAM_WORKFLOW.md): `docs/TEAM_WORKFLOW.md`
   - [Agents & Skills](https://github.com/JIGGAI/ClawRecipes/blob/main/docs/AGENTS_AND_SKILLS.md): `docs/AGENTS_AND_SKILLS.md`
+  - [Architecture](https://github.com/JIGGAI/ClawRecipes/blob/main/docs/ARCHITECTURE.md): `docs/ARCHITECTURE.md`
   - [Bundled](https://github.com/JIGGAI/ClawRecipes/blob/main/docs/BUNDLED_RECIPES.md): `docs/BUNDLED_RECIPES.md`
   - [Create Recipe Tutorial](https://github.com/JIGGAI/ClawRecipes/blob/main/docs/TUTORIAL_CREATE_RECIPE.md): `docs/TUTORIAL_CREATE_RECIPE.md`
+  - [Contributing](https://github.com/JIGGAI/ClawRecipes/blob/main/CONTRIBUTING.md): `CONTRIBUTING.md`
 
 ## Note
 ClawRecipes is meant to be *installed* and then used to build **agents + teams**.
@@ -149,3 +168,11 @@ Most users should focus on:
 - authoring recipes in their OpenClaw workspace (`<workspace>/recipes/*.md`)
 - scaffolding teams (`openclaw recipes scaffold-team ...`)
 - running the file-first workflow (dispatch → backlog → in-progress → testing → done)
+
+## Goals
+- Release Clawmarket, https://github.com/JIGGAI/ClawMarket, public url https://clawkitchen.ai
+- Release ClawKitchen, https://github.com/JIGGAI/ClawKitchen
+- Merge at least 1 community pull request
+- Daily shipping/pull requests of ClawRecipes features
+- Improve recipes with more detailed agent files
+- Add ability to install skills for agents through ClawKitchen

package/docs/AGENTS_AND_SKILLS.md

@@ -95,30 +95,26 @@ openclaw gateway restart
 
 > Tip: if you later re-run scaffold with `--apply-config`, the recipe’s tool policy may overwrite your manual edits. If you want a change to stick, encode it in the recipe.
 
-## Installing skills (workspace-local)
-ClawRecipes favors **workspace-local** installs so each OpenClaw workspace is self-contained.
+## Installing skills
+ClawRecipes favors **workspace-local** installs so each agent/team workspace is self-contained.
 
 ### Install a skill slug
 ```bash
-openclaw recipes install <skill-slug>
+openclaw recipes install-skill <skill-slug>
 # or non-interactive:
-openclaw recipes install <skill-slug> --yes
+openclaw recipes install-skill <skill-slug> --yes
 ```
 
-This runs ClawHub under the hood and installs into the **current OpenClaw workspace** skills dir:
-- `<workspace>/skills/<skill-slug>`
-
-Examples:
-- standalone agent workspace: `~/.openclaw/workspace-<agentId>/skills/<skill-slug>`
-- team workspace: `~/.openclaw/workspace-<teamId>/skills/<skill-slug>`
-
-> Note: in the new workspace policy, standalone agents live in `~/.openclaw/workspace-<agentId>` and teams live in `~/.openclaw/workspace-<teamId>`. Skill install targeting is still being refined during the experimental phase.
+By default, installs **globally** into `~/.openclaw/skills/`. Use flags to target a specific workspace:
+- `--global` — shared across all agents (default)
+- `--agent-id <id>` — `~/.openclaw/workspace-<agentId>/skills/<skill-slug>`
+- `--team-id <id>` — `~/.openclaw/workspace-<teamId>/skills/<skill-slug>`
 
 ### Install the skills required by a recipe
 If a recipe declares skills in `requiredSkills` or `optionalSkills`:
 
 ```bash
-openclaw recipes install <recipe-id>
+openclaw recipes install-skill <recipe-id>
 ```
 
 That installs the recipe’s declared skills.

package/docs/ARCHITECTURE.md

@@ -0,0 +1,109 @@
+# Architecture
+
+Overview of the ClawRecipes codebase for maintainers.
+
+## Overview
+
+`index.ts` acts as thin CLI wiring: it registers commands via `api.registerCli` and delegates to handlers. Business logic lives in `src/handlers/` and `src/lib/`. The plugin exports `__internal` for test-only access to handlers and lib functions.
+
+## File structure
+
+```
+ClawRecipes/
+├── index.ts                 # Entry point: CLI wiring, delegates to handlers
+├── src/
+│   ├── handlers/            # One file per command group
+│   │   ├── cron.ts          # Cron reconciliation (used during scaffold)
+│   │   ├── install.ts       # install-skill, install (marketplace recipe)
+│   │   ├── recipes.ts       # list, show, status, bind, unbind, bindings
+│   │   ├── scaffold.ts      # scaffold (single agent)
+│   │   ├── team.ts          # scaffold-team, migrate-team, remove-team
+│   │   └── tickets.ts       # tickets, move-ticket, assign, take, handoff, dispatch, complete
+│   └── lib/                 # Shared logic
+│       ├── recipes-config.ts # OpenClaw config load/write, bindings, agent snippets
+│       ├── recipes.ts       # Recipe listing, loading, workspace paths
+│       ├── recipe-id.ts     # Pick recipe id (auto-increment)
+│       ├── scaffold-utils.ts # Shared scaffold logic
+│       ├── ticket-workflow.ts # Ticket stages, move, assign, handoff
+│       ├── ticket-finder.ts  # Ticket lookup by id/number
+│       ├── lanes.ts         # Workflow stages (backlog, in-progress, testing, done)
+│       ├── cleanup-workspaces.ts
+│       ├── remove-team.ts   # Team uninstall logic
+│       └── ...              # prompt, template, skill-install, fs-utils, etc.
+├── recipes/                 # Bundled recipe markdown files
+├── scripts/                 # Smell-check, scaffold smoke, etc.
+└── tests/                   # Vitest unit tests
+```
+
+## Handler-to-command map
+
+| Handler   | Commands |
+|-----------|----------|
+| recipes   | list, show, status, bind, unbind, bindings |
+| scaffold  | scaffold |
+| team      | scaffold-team, migrate-team, remove-team |
+| tickets   | tickets, move-ticket, assign, take, handoff, dispatch, complete |
+| install   | install-skill (ClawHub skills), install (marketplace recipe), install-recipe (alias) |
+| cron      | Reconciled during scaffold (no standalone command) |
+
+## Shared scaffold flow
+
+Both `scaffold` and `scaffold-team` use:
+
+- `scaffoldAgentFromRecipe` — creates workspace, writes recipe-managed files, applies agent config
+- `reconcileRecipeCronJobs` — when a recipe declares `cronJobs`, installs/updates cron jobs per `cronInstallation` config
+
+Cron behavior applies to both commands when the recipe has `cronJobs` in frontmatter.
+
+## Data flow
+
+```mermaid
+flowchart LR
+    subgraph cli [CLI]
+        Cmd[recipes list/show/status/...]
+    end
+    subgraph idx [index.ts]
+        IndexTS[registerCli]
+    end
+    subgraph handlers [Handlers]
+        HRecipes[recipes.ts]
+        HScaffold[scaffold.ts]
+        HTeam[team.ts]
+        HTickets[tickets.ts]
+        HInstall[install.ts]
+    end
+    subgraph lib [Lib]
+        LibRecipes[recipes-config]
+        LibScaffold[scaffold-utils]
+        LibTickets[ticket-workflow]
+    end
+    Cmd --> IndexTS
+    IndexTS --> HRecipes
+    IndexTS --> HScaffold
+    IndexTS --> HTeam
+    IndexTS --> HTickets
+    IndexTS --> HInstall
+    HRecipes --> LibRecipes
+    HScaffold --> LibScaffold
+    HTeam --> LibScaffold
+    HTickets --> LibTickets
+```
+
+## Key decisions
+
+- **Tool policy preservation**: When a recipe omits `tools`, the scaffold preserves the existing agent's tool policy (rather than resetting it). See scaffold logic and tests.
+- **`__internal` export**: Unit tests import handlers and lib helpers via `__internal`; these are not part of the public plugin API.
+
+## Quality automation
+
+- **smell-check**: `npm run smell-check` runs:
+  - **ESLint**: `no-explicit-any`, `complexity`, `max-lines-per-function`, `max-params` (src/; index.ts exempt from complexity/lines)
+  - **jscpd**: Duplicate code detection (≥8 lines, ≥50 tokens)
+  - **Pattern grep**: `as any` in src/ (max 10), TODO/FIXME/XXX (max 20)
+- **lint**: `npm run lint` / `npm run lint:fix`
+- **tests**: `npm test` (vitest), `npm run test:coverage`
+- **CI**: `.github/workflows/ci.yml` runs test:coverage, smell-check, npm audit
+
+---
+
+If this doc is outdated, please submit a PR to update it.

package/docs/BUNDLED_RECIPES.md

@@ -19,8 +19,8 @@ openclaw recipes scaffold project-manager --agent-id pm --name "Project Manager"
 ```
 
 What it writes:
-- `agents/pm/SOUL.md`
-- `agents/pm/AGENTS.md`
+- `workspace-pm/SOUL.md`
+- `workspace-pm/AGENTS.md`
 
 Default tool policy (recipe-defined):
 - allows: `group:fs`, `group:web`, plus `cron` and `message`
@@ -272,18 +272,7 @@ openclaw recipes scaffold-team financial-planner-team --team-id financial-planne
 Roles:
 - lead, advisor, analyst, tax, insurance, ops
 
-## 17) `stock-trader-team` (team)
-**Use when:** you want a trading workflow: research/signals/risk/journaling.
-
-Scaffold:
-```bash
-openclaw recipes scaffold-team stock-trader-team --team-id stock-trader-team-team --apply-config
-```
-
-Roles:
-- lead, researcher, signals, risk, journal, ops
-
-## 18) `crypto-trader-team` (team)
+## 17) `crypto-trader-team` (team)
 **Use when:** you want a crypto trading workflow with onchain research.
 
 Scaffold:

package/docs/COMMANDS.md

@@ -46,18 +46,13 @@ Options:
 - `--overwrite-recipe` (overwrite the generated workspace recipe file if it already exists)
 - `--overwrite` (overwrite recipe-managed files)
 - `--apply-config` (write/update `agents.list[]` in OpenClaw config)
+- Cron: see Cron installation under scaffold-team.
 
 Also writes a workspace recipe file:
 - `~/.openclaw/workspace/recipes/<recipeId>.md`
 
 ## `scaffold-team <recipeId>`
 
-### Cron installation config
-If a recipe declares `cronJobs`, scaffold will reconcile those jobs using the plugin config key:
-- `plugins.entries.recipes.config.cronInstallation`: `off | prompt | on`
-  - `off`: never install/reconcile
-  - `prompt` (default): prompt each run (default answer is **No**)
-  - `on`: install/reconcile; new jobs follow `enabledByDefault`
 Scaffold a shared **team workspace** + multiple agents from a **team** recipe.
 
 ```bash
@@ -91,30 +86,55 @@ Standard folders:
 Also creates agent config entries under `agents.list[]` (when `--apply-config`), with agent ids:
 - `<teamId>-<role>`
 
-## `install <idOrSlug> [--yes]`
+### Cron installation
+If a recipe declares `cronJobs`, scaffold and scaffold-team reconcile those jobs using the plugin config key:
+- `plugins.entries.recipes.config.cronInstallation`: `off | prompt | on`
+  - `off`: never install/reconcile
+  - `prompt` (default): prompt each run (default answer is **No**)
+  - `on`: install/reconcile; new jobs follow `enabledByDefault`
+
+Applies to both `scaffold` and `scaffold-team` when the recipe declares `cronJobs`.
+
+## `install-skill <idOrSlug> [--yes]`
 Install skills from ClawHub (confirmation-gated).
 
-Default behavior: **global install** into `~/.openclaw/skills`.
+Default: **global** into `~/.openclaw/skills`.
 
 ```bash
 # Global (shared across all agents)
-openclaw recipes install agentchat --yes
+openclaw recipes install-skill agentchat --yes
 
 # Agent-scoped (into workspace-<agentId>/skills)
-openclaw recipes install agentchat --yes --agent-id dev
+openclaw recipes install-skill agentchat --yes --agent-id dev
 
 # Team-scoped (into workspace-<teamId>/skills)
-openclaw recipes install agentchat --yes --team-id development-team-team
+openclaw recipes install-skill agentchat --yes --team-id development-team-team
 ```
 
+Options:
+- `--yes` — skip confirmation
+- `--global` — install into global skills (default when no scope flags)
+- `--agent-id <id>` — install into agent workspace
+- `--team-id <id>` — install into team workspace
+
 Behavior:
 - If `idOrSlug` matches a recipe id, installs that recipe’s `requiredSkills` + `optionalSkills`.
 - Otherwise treats it as a ClawHub skill slug.
-- Installs via:
-  - `npx clawhub@latest --workdir <targetWorkspace> --dir skills install <slug>` (agent/team)
-  - `npx clawhub@latest --workdir ~/.openclaw --dir skills install <slug>` (global)
-- Confirmation-gated unless `--yes`.
-- In non-interactive mode (no TTY), requires `--yes`.
+- Installs via `npx clawhub@latest ...`. Confirmation-gated unless `--yes`. In non-interactive mode (no TTY), requires `--yes`.
+
+## `install <slug>`
+Install a marketplace recipe into your workspace recipes dir (by slug).
+
+```bash
+openclaw recipes install development-team
+openclaw recipes install development-team --overwrite
+```
+
+Options:
+- `--registry-base <url>` — Marketplace API base URL (default: `https://clawkitchen.ai`)
+- `--overwrite` — overwrite existing recipe file
+
+Use `install-recipe` as an alias for this command.
 
 ## `bind`
 Add/update a multi-agent routing binding (writes `bindings[]` in `~/.openclaw/openclaw.json`).
@@ -166,10 +186,58 @@ Options:
 - `--mode move|copy`
 - `--overwrite` (merge into existing destination)
 
+## `remove-team`
+Safe uninstall: remove a scaffolded team workspace, agents from config, and stamped cron jobs.
+
+```bash
+openclaw recipes remove-team --team-id development-team-team --plan --json
+openclaw recipes remove-team --team-id development-team-team --yes
+```
+
+Options:
+- `--team-id <teamId>` (required)
+- `--plan` — print plan and exit without applying
+- `--json` — output JSON
+- `--yes` — skip confirmation (apply destructive changes)
+- `--include-ambiguous` — also remove cron jobs that only loosely match the team (dangerous)
+
+Notes:
+- Confirmation-gated by default. Use `--yes` to apply without prompting.
+- Cron cleanup removes only cron jobs stamped with `recipes.teamId=<teamId>`.
+- Restart required after removal: `openclaw gateway restart`
+
 ## `dispatch`
-Convert a natural-language request into file-first execution artifacts.
+Convert a natural-language request into file-first execution artifacts (inbox + backlog ticket + assignment stubs).
+
+```bash
+openclaw recipes dispatch \
+  --team-id development-team-team \
+  --request "Add a customer-support team recipe" \
+  --owner lead
+```
+
+Options:
+- `--team-id <teamId>` (required)
+- `--request <text>` (optional; prompts in TTY)
+- `--owner dev|devops|lead|test` (default: `dev`)
+- `--yes` (skip review prompt)
+
+Creates:
+- `workspace-<teamId>/inbox/<timestamp>-<slug>.md`
+- `workspace-<teamId>/work/backlog/<NNNN>-<slug>.md`
+- `workspace-<teamId>/work/assignments/<NNNN>-assigned-<owner>.md`
+
+Ticket numbering:
+- Scans `work/backlog`, `work/in-progress`, `work/testing`, `work/done` and uses max+1.
 
-## `tickets`
+Review-before-write:
+- Prints a JSON plan and asks for confirmation unless `--yes`.
+
+## Ticket workflow commands
+
+The following commands manage the file-first ticket flow (`work/backlog` → `in-progress` → `testing` → `done`).
+
+### `tickets`
 List tickets for a team across the standard workflow stages.
 
 ```bash
@@ -202,7 +270,7 @@ openclaw recipes cleanup-workspaces --prefix smoke- --prefix qa- --yes
 openclaw recipes cleanup-workspaces --json
 ```
 
-## `move-ticket`
+### `move-ticket`
 Move a ticket file between workflow stages and update the ticket’s `Status:` field.
 
 ```bash
@@ -217,7 +285,7 @@ Stages:
 - `testing` → `Status: testing`
 - `done` → `Status: done` (optional `Completed:` timestamp)
 
-## `assign`
+### `assign`
 Assign a ticket to an owner (updates `Owner:` and creates an assignment stub).
 
 ```bash
@@ -227,14 +295,14 @@ openclaw recipes assign --team-id <teamId> --ticket 0007 --owner lead
 
 Owners (current): `dev|devops|lead|test`.
 
-## `take`
+### `take`
 Shortcut: assign + move to in-progress.
 
 ```bash
 openclaw recipes take --team-id <teamId> --ticket 0007 --owner dev
 ```
 
-## `handoff`
+### `handoff`
 QA handoff in one step: move a ticket to `work/testing/`, set `Status: testing`, assign to a tester (default `test`), and write/update the assignment stub.
 
 ```bash
@@ -246,33 +314,9 @@ Notes:
 - Creates `work/testing/` if missing.
 - Idempotent: if the ticket is already in `work/testing/`, it won’t re-move it; it will ensure fields + assignment stub.
 
-## `complete`
-Shortcut: move to done + ensure `Status: done` + add `Completed:` timestamp.
+### `complete`
+Shortcut: move to done + ensure `Status: done` + add `Completed:` timestamp. No confirmation prompt.
 
 ```bash
 openclaw recipes complete --team-id <teamId> --ticket 0007
 ```
-
-```bash
-openclaw recipes dispatch \
-  --team-id development-team-team \
-  --request "Add a customer-support team recipe" \
-  --owner lead
-```
-
-Options:
-- `--team-id <teamId>` (required)
-- `--request <text>` (optional; prompts in TTY)
-- `--owner dev|devops|lead|test` (default: `dev`)
-- `--yes` (skip review prompt)
-
-Creates (createOnly):
-- `workspace-<teamId>/inbox/<timestamp>-<slug>.md`
-- `workspace-<teamId>/work/backlog/<NNNN>-<slug>.md`
-- `workspace-<teamId>/work/assignments/<NNNN>-assigned-<owner>.md`
-
-Ticket numbering:
-- Scans `work/backlog`, `work/in-progress`, `work/testing`, `work/done` and uses max+1.
-
-Review-before-write:
-- Prints a JSON plan and asks for confirmation unless `--yes`.

package/docs/INSTALLATION.md

@@ -7,11 +7,11 @@ This repo is an **OpenClaw plugin** (not a standalone CLI). OpenClaw loads it an
 ## Prerequisites
 - OpenClaw installed and working (`openclaw --version`)
 - Node.js available (OpenClaw uses Node to load plugins)
-- (For `recipes install`) you’ll need access to ClawHub (the command runs `npx clawhub@latest ...`).
+- (For `recipes install-skill`) you’ll need access to ClawHub (the command runs `npx clawhub@latest ...`).
 
 ## Install
 ### Option A (preferred): install from npm
-Once published, you can install directly via npm:
+When published on npm, you can install directly:
 
 ```bash
 openclaw plugins install @jiggai/recipes
@@ -34,7 +34,7 @@ openclaw gateway restart
 openclaw plugins list
 ```
 
-### Option B: already cloned
+### Option C: already cloned
 ```bash
 openclaw plugins install --link ~/clawrecipes
 openclaw gateway restart
@@ -47,7 +47,7 @@ openclaw plugins list
 # look for id: recipes
 ```
 
-4) Try a basic command:
+Try a basic command:
 ```bash
 openclaw recipes list
 ```
@@ -77,7 +77,7 @@ openclaw gateway restart
 - Check: `openclaw plugins list`
 - Verify `openclaw.plugin.json` exists at repo root and has `id: "recipes"`.
 
-### `recipes install` fails
+### `recipes install-skill` fails
 - Run `npx clawhub@latest --help` to confirm the CLI can run.
 - Ensure you are logged into ClawHub if required (`npx clawhub@latest login`).
 - Confirm the install scope you intended:

package/docs/RECIPE_FORMAT.md

@@ -9,7 +9,7 @@ They can be:
 ## File locations
 Recipes are discovered from:
 - Built-in: `recipes/default/*.md` inside this plugin
-- Workspace-local: `<workspaceRoot>/recipes/*.md` (default)
+- Workspace-local: `<openclawWorkspace>/recipes/*.md` (default). `<openclawWorkspace>` is your OpenClaw workspace root (typically `~/.openclaw/workspace` or the directory configured in OpenClaw)
 
 ## Frontmatter (common)
 ```yaml
@@ -32,7 +32,7 @@ These are **ClawHub skill slugs**.
 
 They’re used by:
 - `openclaw recipes status` (detect missing skills)
-- `openclaw recipes install <recipeId>` (install the listed skills)
+- `openclaw recipes install-skill <recipeId>` (install the listed skills)
 
 ## Agent recipes
 Agent recipes use templates + files.

package/docs/TEAM_WORKFLOW.md

@@ -21,6 +21,9 @@ When you scaffold a team:
 ```
 
 ## The loop
+
+CLI commands: `dispatch`, `tickets`, `move-ticket`, `assign`, `take`, `handoff`, `complete`. See [COMMANDS.md](COMMANDS.md) for full reference.
+
 1) **Intake**
 - New requests land in `inbox/`.
 
@@ -88,7 +91,7 @@ Then restart the gateway.
 Tip: use the `agents_list` tool to see what’s currently allowed.
 
 ## Dispatcher command
-The lead can convert a natural-language request into artifacts with:
+The lead can convert a natural-language request into artifacts with [dispatch](COMMANDS.md#dispatch):
 
 ```bash
 openclaw recipes dispatch --team-id <teamId> --request "..." --owner dev

package/docs/TUTORIAL_CREATE_RECIPE.md

@@ -29,7 +29,7 @@ kind: team
 version: 0.1.0
 description: A tiny demo team
 
-# Optional: skill slugs to install with `openclaw recipes install my-first-team`
+# Optional: skill slugs to install with `openclaw recipes install-skill my-first-team`
 requiredSkills: []
 
 team:
@@ -133,13 +133,12 @@ This will propose (or write, with `--yes`) three artifacts:
 Tickets move through lanes:
 - `work/backlog/` → `work/in-progress/` → `work/testing/` → `work/done/`
 
-- Move the ticket from `work/backlog/` → `work/in-progress/`
-- Do the work
-- When ready for QA:
-  - Move the ticket to `work/testing/`
-  - Set `Owner: test` and add **Verification steps** to the ticket
-- After verification:
-  - Move the ticket to `work/done/` and add a short completion report
+You can move tickets manually (edit files) or use the CLI:
+- `openclaw recipes take --team-id my-first-team-team --ticket 0001 --owner worker` — assign and move to in-progress
+- `openclaw recipes handoff --team-id my-first-team-team --ticket 0001` — move to testing, assign to test
+- `openclaw recipes complete --team-id my-first-team-team --ticket 0001` — move to done
+
+See `docs/COMMANDS.md` for `move-ticket`, `assign`, and other ticket commands.
 
 ## Common mistakes
 - **Forgetting the `-team` suffix** on `--team-id` (required).

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "recipes",
   "name": "Recipes",
   "description": "Markdown recipes that scaffold agents and teams (workspace-local).",
-  "version": "0.2.22",
+  "version": "0.3.0",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jiggai/recipes",
-  "version": "0.2.24",
+  "version": "0.3.0",
   "description": "ClawRecipes plugin for OpenClaw (markdown recipes -> scaffold agents/teams)",
   "main": "index.ts",
   "type": "commonjs",

package/recipes/default/business-team.md

@@ -268,6 +268,26 @@ templates:
     - Research briefs → outbox/research/
     - Metrics definitions/dashboards notes → shared-context/metrics/
 
+files:
+  - path: SOUL.md
+    template: soul
+    mode: createOnly
+  - path: AGENTS.md
+    template: agents
+    mode: createOnly
+  - path: TOOLS.md
+    template: tools
+    mode: createOnly
+  - path: STATUS.md
+    template: status
+    mode: createOnly
+  - path: NOTES.md
+    template: notes
+    mode: createOnly
+tools:
+  profile: "business"
+  allow: ["group:fs", "group:web"]
+  deny: ["exec"]
 ---
 
 # Business Team Recipe

package/recipes/default/development-team.md

@@ -7,17 +7,25 @@ kind: team
 cronJobs:
   - id: lead-triage-loop
     name: "Lead triage loop"
-    schedule: "*/30 7-23 * * 1-5"
-    timezone: "America/New_York"
-    message: "Automated lead triage loop: triage inbox/tickets, assign work, and update notes/status.md. Anti-stuck: if lowest in-progress is HARD BLOCKED, advance the next unblocked ticket (or pull from backlog). If in-progress is stale (>12h no dated update), comment or move it back."
-    enabledByDefault: true
+    schedule: "*/30 8-23 * * 1-5"
+    agentId: "{{teamId}}-lead"
+    channel: "last"
+    message: "Lead triage loop (automated). Goal: keep tickets moving. Steps: run ticket hygiene; inspect board; pull next actionable work into in-progress; assign owners; write updates to tickets (## Comments) and notes/status.md. If lowest-numbered in-progress is hard-blocked, advance the next unblocked ticket (or pull from backlog)."
+    enabledByDefault: false
   - id: execution-loop
     name: "Execution loop"
-    schedule: "*/30 7-23 * * 1-5"
-    timezone: "America/New_York"
-    message: "Automated execution loop: make progress on in-progress tickets, keep changes small/safe, and update notes/status.md."
+    schedule: "*/30 8-23 * * 1-5"
+    agentId: "{{teamId}}-lead"
+    channel: "last"
+    message: "Execution loop (automated). Goal: make concrete progress on the lowest-numbered in-progress ticket. Run ticket hygiene; perform repo lint/build checks (avoid noisy tests unless defined); update ticket + notes/status.md. Send a message only when there is a material change."
+    enabledByDefault: false
+  - id: pr-watcher
+    name: "PR watcher"
+    schedule: "*/30 8-23 * * 1-5"
+    agentId: "{{teamId}}-lead"
+    channel: "last"
+    message: "PR watcher (automated). Goal: watch ticket-linked PR URLs; summarize failing checks; if merged, move tickets to done with a short completion report. Requires GitHub access/auth on the controller."
     enabledByDefault: false
-  # pr-watcher omitted (enable only when a real PR integration exists)
 requiredSkills: []
 team:
   teamId: development-team
@@ -64,6 +72,7 @@ templates:
 
     Team: {{teamId}}
     Shared workspace: {{teamDir}}
+    Role: lead
 
     ## Guardrails (read → act → write)
 
@@ -72,24 +81,26 @@ templates:
        - `notes/plan.md`
        - `notes/status.md`
        - `shared-context/priorities.md`
-       - the relevant ticket(s)
+       - the current ticket
+
+    During work (every loop):
+    1) Run hygiene:
+       - `./scripts/ticket-hygiene.sh`
 
     After you act:
     1) Write back:
-       - Update tickets with decisions/assignments.
-       - Keep `notes/status.md` current (3–5 bullets per active ticket).
+       - Update the ticket with decisions/assignments and a dated entry under `## Comments`.
+       - Keep `notes/status.md` current (add 3–5 bullets per active ticket).
+       - Append detailed logs/output to `shared-context/agent-outputs/` (append-only).
 
     ## Curator model
 
-    You are the curator of:
+    You curate:
     - `notes/plan.md`
     - `shared-context/priorities.md`
 
-    Everyone else should append to:
+    Other agents should not edit curated files; they append to:
     - `shared-context/agent-outputs/` (append-only)
-    - `shared-context/feedback/`
-
-    Your job is to periodically distill those inputs into the curated files.
 
     ## File-first workflow (tickets)
 
@@ -101,29 +112,9 @@ templates:
     - `work/in-progress/` — tickets currently being executed
     - `work/testing/` — tickets awaiting QA verification
     - `work/done/` — completed tickets + completion notes
-    - `notes/plan.md` — current plan / priorities (curated)
-    - `notes/status.md` — current status snapshot
-    - `shared-context/` — shared context + append-only outputs
-
-    ### Ticket numbering (critical)
-    - Backlog tickets MUST be named `0001-...md`, `0002-...md`, etc.
-    - The developer pulls the lowest-numbered ticket assigned to them.
-
-    ### Ticket format
-    See `TICKETS.md` in the team root. Every ticket should include:
-    - Context
-    - Requirements
-    - Acceptance criteria
-    - Owner (dev/devops)
-    - Status
-
-    ### Your responsibilities
-    - For every new request in `inbox/`, create a normalized ticket in `work/backlog/`.
-    - Curate `notes/plan.md` and `shared-context/priorities.md`.
-    - Keep `notes/status.md` updated.
-    - When work is ready for QA, move the ticket to `work/testing/` and assign it to the tester.
-    - Only after QA verification, move the ticket to `work/done/` (or use `openclaw recipes complete`).
-    - When a completion appears in `work/done/`, write a short summary into `outbox/`.
+
+    Handoff to QA (keeps assignment stubs consistent):
+    - `openclaw recipes handoff --team-id {{teamId}} --ticket <NNNN> --yes`
 
   dev.soul: |
     # SOUL.md
@@ -134,26 +125,32 @@ templates:
   dev.agents: |
     # AGENTS.md
 
-    Team: {teamId}
-    Shared workspace: {teamDir}
+    Team: {{teamId}}
+    Shared workspace: {{teamDir}}
     Role: dev
 
     ## Guardrails (read → act → write)
-    Before you act:
-    1) Read:
-       - `notes/plan.md`
-       - `notes/status.md`
-       - relevant ticket(s) in `work/in-progress/`
-       - any relevant shared context under `shared-context/`
 
-    After you act:
-    1) Write back:
-       - Put outputs in the agreed folder (usually `outbox/` or a ticket file).
-       - Update the ticket with what you did and where the artifact is.
+    Before you change anything, read:
+    - `notes/plan.md`
+    - `notes/status.md`
+    - `shared-context/priorities.md`
+    - the current ticket
 
-    ## Workflow
-    - Prefer a pull model: wait for a clear task from the lead, or propose a scoped task.
-    - Keep work small and reversible.
+    Quick hygiene around stage moves:
+    - `./scripts/ticket-hygiene-dev.sh`
+
+    After you act, write back:
+    - Update the ticket with what you did + verification steps.
+    - Check/respond in the ticket’s `## Comments` section (especially if you were pinged).
+    - Add 3–5 bullets to `notes/status.md`.
+    - Append detailed logs/output to `shared-context/agent-outputs/` (append-only).
+
+    ## Pull system
+
+    - Continue any ticket already assigned to you in `work/in-progress/`.
+    - Otherwise pull the lowest-numbered assigned ticket from `work/backlog/` and move it to `work/in-progress/`.
+    - Keep changes small and reversible.
   devops.soul: |
     # SOUL.md
 
@@ -241,26 +238,30 @@ templates:
   test.agents: |
     # AGENTS.md
 
-    Team: {teamId}
-    Shared workspace: {teamDir}
+    Team: {{teamId}}
+    Shared workspace: {{teamDir}}
     Role: test
 
     ## Guardrails (read → act → write)
-    Before you act:
-    1) Read:
-       - `notes/plan.md`
-       - `notes/status.md`
-       - relevant ticket(s) in `work/in-progress/`
-       - any relevant shared context under `shared-context/`
 
-    After you act:
-    1) Write back:
-       - Put outputs in the agreed folder (usually `outbox/` or a ticket file).
-       - Update the ticket with what you did and where the artifact is.
+    Before you verify anything, read:
+    - `notes/plan.md`
+    - `notes/status.md`
+    - `shared-context/priorities.md`
+    - the ticket in `work/testing/`
 
-    ## Workflow
-    - Prefer a pull model: wait for a clear task from the lead, or propose a scoped task.
-    - Keep work small and reversible.
+    After you verify, write back:
+    - Record QA verification (preferred): create `work/testing/<ticket>.testing-verified.md`.
+      - Alternative: add a clear `## QA verification` section in the ticket.
+    - If failing: write a concise bug note, then move the ticket back to `work/in-progress/` and assign to the right owner.
+    - Check/respond in the ticket’s `## Comments` section.
+    - Add 3–5 bullets to `notes/status.md`.
+    - Append detailed logs/output to `shared-context/agent-outputs/` (append-only).
+
+    ## Testing lane workflow
+
+    - Work from `work/testing/`.
+    - Follow the ticket’s “How to test” steps and validate acceptance criteria.
   test.tools: |
     # TOOLS.md
 

package/src/handlers/cron.ts

@@ -9,6 +9,36 @@ import { toolsInvoke, type ToolTextResult } from "../toolsInvoke";
 
 export type CronInstallMode = "off" | "prompt" | "on";
 
+function interpolateTemplate(input: string | undefined, vars: Record<string, string>): string | undefined {
+  if (input == null) return undefined;
+  let out = String(input);
+  for (const [k, v] of Object.entries(vars)) {
+    out = out.replaceAll(`{{${k}}}`, v);
+  }
+  return out;
+}
+
+function applyCronJobVars(
+  scope: CronReconcileScope,
+  j: { id: string; name?: string; schedule?: string; timezone?: string; channel?: string; to?: string; agentId?: string; description?: string; message?: string; enabledByDefault?: boolean },
+): typeof j {
+  const vars: Record<string, string> = {
+    recipeId: scope.recipeId,
+    ...(scope.kind === "team" ? { teamId: scope.teamId } : { agentId: scope.agentId }),
+  };
+  return {
+    ...j,
+    name: interpolateTemplate(j.name, vars),
+    schedule: interpolateTemplate(j.schedule, vars),
+    timezone: interpolateTemplate(j.timezone, vars),
+    channel: interpolateTemplate(j.channel, vars),
+    to: interpolateTemplate(j.to, vars),
+    agentId: interpolateTemplate(j.agentId, vars),
+    description: interpolateTemplate(j.description, vars),
+    message: interpolateTemplate(j.message, vars),
+  };
+}
+
 type OpenClawCronJob = {
   id: string;
   name?: string;
@@ -145,15 +175,29 @@ async function resolveCronUserOptIn(
   mode: CronInstallMode,
   recipeId: string,
   desiredCount: number
-): Promise<{ userOptIn: boolean } | { return: { ok: true; changed: false; note: string; desiredCount: number } }> {
+): Promise<
+  | { userOptIn: boolean; enableInstalled: boolean }
+  | { return: { ok: true; changed: false; note: string; desiredCount: number } }
+> {
   if (mode === "off") return { return: { ok: true, changed: false, note: "cron-installation-off" as const, desiredCount } };
-  if (mode === "on") return { userOptIn: true };
+  if (mode === "on") return { userOptIn: true, enableInstalled: true };
+
+  // mode === "prompt"
+  // In non-interactive runs we still reconcile (create/update) cron jobs, but always DISABLED.
+  // This keeps scaffold idempotent and avoids silently skipping cron job stamping.
+  if (!process.stdin.isTTY) {
+    console.error(
+      `Non-interactive mode: cronInstallation=prompt; reconciling ${desiredCount} cron job(s) as disabled (no prompt).`
+    );
+    return { userOptIn: false, enableInstalled: false };
+  }
 
   const header = `Recipe ${recipeId} defines ${desiredCount} cron job(s).\nThese run automatically on a schedule. Install them?`;
   const userOptIn = await promptYesNo(header);
   if (!userOptIn) return { return: { ok: true, changed: false, note: "cron-installation-declined" as const, desiredCount } };
-  if (!process.stdin.isTTY) console.error("Non-interactive mode: defaulting cron install to disabled.");
-  return { userOptIn };
+
+  const enableInstalled = await promptYesNo("Enable the installed cron jobs now? (You can always enable later)");
+  return { userOptIn, enableInstalled };
 }
 
 async function createNewCronJob(opts: {
@@ -183,12 +227,13 @@ async function updateExistingCronJob(opts: {
   prevSpecHash: string | undefined;
   specHash: string;
   userOptIn: boolean;
+  enableInstalled: boolean;
   key: string;
   now: number;
   state: Awaited<ReturnType<typeof loadCronMappingState>>;
   results: CronReconcileResult[];
 }) {
-  const { api, j, name, existing, prevSpecHash, specHash, userOptIn, key, now, state, results } = opts;
+  const { api, j, name, existing, prevSpecHash, specHash, userOptIn, enableInstalled, key, now, state, results } = opts;
   if (prevSpecHash !== specHash) {
     await cronUpdate(api, existing.id, buildCronJobPatch(j, name));
     results.push({ action: "updated", key, installedCronId: existing.id });
@@ -199,6 +244,11 @@ async function updateExistingCronJob(opts: {
     await cronUpdate(api, existing.id, { enabled: false });
     results.push({ action: "disabled", key, installedCronId: existing.id });
   }
+
+  if (userOptIn && enableInstalled && !existing.enabled) {
+    await cronUpdate(api, existing.id, { enabled: true });
+    results.push({ action: "updated", key, installedCronId: existing.id });
+  }
   state.entries[key] = { installedCronId: existing.id, specHash, updatedAtMs: now, orphaned: false };
 }
 
@@ -212,31 +262,47 @@ async function reconcileOneCronJob(
     results: CronReconcileResult[];
   },
   j: (ReturnType<typeof normalizeCronJobs>)[number],
-  userOptIn: boolean
+  userOptIn: boolean,
+  enableInstalled: boolean
 ) {
   const { api, scope, state, byId, now, results } = ctx;
-  const key = cronKey(scope, j.id);
-  const name = j.name ?? `${scope.kind === "team" ? scope.teamId : scope.agentId} • ${scope.recipeId} • ${j.id}`;
+  const jj = applyCronJobVars(scope, j);
+  const key = cronKey(scope, jj.id);
+  const name =
+    jj.name ?? `${scope.kind === "team" ? scope.teamId : scope.agentId} • ${scope.recipeId} • ${jj.id}`;
   const specHash = hashSpec({
-    schedule: j.schedule,
-    message: j.message,
-    timezone: j.timezone ?? "",
-    channel: j.channel ?? "last",
-    to: j.to ?? "",
-    agentId: j.agentId ?? "",
+    schedule: jj.schedule,
+    message: jj.message,
+    timezone: jj.timezone ?? "",
+    channel: jj.channel ?? "last",
+    to: jj.to ?? "",
+    agentId: jj.agentId ?? "",
     name,
-    description: j.description ?? "",
+    description: jj.description ?? "",
   });
 
   const prev = state.entries[key];
   const existing = prev?.installedCronId ? byId.get(prev.installedCronId) : undefined;
-  const wantEnabled = userOptIn ? Boolean(j.enabledByDefault) : false;
+  const wantEnabled = userOptIn ? (enableInstalled ? true : Boolean(jj.enabledByDefault)) : false;
 
   if (!existing) {
-    await createNewCronJob({ api, scope, j, wantEnabled, key, specHash, now, state, results });
+    await createNewCronJob({ api, scope, j: jj, wantEnabled, key, specHash, now, state, results });
     return;
   }
-  await updateExistingCronJob({ api, j, name, existing, prevSpecHash: prev?.specHash, specHash, userOptIn, key, now, state, results });
+  await updateExistingCronJob({
+    api,
+    j: jj,
+    name,
+    existing,
+    prevSpecHash: prev?.specHash,
+    specHash,
+    userOptIn,
+    enableInstalled,
+    key,
+    now,
+    state,
+    results,
+  });
 }
 
 async function reconcileDesiredCronJobs(opts: {
@@ -244,6 +310,7 @@ async function reconcileDesiredCronJobs(opts: {
   scope: CronReconcileScope;
   desired: ReturnType<typeof normalizeCronJobs>;
   userOptIn: boolean;
+  enableInstalled: boolean;
   state: Awaited<ReturnType<typeof loadCronMappingState>>;
   byId: Map<string, OpenClawCronJob>;
   now: number;
@@ -258,7 +325,7 @@ async function reconcileDesiredCronJobs(opts: {
     results: opts.results,
   };
   for (const j of opts.desired) {
-    await reconcileOneCronJob(ctx, j, opts.userOptIn);
+    await reconcileOneCronJob(ctx, j, opts.userOptIn, opts.enableInstalled);
   }
 }
 
@@ -290,7 +357,16 @@ export async function reconcileRecipeCronJobs(opts: {
   const desiredIds = new Set(desired.map((j) => j.id));
   const results: CronReconcileResult[] = [];
 
-  await reconcileDesiredCronJobs({ ...opts, desired, userOptIn: optIn.userOptIn, state, byId, now, results });
+  await reconcileDesiredCronJobs({
+    ...opts,
+    desired,
+    userOptIn: optIn.userOptIn,
+    enableInstalled: optIn.enableInstalled,
+    state,
+    byId,
+    now,
+    results,
+  });
   await disableOrphanedCronJobs({
     api: opts.api,
     state,

package/docs/CLEANUP_TODO.md

@@ -1,31 +0,0 @@
-# Cleanup TODO
-
-## Infrastructure
-
-- [x] Add @vitest/coverage-v8, test:coverage script
-- [x] Create TEST_COVERAGE_PROGRESS.md, CODE_SMELLS_TRACKER.md
-- [x] Run baseline coverage, populate progress doc
-- [x] Update TEST_COVERAGE_PROGRESS.md after each coverage batch
-
-## Code Smells
-
-- [x] Extract fileExists to src/lib/fs-utils
-- [x] Extract stableStringify to src/lib/stable-stringify
-- [x] Unify parseFrontmatter/normalizeCronJobs (use recipe-frontmatter)
-- [x] Replace magic numbers in toolsInvoke
-
-## Test Coverage
-
-- [x] lanes.ts
-- [x] ticket-finder.ts
-- [x] cleanup-workspaces (expand)
-- [x] remove-team (expand)
-- [x] marketplaceFetch (with fetch mock)
-- [x] toolsInvoke (with fetch mock)
-- [x] Extracted config, template, cron-utils, agent-config
-- [x] index.ts handlers (via extraction or integration)
-
-## Final
-
-- [x] Set coverage thresholds (phased: 25% baseline; target 95%)
-- [x] Verify npm run test:coverage passes

package/docs/CODE_SMELLS_TRACKER.md

@@ -1,42 +0,0 @@
-# Code Smells Tracker
-
-| # | Smell | Status | Priority | Notes |
-|---|-------|--------|----------|-------|
-| 1 | fileExists duplicated (index, ticket-finder, ticket-workflow, lanes, remove-team) | done | high | Extracted to src/lib/fs-utils |
-| 2 | stableStringify duplicated (index, bindings) | done | high | Extracted to src/lib/stable-stringify |
-| 3 | parseFrontmatter/normalizeCronJobs duplicated (index, recipe-frontmatter) | done | high | Unified; recipe-frontmatter extended with message/task/prompt |
-| 4 | Magic numbers in toolsInvoke (30_000, 150*attempt) | done | medium | Extracted as TOOLS_INVOKE_TIMEOUT_MS, RETRY_DELAY_BASE_MS |
-| 5 | index.ts god file (~2500 lines) | done | low | Extracted handlers to src/handlers/; index now ~670 lines (Phase 3) |
-| 6 | Duplicate ticket-finding logic (ticket-workflow vs ticket-finder) | done | medium | ticket-workflow now delegates to ticket-finder |
-| 7 | Duplicated ticket regex patterns | done | low | TICKET_FILENAME_REGEX in ticket-finder; tickets uses it |
-| 8 | Hardcoded "recipes" in scaffold | done | low | scaffold uses cfg.workspaceRecipesDir |
-| 9 | Lane path duplication in tickets | done | low | tickets uses ticketStageDir from lanes |
-| 10 | Magic numbers (1000, 18789, 0000) | done | low | MAX_RECIPE_ID_AUTO_INCREMENT, GATEWAY_DEFAULT_PORT, DEFAULT_TICKET_NUMBER in constants |
-| 11 | Overlapping TicketLane/TicketStage types | done | low | TicketLane = Exclude<TicketStage, "assignments"> in lanes; ticket-finder re-exports |
-| 12 | Config load/write duplicated | done | medium | loadOpenClawConfig, writeOpenClawConfig in recipes-config; all callers use them |
-| 13 | nextTicketNumber inline in dispatch | done | low | Extracted computeNextTicketNumber to ticket-finder |
-| 14 | bindings.ts vs recipes-config duplication | done | low | bindings re-exports from recipes-config; bindings.test uses recipes-config |
-| 15 | Silent catch in handleDispatch | done | low | Documented: non-critical enqueueSystemEvent, nudgeQueued reflects skip |
-| 16 | Duplicate pickRecipeId (scaffold vs team) | done | medium | Extracted to src/lib/recipe-id |
-| 17 | Hardcoded "recipes" in team | done | low | team uses cfg.workspaceRecipesDir |
-| 18 | as any in recipe-frontmatter normalizeCronJobs | done | low | CronJobInput type |
-| 19 | as any in cron.ts (scope, created response) | done | low | Proper types; CronAddResponse, CronReconcileResult |
-| 20 | getCfg trivial wrapper in recipes | done | very low | Inlined getRecipesConfig |
-| 21 | results: any[] in cron | done | low | CronReconcileResult union type |
-
-## Automated smell detection
-
-Run `npm run smell-check` to:
-- **ESLint**: `no-explicit-any`, `complexity`, `max-lines-per-function`, `max-params` (src/; index.ts exempt from complexity/lines)
-- **jscpd**: Duplicate code detection (≥8 lines, ≥50 tokens)
-- **Pattern grep**: `as any` in src/ (max 10), TODO/FIXME/XXX (max 20)
-
-Scripts: `npm run lint`, `npm run lint:fix`, `npm run jscpd`, `npm run smell-check`
-
-## Resolution log
-
-- **Smell 5**: Index handler extraction (Phase 2–3) moved ~1200 lines to src/handlers/{cron,recipes,scaffold,team,tickets,install}.ts. index.ts now thin CLI wiring only.
-- **Smells 6–11**: Additional cleanup: consolidated ticket-finding, extracted regex/constants, used config for recipes dir, ticketStageDir, magic-number constants, unified lane types.
-- **Smells 12–15**: Config helpers (load/write), computeNextTicketNumber, bindings consolidation, silent-catch documentation.
-- **Smells 16–21**: pickRecipeId extracted to recipe-id; team uses workspaceRecipesDir; CronJobInput type; cron types (CronAddResponse, CronReconcileResult); getCfg inlined; config double-lookup comment.
-- **Post-cleanup complete** (Feb 2026): All 21 smells resolved; smell-check passes with 0 warnings. Additional quality improvements: pre-commit hooks (husky + lint-staged), CI coverage enforcement, tsconfig.json, JSDoc for public APIs.

package/docs/SMELLS_TODO.md

@@ -1,23 +0,0 @@
-# Remaining Code Smells — TODO
-
-## Type safety (`as any` / `any`) — DONE
-
-- [x] **cron.ts** — Replaced with OpenClawCronJob, CronJobPatch, OpenClawPluginApi
-- [x] **team.ts** — AgentScaffoldResult, MigrateStep types
-- [x] **recipes-config.ts** — OpenClawConfigMutable
-- [x] **remove-team.ts** — Record<string, unknown>
-- [ ] **index.ts** — ~16 options: any remain (partial: install, scaffold use typed opts)
-- [x] **Misc** — recipes, tickets, agent-config, config, cron-utils, marketplaceFetch, toolsInvoke, lanes, cleanup-workspaces, recipe-frontmatter
-
-## Duplicate code (jscpd) — DONE
-
-- [x] **ticket-workflow.ts** — patchTicketFields extracted
-- [x] **tickets.ts** — dryRunTicketMove extracted
-- [x] **index.ts** — runInstallRecipe, logScaffoldResult extracted
-
-## Remaining (deferred)
-
-- [ ] **Complexity** — reconcileRecipeCronJobs (55), handleScaffoldTeam (27), etc.
-- [ ] **Long functions** — handleScaffoldTeam (163), reconcileRecipeCronJobs (139)
-- [ ] **scaffold.ts ↔ team.ts** — pickRecipeId already shared; further unification optional
-- [ ] **Console in src/lib** — Logging abstraction

package/docs/TEST_COVERAGE_PROGRESS.md

@@ -1,37 +0,0 @@
-# Test Coverage Progress
-
-Target: 95% line coverage.
-
-## Baseline (before cleanup)
-
-| File | % Stmts | % Branch | % Funcs | % Lines | Notes |
-|------|---------|----------|---------|---------|-------|
-| index.ts | 4.16 | 61.53 | 18.42 | 4.16 | God file; most logic untested |
-| src/marketplaceFetch.ts | 0 | 100 | 100 | 0 | Needs fetch mock |
-| src/toolsInvoke.ts | 0 | 100 | 0 | 0 | Needs fetch mock |
-| src/lib/bindings.ts | 91.42 | 66.66 | 100 | 91.42 | Lines 50-52 uncovered |
-| src/lib/cleanup-workspaces.ts | 78.51 | 61.9 | 100 | 78.51 | |
-| src/lib/lanes.ts | 60 | 83.33 | 66.66 | 60 | |
-| src/lib/recipe-frontmatter.ts | 93.54 | 70.83 | 100 | 93.54 | |
-| src/lib/remove-team.ts | 81.51 | 70.58 | 63.63 | 81.51 | |
-| src/lib/scaffold-templates.ts | 100 | 100 | 100 | 100 | |
-| src/lib/shared-context.ts | 100 | 85.71 | 100 | 100 | |
-| src/lib/ticket-finder.ts | 0 | 0 | 0 | 0 | Not yet exercised by tests |
-| src/lib/ticket-workflow.ts | 96.52 | 37.5 | 100 | 96.52 | |
-| **All files** | **18.25** | **58.85** | **48.83** | **18.25** | |
-
-## Gaps to address
-
-- index.ts: extract logic to src/lib and test there; add integration tests for command handlers
-- ticket-finder.ts: add tests
-- marketplaceFetch, toolsInvoke: mock fetch, add tests
-- lanes.ts, cleanup-workspaces, remove-team: expand tests
-
-## Updates
-
-- **Baseline**: Initial coverage run before cleanup work.
-- **Post-cleanup**: 25% overall; src/lib at 91.53%, src/ at 98.36%. index.ts remains low (3.91%) — extraction moved logic to lib. Thresholds set at 25% baseline; target 95% as further index extraction proceeds.
-- **Index handler extraction (Phase 2–3)**: Handler logic moved to src/handlers/; exercised via __internal in integration tests.
-- **Post-extraction baseline** (npm run test:coverage): 56.55% overall; src/ at 98.36%; src/handlers at 66.44%; src/lib at 94.63%; index.ts at 9.62% (thin CLI wiring).
-- **Comprehensive coverage plan** (Phase 1–3): cron-handler, install-handler, prompt, workspace, scaffold, team, tickets, recipes tests added. Thresholds raised to 60% lines/statements, 90% functions. index.ts remains thin wiring; logic exercised via __internal.
-- **CI coverage enforcement** (Feb 2026): CI now runs `npm run test:coverage`; build fails if thresholds are not met. Thresholds: lines 60%, statements 60%, functions 90%, branches 65%.