crabpot/docs/operations.md

Operations

Adding a fixture

1. Add an entry to crabpot.config.json.
2. Run npm test.
3. Run node scripts/sync-fixtures.mjs --materialize.
4. Review .gitmodules and the pinned submodule commit.
5. Commit the manifest and submodule pointer together.

Updating fixtures

git submodule update --remote --recursive plugins/<fixture-id>
npm test

Then inspect the diff. A fixture update is only useful if it either:

• tracks a plugin release we care about,
• adds coverage for a new seam,
• reproduces a compatibility break,
• or proves a contract migration path still works.

CI model

Use a cheap default workflow first:

• validate the manifest
• ensure .gitmodules agrees with crabpot.config.json
• initialize pinned submodules
• run registration-capture smoke checks

Add heavier lanes later for SDK compilation against specific OpenClaw refs:

• openclaw@main
• latest stable release tag
• active beta branch or release candidate