Say what the managed-provider freeze shows when the report cannot be read [#1599]
Say on every page that names the settings surface that the 5.0 line has five tabs [#1574]
Publish the config-as-code reference [#1116]
A docker-first administrator had to read the loader source to stand up a
GitOps-managed provider. The page covers the document and where to get a correct
one, a working example, the same example as environment variables with the four
rules that refuse a source whole, the precedence table, the two secret reference
forms with the compose snippet, what a refusal looks like and that the stored
configuration survives it, and what the settings page shows for a managed
provider.
The text is the draft agreed on the issue, with its settings-page section
replaced by the one written after #1415 and #1416 landed the read-only
rendering. Every load-bearing claim was re-checked against origin/main bf99b374
rather than carried from the draft: the JELLYFIN_SSO_CONFIG__ prefix, the
FormatVersion, the two-member declared surface and the refusal naming it, the
Env and File suffixes, the trim on a referenced file, and the refusal of an
inline secret and of both forms on one field.
Linked from the sidebar beside the options reference, which is the page it
defers to for what each field does, so this one describes the sources and not
the fields.
Signed-off-by: Nils Lehnen <30603423+iderex@users.noreply.github.com>