Links in tables: [Text](Page) instead of [[Text|Page]] GitHub reads the | of a wiki link inside a table cell as a column separator, so every link in a table rendered as raw [[Text text.
Wiki for 4.4: RSS, download order, queue and share limits, managed WireGuard, Prometheus metrics; Known Limitations re-checked against the code Every page re-verified against v4.4.0 (EN and FR). New pages: Managed-WireGuard, RSS-and-Automatic-Downloads, Queue-Share-and-Speed-Limits, Prometheus-Metrics. Known-Limitations: 79 rows fixed in 4.4 moved to a Fixed in 4.4 section.
Categories: a category routes on its mode; placement and strategy are not applied The page described placement, strategies (all, least_torrents) and per-agent save paths as working. No 4.x release reads them: the engine comes from the category's mode (or an explicit engine at add), the path from the category (or an explicit path), and an add with neither is refused. Rewritten EN+FR to say so, with the old fields called out as accepted but ignored. Mentions of placement elsewhere follow.
Punctuate like a human: commas, not hyphens Replacing the em dashes with a spaced hyphen swapped one tic for another. Nobody writes that. Prose gets a comma, an aside that interrupts a sentence gets parentheses, and a heading that names a thing then explains it gets a colon.
Style pass: no warning emoji, fewer verbal tics Same house style as the UI. The six warning emoji are gone: the bold lead-in already says it is a warning, so the icon was decoration. Trims the words that read as filler once you notice them - deliberately, on purpose, by construction, simply, note that, under the hood. Where the intent genuinely is the point the sentence keeps saying so, and the rest just state the fact. The language-switch flags stay: they are the navigation, not decoration.
Drop the em dashes Same house style as the UI: no em dashes. 355 of them across the wiki, most added by this documentation pass. Replaced with a plain hyphen, which is what the surrounding prose and the commit log already use.
Concepts and Architecture: SQLite as the primary source, and jobs Two claims had gone stale. Category changes were described as hoard-only; they work on either engine now, and that is the whole mechanism by which a race torrent is handed to the hoard. And persistence was described as a store sitting next to resume files, when resume data moved into the store in v3.100.0 -- along with the job queue, which the mental model did not mention at all. Adds jobs as a fourth concept, since work that outlives a request is now something an operator sees in the UI and has to reason about. Notes what actually dominates a cold boot at six figures, which is parsing the .torrent blobs rather than reading resume records -- the useful thing to know before optimising the wrong half. Also drops '100k+ torrents' for the measured 196k.
docs(wiki): French translation of all pages (-FR) + per-page language switch + bilingual sidebar