docs: one owner for the one-log rule, and an honest scope on the census

The one-work-log rule was written near-verbatim in four places — okf-spec,
okf-maintenance, log.md's preamble, and APPEND_SYSTEM.md. Four copies is four
authorities: each can be edited alone, and the next reader cannot tell which one the
linter implements. okf-spec.md owns it; maintenance now carries the action (collapse
a second log into the root, then re-run the linter) instead of re-arguing it; the log
page points at the rule rather than restating it. APPEND_SYSTEM keeps its imperative —
a system prompt cannot fetch a link at the moment of writing — but no longer carries
the duplicated reasoning.

`inventory/index.md` advertised "all userspace program configuration on the
workstation". The one page in that directory measures `~/.config` on blankpad: not
`~/.local/share`, not system package state, not the servers. A coverage claim that
names what was measured is the difference between a census and an alibi.

Refs #60

omp-docs/references/okf-maintenance.md

@@ -21,12 +21,11 @@ Knowledge bundles rot. It is the nature of knowledge to attract cobwebs, much li
 
 ## Change Tracking with `log.md`
 
-Every OKF bundle has a `log.md`, and it is the bundle's **only** work log: one file,
-at the bundle root. A subdirectory never gets its own — not `core/log.md`, not
-`notes.md`, not a per-project, per-branch or per-run diary. Sprawl is not caution:
-with fifty logs the entry is never where the next agent looks, and each copy re-dates
-the same event on its own authority. `scripts/kb-lint.sh` reports any `log.md` that is
-not the root's.
+Exactly one `log.md` per bundle, at the bundle root — [okf-spec.md](okf-spec.md) owns that rule
+and `scripts/kb-lint.sh` enforces it, reporting any `log.md` that is not the root's. The
+maintenance action is collapse, never coexistence: when a second log turns up (`core/log.md`,
+`notes.md`, a per-run diary), move its entries into the root log under their own dates, delete
+the file, and re-run the linter.
 
 **Format:** one dated section per day, newest first; a few lines per change — what
 happened, and the durable lesson. It is not a file manifest.