Plugin development checklist

Before packaging

• Choose a stable plugin ID and effect/processor IDs; these identifiers are persisted with projects.
• Keep executable registration code in the entrypoint declared by plugin.json.
• Define explicit processor types: video, audio, generator or timeline processor. The 1.1 editor UI update does not merge them.
• Validate parameters and return the documented processor result shapes. Keep expensive or blocking operations outside the paint loop.
• Use host-owned native controls where possible. For custom windows, specify PluginWindowOptions only when overriding the shared default size or styling.
• Check your plugin ZIP installs with the 1.1 Plugin Manager and renders correctly on a real project.
• Confirm a failed import or processor exception is reported in Debug Log instead of crashing the editor.

Compatibility note

The 1.1 Plugin API keeps the 1.0 processor and registration contracts. The default PluginWindowOptions styling now uses the shared editor constants (WINDOW_HEADER_HEIGHT, WINDOW_RADIUS) rather than hardcoded per-plugin defaults. Test custom-drawn title bars if your plugin relies on pixel-exact measurements.