The gitea module makes the organisation's repositories from its config, protected before any team reaches them; no tool creates in the organisation (issue 1124, ADR 0428) #363

Merged

mesh-tools merged 4 commits from fix/1124-repositories-config into main 2026-10-18 15:05:04 +00:00

Conversation 2 Commits 4 Files Changed 14

+1654 -133

mesh-tools commented 2026-10-18 15:01:40 +00:00

Member

Copy Link

Copy Source

Builds ADR 0428 (as corrected by its version 15) and fixes issue 1124.

• New config value repositories (trusted, default {}), rendered to a file.
• New Go program cmd/repositories (repositories sync), a run-once process and the module's last resource, run at start and whenever the value's file changes. For each listed repository that does not exist: made under the setup account, main rule letting that login alone push, first commit (README and a merge-check.sh declaring Go), rule narrowed (no push, mesh-tools alone merges, mesh/repo-check and mesh/merge-gate required), moved into novox, and the rule read back and put right there. An existing repository only has its rule put right; statuses are only added. A repository out of the value is never touched.
• A refused step stops only that repository; the program exits 1 with one stderr line per refusal (repository, step, forge answer), so the node-engine raises apply-failing and reruns it at every apply. The condition carrying those lines is issue 1127.
• gitea_create_repo loses its owner argument (TS); test/create-repo.test.ts replaced by test/no-org-create.test.ts.

Acceptance criteria: issue 1124, note 2 (AC1-AC8, each cited by its tests as 1124/AC<n>).

Try before this pull request: mesh-controller.try build-1792335551733911180 passed at 1176163 (Go and TypeScript parts, 59 s).

Delivery: moves the gitea module on novox. After it, the operator approves the config value repositories listing the existing repositories and mesh-delivery.

Reviewed-by: reviewer-1124@shanks at 11761637cf

Builds ADR 0428 (as corrected by its version 15) and fixes issue 1124. - New config value `repositories` (trusted, default {}), rendered to a file. - New Go program `cmd/repositories` (`repositories sync`), a run-once process and the module's last resource, run at start and whenever the value's file changes. For each listed repository that does not exist: made under the setup account, main rule letting that login alone push, first commit (README and a `merge-check.sh` declaring Go), rule narrowed (no push, mesh-tools alone merges, `mesh/repo-check` and `mesh/merge-gate` required), moved into novox, and the rule read back and put right there. An existing repository only has its rule put right; statuses are only added. A repository out of the value is never touched. - A refused step stops only that repository; the program exits 1 with one stderr line per refusal (repository, step, forge answer), so the node-engine raises apply-failing and reruns it at every apply. The condition carrying those lines is issue 1127. - `gitea_create_repo` loses its `owner` argument (TS); `test/create-repo.test.ts` replaced by `test/no-org-create.test.ts`. Acceptance criteria: issue 1124, note 2 (AC1-AC8, each cited by its tests as `1124/AC<n>`). Try before this pull request: mesh-controller.try build-1792335551733911180 passed at 1176163 (Go and TypeScript parts, 59 s). Delivery: moves the gitea module on novox. After it, the operator approves the config value `repositories` listing the existing repositories and `mesh-delivery`. Reviewed-by: reviewer-1124@shanks at 11761637cf81f118c4f64d5fed6171eed85c8dea

mesh-tools added 4 commits 2026-10-18 15:01:40 +00:00

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) 94b49a296f

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) df275b3c6e

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) 8c587d0f00

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) 11761637cf

mesh-tools commented 2026-10-18 15:01:50 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@11761637cf81 — delivered since 2026-10-18T15:08:48Z

Delivery plan — builds gitea → novox; no bus step

• tier 0: gitea
• novox: receives gitea
• gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it
• gitea keeps data (ADR 0233): what it holds is backed up before it moves

Machines

• gitea on every machine running it: sent

Transitions

• 2026-10-18 15:01 (new) → proposed (announced): novox/mesh-catalog#363's head announced
• 2026-10-18 15:04 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-18 15:04 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-18 15:05 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-18 15:05 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
• 2026-10-18 15:08 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@11761637cf81` — **delivered** since 2026-10-18T15:08:48Z **Delivery plan** — builds gitea → novox; no bus step - tier 0: gitea - novox: receives gitea - gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - gitea on every machine running it: sent **Transitions** - 2026-10-18 15:01 (new) → proposed (announced): novox/mesh-catalog#363's head announced - 2026-10-18 15:04 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-18 15:04 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-18 15:05 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-18 15:05 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-18 15:08 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools commented 2026-10-18 15:04:22 +00:00

Author

Member

Copy Link

Copy Source

Merge check at 11761637
Judged: head 11761637cf81 merged into trunk e47d0694c752; read beside it: mesh-controller 48e9656c670b, mesh-controller-main 48e9656c670b, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5

• mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: gitea)
• mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds gitea → novox; no bus step

• tier 0: gitea
• novox: receives gitea
• gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it
• gitea keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on ace as build-1792335704603345800 (builds --log build-1792335704603345800).

✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.481045ms)
✔ a start heard after the verdict writes nothing (0.427303ms)
✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.549863ms)
✔ an old run's verdict redelivered after a recheck's pending is not written over it (0.935999ms)
[gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check the forge holds pending; not written
[gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check now pending; not written
✔ an old run's verdict in flight when the recheck comes lands before the recheck's pending (3.409647ms)
✔ a rechecked head says where its new run is: building on which machine (0.717949ms)
✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.558279ms)
✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.582294ms)
✔ a recheck the forge does not take fails its caller, and the head is as it was (0.538071ms)
✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (10.002429ms)
✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (0.280648ms)
✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (1.490331ms)
✔ a repository as the mesh clones it is told from another (0.264638ms)
✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (5.787327ms)
✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (48.082947ms)
✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (15.721747ms)
✔ gitea_api still writes what an author writes (5.465022ms)
✔ gitea_branch_protection_set only strengthens (13.975926ms)
✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (45.55132ms)
✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (142.213527ms)
✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (16.667495ms)
✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (13.117534ms)
✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (27.058744ms)
✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (56.285383ms)
✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (21.716294ms)
✔ gitea_api sends the path it judged, and refuses moving a pull request's base (4.112448ms)
✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (6.905919ms)
✔ a rule named for a branch is not made weaker than the glob rule that guards it now (14.289695ms)
✔ a repository owner or name is never another path (0.256181ms)
✔ the judges, without a forge (0.391455ms)
✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.269397ms)
✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (1.751963ms)
✔ gitea_api never approves a pull request nor requests changes: those are the operator's (2.422273ms)
✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.93283ms)
✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each head approved (81.166926ms)
✔ gitea_merge_pull_request refuses a head the Approve did not name (20.170388ms)
✔ a group of two merges in one pass: the sibling's merge of the composed head does not stop the member's merge (issue 1049) (15.982266ms)
✔ gitea_create_repo has no owner argument and posts only to the tools' own user's repositories (1124/AC8) (45.738921ms)
✔ the tools' team cannot create in the organisation and its token holds no write:organization (1124/AC8) (0.350569ms)
✔ no ready mark, trusted ready-authors setting or approval-by-mark rule is left in the module (9.847068ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (31.154221ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.510098ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (14.220425ms)
✔ a lookup the forge refuses is thrown, not read as no module (3.461106ms)
✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (4.962515ms)
✔ a new head beyond the newest 20 open pull requests is announced, exactly once (57.434042ms)
✔ a pass pages until it reaches back past its floor, and no further (25.986849ms)
✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (27.431855ms)
✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (7.249715ms)
✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (3.254357ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (3.664508ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.288532ms)
✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.658478ms)
✔ another branch's body carries no merge whitelist (0.238088ms)
✔ the rule main is put right in the forge's own words: the body a setup sends carries no status checks of its own (0.320503ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (22.521407ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.118131ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.815723ms)
✔ no verdict sets warning on a required check; only a person's decision fails (1.143449ms)
✔ a commit status is set on the commit, under the merge check's context (40.155308ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.454625ms)
✔ a head announced is pending in the build queue, since the local time it was announced (0.361589ms)
✔ a composed verdict sets every member's gate at its own head, naming its trunk and the group (0.516842ms)
✔ a member's own verdict with a composed gate layer leaves the gate to the composed verdict, in either order (0.502465ms)
✔ the vault's token is used, a setting of it is ignored and said once, without its value (2.896322ms)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 at bbbbbbbbbbbb, it is now at dddddddddddd: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was closed unmerged: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 merged onto cccccccccccc, its main is now eeeeeeeeeeee: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-host's main moved from 444444444444 to 333333333333: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head dddddddddddd onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382)
✔ both statuses name the siblings the verdict read, keeping the verdict word and the start of its reason within 140 characters (2.166713ms)
✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (0.387819ms)
✔ a verdict without siblings is said exactly as before (an older controller) (0.742516ms)
✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (0.982496ms)
✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (2.26157ms)
✔ a sibling closed unmerged puts the member's verdict out of date (0.306616ms)
✔ a move of the sibling's base puts it out of date, naming both commits (0.381697ms)
✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.568188ms)
✔ a merge of another head, or onto another base, is a move (0.751222ms)
✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.67048ms)
✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.582054ms)
✔ the group rule names every missing thing: the group status at each head read, and each head the Approve does not cover (1.268544ms)
✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.243949ms)
✔ without the composed verdict's siblings, a sibling's own merge of its new head is a move (the pin of issue 1049) (0.275117ms)
✔ a composed verdict names the siblings of each member at the heads and base commits it composed, so a sibling's own merge of its new head is no move (issue 1049) (0.761672ms)
✔ a composed verdict keeps nothing for a member it cannot name, and a group of one is none (issue 1049) (0.248797ms)
✔ a consumer that asks nothing, or write, publishes: the package team (1.518574ms)
✔ a consumer that asks to read joins the readers, who write no package (0.44688ms)
✔ a reader is made, put on the readers team, and taken off the package team (0.555784ms)
✔ a publisher is made and put on the package team, as before (0.216527ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (32.23848ms)
✔ second start: reuses the kept token, mints nothing (19.844987ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (22.053607ms)
✔ a token kept with write:admin by an earlier build is minted again without it at the next start, and the forge drops the old one (26.612707ms)
✔ a kept token lacking a scope the tools need: the forge refuses the call for the scope, the token is re-minted with the whole list, and the call goes through (25.174944ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (21.11839ms)
✔ concurrent first calls share one mint (12.963163ms)
✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (15.627461ms)
✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (76.837739ms)
✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (7.196775ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (14.476528ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.588506ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (20.605305ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.200215ms)
✔ nothing to mint with and no token: the client says what is missing (0.170691ms)
[gitea] no tools — no Gitea token, and nothing to mint one with — set MESH_GITEA_TOKEN, or MESH_GITEA_ADMIN_USER, MESH_GITEA_ADMIN_PASSWORD_FILE, MESH_GITEA_STATE_DIR
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-x8Ty9a/state/token
✔ the tools register once there is a way to a token, and the first call mints it (26.543417ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-mx23rS/state/token
✔ a pull request can be closed, read and cleaned up through the tools (37.460933ms)
[gitea] no token kept — minting one
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-hMTNck/state/token
✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (65.044254ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-NThhDp/state/token
✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (42.253793ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-nWysld/state/token
✔ what a base's protection asks is read from the branch, which the tools' account may read, not from the rules' list it may not (44.658972ms)
[gitea] the kept token was minted with other scopes than the tools take now — minting one with them
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-CQDGno/state/token
[gitea] deleted 1 token(s) named "mesh-tools" the admin account "mesh-admin" held: the tools act as "mesh-tools" now
✔ the administrator's token from before goes: a kept admin token is minted again for the tools' account, and the forge drops the old one (41.939911ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-hkDhpW/state/token
✔ a tools' account someone made an administrator is made a plain account again at the next mint (35.87863ms)
✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.79285ms)
✔ the manifest hands the tools their account, and the Go forge bundle holds no administrator password (0.671512ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-twrnBb/state/token
✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (37.618671ms)
[gitea] no token kept — minting one
✔ a mint that fails leaves the administrator's old token in place: the tools are never left without one (25.647142ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-3rMM8y/state/token
[gitea] FAILED to delete the token(s) named "mesh-tools" the admin account "mesh-admin" holds — tried again at the next start: Gitea DELETE /users/mesh-admin/tokens/902 (named mesh-tools): 500 {"message":"the forge is not well"}
✔ an old token that cannot be deleted after the mint is said, the new token kept, and deleted at the next start (43.034409ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-htKtfK/state/token
✔ a team another process made between the look and the create is found, not a failure (36.696697ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-FSBXc2/state/token
✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (35.200456ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-1zErhu/state/token
✔ a glob rule covering main keeps its statuses when main is given a rule of its own name (issue 948, review round 1) (39.438871ms)
✔ a start with the token kept still puts main's rules right: the module's start asks for it each time (issue 948, review round 1) (13.442974ms)
[gitea] novox/mesh-host's main moved from a2c2c35bbbbb to d28ca95ccccc: 25 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323)
[gitea] novox/mesh-host's main moved from d28ca95ccccc to ffffffffffff: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323)
[gitea] novox/mesh-host: whether a trunk moved could not be weighed, so it is weighed again on the next pass — the forge is away
[gitea] novox/mesh-host's main moved from a2c2c35bbbbb to d28ca95ccccc: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323)
[gitea] novox/mesh-controller's feat/57-config-and-provisioning moved from eeeeeeeeeeee to d28ca95ccccc: 1 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323)
✔ both statuses say the head and the trunk commit the verdict judged, first, whatever the summary's length (2.093064ms)
✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (0.911703ms)
✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (3.10137ms)
✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.383872ms)
✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.428516ms)
✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.275628ms)
✔ a verdict that landed out of date keeps its account on the pull request (0.23433ms)
✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.405623ms)
✔ a signed event is published on the bus and acted on once (49.739ms)
✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (30.621249ms)
✔ an event and the poll seeing the same head announce it once (0.375806ms)
✔ each forge event is named in the module's stream and trimmed (0.597152ms)
✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.279044ms)
✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (0.942561ms)
✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (3.280325ms)
✔ a forge that makes no system webhook is said, never taken as heard (0.603925ms)
✔ the receiver tells what it verified and what it refused (6.231131ms)
✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (0.896274ms)
✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.341432ms)
✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.272973ms)
✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.186169ms)
✔ a pull request's edit event carries its description, and no other pull request event does (issue 1079) (0.194976ms)
ℹ tests 157
ℹ suites 0
ℹ pass 157
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 743.672562

**Merge check** at `11761637` Judged: head `11761637cf81` merged into trunk `e47d0694c752`; read beside it: mesh-controller `48e9656c670b`, mesh-controller-main `48e9656c670b`, mesh-host `6469e8238443`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: gitea) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds gitea → novox; no bus step - tier 0: gitea - novox: receives gitea - gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on ace as `build-1792335704603345800` (`builds --log build-1792335704603345800`). ``` ✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.481045ms) ✔ a start heard after the verdict writes nothing (0.427303ms) ✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.549863ms) ✔ an old run's verdict redelivered after a recheck's pending is not written over it (0.935999ms) [gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check the forge holds pending; not written [gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check now pending; not written ✔ an old run's verdict in flight when the recheck comes lands before the recheck's pending (3.409647ms) ✔ a rechecked head says where its new run is: building on which machine (0.717949ms) ✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.558279ms) ✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.582294ms) ✔ a recheck the forge does not take fails its caller, and the head is as it was (0.538071ms) ✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (10.002429ms) ✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (0.280648ms) ✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (1.490331ms) ✔ a repository as the mesh clones it is told from another (0.264638ms) ✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (5.787327ms) ✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (48.082947ms) ✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (15.721747ms) ✔ gitea_api still writes what an author writes (5.465022ms) ✔ gitea_branch_protection_set only strengthens (13.975926ms) ✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (45.55132ms) ✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (142.213527ms) ✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (16.667495ms) ✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (13.117534ms) ✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (27.058744ms) ✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (56.285383ms) ✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (21.716294ms) ✔ gitea_api sends the path it judged, and refuses moving a pull request's base (4.112448ms) ✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (6.905919ms) ✔ a rule named for a branch is not made weaker than the glob rule that guards it now (14.289695ms) ✔ a repository owner or name is never another path (0.256181ms) ✔ the judges, without a forge (0.391455ms) ✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.269397ms) ✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (1.751963ms) ✔ gitea_api never approves a pull request nor requests changes: those are the operator's (2.422273ms) ✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.93283ms) ✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each head approved (81.166926ms) ✔ gitea_merge_pull_request refuses a head the Approve did not name (20.170388ms) ✔ a group of two merges in one pass: the sibling's merge of the composed head does not stop the member's merge (issue 1049) (15.982266ms) ✔ gitea_create_repo has no owner argument and posts only to the tools' own user's repositories (1124/AC8) (45.738921ms) ✔ the tools' team cannot create in the organisation and its token holds no write:organization (1124/AC8) (0.350569ms) ✔ no ready mark, trusted ready-authors setting or approval-by-mark rule is left in the module (9.847068ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (31.154221ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.510098ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (14.220425ms) ✔ a lookup the forge refuses is thrown, not read as no module (3.461106ms) ✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (4.962515ms) ✔ a new head beyond the newest 20 open pull requests is announced, exactly once (57.434042ms) ✔ a pass pages until it reaches back past its floor, and no further (25.986849ms) ✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (27.431855ms) ✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (7.249715ms) ✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (3.254357ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (3.664508ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.288532ms) ✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.658478ms) ✔ another branch's body carries no merge whitelist (0.238088ms) ✔ the rule main is put right in the forge's own words: the body a setup sends carries no status checks of its own (0.320503ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (22.521407ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.118131ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.815723ms) ✔ no verdict sets warning on a required check; only a person's decision fails (1.143449ms) ✔ a commit status is set on the commit, under the merge check's context (40.155308ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.454625ms) ✔ a head announced is pending in the build queue, since the local time it was announced (0.361589ms) ✔ a composed verdict sets every member's gate at its own head, naming its trunk and the group (0.516842ms) ✔ a member's own verdict with a composed gate layer leaves the gate to the composed verdict, in either order (0.502465ms) ✔ the vault's token is used, a setting of it is ignored and said once, without its value (2.896322ms) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 at bbbbbbbbbbbb, it is now at dddddddddddd: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was closed unmerged: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 merged onto cccccccccccc, its main is now eeeeeeeeeeee: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-host's main moved from 444444444444 to 333333333333: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head dddddddddddd onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382) ✔ both statuses name the siblings the verdict read, keeping the verdict word and the start of its reason within 140 characters (2.166713ms) ✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (0.387819ms) ✔ a verdict without siblings is said exactly as before (an older controller) (0.742516ms) ✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (0.982496ms) ✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (2.26157ms) ✔ a sibling closed unmerged puts the member's verdict out of date (0.306616ms) ✔ a move of the sibling's base puts it out of date, naming both commits (0.381697ms) ✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.568188ms) ✔ a merge of another head, or onto another base, is a move (0.751222ms) ✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.67048ms) ✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.582054ms) ✔ the group rule names every missing thing: the group status at each head read, and each head the Approve does not cover (1.268544ms) ✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.243949ms) ✔ without the composed verdict's siblings, a sibling's own merge of its new head is a move (the pin of issue 1049) (0.275117ms) ✔ a composed verdict names the siblings of each member at the heads and base commits it composed, so a sibling's own merge of its new head is no move (issue 1049) (0.761672ms) ✔ a composed verdict keeps nothing for a member it cannot name, and a group of one is none (issue 1049) (0.248797ms) ✔ a consumer that asks nothing, or write, publishes: the package team (1.518574ms) ✔ a consumer that asks to read joins the readers, who write no package (0.44688ms) ✔ a reader is made, put on the readers team, and taken off the package team (0.555784ms) ✔ a publisher is made and put on the package team, as before (0.216527ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (32.23848ms) ✔ second start: reuses the kept token, mints nothing (19.844987ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (22.053607ms) ✔ a token kept with write:admin by an earlier build is minted again without it at the next start, and the forge drops the old one (26.612707ms) ✔ a kept token lacking a scope the tools need: the forge refuses the call for the scope, the token is re-minted with the whole list, and the call goes through (25.174944ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (21.11839ms) ✔ concurrent first calls share one mint (12.963163ms) ✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (15.627461ms) ✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (76.837739ms) ✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (7.196775ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (14.476528ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.588506ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (20.605305ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.200215ms) ✔ nothing to mint with and no token: the client says what is missing (0.170691ms) [gitea] no tools — no Gitea token, and nothing to mint one with — set MESH_GITEA_TOKEN, or MESH_GITEA_ADMIN_USER, MESH_GITEA_ADMIN_PASSWORD_FILE, MESH_GITEA_STATE_DIR [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-x8Ty9a/state/token ✔ the tools register once there is a way to a token, and the first call mints it (26.543417ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-mx23rS/state/token ✔ a pull request can be closed, read and cleaned up through the tools (37.460933ms) [gitea] no token kept — minting one [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-hMTNck/state/token ✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (65.044254ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-NThhDp/state/token ✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (42.253793ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-nWysld/state/token ✔ what a base's protection asks is read from the branch, which the tools' account may read, not from the rules' list it may not (44.658972ms) [gitea] the kept token was minted with other scopes than the tools take now — minting one with them [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-CQDGno/state/token [gitea] deleted 1 token(s) named "mesh-tools" the admin account "mesh-admin" held: the tools act as "mesh-tools" now ✔ the administrator's token from before goes: a kept admin token is minted again for the tools' account, and the forge drops the old one (41.939911ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-hkDhpW/state/token ✔ a tools' account someone made an administrator is made a plain account again at the next mint (35.87863ms) ✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.79285ms) ✔ the manifest hands the tools their account, and the Go forge bundle holds no administrator password (0.671512ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-twrnBb/state/token ✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (37.618671ms) [gitea] no token kept — minting one ✔ a mint that fails leaves the administrator's old token in place: the tools are never left without one (25.647142ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-3rMM8y/state/token [gitea] FAILED to delete the token(s) named "mesh-tools" the admin account "mesh-admin" holds — tried again at the next start: Gitea DELETE /users/mesh-admin/tokens/902 (named mesh-tools): 500 {"message":"the forge is not well"} ✔ an old token that cannot be deleted after the mint is said, the new token kept, and deleted at the next start (43.034409ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-htKtfK/state/token ✔ a team another process made between the look and the create is found, not a failure (36.696697ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-FSBXc2/state/token ✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (35.200456ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-1zErhu/state/token ✔ a glob rule covering main keeps its statuses when main is given a rule of its own name (issue 948, review round 1) (39.438871ms) ✔ a start with the token kept still puts main's rules right: the module's start asks for it each time (issue 948, review round 1) (13.442974ms) [gitea] novox/mesh-host's main moved from a2c2c35bbbbb to d28ca95ccccc: 25 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323) [gitea] novox/mesh-host's main moved from d28ca95ccccc to ffffffffffff: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323) [gitea] novox/mesh-host: whether a trunk moved could not be weighed, so it is weighed again on the next pass — the forge is away [gitea] novox/mesh-host's main moved from a2c2c35bbbbb to d28ca95ccccc: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323) [gitea] novox/mesh-controller's feat/57-config-and-provisioning moved from eeeeeeeeeeee to d28ca95ccccc: 1 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323) ✔ both statuses say the head and the trunk commit the verdict judged, first, whatever the summary's length (2.093064ms) ✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (0.911703ms) ✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (3.10137ms) ✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.383872ms) ✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.428516ms) ✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.275628ms) ✔ a verdict that landed out of date keeps its account on the pull request (0.23433ms) ✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.405623ms) ✔ a signed event is published on the bus and acted on once (49.739ms) ✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (30.621249ms) ✔ an event and the poll seeing the same head announce it once (0.375806ms) ✔ each forge event is named in the module's stream and trimmed (0.597152ms) ✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.279044ms) ✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (0.942561ms) ✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (3.280325ms) ✔ a forge that makes no system webhook is said, never taken as heard (0.603925ms) ✔ the receiver tells what it verified and what it refused (6.231131ms) ✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (0.896274ms) ✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.341432ms) ✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.272973ms) ✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.186169ms) ✔ a pull request's edit event carries its description, and no other pull request event does (issue 1079) (0.194976ms) ℹ tests 157 ℹ suites 0 ℹ pass 157 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 743.672562 ```

mesh-tools merged commit cfb90d7b2f into main 2026-10-18 15:05:04 +00:00

mesh-tools deleted branch fix/1124-repositories-config 2026-10-18 15:05:05 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#363