# BW AI Schema Pro — Known Issues

**Last Updated:** 2026-05-06

Track active bugs, limitations, and workarounds here. Resolved issues should be moved to the CHANGELOG under the version that fixed them.

## Active

### Update URI flipped from bwgeo to plugins.bowden.works — RESOLVED in 2.1.4 (2026-05-06)
**Resolution:** Shipped 2.1.4 from the legacy bwgeo server with the new `Update URI` header and the update-checker URL pointed at `https://plugins.bowden.works/wp-json/bw/v1/update-check?slug=bw-ai-schema-pro`. Customer sites will pick up 2.1.4 from bwgeo on their next update poll, then future polls go to the new server.
**Watch:** `/srv/apps/bwgeo/wp-content/uploads/plugin-updates/update-log.json` — sites running 2.1.4 will show `installed_version: 2.1.4`. Once all 16 sites have flipped (~1–2 weeks), the legacy bwgeo distribution can be retired.

### Version constant naming mismatch — RESOLVED via in-plugin shim (2026-05-06)
**Detail:** BW tooling (`tools/bump-version.sh`, `tools/test-plugin.sh`) derives the version constant name from the plugin slug: for `bw-ai-schema-pro` it expects `BW_AI_SCHEMA_PRO_VERSION`. This plugin's grandfathered `BW_SCHEMA_VERSION` doesn't match.
**Resolution:** Added a one-line compat alias in `bw-ai-schema-pro.php` next to the existing constant:
```php
define( 'BW_AI_SCHEMA_PRO_VERSION', BW_SCHEMA_VERSION );
```
BW tooling now sees the expected constant; plugin internals continue using `BW_SCHEMA_VERSION`. The shim lives entirely inside this plugin — no changes to shared `tools/` or `docs/CLAUDE-STANDARDS.md`. Sunsets at the 3.0.0 rename (see ROADMAP.md).

### `bw_schema_*` prefix doesn't match BW slug-derived standard
**Severity:** Documentation/discoverability only — not a functional bug.
**Detail:** BW standard says prefix `bw_<slug_underscore>_` for hooks/options/meta. This plugin uses `bw_schema_*` instead of `bw_ai_schema_pro_*`. This is **deliberately grandfathered** — see `CLAUDE.md` and `docs/ROADMAP.md`. New code in this plugin should keep using `bw_schema_*` for internal consistency until the planned rename.

### Class file names don't match BW pattern
**Severity:** Documentation/discoverability only.
**Detail:** Files in `includes/` are `class-bw-schema-*.php` instead of `class-bw-ai-schema-pro-*.php`. Same root cause as the prefix issue; same grandfather treatment.

### Sparse `docs/SPEC.md` and `docs/ARCHITECTURE.md`
**Severity:** Tech-debt.
**Detail:** Imported plugin had no spec or architecture docs. The current docs are stubs. They should be filled in by reading the code; until then, contributors fall back on reading source. The "Data Storage" inventory in ARCHITECTURE.md is required before the 3.0.0 rename can write its data migration.

### CHANGELOG history pre-2.1.3 not captured
**Severity:** Cosmetic.
**Detail:** The plugin's release history before the 2026-05-06 import isn't in CHANGELOG.md. If we want it, it would need to be reconstructed from the legacy bwgeo `update-log.json` and any prior changelog notes.

## Resolved

(see CHANGELOG.md)