Milestones
List view
Security and quality alerts are worked before anything else; every open alert is one issue here (rule of 2026-09-05, fleet-wide since 2026-09-06).
No due date•1/2 issues closedStep eight. A reproducible build, a container that produces it, an artifact an operator can serve, and the plan for the domain.
No due date•11/16 issues closedStep seven. What the site collects, what it sends, and where personal data goes.
No due date•7/11 issues closedStep six. The jellyfin-plugin-sso merge gate as the target, item by item, with a written reason for every deviation.
No due date•29/33 issues closedStep five. The budget as numbers a build can miss, accessibility as a gate, and the separate harness for what cannot be judged without a live site.
No due date•8/14 issues closedStep four. Landing, install, one page per plugin, the design system, and the checks that keep the links and the markup honest.
No due date•28/33 issues closedStep three. One machine-readable roster, read by the build, cross-checked against what is actually published.
No due date•13/16 issues closedStep two. Language, toolchain, repository layout, the build verb, the test harness, the rule that every test runs without a display and without elevation, and the checks under the names a ruleset can require.
No due date•41/44 issues closedStep one. The questions that shape everything else, answered in writing with their reasons, before any code depends on them.
No due date•16/18 issues closed