Shorten §710's live option to the router's 24-character bound
mesh/delivery closed: a newer head of the same pull request
mesh/check failed (2): ace: novox/hq#573 does not merge into the trunk: files in conflict: 03-DESIGN/01-to-…; and 1 more | f6873cfb6125 on 1f368771f698

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
2026-11-12 10:22:36 +01:00
parent 462a80b990
commit f6873cfb61
@@ -95,7 +95,7 @@ choice within the record it cites, tested against [the principles](../../../00-M
fingerprint, the kept data, its form and the node's reason in its own words, and says "<module> keeps running
its newer build until you answer. Started on the live data, the older build reads data written in the newer
form." Two options, each of level acknowledge: `hold`, "Keep it held", does "the node keeps running the newer
build, and the revert waits"; `live`, "Start it on the live data", does "the node starts the older build on the
build, and the revert waits"; `live`, "Start on the live data", does "the node starts the older build on the
live data as it is, with nothing restored". It expires after the assigner's `AskLasts`, `OnExpiry` "the module
keeps running its newer build". The answer is read from the router's record of the ask (§700).
- **Raises the condition**, through mesh-sdk's finding writer (§461), with the finding `revert-held` (scope