P1.3: Version markers: apiVersion/schemaVersion in /api/status + /internal/engine-config; schema_version table

[genwave-radio]

Migrated from the pre-publish internal tracker (gitea-#248, opened 2026-07-16).

📄 Plugin-readiness session 2026-07-16 — docs/architecture/roadmap.md item P1.3 (gap: M5, M6). ADR-0001 accepted (D1 in-process compile-time, D4 db-per-tenant lean).

Evidence: No API/protocol versioning anywhere; no schema-version table (migrations are hand-idempotent bash re-run every launch).

What: Markers only, not a compatibility regime: {apiVersion, schemaVersion} in the two status surfaces; schema_version row stamped by each migration script (D5).

Size: S

What breaks if deferred: Fleet tooling can't detect drift; mixed-version debugging is blind.

[genwave-radio]

Re-graded P1 → P2 (2026-09-22). "P1.3" in the title is the 2026-07-16 roadmap item number, not a severity; the label was carried over from it. Size S, still on the pre-launch ship list (row 4, first-day defects).

[genwave-radio]

Shipped in v5.14.0 (F211). Demo: /api/status version = {app: v5.14.0, build: 5.14.0, schema: {expected: 49, applied: 49}}; journal 48/48 rows stamped v5.14.0; engine logs GW_APP_VERSION=v5.14.0.