summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHermes SysOp <sysop@webx11.duckdns.org>2026-11-14 18:05:27 +0100
committerHermes SysOp <sysop@webx11.duckdns.org>2026-11-14 18:05:27 +0100
commit2e16127f5cbff1cdec9f38f3a721afcaeddd0b97 (patch)
treec361e857c439c67cf83baa39b67f8007c786e582
parent1975106e9aa221af629da749ae95c572a8a84821 (diff)
docs: boot-path audit (dav-auth unit), the two checker fixes, and the scheduled cold startHEADv4.6.168main
-rw-r--r--CHANGELOG.md8
1 files changed, 6 insertions, 2 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md
index ee2fd17..7375030 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,9 +4,9 @@ Generated from git history by `scripts/build-changelog.py` — do not edit by ha
<!-- generated:start -->
-## v4.6.168 — 2026-11-12
+## v4.6.168 — 2026-11-14
-_Touches modules (3), main.html (1), CHANGELOG.md (1) · fix 1, docs 1_
+_Touches data (5), modules (3), CHANGELOG.md (2), scripts (2) · fix 2, docs 1, project 1_
- **`ui` now works in classic — it was being answered by the AI (v4.6.168)** `03812fd`
- Operator report: "Ui command don't work". It was worse than a broken command: typing `ui` in the classic terminal printed
@@ -14,6 +14,10 @@ _Touches modules (3), main.html (1), CHANGELOG.md (1) · fix 1, docs 1_
- and an AI turn answered it. Three layers each looked healthy on its own:
- … run `git show <sha>` for the rest
- **V4.6.168 change-history — why `ui` was answered by the AI** `9fb133a`
+- **Cron artefacts — feedback snapshot, health/anomaly reports, regenerated admin pages** `45b1533`
+- **Two checkers stopped manufacturing false audit signals** `3e03949`
+ - Both defects are parser bugs in tooling, and both were producing a signal the operator sees on every run. Plan 2026-11-13_062052, implemented as written.
+ - … run `git show <sha>` for the rest
## v4.6.165 — 2026-11-12