docs: --test flag, and confirm hand-editing config.yaml still works
CLI Usage gains --test with its exit-code table. The codes are the reason
anyone would script this, so they are documented as three distinct meanings
rather than pass/fail: a config that will not parse is a different problem
from a service that will not answer.
Troubleshooting gains a short answer to a question the config cache will
otherwise cause someone to ask: yes, editing config.yaml by hand still takes
effect immediately. The cache revalidates against the file on every read.
Worth stating where a worried person will look, not only in the changelog.
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.