docs: correct the pinned image tag
The release workflow strips the v, so the image is :2.0.0 while the git tag
is v2.0.0. Verified against the registry rather than inferred -- anyone
following the previous table would have hit manifest-unknown on their first
pin.
docs: v2.0.0
Home leads with an upgrade section, because the single most useful thing to
tell someone already running v1.6 is that nothing changes until they change
it. The three settings actually worth turning on are named in one table
rather than left to be discovered across four pages.
Installation names the image tags properly -- :latest, a pinned :v2.0.0, and
:dev -- and says why you might pin: so upgrades are a deliberate act rather
than a side effect of docker compose pull.
Detection & Actions gained a pointer to operating modes at the end. Everything
on that page describes Automatic mode, which was true and unstated; a reader
following it in Monitor mode would have watched nothing happen and had no
idea why.
Home's feature list gained operating modes and replacement tracking, which
shipped after the page was last written.
docs: repair the Docker compose example in Installation
Two paragraphs had been pasted inside the YAML fence, between
`environment:` and its `- TZ=America/New_York` value. Anyone who copied
that block got a compose file with a dangling `environment:` key and two
sentences of English where the value should be -- it does not parse, and the
error it produces points at the environment key rather than at the prose, so
it is not obvious what went wrong.
The prose is correct and worth keeping; it now sits after the closing fence
where it was meant to be.
Also in this file:
- seven em dashes were double-encoded (`a-EUR-`), left over from a
UTF-8 payload that was decoded as cp1252 somewhere upstream. This page
was the only one affected; every other page checked clean.
- line endings normalised to LF, matching the rest of the wiki. The file
had CRLF throughout, which made every diff against it show the whole
file as changed and hid real edits.
- the persistent-data table now names the tables added since v1.6.0
(inspections, quarantine holds, model validation results) rather than
stopping at grab attribution.
No content was rewritten beyond the compose block.
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.
Update wiki: v2 scoring formula, model selector, tasks/updates/backups pages, daemon mode, PUID/PGID, dev container