655 Commits

Include renames

Author	SHA1	Message	Date
jochen	cbd9f092d8	ADR 0270 and 0271 accepted: their home in designs 47 and 45, and the glossary's final states ... The operator accepted both on 2026-10-09. Design 47's state table gains covered and what ends a held delivery by itself, and its group the wait for a composed check and the lift; design 45's signals table gains S17 and its planned bus step says the wait is told at once. The glossary's delivery entry names its six final states.	2026-10-09 09:24:30 +02:00
jochen	b04498c01f	ADR 0270: the forge's ancestry decides covered, and say what covered means and does not (review of #241) ... Merge order on a protected trunk is kept only as the first filter; the forge's compare, through a new read-only tool, decides whether a later merge contains a held one. A merge held without a passing check is covered only by a later delivery whose own check passed. Covered says a later merge that contains it was delivered, not that the change runs: a revert in between stays possible. A delivery that only adds a module is delivered whatever its build does, and covered wins over go when a person's walk fails between two readings. The glossary gains covered beside superseded and delivered. ADR 0271 names the bus upgrade as the mesh call and says S17 clears once the step sent the new bus.	2026-10-09 02:58:36 +02:00
jochen	31e78d62d4	Name the pull requests that build ADR 0270 and 0271	2026-10-09 02:35:05 +02:00
jochen	6163a74bb2	ADR 0270 and 0271 (proposed): a held delivery whose change runs ends by itself; a send held for the bus's step is told at once ... Issues 319 and 316: fifteen held deliveries asked a person a question with no right answer, and stop, the only way out, records a delivered change as an error. ADR 0270 delivers a merge that moves nothing at once, adds the final state covered for a merge a later delivered walk of the same trunk carried, and lifts a group hold once its composed check passed. Issue 336: a send held for the bus's planned step raised nothing for 28 minutes. ADR 0271 adds row S17, said at the first refusal for the operator with the verb, keeps S3 from calling it lateness, and has the delivery plan say before the merge that a person's bus upgrade follows. Each issue's diagnosis says what the fix does and how to verify it once delivered.	2026-10-09 02:34:18 +02:00
jochen	9bd0dcc611	Merge remote-tracking branch 'origin/issues/336-a-send-held-for-the-bus-step-raises-nothing' into decision/0270-0271-held-deliveries-end-and-bus-step-said	2026-10-09 02:31:05 +02:00
mesh-admin	4b6642de5e	Merge pull request 'Issue 339: the merge order against mesh-host #61, used-as-found as a behaviour change, the review's follow-ups' (#236) from issues/339-review-follow-ups into main	2026-10-08 23:55:39 +00:00
jochen	1d9d535912	Issue 339: an unmarked file counts as trusted, and the rollback hazard of the trusted field and its fix	2026-10-09 01:42:51 +02:00
jochen	a93ecf90ea	Issue 319: record why no walk opened, and the four held deliveries closed with stop ... A new module counts as something to move, so its delivery is held; a later walk reaches only the delivery whose merge is its commit. Four covered deliveries were stopped before this issue was found, and their merged pull requests now say error.	2026-10-09 01:38:02 +02:00
jochen	5d054b722d	Issue 339: the terminal's settings are derived from what a module serves and which files it trusts; a found directory is its own condition the gate never reads as a fault	2026-10-09 01:24:14 +02:00
jochen	5fbd89c062	Issue 339: the gate reads a directory used as found as a wait for a person; the trust anchors are the terminal's	2026-10-09 00:55:54 +02:00
jochen	ab027691e1	Issue 339: name the merge order against mesh-host #61, record used-as-found as a behaviour change, and the review's follow-ups	2026-10-09 00:28:55 +02:00
jochen	ac3a67ebab	Issue 339: any caller of the settings verb could have the node-engine hand a system directory to an account ... Located in the controller (places and accesses taken through every verb, no line-break check) and the node-engine (a found directory chowned as root, through a link too, and any path mounted). ADR 0266's boundary depends on the fix.	2026-10-09 00:00:04 +02:00
mesh-admin	d0be529194	Merge pull request 'Issue 337: the store's reader can read the controller's signing key (critical)' (#230) from issues/337-the-stores-reader-can-read-the-controllers-signing-key into main	2026-10-08 20:16:30 +00:00
jochen	7f78016f07	Issue 337: say that only what is gone is reported revoked, and that a grant the reader passed on is taken back with CASCADE	2026-10-08 22:11:16 +02:00
jochen	b17839a7db	Issue 337 after review: say control-node, drop the store's operational settings, and match the fix's revoke-by-grantor and read-back ... Adds what the fix cannot see (definer functions and views; the name check as a backstop) and, as a follow-up, that the reader's read-only session is a default a statement can turn off, so the missing write grants are the guard.	2026-10-08 22:02:30 +02:00
mesh-admin	4955a663d3	Merge pull request 'Issue 335: a build that passed its gate was failed and put back by the first machine's later reports' (#227) from issues/335-a-passed-gate-was-failed-by-later-reports into main	2026-10-08 19:51:27 +00:00
jochen	bbbaf943e8	Issue 335: resolved by mesh-controller#165 (8170fc5) with replay R335	2026-10-08 21:49:00 +02:00
jochen	6c297214ad	Issue 337: the store's reader could read the controller's signing key and every secret the store holds ... Opened and diagnosed: pg_read_all_data on the login the store seat's query runs as. Says what the store can and cannot tell about whether the key was read, why it should be rotated once the fix is taken, and that no rotation mechanism exists yet. The fix is mesh-catalog PR 143.	2026-10-08 21:46:01 +02:00
jochen	6fdaeb79ba	Issue 334 and ADR 0264: an ask a seat gave up on can only be dropped for now ... The review refused a grant over every seat's queue, and a copy published again left the original stuck in it.	2026-10-08 21:08:12 +02:00
jochen	b0986e2ae0	Issue 330: name the installer's user list among its fixes	2026-10-08 21:08:12 +02:00
jochen	d1e0e121d6	ADR 0264 and issue 330: keep what a consumer gives up on until a person acts ... Design 25 promised a dead-letter stream nothing built; a message a consumer gave up on was lost after a week, silently once its condition cleared.	2026-10-08 21:08:12 +02:00
jochen	e6f0e7e359	Issue 336: a send held for the bus's planned step raises no condition, so the operator is never asked ... For 28 minutes on 2026-10-08 every send to the control-node waited for a bus upgrade only a person can start, and nothing but a walk's note said so. Located in the controller: the refusal is kept as the walk's note, S3 fires only past a 30-minute bound with generic words, and probe DB reads only a running step.	2026-10-08 20:58:44 +02:00
jochen	f346efb938	Issue 335: leave fixed-by for the merge, and call the put-back refusal a guard	2026-10-08 20:49:40 +02:00
mesh-admin	4eb8be9e66	Merge pull request 'ADR 0263 (accepted), research 038, design 52: a share is a provision, a node mounts it on demand' (#221) from feat/mounts-module into main	2026-10-08 18:39:59 +00:00
jochen	b409537dbc	Issue 335: a build that passed its gate was failed and put back by the first machine's later reports ... Recorded so the gate's verdict is known to be final, and the replay R335 holds it.	2026-10-08 20:27:36 +02:00
jochen	c3a0f7a595	ADR 0265 and issue 327: answer read verbs on the serving connection and name every connection ... Hundreds of short connections an hour, all named mesh-controller, hid any client reconnecting in a loop.	2026-10-08 20:04:19 +02:00
jochen	34899385ec	Accept ADR 0263 with the operator's choices: one share per folder so backups are never exported, mesh machines only	2026-10-08 18:23:23 +02:00
mesh-admin	acc82aa5e4	Merge pull request 'Issue 332: the service manager could neither clear a failed unit nor say what wants it' (#222) from issues/332-the-service-manager-cannot-clear-or-explain-a-failed-unit into main	2026-10-08 15:52:54 +00:00
jochen	fd6c452e61	Issue 332: add unlink-dangling and the glob refusal from the review ... disable cannot remove a link whose unit file is gone, so the verb that finds it needed one that removes it.	2026-10-08 17:40:00 +02:00
jochen	c3a20baece	Issue 332: the service manager could neither clear a failed unit nor say what wants it ... A leftover user unit stayed raised on the workstation: no seat verb showed the dangling enable link that keeps asking for it, or reset its failed record, so the only step left was a shell. Lands per ADR 0246.	2026-10-08 17:21:16 +02:00
jochen	7d60650ae7	Issue 331: resolve it, now the sensors condition is seen to clear on the laptop	2026-10-08 17:12:50 +02:00
jochen	a97efa99f8	Issue 331: name the pull requests that fix it and its replay R331 ... Status stays located until the sensors condition on the laptop is seen to clear.	2026-10-08 17:11:33 +02:00
mesh-admin	72e0a851cf	Merge pull request 'Issue 331: a declared tool check is never asked on the live link' (#218) from issue/331-a-tool-check-is-never-asked into main	2026-10-08 15:06:55 +00:00
jochen	33b0ee3d53	Issue 331: state how the fix is proved, what CI still skips, and that the grants hold live	2026-10-08 17:02:52 +02:00
jochen	6dda1b1d77	ADR 0261: one condition per pending assignment, and a raised row kept until it clears ... The second review of mesh-controller#150 changed points 1, 6 and 7; say what the code now does.	2026-10-08 16:46:42 +02:00
jochen	3a09387c8e	ADR 0261: an assignment made while its module's build runs is kept pending ... The review of mesh-controller#150 found the controller now makes an assignment after the person's act, which no record decided. Decide it, cite it from the glossary and to-be 45, and correct issue 325's account of what is settled where and what is sent.	2026-10-08 16:46:40 +02:00
jochen	63754ca874	Issue 325: assign said no module of that name while the module's build ran ... Register the symptom and the fix in mesh-controller#150 (replay R325 in mesh-lab#68), and name the pending assignment in the glossary.	2026-10-08 16:46:40 +02:00
jochen	08e065fbb6	Issue 331: record why no declared tool check was ever asked on a live machine	2026-10-08 16:45:21 +02:00
jochen	c64a7b3d4a	Issues 326-330: register research 036's live bus faults, each diagnosed ... The bus's own numbers were unexplained and raised by nothing. Measured again read-only: mesh-delivery rewrites unchanged deliveries (326), every controller verb dials its own connection (327), API errors have no reader (328), event consumers outlive their declaration (329), and design 25's dead-letter stream was never built (330). The two slow consumers join issue 270, whose missing system account they share.	2026-10-08 16:27:34 +02:00
mesh-admin	a95e8060c3	Merge pull request 'ADR 0257, issues 321-323, research 035: record the bases builds copy; what the pre-mesh images are' (#207) from decision/a-copied-base-is-recorded into main	2026-10-08 14:02:47 +00:00
mesh-admin	f5f4eedf7a	Merge pull request 'ADR 0254: a wait for a person's new login is not a gate's failure, and each module of a send keeps its own pass (issue 318)' (#204) from fix/318-a-wait-for-a-person-is-not-a-failure into main	2026-10-08 13:03:12 +00:00
jochen	3bfedcfa15	ADR 0258 and issue 324: the live window, data loss never silenced from a click, and where to give what no notification can ... The second review found the fix could not read what the live build kept, missed quiet warnings known from history, and let a click silence data loss.	2026-10-08 14:56:48 +02:00
jochen	b6690c38cf	ADR 0257: platforms go only in a confirmed collect; say what stays, and what a rollback costs ... The sweep after a build is real collection with no dry run in front of it, so it lets an index go alone (review of #207).	2026-10-08 14:53:04 +02:00
jochen	f5d08f4b6f	Issue 324: name the pull requests that fix it	2026-10-08 14:40:30 +02:00
jochen	dd149a72c0	Issue 324 and ADR 0258: a desk click performs only an acknowledgement ... Review found that ADR 0253 let any process at the operator's session release, stop or start a delivery in the operator's name, and that its tokens, fallback words and quiet warnings failed on the paths that go wrong.	2026-10-08 14:40:02 +02:00
jochen	01e48196f7	Narrow ADR 0254 to what the walk path does, and say what a pending relogin excuses (issue 318)	2026-10-08 14:38:08 +02:00
jochen	781681a117	ADR 0254: a wait for a person's new login passes the gate, so one module's wait stalls no walk (issue 318)	2026-10-08 14:25:40 +02:00
jochen	59bc551b5b	ADR 0257, issues 321-323, research 035: record the bases builds copy, and say what the pre-mesh images are ... The store's tools counted 23.8 GiB nothing records: copied bases the sweep could never let go of, platforms a let-go index left behind, and images from before the mesh. Package retention read no lockfile, so it kept versions by age alone.	2026-10-08 14:08:45 +02:00
jochen	356c5f23f4	ADR 0253: say whether the operator is needed, keep quiet what needs nothing, answer from the notification ... The operator read the reworded popup and could not tell whether to act, and was sent to open a session to act at all. The record now decides the verdict, the quiet rule and the path by which a notification is answered.	2026-10-08 14:00:38 +02:00
jochen	fc3c42318f	Issue 320: name the pull requests that fix it	2026-10-08 13:29:33 +02:00