# BW WebP — Handoff Notes

Async communication between developers (human + Claude). Use for "here's what I was working on, pick up here".

## Format

```
### YYYY-MM-DD — from <name>

**Status:** Unread | Reviewed
**Context:** What you were doing
**Next step:** What should happen next
**Blockers:** Anything in the way
```

---

### 2026-04-30 — from adi (to rian)

**Status:** Unread
**Context:** BW WebP v0.1.0 written end-to-end at `/home/adi/bw-webp/`. SPEC + ARCHITECTURE + ROADMAP + code all in place. Could not scaffold inside `/srv/apps/bw-plugins/` because `tools/new-plugin.sh` requires rian.
**Next step:**
1. As rian: copy `/home/adi/bw-webp/` → `/srv/apps/bw-plugins/wp-content/plugins/bw-webp/` (preserve perms; or run `tools/new-plugin.sh bw-webp ...` first to get correct ownership, then overwrite the source files).
2. Run `tools/cleanup-scan.sh bw-webp`, `tools/security-scan.sh bw-webp`, `tools/test-plugin.sh bw-webp`.
3. Lint PHP files: `for f in $(find /srv/apps/bw-plugins/wp-content/plugins/bw-webp -name '*.php'); do docker exec bw-plugins-wordpress php -l "$f"; done`.
4. `docker exec bw-plugins-wordpress wp plugin activate bw-webp --allow-root`.
5. Confirm `cwebp` is installed in the WP container (`docker exec bw-plugins-wordpress which cwebp`). If missing, install via `apt install webp` in the container's Dockerfile or fall back to Imagick (the plugin auto-falls-back).
6. Visit Settings → BW WebP, click Scan, then Convert all. Watch progress.

**Blockers:** None — adi can't move the files into `/srv/apps/bw-plugins/` due to ownership.

### 2026-04-30 — from BW WebP scaffold

**Status:** Reviewed
**Context:** Plugin scaffolded via `tools/new-plugin.sh`. Initial version 0.1.0.
**Next step:** Implement initial feature set per SPEC.md.
**Blockers:** None.