docs: replacement outcome tracking
Documented on the Prowlarr scoring page rather than with quarantine and
severity: the point of this feature is what it tells you about an indexer,
which is why the UI puts it on the Indexers Stats tab too.
Leads with the distinction that motivates it -- an indexer whose mistakes get
replaced cleanly versus one whose mistakes are never replaced at all, which
the health score cannot separate -- rather than with the mechanism.
Also records why Lidarr is excluded, since 'unsupported for one app only'
invites someone to just switch it on. The reason is that each app needs a
different history endpoint and the wrong one returns HTTP 200 with unfiltered
data rather than an error, so guessing is silently destructive here.
docs: operating modes
Documented on Quarantine-and-Severity rather than as a new page. Modes,
severity and quarantine are three layers of one question -- what happens when
a rule matches -- and splitting the answer across two pages would mean the
reader has to find both to understand either. The mode goes first because it
is the coarsest control: someone running Monitor does not need to read about
severity bands at all.
Covers the ceiling semantics explicitly (it does not rewrite your thresholds,
and can only ever reduce an outcome), why the banner exists, that Monitor and
--dry-run are the same behaviour with the flag winning, and how to tell
below_severity_floor apart from capped_by_operating_mode when working out why
something was not deleted.
Configuration gains the key in both the YAML sample and the reference table.
Sidebar renamed so someone looking for modes can find them.
Also fixed a self-link: the Quarantine review queue is a page in the web UI,
not a wiki page, and this document was linking to itself for it.
docs: document the AI master switch
Follows 4916959 / 44473b5, which added an Enable AI features toggle to
Settings -> AI and made it the single control for every AI feature.
AI-and-Model-Validation
New "The master switch" section up front: what stops when it is off, that
no Ollama request is made at all, and that turning it off erases nothing --
URL, model and system prompt stay on disk so switching back on restores
what you had. Notes the upgrade behaviour: an install that already had a
working URL stays enabled, only new installs start off.
Removed "Leave the Ollama URL blank and everything else works unchanged" --
that advice predates the switch and is now the wrong way to do it.
Configuration Added ollama.enabled to the example and the key table,
including the upgrade behaviour. Reworded the Ollama intro,
which said "when configured" and now also means "when
enabled".
FAQ "Do I need Ollama" now says it ships off and names the
switch, instead of telling readers to blank the URL.
Home AI scoring is called out as off by default.
Web-UI The AI pane row leads with the master switch.
Verified: no stale "leave the URL blank" phrasing remains anywhere, all 86
internal links across 17 pages resolve, every file is valid UTF-8.
docs: bring the wiki up to date and add navigation
Structural
_Sidebar.md persistent navigation on every page, grouped getting-started /
how-it-works / using-it / help. GitHub renders this alongside
every page; without it readers had to return to Home to get
anywhere, and Home's hand-maintained index had already drifted
out of sync with the actual filenames.
_Footer.md repo / releases / issues links on every page.
New pages
Quarantine-and-Severity severity grading, the three bands, the review
queue and its three outcomes, timeouts. This was
previously undocumented and would otherwise have
been split across three pages.
AI-and-Model-Validation Ollama setup, the three validation tests, the
gate and the forced state, context requirements.
AI content had been scattered across
Configuration, Prowlarr scoring and Notifications.
API /api/health, /api/status, /api/scan, /api/logs.
The JSON API existed and was entirely
undocumented; Home did not mention it at all.
Fixed
Home [Docker](Docker) and [CLI](CLI) were broken -- no such
pages; the files are Installation and CLI-Usage. Rewritten
with a task-ordered getting-started path, corrected
Pushover -> Apprise (stale since v1.5), and a features list
that reflects quarantine, severity and model validation.
Detection The action sequence went straight from match to delete. It
now documents grading, the three bands, the evidence trail
and correlation IDs, and the client-delete failure path.
Also corrected Pushover -> Apprise.
Web-UI Added Quarantine and Settings -> AI. Corrected the Settings
pane list, which named panes that do not exist and omitted
several that do. Stats is a tab in the Indexers hub, not a
page, since v1.6.0.
Configuration Added the remediation block. Completed the ollama table --
system_prompt and update_check_hours were missing -- and
noted the measured context requirement.
Notifications Added the quarantine event and its fallback to `action`.
Noted that the Ollama toggles are gated on AI being set up.
FAQ "Will it delete good torrents" now covers quarantine. Added
two questions: whether AI is required (it is not) and how
to check a model before relying on it.
Troubleshooting Deleted-good-torrent now explains how to trace it via the
inspection record and three ways to prevent a repeat. Added
stuck-in-quarantine, nothing-ever-quarantined, and Ollama
returning nonsense.
CLI-Usage --daemon also sweeps quarantine timeouts.
Installation Re-encoded from CP1252 to UTF-8. It held 22 non-ASCII bytes
that GitHub renders as mojibake.
Verified: all 86 internal links across 17 pages resolve, and every page is
reachable from the sidebar.
docs: update notifications to Apprise, add multi-client torrent support
wiki: update all pages for v1.4.0 features
Update wiki: v2 scoring formula, model selector, tasks/updates/backups pages, daemon mode, PUID/PGID, dev container
docs: add Ollama AI scoring documentation