Historical firmware compatibility

Existing devices

Older V1-family framing and historical SDKs remain in the backend/research archive. Customer devices were not queried or changed in production during this overhaul, so active legacy usage is unknown. Local schema and gateway tests preserve compatibility.

Existing firmware tooling is available at /dashboard/compatibility for existing devices with published historical layouts, including during migration. Enroll through Schema, publish an unused slot, download and validate new firmware, then rotate/revoke prior Secure V2 credentials as appropriate. Enrollment alone does not revoke a legacy credential. Coordinate legacy retirement explicitly; do not assume encryption settings can migrate firmware automatically.

Legacy fleet profiles/bulk registration are not Secure V2 enrollment. They are separated from the normal new-device flow; Secure V2 fleet bulk provisioning remains future work. Historical Protocol Lab records are preserved and clearly labeled.