# BW AI Schema Pro — 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-07-22 — from adi + Claude (2.4.0 Accommodations module)

**Status:** Unread
**Context:** Built the Rooms/Accommodations module for resort clients — room-level
`HotelRoom`/`Suite` schema wired into the property Organization via
`containsPlace[]`. Staged at 2.4.0, scans clean, verified end-to-end on the dev
site. Spec: `docs/SPEC-accommodations.md`; full detail in `docs/SESSION-LOG.md`.
**Next step:** Two things need someone with docker access (i.e. rian):
1. Run `tools/test-plugin.sh bw-ai-schema-pro` — this session couldn't; its lint
   step needs docker and reports false syntax errors for every file without it.
2. **Release decision.** Not made. ~8 production customer sites; nobody has asked
   for this module yet, so there's no rush to push it to them.
**Blockers:** None for the code. Worth deciding before a client build: whether
multi-property (a Resort CPT + room→resort relation) is needed soon, since that's
the one deferred piece that would change the data model rather than just add to it.

### 2026-05-06 — from rian + Claude (import session)

**Status:** Unread
**Context:** Imported the plugin source from `/srv/apps/bwgeo/wp-content/plugins/bw-ai-schema-pro/` into the bw-plugins framework. Source files copied verbatim — no functional changes. Scaffolded the BW meta files (CHANGELOG, README, LICENSE, uninstall, CLAUDE.md, docs/). Documented the prefix-mismatch grandfathering and the rename intent in `docs/ROADMAP.md` and `docs/KNOWN-ISSUES.md`.
**Next step:** Pick *one* of these as the next concrete action:
1. Run the BW scans (`cleanup-scan.sh`, `security-scan.sh`, `test-plugin.sh`) to surface real issues. Expect `test-plugin.sh` to fail on the version-constant check until that's resolved.
2. Decide how to resolve the version-constant mismatch (compat shim vs. tooling override — see KNOWN-ISSUES.md).
3. Plan the update-server flip release (2.1.4) — register the plugin in `bw-update-server`, build the URL-flip release from the legacy bwgeo server.
4. Start filling in `docs/ARCHITECTURE.md` "Data Storage" — needed before the 3.0.0 prefix-rename migration can be designed.
**Blockers:** Rename target slug not yet decided (rian wants to rename but doesn't have a good name). Doesn't block the import work — only the 3.0.0 prefix conformance.