8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	70b16dc594	Merge origin/main (keep-main-rules) and fix/forge-requires-no-status (ADR 0534): no required status anywhere, and with keep-main-rules false the program takes away a required status once and changes nothing else	2026-10-23 17:20:19 +02:00
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	d2036f2a63	gitea: require no status on main, judge mesh/check in the merge tool instead (ADR 0534) ... The forge's required status was a second copy of the gate mesh-delivery and the merge tool already keep; a stuck status writer held it too (issues 1886, 1891) and only a hand change at the forge let a fix merge. Main keeps no push, the tools' merge whitelist and no administrator override. The merge tool judges mesh/check whether or not the branch requires it, and on a branch that requires none merges only a head the operator's Approve names. The protection tool loses its status argument.	2026-10-23 12:01:57 +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
fix-forge-awg	3cdea45f90	Keep main's rule right at every start and copy a covering glob's checks (issue 948, review round 1)	2026-10-16 21:35:51 +02:00
fix-forge-awg	7807135a1b	Main takes no push and only mesh-tools merges, set by setup and guarded (issue 948, ADR 0398 §2)	2026-10-16 21:28:43 +02:00
mesh-tools	0260ae92f6	Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main	2026-10-16 09:42:45 +00:00
mesh-adminandClaude Opus 5.5	48f0662fde	Make the forge's tools act as an account of their own, not the administrator (issue 469, ADR 0365 clause 2) ... The tools' token reached everything the administrator may do, so their boundary rested on their own guards. The gitea module now makes a plain account, mesh-tools, with the admin login, gives it write on code, issues and pull requests of every novox repository through one team, and mints the tools' token for it; the admin's old token goes only after the new one is kept. The Go forge bundle sends that token, never the admin login. The forge shows protection rules only to a repository administrator, so every check reads a branch's protection from the branch. mesh-admin stays a ready author, so marks made before the move keep counting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 22:28:25 +00:00