maw-plugins

Extracted maw verb plugins — ship-tier WASM artifacts with sha256 pins, one package per verb under packages/NN-verb/.

These are the verbs moved out of the maw core (lean-core extraction) into installable plugins. Each package ships a committed plugin.wasm built for wasm32-unknown-unknown, pinned by sha256 in its manifest.

Layout

packages/
├── 20-costs/            ← weight 20: tools
│   ├── Cargo.toml       # cdylib crate, extism-pdk = "1.4"
│   ├── src/lib.rs       # plugin implementation
│   ├── plugin.wasm      # committed ship artifact
│   └── plugin.json      # manifest — artifact.sha256 pin, cli surface, capabilities
├── 20-mega/
├── 50-incubate/         ← weight 50: features
└── ...

Number prefix = weight = execution order (lower fires first).

Fleet plugins (imported from maw-rs fleet-plugins/)

The shipped fleet plugins were extracted out of maw-rs (repo split phase 1, 2026-07-15) and live here under their bare, unprefixed names — maw-rs's baked install hints (KNOWN_FLEET_PLUGIN_VERBS) reference Soul-Brews-Studio/maw-plugins/packages/<dir> verbatim, so these dirs must not be renamed:

• packages/atlas, packages/hermes, packages/squad, packages/team, packages/cross-team-queue — ship-tier WASM (AssemblyScript source in src/plugin.ts, committed plugin.wasm pinned by artifact.sha256 in plugin.json, rebuild manifest in plugin.source.json).
• packages/share, packages/p2p-share — bun-dev tier (TypeScript entry, no WASM artifact).
• packages/maw-menubar — bun-dev + native Swift helper (committed universal bin/maw-menubar, pinned via bundledArtifacts in plugin.json).

The full dev-Bun → ship-WASM ladder and pin lifecycle reference is docs/fleet-plugins.md.

Manifest (plugin.json)

{
  "name": "costs",
  "schemaVersion": 1,
  "target": "wasm",
  "entry": { "kind": "wasm", "path": "plugin.wasm", "export": "handle" },
  "artifact": {
    "path": "./plugin.wasm",
    "sha256": "sha256:<hex digest of the committed plugin.wasm>"
  },
  "capabilities": ["fs:read:claude-projects"],
  "cli": { "command": "costs", "help": "maw costs [--json]" },
  "weight": 20
}

The artifact.sha256 pin must always equal the sha256 of the committed plugin.wasm — CI enforces this.

Authoring a plugin

The pattern is direct extism-pdk — the old maw-plugin-pdk wrapper crate is deleted and is NOT the pattern.

[package]
name = "maw_<verb>_plugin"
version = "0.1.0"
edition = "2021"

[lib]
crate-type = ["cdylib"]

[dependencies]
extism-pdk = "1.4"
serde = { version = "1", features = ["derive"] }
serde_json = "1"

Build:

rustup target add wasm32-unknown-unknown
cargo build --release --target wasm32-unknown-unknown
cp target/wasm32-unknown-unknown/release/maw_<verb>_plugin.wasm plugin.wasm
shasum -a 256 plugin.wasm   # update artifact.sha256 in plugin.json

Host functions (maw_identity, maw_send, …) are provided by the maw-rs WASM host at runtime.

Install

maw plugin install Soul-Brews-Studio/maw-plugins/packages/NN-verb --sha256 <pin>

Known issue: the wasm git-install route is currently blocked by maw-rs#521 — until that lands, install from a local clone instead:

git clone https://github.com/Soul-Brews-Studio/maw-plugins
maw plugin install --path maw-plugins/packages/NN-verb

CI

Every push/PR builds each packages/*/ crate for wasm32-unknown-unknown, runs its tests where present, and verifies pin integrity: the sha256 of the committed plugin.wasm must equal the manifest's artifact.sha256 (taken from plugin.json, falling back to plugin.source.json for dev-tier-active fleet plugins). (Rebuilt wasm is NOT compared against the pin — build determinism is unproven.)

Fleet plugins additionally get their bun tests run (packages/*/src/*.test.ts) and, for maw-menubar, a macOS job that verifies the committed universal helper's sha256 pin, arm64+x86_64 slices, and codesignature, then rebuilds it.

CI also enforces that registry.json — the default mawx resolution root — stays in sync with the packages it pins (bun run registry:check). See docs/registry.md.

License

BUSL-1.1 — Business Source License 1.1, converting to Apache-2.0 on the Change Date. See the LICENSE file for the Additional Use Grant.