Commands and Functions

This is the primary human-readable index of what can be scripted. It exists so future contributors do not have to infer command names, argument shapes, or allowed behaviors from code alone.

Command Surface Principles

• Commands must drive the canonical render pipeline instead of bypassing it.
• Arguments must be explicit, stable, serializable, and documented.
• Visible labels are not command identifiers. Use stable keys and function names instead.
• Every command that changes rendering must be reproducible from the same input state.

Core Command Families

State and content

• loadPlaylist(...) / setPlaylistText(...)
• setCurrentItem(...)
• setThumbnailSource(...)
• setUrlArt(...)
• setQrState(...)

Layout and panel behavior

• setFitMode(...) for accepted modes such as fit height or fit everything
• setHeaderTextVisible(...)
• setGridOrSliderBehavior(...) where a build exposes such controls
• setSafeArea(...), setOverlayVisibility(...), setPanelAspect(...)

Render and export

• renderPanel(...)
• exportPanel(...)
• exportThumbnail(...)
• setExportResolution(...)
• setExportFormat(...)

Argument Expectations

• Use explicit mode names instead of vague values such as “auto” when a behavior materially affects output.
• Resolution arguments should refer to final output size, not screen size.
• Localization-facing arguments should use keys, not raw English labels.
• Feature flags and experimental controls must be documented before they are considered stable.

Example Flow

loadPlaylist(text)
setCurrentItem(itemId)
setThumbnailSource({ mode: "url-art" })
setQrState({ visible: true, content: itemUrl })
setExportResolution("8192x4320")
renderPanel()
exportThumbnail({ format: "png", qualityMode: "master" })