182 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	68dfca1057	Gate the token mint's main-rule write by keep-main-rules too ... The operator, 2026-10-23: "disable the gitea branch protection reset thing". setUpToolsAccount (run at every token mint) called ensureMainMerges regardless; it now does so only when the setting is true.	2026-10-23 15:57:44 +02:00
jschoubben	77f33d317f	Keep main's rules only when the setting keep-main-rules is true (default false) ... The operator, 2026-10-23: "disable the gitea branch protection reset thing". The 10-minute tick and the start-time ensureMainMerges, and the repositories sync's changes to existing repositories' main rules, now run only when the new setting is true; new repositories are still made. The sync says in its outcome that rules were left.	2026-10-23 15:53:30 +02:00
jschoubben	933370df7c	gitea, minio: compile the sources beside themselves in the test script, as the old check did (issue 1891) ... The resolve hook needed the typescript package, which mesh-build-node keeps out of the workspace (notCopied): tsc is reached only as the bin/tsc command. So the test scripts now do what merge-check-typescript.sh did before the tests: tsc over the module's sources with --outDir ., so the sources' ./x.js imports resolve. The emitted .js is ignored by git.	2026-10-23 10:22:41 +02:00
jschoubben	437c524b81	gitea, minio, mosquitto: tests run as the Node build module runs them, tsc -p . then npm test (issue 1891) ... The old TypeScript check compiled every source beside itself, and into dist/, before it ran the tests; mesh-build-node runs `tsc -p .` (these tsconfigs say noEmit) and then the package's test script, so: - gitea and minio: the tests import the .ts sources, which import each other as ./x.js. A resolve hook in test/ resolves such an import, when no .js is there, to the .ts beside it and compiles it with the toolchain's TypeScript (gitea's sources use parameter properties, which type stripping refuses). 57 of gitea's tests and minio's links test failed. - mosquitto: its ctrl test imports ../dist/client.js; its test script now builds first, as gitea's does. Test scripts and a test helper only; what is built and delivered is the same.	2026-10-23 10:18:57 +02:00
jschoubben	dc96d7c2dd	gitea: take a rule's null contexts as the forge's type says, so the strict build the checker runs compiles (issue 1891) ... The checker builds a package with a build script by its tsconfig (strict), where requiredOf and TrunkForge's appliedProtection said status_check_contexts is string[] and BranchProtection says string[] | null: four TS2345 errors, hidden on main behind earlier failures. Types only; the emitted code is the same, and a test holds that null contexts require nothing.	2026-10-23 10:00:09 +02:00
jschoubben	896bd88380	Write mesh/check from the checker's owed state, read by a watch (R2-1) ... R4e round 2 finding R2-1, ADR 0521: the delivery plan draws no edge that orders the forge module before the forge bridge, and the forge module's durable consumer keeps its deliver policy when its filters change, so a check.status the bridge emitted before the forge module consumed it was lost. An in-memory revision guard also forgot itself on a restart. The forge module now reads mesh-delivery-checker.owed, which the checker announces readable, by a watch: the watch hands over the latest value of every key whenever the module starts, so a status written while it was away is written then, and only the latest. Each mesh/check is written once per revision, an older one dropped; a forge refusal is asked again on a bound until written or overtaken; a refused read is said once and asked again until granted. No tool writes mesh/check, and no check.status is consumed.	2026-10-22 21:45:53 +02:00
jschoubben	21b4925892	Merge remote-tracking branch 'origin/fix/r4e-k1' into r4e-int2	2026-10-22 21:28:24 +02:00
jschoubben	0fdfecfa29	K3: pin gitea to mesh-sdk 104533e8, the group's final SDK head after S1 and S2 (ADR 0500 §2)	2026-10-22 21:19:11 +02:00
jschoubben	8d3f81c2c0	Write mesh/check from the forge bridge's own event, never from a tool (K1) ... Review finding K1 of R4e, issue 1301 S4 (ADR 0503 §3, ADR 0513 §4: the forge requires mesh/check alone). gitea_check_status assumed only the bridge could call it, but a tool is told no caller and node-tools invokes every tool, so any session could set mesh/check to success and merge past the checker: the fault issue 293 closed for the two statuses before it. gitea now consumes mesh-delivery-forge-bridge.check.status, a subject the bus grants to the bridge's own account alone, and check.ts writes mesh/check from it: the source is checked, the head's whole sha and the state, and a revision older than one already written on the head is dropped so a redelivered stale pending never hides a verdict; a forge refusal throws, so the event is delivered again. gitea_check_status is removed, and gitea_commit_status keeps refusing mesh/check.	2026-10-22 21:14:01 +02:00
jschoubben	8f10d3192c	K3: pin gitea to mesh-sdk 875c680d, the group's one SDK head (ADR 0500 §2) ... gitea's Go code (cmd/repositories) changes in the R4e group, so it pins the SDK head every other member pins; it still held 66e8fdaa.	2026-10-22 21:08:33 +02:00
jschoubben	c97cea21cf	Merge feat/r4e-leaf into feat/r4e (R4e integration) ... gitea's index.ts conflicted on imports: kept both, the leaf's statesAnnouncement and the gate's checkStatusTool. mesh-delivery-gate is pinned to the sdk lane's newest head d1af87a (the leaf had a90f523) until the final SDK head.	2026-10-22 20:34:48 +02:00
jschoubben	a18eeeef5a	Say gitea's states with the SDK's emit, as the toolchain's SDK has no keeps yet (issue 1790, issue 1852)	2026-10-22 19:04:21 +02:00
jschoubben	c112df0c1c	Announce the states the forge module keeps (issue 1790, ADR 0495 §2 §5)	2026-10-22 18:03:06 +02:00
jschoubben	b07a101caf	Answer each named path's git object id from gitea_commit_trees (issue 1758, S1-S2, ADR 0499 §3)	2026-10-22 17:59:23 +02:00
jschoubben	f1f18bf2bd	mesh-delivery-gate: read mesh/check alone on a base that requires it (issue 1302, S1-S10) ... Once main requires mesh/check, the controller publishes no verdict for it and the gate, which moved deliveries on the controller's checked, would hold every pull request proposed. A head's mesh/check is now its verdict, from the forge's status event (gitea now sends the status's words) or its open pull requests. The Approve is asked only on the checker's verdict at exactly the heads the ask covers, so a member judged alone never passes its group; a group on mesh/check asks no composed check and owes no mesh/merge-gate; a member's mesh/check that changes withdraws the ask. Nothing is asked of the controller for such a base, and recheck refuses, naming checker_pull. hq's mesh/repo-check keeps today's path.	2026-10-22 17:50:25 +02:00
jschoubben	c41c968086	gitea: judge and write only the statuses a base requires, so merges go on mesh/check (issue 1301, S5-S7) ... Once main requires mesh/check, nothing writes mesh/merge-gate, and the merge tool, which judged on it, would refuse every merge. It now judges on the status the base requires: mesh/check's line names the trunk it judged, an out-of-date one is refused and nothing is asked (the checker re-checks on a trunk move, ADR 0447 §4); hq's mesh/repo-check is judged as before. The announcer, the verdict, a trunk's move and a build's start write the controller's two statuses only where a base still requires them, so hq keeps mesh/repo-check and no stale mesh/merge-gate appears anywhere else.	2026-10-22 17:49:53 +02:00
jschoubben	939475cb63	gitea: only the forge bridge writes mesh/check, through a tool of its own (issue 1301, S4) ... Once main requires mesh/check, a hand that set it could pass a merge past the checker, the gap issue 293 closed for the two statuses before it. gitea_commit_status now refuses mesh/check in every state, and the new gitea_check_status writes it alone; the bus grants that tool only to a module whose manifest invokes it, the forge bridge (the lead's choice A).	2026-10-22 17:49:53 +02:00
jschoubben	5e24deb0f1	gitea: require mesh/check in place of the two old statuses on every main the gate judges (issue 1301, S1-S3) ... ADR 0447 §1 has main require mesh/check alone. The repositories program now requires it in place of mesh/merge-gate and mesh/repo-check on every listed repository and on every other one whose main requires mesh/merge-gate, so the switch needs no hand-kept list (lead decisions L4, L11). A main requiring mesh/repo-check alone (hq) keeps it until issue 1296 (ADR 0503 §5).	2026-10-22 17:49:53 +02:00
jschoubben	ce8d52ed0b	Let gitea read the image build module's keys, so its key is the builders' (issue 1703f)	2026-10-22 10:27:01 +02:00
jschoubben	77f3963d83	Test that the gitea bundle's import resolves while its binds are refused (issue 1793)	2026-10-22 00:49:27 +02:00
jschoubben	49a28f8537	Start the gitea bundle's binds without awaiting them, so its handshake is answered while a refused bind is asked again (issue 1793)	2026-10-22 00:45:54 +02:00
jschoubben	0d2686b5eb	Bind the gitea bundle's event consumers again until they hold, so a refusal at its start no longer ends it and loses verdicts (issue 1793)	2026-10-22 00:37:30 +02:00
jschoubben	59b13d091d	Ask no check of a group member that waits on its composed check, and stop asking a merge refused the same way with no trunk move (issue 1106)	2026-10-21 21:57:32 +02:00
jschoubben	0a7c58766c	Pin gitea, keycloak, mesh-provisioner-client, postgres and route-adapter to a commit of mesh-sdk main, since the pinned one is on a feature branch only (issue 1663)	2026-10-21 14:07:01 +02:00
mesh-tools	324e331184	Anchor patch hunks as git apply does, refuse patches touching non-100644 files by their real mode, survive bare-CR context lines (issue 1604 review)	2026-10-21 09:52:10 +00:00
mesh-tools	e5cfcb316a	Fall back to the tool's own patch applier when the forge answers 500, with tests (issue 1604)	2026-10-21 09:21:59 +00:00
mesh-tools	e6053262e4	Apply a unified diff in the forge tool itself, for the patches the forge's diffpatch refuses (issue 1604)	2026-10-21 09:20:25 +00:00
mesh-tools	298a0b8eda	Test the forge account provider's builder entries, and add the Go build module's manifest, ssh files and README (issues 1481, 1483), part 6 of 17	2026-10-20 20:48:52 +00:00
mesh-tools	fb52442b50	Serve a build module's key from its own state, read-only on nox-builder, in the forge account provider (issue 1482), part 5 of 17	2026-10-20 20:47:25 +00:00
mesh-tools	5702046667	Make the builders team and the read-only nox-builder keys in the forge account library, and watch the build modules' keys (issues 1481, 1482), part 4 of 17	2026-10-20 20:46:23 +00:00
mesh-tools	dc3a177410	Let a commit copy files from another forge repository, so a large move is not typed through the caller	2026-10-20 01:07:28 +00:00
jschoubben	75957fc3c0	Hash the root tree from the root's entries, since the forge names the commit (issue 1234) ... The listing's top sha is the commit's, not the root tree's (seen live, novox/mesh-delivery at 7f61817), so gitea_commit_trees now computes the root tree as git does, from the entries without a slash. The query keys recursive and per_page stay in the allow-list: read flags only.	2026-10-19 14:52:29 +02:00
jschoubben	ea83746297	Give the forge bridge a merge commit's trees in one call, and a pull request's head branch (issue 1234) ... gitea_commit_trees reads the commit's recursive tree listing and answers the root tree and the tree of every directory holding a module.json; a cut listing fails loudly. gitea_open_pulls entries gain head. The query keys recursive and per_page join the allow-list, read flags only. mesh-delivery decodes open pulls with json.Unmarshal into a struct (cmd/mesh-delivery/ports.go:405-410), which ignores the added key.	2026-10-19 14:50:19 +02:00
jschoubben	54db38be08	gitea: a repository the module makes refuses an administrator's merge past its checks (issue 1141) ... narrowed never set block_admin_merge_override, so novox/mesh-delivery's main let an administrator merge past mesh/merge-gate and mesh/repo-check, unlike every other repository's main since 2026-10-07. narrowed sets it and isRight requires it, so the module's next start puts mesh-delivery right.	2026-10-18 18:10:29 +02:00
jschoubben	e75e793a4b	gitea: fill repositories.json through the provisioner client, so an approved value lands at once (issue 1128) ... The file was merged by the controller (merge, takes-config), which writes a config change only on the node's next send (ADR 0348 §10): the operator's Approve of the mesh-delivery repository set the value and nothing made it. A plain template saying ${config:repositories} is filled by the provisioner client on config-changed, and the node-engine reruns the run-once program that names the file under restart-on.	2026-10-18 17:40:59 +02:00
jschoubben	11761637cf	Put main's rule right again once a new repository is in the organisation: the forge drops a merger without access, and under the setup account the tools' account has none (issue 1124, ADR 0428 §3, review round 1)	2026-10-18 16:58:17 +02:00
jschoubben	8c587d0f00	Let the repositories pass's failed exit be its gate: a run-once step the node-engine runs again until it passes, its stderr naming each refused repository, step and forge answer, instead of a health check of its own (issue 1124, ADR 0428 §6)	2026-10-18 16:52:29 +02:00
jschoubben	df275b3c6e	Make the organisation's repositories from the gitea module's config value, protected under the setup account before they join the organisation, and take the owner argument from gitea_create_repo, since a repository's maker becomes its administrator (issue 1124, ADR 0428)	2026-10-18 16:49:12 +02:00
jschoubben	94b49a296f	Test that the gitea module makes the organisation's repositories from its config, protected before any team reaches them, and that no tool creates in the organisation (issue 1124, ADR 0428)	2026-10-18 16:45:49 +02:00
jschoubben	0d3f0fd3fc	Let gitea_create_repo create in an organisation, saying the forge's refusal, so novox repositories can be made through the tools (issue 1124)	2026-10-18 15:45:01 +02:00
jschoubben	50fee22d0a	Test that gitea_create_repo creates in an organisation and says the forge's refusal (issue 1124)	2026-10-18 15:44:38 +02:00
jschoubben	68e3326d4c	Providers and the provisioner client take the SDK that reads an ended assignment as a removed key (issue 1098)	2026-10-18 02:40:18 +02:00
jschoubben	6556e61485	Read a pull request's review record again when its description is edited, and ask the Approve again if it was unanswered (issue 1079)	2026-10-18 01:12:40 +02:00
jschoubben	da094008ea	A group's composed verdict names each member's siblings at the heads it composed, so a sibling's own merge is no move (issue 1049)	2026-10-18 01:08:26 +02:00
jschoubben	47e42806ff	Leave a composed member's gate to the group's verdict, reword the mark leftovers, restore main's merge-check.sh (issues 1022, 978)	2026-10-17 21:33:03 +02:00
jschoubben	2d3b61ec45	Merge a group in one pass on its one Approve, with no order and no turns (issue 978) ... A group has no order: mesh-delivery asks the controller for none, reads no after: line (it says once that the line is not read), merges every member in one pass once the composed check passed and the Approve covers the heads, and gives the plan its word once every member is merged. A failed member stops no other. The composed verdict sets each member's mesh/merge-gate (pending, saying why, until one stands), the groups answer says composed_gate, and a trunk move asks the out-of-date members' checks at once and merges on the same Approve (issue 1047).	2026-10-17 20:54:16 +02:00
jschoubben	668444785d	Ask the Approve as soon as the checks pass, with no ready mark (issue 1022) ... The review finishes before the push and its record is a Reviewed-by line in the description, so the mark repeated what the push meant. mesh-delivery asks the operator when a pull request's checks pass, keeps an ask through a trunk move by asking the check again at once, and hands the merge tool the approved heads, which replace the forge review of each sibling.	2026-10-17 20:44:54 +02:00
mesh-tools	652b00b25b	Say on every directory how it treats files it does not know, and check it (issue 1024, ADR 0422) ... Every directory and archive resource carries `unknown`: move-out for a home folder whose program writes nothing there (the node-engine, delivered in mesh-host #117, moves the rest to ~/.local/state/mesh-moved/<module>/ with a list), module for ~/.ssh and ~/.claude, program elsewhere; `knows` keeps what a program or the operator relies on (powerlevel10k's compiled files, i3's scripts and the asus/g14 drop-ins, dunst's slack rule, betterbird's records, node-env's forge credential, issue 1033). Two shared folders are no longer declared. Each module's README says it. checks/owned holds every manifest to it; checks/sshdir stays while main's merge check runs it (issue 1035). Tests that pin a manifest follow the new key only. Reviewed in three rounds.	2026-10-17 16:23:03 +00:00
jschoubben	add91ff048	issue 976: the forge's announcements get a deterministic message id; the announcement files go, the poll's watermark is kept in the module's state	2026-10-17 13:52:47 +02:00
mesh-tools	3a2560dc51	One forge user, nox-agent, for every machine's agents' SSH pushes, each machine's key titled by machine (issue 991, ADR 0410)	2026-10-17 00:46:43 +00:00