12 Commits

Include renames

Author	SHA1	Message	Date
jochen	424a7eec82	Keep what discovery heard when a round hears nothing, and fetch only changed announcements (issue 554) ... A round in which no PING reached the laptop's console within the 750 ms window was taken as the mesh's answer that nothing is there, and replaced the index: every seat and module call was refused for five seconds at a time. Discovery now waits up to its patience for a first PING, a round that heard nothing is not kept, a runtime not heard this round is resolved from what it announced last (said with its age), and a round that misses runtimes is logged once. A PING carries a digest of what the instance serves, so an unchanged announcement is not pulled again every round (some 880 kB to the laptop).	2026-10-12 13:56:50 +02:00
jochen	3f0c1a6cec	Serve a key's kept values so the issue tracker can carry them into its log (ADR 0307, issue 502) ... mesh/state.history answers every value a bucket still keeps for a key, oldest first, to whoever may get it, by the same watch the runtime already uses, so no new grant is needed.	2026-10-12 10:18:34 +02:00
jochen	82aefe1988	Refuse a credential in a log entry and take a full 256 KiB value with its expect header (ADR 0297 review) ... A log keeps what it is given for good, so the state guard against secrets applies to it too; the stream holds 260 KiB a message so the headers an append carries never push a 256 KiB value over.	2026-10-11 19:20:31 +02:00
jochen	d535dd5322	Serve a module's log verbs so its record outlives a bucket's cap and the events' week (ADR 0297, issues 501, 502) ... The runtime answers mesh/log.append, read, last and info for a log issued in the module's membership, by publish, batch direct get and stream info alone. A stale expect is refused as a lost state update, so a module tells it by the same code.	2026-10-11 19:18:46 +02:00
jschoubben	ab0f888d67	node-tools: a tool call names its caller, and the module is told it from the subject (hq issue 365) ... Each tool and seat verb is also served on its caller-named subject, kind call with the caller's bus user last, which the controller grants each user with its own name alone; the runtime hands the module that caller in the call's _meta, never from the body. Calls through the runtime (the console and modules' invokes) ask the caller-named subject first and the old one only when the first reached nobody: nothing serves it yet, or the bus refused it because the grant is not delivered yet, which ends the call at once rather than after 30 s. The old subjects stay served and say no caller for one release (hq issue 464).	2026-10-11 05:19:08 +02:00
jochen	1eaa1abbe9	Prove a write by compare-and-set loses no update under contention, on a real bus (hq research 042) ... The issues module will hand out numbers through mesh/state.create and update. Two writers incrementing one counter a thousand times each through the module's bus now end at two thousand with every number handed out once; a stale, zero or future revision is refused with the lost-write code and writes nothing; a deleted key can be created again; and the lost-write code reaches a bundle wrapped or not, and no other refusal carries it. Both runtime tests run in the check's bundleless list, so mesh/repo-check runs them. Part of the issue tracker decision, hq research 042.	2026-10-10 12:31:06 +02:00
jochen	127047edd6	Serve a module from a runtime on its own account instead of switching users, keep bus words from bundles, and never give up a channel's work (hq ADR 0259 revision)	2026-10-09 10:12:39 +02:00
jochen	aa209313c2	Rank a search the same whatever order discovery heard things in ... A tie went to whichever tool discovery listed first, so docker logs found docker_secrets_in_logs before docker_logs on some runs. A name the query says whole wins, then the shorter name.	2026-10-07 20:27:26 +02:00
jochen	49cb06f6c5	Find a tool by the shell command it replaces, best first (hq ADR 0245) ... The agent searched with journalctl, logs and docker ps and found nothing, so it went over ssh. Search now reads what each verb and tool replaces from the controller's records, matches a command line against it, ranks the matches, and says the command it matched.	2026-10-07 19:21:13 +02:00
jochen	0a5dbc7e9a	Cite the hq issues by the numbers they were given: 285, 286, 287	2026-10-07 02:00:11 +02:00
jochen	dac4d423a8	Reach a seat and a module of one name each: list the seat's verbs, and route a machine's address to the module ... mesh-delivery is the delivery's seat and the module holding it, which answers the seat's verbs with tools of the same names. Discovery keyed the seat's verbs and the module's tools in one namespace, so the module's tool took the key and the seat was listed with no verb; and every address with the name resolved to the seat, so neither the seat's verbs nor the module's tools could be called. The keys are apart, and `<node>/<module>.<tool>` reaches the module when the module serves it (novox/hq issue 284).	2026-10-07 01:37:46 +02:00
jochen	14bff5dfd7	Check the tool runtime's own code before it merges, every test on a bus of its own (hq ADR 0237) ... A merge-check.sh, the repository's layer of the mesh's merge check (mesh/repo-check): format, vet, and node-tools' suite under the race detector. The tests shared one bus and had to run one package at a time; like the controller's (#97), each now starts a server of its own at the release go.mod pins, held to the catalogue's bus image by a test. What cannot run in the check — bundles that need @novox/mesh-sdk — is said as not tested.	2026-10-06 22:04:46 +02:00