feat: openclaw qa toolkit

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets).
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md).

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.4/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

AGENTS.md

@@ -4,6 +4,22 @@
 
 **Writing Markdown**: Do not wrap text to 80 chars; let it run freely.
 
+## Tooling
+
+**Package manager**: npm workspaces (root `package.json` declares `"workspaces": ["packages/*"]`).
+
+**Runtime**: Node (ESM only, `"type": "module"`).
+
+**Language**: TypeScript with `strict: true`, `module: NodeNext`. Each package has a `tsconfig.build.json` (emits `dist/`) and a `tsconfig.json` (`noEmit`, includes `src` + `test`).
+
+**Linter / formatter**: Biome (`biome.json` at root). `npm run lint` / `npm run lint:fix`.
+
+**Test runner**: Vitest (`vitest run`). Per-package: `npm test --workspace <name>`. All packages: `npm test`.
+
+**Releases**: Changesets (`.changeset/`). Author a changeset with `npm run changeset`; publish via `npm run changeset:publish`. Base branch: `main`. Default access: `public`.
+
+**Workspace scripts** (root): `build`, `test`, `clear`, `lint`, `lint:fix` — all fan out to packages via `npm run <name> --workspaces --if-present`.
+
 ## AlignFirst - Ticket ID, Commit Message, Branch Name
 
 _Ticket ID_: Format is numeric. Use the ticket ID if explicitly provided. Otherwise, deduce it from the current branch name (no confirmation needed). If the branch name is unavailable, get it via `git branch --show-current`. Only ask the user as a last resort.
@@ -13,3 +29,12 @@ Commit message convention: we use conventional commit, e.g., `feat: [#123] add n
 Branch naming convention: `<type>/<ticket-id>` (with type from conventional commit, e.g., `feat/123`, `fix/123`, `refactor/123`, `chore/123`).
 
 Add `docs/code-style.md` and `docs/code-quality.md` to every plan.
+
+## Packages
+
+- `@paleo/docmap` — lightweight documentation system for AI agents and humans
+- `@paleo/openclaw-channel-mock-core` — shared library for synthetic OpenClaw channel plugins (bus, actions, factories)
+- `@paleo/openclaw-slack-mock` — Slack-shaped channel plugin for QA scenarios
+- `@paleo/openclaw-discord-mock` — Discord-shaped channel plugin for QA scenarios
+- `@paleo/openclaw-qa-runner` — Dockerised regression-test harness (bus, scenario driver, judge, Compose stack)
+- `@paleo/worktree-env` — worktree-based concurrent local environment kernel

README.md

@@ -17,7 +17,3 @@ Collaborative spec/plan/AAD/review protocols. See [alignfirst-skills.md](alignfi
 ## Autonomous agent (experimental)
 
 We're currently working on building an AI developer with _OpenClaw_. See [autonomous-agent.md](autonomous-agent.md).
-
-----
-
-**License:** CC0 1.0 Universal.

autonomous-agent.md

@@ -13,6 +13,10 @@ export ALIGNFIRST_AGENT_LOG_DIR=path/to/directory # Write input/output logs
 export ALIGNFIRST_AGENT_SKIP_PERMISSIONS=1        # Use --dangerously-skip-permissions instead of --permission-mode auto
 ```
 
+## OpenClaw QA toolkit
+
+`@paleo/openclaw-qa-runner` and three companion channel packages — a Dockerised regression-test harness that drives OpenClaw through synthetic Discord and Slack channels. See [packages/openclaw-qa-runner/README.md](packages/openclaw-qa-runner/README.md).
+
 ### OpenClaw Playbook (experimental)
 
 The `alignfirst-coaching` skill ships a reference that teaches OpenClaw how to handle branches, worktrees, commits, PRs/MRs etc. on the project side, and organize the chat with the user through Discord/Slack threads on the user side. Still in development.