Nothing reads decision records from hq: records_decisions retired, reserve asks the knowledge base, an empty import refuses (hq issue 488)

Once the records leave hq (issue 426), records_decisions would answer every topic empty, reserve would read 0
and hand out 0001 from a counter not started, and import would say it created nothing as a success. reserve now
starts and raises its counters above mesh-knowledge's knowledge_highest, the floor alone starting one (with a
warning) when it is silent and nothing spent with neither.

modules/mesh-knowledge/README.md

@@ -29,6 +29,11 @@ accepted only on the operator's Approve, given on a channel that proves who answ
 `ask`, `get`, `holds` and `history` stay within `bound` bytes (4096 unless asked for, at most 65536) and say what they cut
 and how to read the rest. The module's own tool `knowledge_health` answers its health (below).
 
+Its tool `knowledge_highest` answers the highest decision and research number it holds, every number spent
+counted (accepted, proposed, reserved or withdrawn): the issue tracker's `reserve` starts and raises its counters
+above them (hq issue 488). It refuses while nothing is held. It is a tool of the module, not a verb of the seat,
+which serves the verbs ADR 0290 rule 6 names.
+
 **Who acted** is the caller as the runtime proves it, never an argument: no verb takes one. The tool runner takes
 the caller's bus user from the caller-named subject a call arrived on and hands it through the SDK
 (`stdio.CallerOf`, hq issue 365). A call on the subject that names no caller (served beside it for one release, hq
@@ -103,7 +108,8 @@ record it goes out from.
 ## The import
 
 `import` reads hq through the records module at the commit its checkout stands at. With `commit`, it refuses a
-checkout standing elsewhere. It writes every decision record and research effort whole, as version 1, naming the
+checkout standing elsewhere. At a commit where hq holds no decision record and no research effort (the records
+have left it, hq issue 426), it refuses and says so, rather than answering "nothing created" as a success. It writes every decision record and research effort whole, as version 1, naming the
 commit and path it came from. It creates only what is absent and never overwrites. It never asks for a number, so
 no counter moves. A second run changes nothing and says so. `dry-run` writes nothing. From a terminal,
 `mesh-knowledge dry-run <hq checkout>` gives the same dry run over a checkout on disk, against an empty knowledge