wao 0.41.3 → 0.41.5

package/esm/workspace/.claude/skills/test-device/SKILL.md

@@ -1,114 +0,0 @@
----
-name: test-device
-description: "Test HyperBEAM Erlang devices with WAO SDK integration tests. Launches real HyperBEAM and tests device via HTTP. Use when user says 'test the device', 'run device tests', or 'verify the Erlang module'. Not for eunit — use /build-device."
-argument-hint: "<task-id>"
-disable-model-invocation: true
-allowed-tools: Read, Write, Edit, Bash, Grep, Glob
----
-
-Write and run WAO SDK integration tests for HyperBEAM Erlang devices. Launches a real HyperBEAM node and tests devices via HTTP.
-
-## Resolve HyperBEAM path
-
-Read `.env.hyperbeam` and extract the `CWD` value:
-
-```bash
-grep '^CWD=' .env.hyperbeam 2>/dev/null | cut -d= -f2-
-```
-
-If `.env.hyperbeam` doesn't exist or has no `CWD`, **STOP immediately** and tell the user:
-
-> No HyperBEAM configured. Device integration tests require a HyperBEAM installation.
->
-> Set it up by adding a `CWD` entry to `.env.hyperbeam`:
-> ```bash
-> echo "CWD=/path/to/your/HyperBEAM" >> .env.hyperbeam
-> ```
-
-Then verify the directory exists:
-
-```bash
-test -d "$HB_DIR/src" && echo "HyperBEAM: OK" || echo "HyperBEAM: MISSING"
-```
-
-If `MISSING`, stop and tell the user the path in `.env.hyperbeam` is invalid.
-
-Do NOT mark the task as done. Set the task status to `"pending"` and stop.
-
-## Steps
-
-1. Read `tasks.json` and find the task matching `$ARGUMENTS` (task id). Update its status to `"in_progress"`.
-
-2. Kill stale HyperBEAM processes:
-
-   ```bash
-   pkill -f beam.smp 2>/dev/null || true
-   ```
-
-3. Read `docs/wao-sdk.md` for HB class patterns (spawn, schedule, compute).
-
-4. **Write integration tests** in `test/{name}-device.test.js`:
-
-   The `HyperBEAM` class reads `.env.hyperbeam` automatically via `dotenv`, so it will find the correct `CWD`. No need to pass it manually.
-
-   ```js
-   import { describe, it, before, after } from "node:test"
-   import assert from "node:assert"
-   import { HB, HyperBEAM, acc } from "wao/test"
-
-   describe("{name} device integration", () => {
-     let hbeam, hb
-
-     before(async () => {
-       hbeam = await new HyperBEAM({ reset: true }).ready()
-       hb = hbeam.hb
-     })
-
-     after(async () => {
-       if (hbeam) await hbeam.kill()
-     })
-
-     it("should spawn process with device", async () => {
-       const { id } = await hb.spawn({
-         "execution-device": "dev_{name}@1.0",
-       })
-       assert.ok(id)
-     })
-
-     it("should handle action via device", async () => {
-       const { id } = await hb.spawn({
-         "execution-device": "dev_{name}@1.0",
-       })
-       const result = await hb.schedule({
-         process: id,
-         action: "MyAction",
-         tags: { /* ... */ },
-       })
-       assert.ok(result)
-     })
-
-     // Test all device operations:
-     // - Spawn with device
-     // - Each exported action
-     // - Error handling (invalid action, bad input)
-     // - State persistence across messages
-     // - Device stacks (if applicable)
-   })
-   ```
-
-5. Run the tests:
-
-   ```bash
-   yarn test test/{name}-device.test.js
-   ```
-
-6. If any tests fail:
-   - Read the error output
-   - Check if HyperBEAM started correctly
-   - Fix the test or device code
-   - Kill stale processes and re-run
-   - Repeat until **100% pass**
-
-7. Always ensure HyperBEAM is killed after tests (check `after()` hook).
-
-8. Update the task status to `"done"` in `tasks.json`.

package/esm/workspace/.claude/skills/test-e2e/SKILL.md

@@ -1,103 +0,0 @@
----
-name: test-e2e
-description: "Playwright E2E tests with live HyperBEAM backend. Launches HB via WAO SDK, runs browser tests. Use when user says 'run E2E tests', 'test the frontend', or 'browser tests'. Not for vitest — use /build-frontend."
-argument-hint: "<task-id>"
-disable-model-invocation: true
-allowed-tools: Read, Write, Edit, Bash, Grep, Glob
----
-
-Write and run Playwright E2E tests with a live HyperBEAM backend. Tests full user flows in the browser.
-
-## Steps
-
-0. Check prerequisites:
-```bash
-test -d frontend/e2e && echo "OK" || echo "ERROR: No e2e/ directory"
-cd frontend && npx playwright --version 2>/dev/null || echo "ERROR: Playwright not installed"
-```
-If Playwright is missing: `cd frontend && npx playwright install`
-
-1. Read `tasks.json` and find the task matching `$ARGUMENTS` (task id). Update its status to `"in_progress"`.
-
-2. Kill stale HyperBEAM processes:
-
-   ```bash
-   pkill -f beam.smp 2>/dev/null || true
-   ```
-
-3. **Write Playwright tests** in `frontend/e2e/`:
-
-   ```js
-   import { test, expect } from "@playwright/test"
-
-   test.describe("{feature} E2E", () => {
-     test("full user flow", async ({ page }) => {
-       await page.goto("http://localhost:5173")
-
-       // Wait for app to load
-       await expect(page.locator("h1")).toBeVisible()
-
-       // Test wallet connection flow
-       // (mock ArConnect via page.addInitScript if needed)
-
-       // Test process interaction
-       // - Fill form inputs
-       // - Click submit
-       // - Wait for response from AO process
-       // - Verify UI updates
-
-       // Test error states
-       // - Network failure
-       // - Invalid input
-     })
-   })
-   ```
-
-4. **Write global setup** if needed for HyperBEAM lifecycle:
-
-   ```js
-   // frontend/e2e/global-setup.js
-   import { HyperBEAM } from "wao/test"
-
-   let hbeam
-
-   export default async function globalSetup() {
-     hbeam = await new HyperBEAM({ reset: true }).ready()
-     process.env.HYPERBEAM_URL = hbeam.url
-   }
-
-   export async function globalTeardown() {
-     if (hbeam) await hbeam.kill()
-   }
-   ```
-
-   Reference in `frontend/playwright.config.js`:
-   ```js
-   export default {
-     globalSetup: "./e2e/global-setup.js",
-     globalTeardown: "./e2e/global-setup.js",
-     use: { baseURL: "http://localhost:5173" },
-   }
-   ```
-
-5. Ensure the Vite dev server is running (or start it):
-
-   ```bash
-   cd frontend && npm run dev &
-   ```
-
-6. Run E2E tests:
-
-   ```bash
-   cd frontend && npx playwright test
-   ```
-
-7. If any tests fail:
-   - Read the error output and screenshots (if any)
-   - Fix the test or frontend code
-   - Re-run
-   - Repeat until **100% pass**
-
-8. Kill the Vite dev server and HyperBEAM after tests.
-
-9. Update the task status to `"done"` in `tasks.json`.

package/esm/workspace/.claude/skills/test-hb/SKILL.md

@@ -1,76 +0,0 @@
----
-name: test-hb
-description: "Run HyperBEAM integration tests. Starts a local Erlang HyperBEAM node and tests AOS processes on the full production stack. Use when user says 'test on HyperBEAM', 'run integration tests', or 'test the full stack'. Not for in-memory tests — use /test."
-argument-hint: "[test-file]"
-disable-model-invocation: true
-allowed-tools: Bash, Read, Grep
----
-
-Run HyperBEAM integration tests. These spawn a real Erlang node — different from in-memory AOS tests (`/test`).
-
-## Steps
-
-1. Kill any stale HyperBEAM / beam.smp processes:
-
-```bash
-lsof -ti :10000-10010 | xargs -r kill -9 2>/dev/null || true
-pkill -f beam.smp 2>/dev/null || true
-```
-
-2. Check that HyperBEAM is configured via `.env.hyperbeam`:
-
-```bash
-grep '^CWD=' .env.hyperbeam 2>/dev/null | cut -d= -f2-
-```
-
-If `.env.hyperbeam` doesn't exist or has no `CWD`, **STOP** and tell the user:
-
-> No HyperBEAM configured. Integration tests require a HyperBEAM installation.
->
-> During project creation (`npx wao create`), choose option 1 (clone) or 2 (link).
-> Or configure it now:
-> ```bash
-> echo "CWD=/path/to/your/HyperBEAM" >> .env.hyperbeam
-> ```
-
-Then verify the path exists:
-
-```bash
-HB_DIR=$(grep '^CWD=' .env.hyperbeam | cut -d= -f2-)
-test -d "$HB_DIR/src" && echo "HyperBEAM: OK" || echo "HyperBEAM: MISSING"
-```
-
-If `MISSING`, stop and tell the user the CWD path in `.env.hyperbeam` is invalid.
-
-3. Run the tests:
-
-```bash
-# Specific file (if argument provided)
-yarn test $ARGUMENTS
-
-# Default HyperBEAM tests
-yarn test test/hyperbeam.test.js
-```
-
-The `HyperBEAM` class reads `.env.hyperbeam` automatically via `dotenv`, so it picks up the correct `CWD`.
-
-4. Report results:
-   - Show pass/fail count
-   - If HyperBEAM fails to start, check Erlang/OTP is installed (`erl -eval 'halt().'`)
-   - If port conflicts, suggest running `/test-hb` again (it cleans up first)
-   - Always ensure HyperBEAM process was killed after tests
-
-## Troubleshooting
-
-### HyperBEAM fails to start
-- Check Erlang is installed: `erl -eval 'halt().'`
-- Requires Erlang/OTP 27+
-- Check `.env.hyperbeam` CWD path is valid
-
-### Port already in use after cleanup
-- Wait 2-3 seconds for port release, then retry
-- Check for zombie processes: `ps aux | grep beam`
-
-### Tests pass locally but fail in CI
-- CI may lack Erlang — skip HB tests with env flag
-- Ensure HyperBEAM binary is cached in CI

package/esm/workspace/.claude/skills/validate/SKILL.md

@@ -1,96 +0,0 @@
----
-name: validate
-description: "Post-build validation. Runs tests, checks Lua pitfalls, verifies AOS script coverage, and reports results. Use after building, before deploying, or when user says 'check everything', 'are tests passing', or 'validate'."
-argument-hint: "[test-file]"
-disable-model-invocation: true
-allowed-tools: Bash, Read, Grep, Glob
----
-
-Run post-build validation to verify code quality before declaring a task done.
-
-## Steps
-
-### Gate 1: Unit tests
-
-Run in-memory AOS tests (mainnet WASM device):
-
-```bash
-yarn test $ARGUMENTS 2>&1
-```
-
-If `$ARGUMENTS` is empty, run the full suite: `yarn test`
-
-If any tests fail, report the failures and stop. Do not proceed until all tests pass.
-
-### Gate 2: HyperBEAM integration
-
-If `HyperBEAM/` directory exists and Erlang is available:
-
-```bash
-yarn test test/hyperbeam.test.js 2>&1
-```
-
-Skip this gate if HyperBEAM is not set up. Report "skipped (no HyperBEAM)" in the summary.
-
-### Gate 3: Custom module tests
-
-If `custom-lua/` or `custom-wasm/` directory exists and has module files:
-
-```bash
-ls test/*-module.test.js 2>/dev/null && yarn test test/*-module.test.js 2>&1
-```
-
-Skip this gate if no custom modules. Report "skipped (no custom modules)" in the summary.
-
-### Gate 4: Frontend tests
-
-If `frontend/` directory exists:
-
-```bash
-cd frontend && npm run test:unit 2>&1
-```
-
-Skip this gate if no frontend. Report "skipped (no frontend)" in the summary.
-
-### Lua pitfalls
-
-Run the validation script:
-```bash
-bash .claude/skills/validate/scripts/check-lua.sh
-```
-If the script reports issues, fix them before proceeding.
-
-The script checks for:
-- `Send().receive()` — broken on genesis-wasm
-- Lowercase Action tags in `Handlers.add`
-- `bint()` without `require('.bint')`
-- `json.encode`/`json.decode` without `require('json')`
-
-4. Verify AOS script coverage:
-
-   - List all `Handlers.add` calls in `src/*.lua`
-   - List all test files in `test/*.test.js`
-   - For each script, check that at least one test sends a message with that action
-   - Report any AOS scripts without test coverage
-
-5. Check for uncaught error paths:
-
-   - Scripts that read `msg.Tags.*` without nil checks
-   - Scripts that use `bint()` on potentially nil values
-   - Scripts that modify state without validation
-
-6. Report a summary:
-
-```
-## Validation Results
-
-Gate 1 — Unit tests:        X passed, Y failed
-Gate 2 — HyperBEAM:         PASS / FAIL / skipped (no HyperBEAM)
-Gate 3 — Custom modules:    PASS / FAIL / skipped (no custom modules)
-Gate 4 — Frontend tests:    PASS / FAIL / skipped (no frontend)
-Lua pitfalls:                none found (or list issues)
-AOS script coverage:         X/Y AOS scripts have tests
-Uncaught errors:             none found (or list issues)
-
-Overall: PASS / FAIL
-```

package/esm/workspace/.claude/skills/validate/scripts/check-lua.sh

@@ -1,41 +0,0 @@
-#!/bin/bash
-# Programmatic Lua pitfall checker for AOS scripts in src/
-# Run: bash .claude/skills/validate/scripts/check-lua.sh
-
-ERRORS=0
-
-for f in src/*.lua; do
-  [ -f "$f" ] || continue
-
-  # Check Send().receive() — broken on genesis-wasm
-  if grep -n 'Send(.*).receive()' "$f"; then
-    echo "ERROR: $f uses Send().receive() — broken on genesis-wasm"
-    ERRORS=$((ERRORS + 1))
-  fi
-
-  # Check lowercase action in Handlers.add
-  if grep -nP 'Handlers\.add\([^,]+,\s*"[a-z]' "$f"; then
-    echo "WARNING: $f may have lowercase Action tag"
-    ERRORS=$((ERRORS + 1))
-  fi
-
-  # Check bint without require
-  if grep -q 'bint(' "$f" && ! grep -q "require.*bint" "$f"; then
-    echo "ERROR: $f uses bint() without require('.bint')"
-    ERRORS=$((ERRORS + 1))
-  fi
-
-  # Check json without require
-  if grep -qE 'json\.(encode|decode)' "$f" && ! grep -q "require.*json" "$f"; then
-    echo "ERROR: $f uses json without require('json')"
-    ERRORS=$((ERRORS + 1))
-  fi
-done
-
-echo "---"
-if [ $ERRORS -eq 0 ]; then
-  echo "Lua pitfall check: PASS (0 issues)"
-else
-  echo "Lua pitfall check: FAIL ($ERRORS issues)"
-  exit 1
-fi