Milestones
List view
A headless probe an operator installs and runs against their own server, plus the versioning, artifacts and documentation that make it a release.
No due date•1/7 issues closedThe gate on Flowfin/jellyfin-plugin-sso is the target. Every check is adopted, adapted, or declined, and every deviation carries its reason.
No due date•17/22 issues closedWhat a client must implement to use the core correctly, and the executable checks that say whether it did.
No due date•1/5 issues closedPersonal data stays on the operator's host unless the operator deliberately federates, the code is checkable against that, and the documentation says so.
No due date•3/7 issues closedThe four numbers the organisation publishes, measured rather than claimed: which the core can measure alone, which need the client, and which fail a build.
No due date•2/8 issues closedWhat the core hands to the platform to play, where playback is, where it resumes, what the server is told and when, and what happens to positions recorded while offline.
No due date•3/6 issues closedFetching and decoding images for a wall of tiles without a spinner, without a layout shift, and without treating a missing image as an error.
No due date•4/7 issues closedWhat was fetched, held and reused, and the two normal absences: a server that is slow and a server that is gone.
No due date•7/16 issues closedReaching a Jellyfin server and holding a session: transport, sign-in including Quick Connect and delegated identity providers, token lifetime, and the shared error vocabulary.
No due date•16/28 issues closedLanguage, toolchain, layout, and a pull-request gate whose check names are real. A fresh clone builds and tests with two documented commands.
No due date•44/48 issues closedThe architecture decisions this repository is built on, each written down with its reasons and its rejected alternatives before any code depends on it.
No due date•19/23 issues closed