Correct stale plain-HTTP fallback description Copilot caught in review
Said the console silently falls back to plain HTTP with no certificate.
The real, current behavior (docs/security.md is the authority):
Stage 2 refuses to start without one, FLOD_ALLOW_INSECURE_HTTP=1 opts
back in explicitly. This wiki page was never updated after that fix
landed.
Update for 1.2.0: the Anomalous state, evasion-resistant features, the privilege-separated install layout, and the rate baseline freeze fix
Home.md and Dashboard.md: a second model, an Isolation Forest, now runs
alongside the classifier and surfaces a new Anomalous state; randomized
source spoofing detection is now partially addressed by three new
features invariant under address forgery, corrected from the previous
claim that this needed features the pipeline did not extract.
Configuration.md: documents --max-baseline-freeze-windows, points
training at scripts/train.sh, and adds a note on generator timing
regularity.
Troubleshooting.md: corrects 'Everything Is Flagged and It Never Stops'
this now resolves on its own after the configured freeze cap, not only
by wiping the baseline by hand.
Installation.md: corrects the install, admin-account-creation, and
update instructions for the privilege-separated layout (Stage 2's code
and venv in /opt/flod/stage2, state in /var/lib/flod, neither in the
checkout), which the previous wording did not reflect and which would
have created an admin account in a database the running service never
reads.
docs: split the wiki into 1.x and 0.x lines for the 1.0.0 release