0.5.0

The package is now @feralfile/display (npm i @feralfile/display). The button reads Display on Art Computer, and pairing and casting go over relay v2 with a display grant the Art Computer issues. @feralfile/play stops at 0.4.0 and is deprecated on npm with a pointer here.

Renamed. Change the dependency and the import specifier. The Play names stay as deprecated aliases through 0.5.x and go in 0.6.0: mountPlayOnArtComputerButton → mountDisplayOnArtComputerButton, PlayOnArtComputerButtonOptions/Handle → DisplayOnArtComputerButton…, PlayError/PlayErrorCode → DisplayError/DisplayErrorCode (the same class, so instanceof PlayError still matches), and the CSS classes ff-ac-play* → ff-ac-display* (the button carries both). The default dialog title is "Display on your Art Computer". The messages that said press play now say try again, and an error's name is "DisplayError". Match on code, which is unchanged. buttonLabel and dialog.copy overrides work as before. The self-hosted bundle is display.js; this release also attaches play.js.

Breaking (relay v2, display grant): there is no relayer token, no /api/cast and no relayerBaseUrl. The grant and its keys live in IndexedDB (the database keeps the name ff-play, so stored grants survive the rename). hasStoredEphemeralBrowserSession, readStoredEphemeralBrowserSession and clearStoredEphemeralBrowserSession are async and take only the origin. DisplayDp1PlaylistOptions gains socketFactory and timeoutMs. Stored 0.4 sessions are removed on first use, so each visitor pairs once more. 0.5 needs an Art Computer on FF OS with display grants; older firmware fails with device_unsupported. Full list: "Upgrading from 0.4.x" in clients/session-recipient/js/README.md.

Adopt when FF OS 3.0.0 is broadly deployed. 0.5 needs an Art Computer on FF OS 3.0.0 (display grants); 3.0.0 is at staging and no fielded FF1 runs it yet, so integrators stay on @feralfile/play 0.4.0 until then (ffos-user#430, feral-file#3551). The deprecation on 0.4.0 is lifted.