68 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	eaec209a37	Stop the stdio channel holding its lock across a pipe write, so a refused subscribe cannot deadlock it (issue 1286)	2026-10-19 21:51:13 +02:00
jschoubben	9ade199740	Give the build fixture the path the controller writes for build-agent (issue 1233)	2026-10-19 14:42:04 +02:00
jschoubben	0596f44414	Say a build's directory and a pull request's module directories in the SDK (issue 1233)	2026-10-19 14:40:19 +02:00
jschoubben	732238cb6a	Cite the controller's lines rightly, and say the newest key holds an id (issue 1223, review round 1)	2026-10-19 13:46:36 +02:00
jschoubben	845c8b0e56	Give the build record's layout to readers outside the controller (issue 1223)	2026-10-19 13:44:09 +02:00
jschoubben	a39661aa36	Prove the source fingerprint against three builds the live builder recorded (issue 1203)	2026-10-19 11:03:46 +02:00
jschoubben	662fb0a57c	Map every byte the router's id refuses in an ask id, so a group with = gives a usable ask (issue 1201)	2026-10-19 10:37:03 +02:00
jschoubben	0bc5659076	Make every ask id end in a digest of its key so two keys never share an id (issue 1201)	2026-10-19 10:34:59 +02:00
jschoubben	c23833d3e5	Move the source fingerprint into one function the builder and the indexer both call (issue 1203)	2026-10-19 10:34:19 +02:00
jschoubben	0ae600dc97	Give a module one subject and one layout to say a condition to the operator (issue 1202)	2026-10-19 10:33:53 +02:00
jschoubben	15af148520	Give the gate's merges, asks and owed acts and the teller's answers one layout the parts read (issue 1201)	2026-10-19 10:33:17 +02:00
jschoubben	6d620f24b7	Give the source revision, candidates, modules and forge messages one layout the parts read (issue 1200)	2026-10-19 10:31:59 +02:00
jochen	cfa20f05ad	Reconnect without limit, as the tool runner does, so a process outlives a bus restart (issue 1192, review round 1 finding 5)	2026-10-19 04:52:10 +02:00
jochen	f1438dff6a	Prove Conn offers no Serve by reflection, and build its AC3 test account through ReadAccount (issue 1171, review round 1 findings 3 and 4)	2026-10-19 04:51:14 +02:00
jochen	1ffbf9ea5b	Make the Term test prove no redelivery instead of passing on a 30s AckWait it never waits out (issue 1190, review round 1 finding 2)	2026-10-19 04:50:07 +02:00
jochen	e05e7130ae	Catch a denied publish at once instead of waiting it out, so an ungranted bucket's refusal names it (issue 1188, review round 1 finding 1)	2026-10-19 04:48:58 +02:00
jochen	80d3975762	Let a process call a tool or a seat verb on its own account, with the tool runner's caller fallback (issue 1191)	2026-10-19 04:41:08 +02:00
jochen	f73ec7457a	Let a process consume its module's work queue, acknowledging, delaying or terminating each message (issue 1190)	2026-10-19 04:38:45 +02:00
jochen	94702bcd79	Let a process read the router's record of its module's own ask (issue 1189)	2026-10-19 04:35:33 +02:00
jochen	de2d944c2a	Let a process read and change its module's state by compare-and-set, and emit with a chosen message id (issue 1188)	2026-10-19 04:34:04 +02:00
jochen	0796341c8d	Let an SDK Emit choose its event's message id, so a repeated publish is kept to one (issue 1187)	2026-10-19 04:26:54 +02:00
jochen	96155dea23	Give mesh-sdk a process's own pinned bus connection, reading its delivered account (issue 1171)	2026-10-19 04:26:01 +02:00
jochen	1361c1b456	Vendor the bus library and give integration tests a bus of their own (issue 1171)	2026-10-19 03:43:19 +02:00
jochen	9908faaa02	Give the SDK's Go check an integration level and vendored dependencies, before a test needs them (issue 1175)	2026-10-19 02:00:12 +02:00
jschoubben	953446cc8f	Give the watchman's stuck keys a layout the controller reads (issue 1153) ... ADR 0433 §2, §3: the watchman writes what stopped moving and the controller's self-check raises it, so the key and value live in the SDK (ADR 0429 §2).	2026-10-18 20:11:04 +02:00
jschoubben	2b420603fe	Give delivery's keys and values one home the node-engine and the parts read (issue 1131)	2026-10-18 18:49:24 +02:00
fix-sdk-pas	a4e7f480b3	Apply the plan's credential form only to an offer that declares a credential (issue 825)	2026-10-16 19:44:26 +02:00
fix-sdk-pas	d7cac79585	Carry the grant-file and keycloak-shape moved-path tests into harness (issue 849)	2026-10-16 19:37:02 +02:00
fix-sdk-pas	377fd6d67d	Move the moved path's shared driving into harness.Moved, so postgres and keycloak keep only what differs (issue 849)	2026-10-16 19:34:02 +02:00
fix-sdk-pas	bb7c82cac6	Move the moved-provider harness and its retirement into go/provider/harness (issue 849)	2026-10-16 19:29:27 +02:00
fix-sdk-pas	0db956dd83	Skip a bad assignment, honour the plan's credential form, delete only what was read, redact every credential form (issue 825)	2026-10-16 19:28:25 +02:00
fix-sdk-pas	40f3658557	Name the vault's credential under vault-name so the state guard accepts the bound entry (issue 945)	2026-10-16 19:26:58 +02:00
mesh-tools	1bc5719b8b	Feature 57 (config and provisioning): release mesh-sdk, the reviewed release branch on top of main	2026-10-16 08:24:11 +00:00
jochen	5933eb757d	go/asks: whole details never digest as another ask's Whole and Details (the review of #25) ... WholeDetails was written after a tag, so an ask with only whole details "+ x: 1" encoded as one whose Whole was "whole-details" and Details "+ x: 1". Whole and Details are now written whenever whole details are given, then the whole details, untagged: the number of trailing values tells the three shapes apart, and an ask without whole details digests as before. The note's comment says what ADR 0347 §5 holds of cuts.	2026-10-13 20:29:24 +02:00
jochen	f4745447ba	go/asks: an ask may carry its Details whole, for a channel that proves who answers (hq issue 383) ... The review of mesh-controller #304: a settings proposal with more than three keys showed only the names of the rest, and its Details could carry no value under the content rule, so Approve bound values the operator never saw. WholeDetails carries every value whole for the note on a proving channel, held to the secret rule alone, as Whole is; it is digested only when given.	2026-10-13 16:56:22 +02:00
jochen	9588871d66	go/asks: a message carries its note apart, and an explanation is held to a glance (hq issues 639 and 383) ... The operator will not read a Telegram ask of thirty plain lines. The secondary words (who asked, what each answer does, the expiry, the fingerprint, how to read it whole) travel as Message.Note, so a channel can show them small or collapsed; an ask's Details go there. Glance names the bound of an explanation: a summary of at most 300 characters, then at most three points of at most 160.	2026-10-13 16:15:20 +02:00
jochen	67bfa22132	go/outward: refuse a password in an address, a value given to an env-style secret name, and base64 wherever its slashes fall (review 53, issue 418) ... node-reads applies CheckSecret to env, unit and configuration files, where user:pass@ in a URL, DB_PASS=, MESH_TOKEN= and name = value with spaces passed, and a random base64 value passed when its slashes or dashes cut it into short pieces. A run is now judged in pieces only where it is a path, base64 padding marks a value, and letters alone are random when the case changes as a random string's does, so a CamelCase name still passes.	2026-10-12 14:27:49 +02:00
jochen	4dc5f29d3e	go/outward: the content rule in one place, so the operator channel and node-reads apply the same one (hq ADR 0310 §4, issue 418) ... The operator channel's rule (messenger's content.go, with the secret class split out as in issue 383's branch) moves here as package outward: Check for what may leave on a channel, CheckSecret for a secret's shape alone, which is what a node-reads answer is held to. The messenger switches to it once mesh-catalog #178, which changes that file, has merged.	2026-10-12 13:52:57 +02:00
jochen	d41d255f28	go: a module reads the values its bucket still keeps for a key, so the tracker can carry them into its log (hq ADR 0307)	2026-10-12 10:17:56 +02:00
jochen	eaed934629	go: a module appends to and reads its log through the runtime, so its record outlives a bucket's history (hq ADR 0297)	2026-10-11 19:16:09 +02:00
jschoubben	d9e24e95a2	go: a tool reads its caller from the runtime, so a record can say who acted (hq issue 365) ... The runtime names the caller it took from the subject a call arrived on in the call's _meta; stdio.CallerOf(args) hands it to the tool. Never read from the arguments, and Unproven when the runtime named none, so a bundle on an older runtime still says, explicitly, that its caller was not proven.	2026-10-11 05:11:08 +02:00
jschoubben	24f5ee81bd	cli: after a failed write take only a refusal, since nothing can have run, and pin that the read keeps the ask's deadline (hq issue 444)	2026-10-11 02:49:17 +02:00
jschoubben	b4900f52b8	cli: read the engine's answer after a failed request write, so a refusal is not lost as a broken pipe (hq issue 444)	2026-10-11 02:43:54 +02:00
jochen	33917f91ac	Refuse every form of path or address in a wait's words, a contradicting healthy answer, and a malformed wait at Waiting ... From the review of mesh-sdk#18: quoted and bracketed paths, home and relative paths, IPv6, host and port, UNC and drive paths passed the check.	2026-10-10 21:10:01 +02:00
jochen	622b6b4f55	Add go/health: a health tool answers healthy, unhealthy or waits (hq ADR 0283, issue 386) ... A module waiting for the operator's secret had only 'not healthy' to say, so its first-node gate failed and the operator was told nothing to do. The answer gains a state and named waits, and Read refuses any wait it cannot check, so a malformed wait never excuses a fault.	2026-10-10 21:06:44 +02:00
jochen	4f3efc98e0	go/asks: an ask says what a channel that proves who answers shows whole, and what Details shows (hq issue 383) ... A settings proposal reached the phone with its values masked, so the operator could not tell what they were approving. An ask now carries Whole, shown in place of Explanation on a kind that proves its sender and carries the ask's answers, and Details, what the Details answer shows. Both enter the digest only when given, so an ask without them digests as before and a router and an asker of different builds still agree on it.	2026-10-10 15:23:41 +02:00
jochen	9c548753b8	go: say an Increment error other than a lost write may have spent its number, refuse null, and prove the writers collided ... The review of 2026-10-10: a timeout can come after the write landed, so a caller tolerates gaps; a null value is no counter; and a contention test where no write was lost would prove nothing.	2026-10-10 12:33:41 +02:00
jochen	c58ce2c7fe	go: a counter by compare-and-set, so a number is handed out once (hq research 042) ... The coming issues module hands out issue numbers from its own state; two instances must never hand out one number twice. Create and Update already write by compare-and-set (ADR 0259), so State(...).Increment reads, writes one more at the revision read, and on a lost write reads and tries again, bounded by the caller's attempts. A lost write past the bound is ErrChanged, any other refusal and a value that is no counter are returned at once: nothing is reported counted that was not written. Part of the issue tracker decision, hq research 042.	2026-10-10 12:31:05 +02:00
jschoubben	f047d0a4a9	go/cli: carry mesh-cli's standard input with its line, bounded at 64 KiB, for the controller's terminal alone ... A secret given at the terminal (secret accept … --from -) has no way through mesh-cli today: the controller runs every line with no standard input. The request now carries it, refused over 64 KiB by mesh-cli and by the reader alike, and MaxRequest grows by what base64 makes of that bound.	2026-10-09 16:33:44 +02:00
jschoubben	16984aafc6	Refuse a warrant for an ask with no expiry, and one that says no time (the confirmation review of 2026-10-09) ... For skipped the expiry check when the warrant carried no time, and an ask with a zero expiry was answered at any time. Neither can be shown to be in time, so neither is acted on.	2026-10-09 13:58:50 +02:00