JSON/config parity (JSON view, export template, CLI panes)

Azure's declarative-config surfaces: the Essentials "JSON View" panel, ARM/Bicep export-template blade, and CLI/Cloud Shell panes.

Why not

Those exist because Azure resources are declarative JSON documents managed by ARM — viewing/exporting the config is the product. Our resources are app content (rows, surveys, canvases) with no config representation a user would act on; a raw row/blob dump serves nobody but a developer with DB access, who already has better tools.

Generic cross-product event bus

Rejected — a platform-wide event bus (topic registry, product subscribers) for cross-product reactions.

Offline editing

Rejected — PWA-style offline resource editing with sync-on-reconnect.