Feature agents-write-git, step 1: agents write with their own accounts, main stays closed, a merge into main waits for the operator (issues 948, 954) #338

2026-10-16T19:38:49Z

mesh-tools commented

2026-10-16 19:38:49 +00:00

Feature agents-write-git, step 1 (hq playbook 07; ADR 0398).

Issue 948, ADR 0398 §1 (b0f86671): the agent's token is minted with write:repository and write:issue, and agent-<node> joins one agents team with write on the org's repositories (the forge tools' team's shape).
§2 (7807135a, 789aa013, 3cdea45f): every repository's main rule refuses pushes and lets only the forge tools' account merge; gitea puts it right at every start and every 10 minutes with the admin login, keeping a covering glob rule's required checks; the guard refuses weakening it.
§4 (417f6956): mesh-delivery merges only into main; a ready mark on another base is left to its author and said once.
§3 (f61e00ae, 4cccd817): a merge into main waits for the operator's Approve over the operator-channel (the knowledge base's warrant pattern: digest, option, level, expiry, Performs); one ask per group; a push to any member ends the ask and its Approve; Decline clears the mark; an expired ask is asked again once.
Issue 954 (4215b405, from feature providers-after-switch-on, at the operator's request): the provisioner client reads the controller's whole plan (at, from, as, names, credential-tool); since mesh-controller #363 it refused gitea's, keycloak's and claude-code's plans.

Reviewed locally by review-awg@novox (larger model), two rounds: round 1 found 3 faults (fixed), round 2 approves. Go unit tests green; gitea's TypeScript tests run in the merge check (not runnable locally).

Not in this step: the terminal Approve (issue 953), git over SSH (ADR 0399, issue 955, step 2). Per ADR 0398 the merge waits for the operator's approval.

Feature agents-write-git, step 1 (hq playbook 07; ADR 0398). - **Issue 948, ADR 0398 §1** (b0f86671): the agent's token is minted with write:repository and write:issue, and `agent-<node>` joins one `agents` team with write on the org's repositories (the forge tools' team's shape). - **§2** (7807135a, 789aa013, 3cdea45f): every repository's main rule refuses pushes and lets only the forge tools' account merge; gitea puts it right at every start and every 10 minutes with the admin login, keeping a covering glob rule's required checks; the guard refuses weakening it. - **§4** (417f6956): mesh-delivery merges only into main; a ready mark on another base is left to its author and said once. - **§3** (f61e00ae, 4cccd817): a merge into main waits for the operator's Approve over the operator-channel (the knowledge base's warrant pattern: digest, option, level, expiry, Performs); one ask per group; a push to any member ends the ask and its Approve; Decline clears the mark; an expired ask is asked again once. - **Issue 954** (4215b405, from feature providers-after-switch-on, at the operator's request): the provisioner client reads the controller's whole plan (at, from, as, names, credential-tool); since mesh-controller #363 it refused gitea's, keycloak's and claude-code's plans. Reviewed locally by review-awg@novox (larger model), two rounds: round 1 found 3 faults (fixed), round 2 approves. Go unit tests green; gitea's TypeScript tests run in the merge check (not runnable locally). Not in this step: the terminal Approve (issue 953), git over SSH (ADR 0399, issue 955, step 2). Per ADR 0398 the merge waits for the operator's approval.

mesh-tools added 10 commits 2026-10-16 19:38:49 +00:00

Give the agent's token write scopes and the agents write team (issue 948, ADR 0398 §1) b0f86671b6

Merge only into main: a ready mark on another base is left to its author (issue 948, ADR 0398 §4) 417f69567c

Main takes no push and only mesh-tools merges, set by setup and guarded (issue 948, ADR 0398 §2) 7807135a1b

Keep the guard's push wording for main (issue 948) 789aa0133f

Ask the operator to Approve a merge into main and merge only on the warrant (issue 948, ADR 0398 §3) f61e00aeaa

Merge branch 'feat/agents-write-git' into feat/agents-write-git-d 0bfece71da

Read the whole plan the controller writes: at, from, as, names and credential-tool (issue 954) 4215b40547

The client decodes a plan strictly, and since the controller carries these fields
(issues 923 and 928) it refused the plans of gitea, keycloak and claude-code.

Keep main's rule right at every start and copy a covering glob's checks (issue 948, review round 1) 3cdea45f90

End a group's ask and Approve when any member is pushed (issue 948, ADR 0398 §3) 4cccd817a0

Merge branch 'feat/agents-write-git' into feat/agents-write-git-d

mesh/merge-gate head 9acd1f51c5cf merged into trunk 8d012fe4e270 — pass: builds gitea, mesh-delivery, mesh-provisioner-client → ace, g14, novox, shanks; no…

Details

mesh/repo-check head 9acd1f51c5cf merged into trunk 8d012fe4e270 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…

Details

mesh/delivery delivered

Details

9acd1f51c5

mesh-tools commented

2026-10-16 19:38:55 +00:00

Delivery novox/mesh-catalog@9acd1f51c5cf — delivered since 2026-10-16T19:49:53Z

Delivery plan — builds gitea, mesh-delivery, mesh-provisioner-client → ace, g14, novox, shanks; no bus step

tier 0: gitea, mesh-delivery, mesh-provisioner-client
ace: receives mesh-provisioner-client
g14: receives mesh-provisioner-client
novox: receives gitea, mesh-delivery, mesh-provisioner-client
shanks: receives mesh-provisioner-client
gitea provides npm-package-registry, git, gitea-read: its consumers are sent again after it
gitea keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-provisioner-client is judged on its first machine

Machines

gitea on every machine running it: sent
mesh-delivery on every machine running it: sent
mesh-provisioner-client on every machine running it: sent

Transitions

2026-10-16 19:38 (new) → proposed (announced): novox/mesh-catalog#338's head announced
2026-10-16 19:42 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-16 19:42 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-16 19:45 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-16 19:45 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-16 19:49 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.

**Delivery** `novox/mesh-catalog@9acd1f51c5cf` — **delivered** since 2026-10-16T19:49:53Z **Delivery plan** — builds gitea, mesh-delivery, mesh-provisioner-client → ace, g14, novox, shanks; no bus step - tier 0: gitea, mesh-delivery, mesh-provisioner-client - ace: receives mesh-provisioner-client - g14: receives mesh-provisioner-client - novox: receives gitea, mesh-delivery, mesh-provisioner-client - shanks: receives mesh-provisioner-client - gitea provides npm-package-registry, git, gitea-read: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-provisioner-client is judged on its first machine **Machines** - gitea on every machine running it: sent - mesh-delivery on every machine running it: sent - mesh-provisioner-client on every machine running it: sent **Transitions** - 2026-10-16 19:38 (new) → proposed (announced): novox/mesh-catalog#338's head announced - 2026-10-16 19:42 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 19:42 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 19:45 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-16 19:45 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-16 19:49 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-16 19:42:43 +00:00

Merge check at 9acd1f51
Judged: head 9acd1f51c5cf merged into trunk 8d012fe4e270; read beside it: mesh-controller 53a3c91f53ce, mesh-controller-main 53a3c91f53ce, mesh-host cd13f7726ef0, mesh-tools 7412c5b6c9c5

mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: gitea, mesh-delivery, mesh-provisioner-client)
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, mesh-delivery, mesh-provisioner-client → ace, g14, novox, shanks; no bus step

tier 0: gitea, mesh-delivery, mesh-provisioner-client
ace: receives mesh-provisioner-client
g14: receives mesh-provisioner-client
novox: receives gitea, mesh-delivery, mesh-provisioner-client
shanks: receives mesh-provisioner-client
gitea provides npm-package-registry, git, gitea-read: its consumers are sent again after it
gitea keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-provisioner-client is judged on its first machine
read by no module's build: modules/mesh-delivery/cmd/mesh-delivery/approval_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/manifest_test.go, modules/mesh-delivery/cmd/mesh-delivery/operator_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-provisioner-client/cmd/mesh-provisioner-client/whole_plan_test.go

Run by the build seat on shanks as build-1792179531703073074 (builds --log build-1792179531703073074).

✔ the accounts that may mark are the setting's, and only the mesh's own when it cannot be read (0.821462ms)
✔ the newest status of each context is kept, with what it said, when and by whom (24.122235ms)
✔ a commit merges only when every required status is a success; a warning blocks (0.74416ms)
✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.313175ms)
✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.971404ms)
✔ a note line is appended once, as the forge's user, in its own repository (19.642642ms)
✔ a note that cannot be written is said, never read as written (0.389886ms)
✔ one view per pull request, found by its marker; only the mesh's statuses (0.559628ms)
✔ a build machine taking the check is said on the head: building on which machine, since the local time (23.68976ms)
✔ the verdict heard while a 'building' write is in flight lands last and stays (9.267632ms)
[gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check now pending; not written
✔ the verdict written while a start's read of the forge is in flight stays the newest status (1.727405ms)
✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.68928ms)
✔ a start heard after the verdict writes nothing (0.638759ms)
✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.753981ms)
✔ an old run's verdict redelivered after a recheck's pending is not written over it (1.115426ms)
[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.232176ms)
✔ a rechecked head says where its new run is: building on which machine (1.129366ms)
✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.853762ms)
✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.6862ms)
✔ a recheck the forge does not take fails its caller, and the head is as it was (0.659419ms)
✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (10.059874ms)
✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (0.314954ms)
✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (3.826744ms)
✔ a repository as the mesh clones it is told from another (0.355815ms)
✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (4.610536ms)
✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (44.619089ms)
✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (23.917332ms)
✔ gitea_api still writes what an author writes (8.892058ms)
✔ gitea_branch_protection_set only strengthens (15.227678ms)
✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (51.497538ms)
✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (135.921116ms)
✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (15.803576ms)
✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (13.786097ms)
✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (26.300957ms)
✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (54.696263ms)
✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (20.869888ms)
✔ gitea_api sends the path it judged, and refuses moving a pull request's base (4.103128ms)
✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (6.644065ms)
✔ a rule named for a branch is not made weaker than the glob rule that guards it now (12.260995ms)
✔ a repository owner or name is never another path (0.320054ms)
✔ the judges, without a forge (0.333334ms)
✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.230293ms)
✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (1.571253ms)
✔ gitea_api never approves a pull request nor requests changes: those are the operator's (1.183497ms)
✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.668027ms)
✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each sibling head reviewed (80.866098ms)
✔ a verdict put out of date by a sibling's move is refused in its own words, and asked again once (20.080937ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (34.033408ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.617349ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (13.633125ms)
✔ a lookup the forge refuses is thrown, not read as no module (5.026082ms)
✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (6.601124ms)
✔ a new head beyond the newest 20 open pull requests is announced, exactly once (66.993419ms)
✔ a pass pages until it reaches back past its floor, and no further (24.243797ms)
✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (23.795541ms)
✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (6.590565ms)
✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (4.516535ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (4.299371ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.378116ms)
✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.846002ms)
✔ another branch's body carries no merge whitelist (0.291534ms)
✔ 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.351555ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (18.638317ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.221438ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.785011ms)
✔ no verdict sets warning on a required check; only a person's decision fails (1.137396ms)
✔ a commit status is set on the commit, under the merge check's context (47.835735ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.454396ms)
✔ a head announced is pending in the build queue, since the local time it was announced (0.285854ms)
✔ the vault's token is used, a setting of it is ignored and said once, without its value (3.165366ms)
[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)
✔ both statuses name the siblings the verdict read, keeping the verdict word and the start of its reason within 140 characters (2.329913ms)
✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (0.441706ms)
✔ a verdict without siblings is said exactly as before (an older controller) (0.882863ms)
✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (1.021085ms)
✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (3.216396ms)
✔ a sibling closed unmerged puts the member's verdict out of date (0.421156ms)
✔ a move of the sibling's base puts it out of date, naming both commits (0.447346ms)
✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (3.742863ms)
✔ a merge of another head, or onto another base, is a move (0.982445ms)
✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.769611ms)
✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.67435ms)
✔ the group rule names every missing thing: the group status at each head read, and each sibling head's review (0.987484ms)
✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.264764ms)
✔ a consumer that asks nothing, or write, publishes: the package team (1.572802ms)
✔ a consumer that asks to read joins the readers, who write no package (0.511217ms)
✔ a reader is made, put on the readers team, and taken off the package team (0.590688ms)
✔ a publisher is made and put on the package team, as before (0.203153ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (35.752792ms)
✔ second start: reuses the kept token, mints nothing (27.93773ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (26.527899ms)
✔ 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 (31.393009ms)
✔ 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 (27.720257ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (22.902638ms)
✔ concurrent first calls share one mint (13.197659ms)
✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (15.661194ms)
✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (64.071458ms)
✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (7.108371ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (13.450583ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.955903ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (20.346891ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.260972ms)
✔ nothing to mint with and no token: the client says what is missing (0.187113ms)
[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-RVtYuu/state/token
✔ the tools register once there is a way to a token, and the first call mints it (28.939955ms)
[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-R2qB29/state/token
✔ a pull request can be closed, read and cleaned up through the tools (37.960294ms)
[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-fNduG1/state/token
✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (74.562598ms)
[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-zG2Bmh/state/token
✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (46.582667ms)
[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-cpfLgk/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 (43.646505ms)
[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-8oANv5/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 (43.3248ms)
[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-yt2xOy/state/token
✔ a tools' account someone made an administrator is made a plain account again at the next mint (36.046977ms)
✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.69182ms)
✔ the manifest hands the tools their account, and the merge-ready authors name it rather than the administrator (0.825842ms)
[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-HGkX0m/state/token
✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (39.989262ms)
[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 (26.820914ms)
[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-bamxZR/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 (45.580552ms)
[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-XSjwHc/state/token
✔ a team another process made between the look and the create is found, not a failure (36.97584ms)
[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-IcKYqm/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.846434ms)
[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-pH0qRA/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) (36.826368ms)
✔ 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) (12.862024ms)
[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 (3.391758ms)
✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (4.091108ms)
✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (4.92016ms)
✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.521608ms)
✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.621999ms)
✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.394736ms)
✔ a verdict that landed out of date keeps its account on the pull request (0.348305ms)
✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.565318ms)
✔ a signed event is published on the bus and acted on once (61.328619ms)
✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (40.080145ms)
✔ an event and the poll seeing the same head announce it once (0.491177ms)
✔ each forge event is named in the module's stream and trimmed (0.71522ms)
✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.775106ms)
✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.40692ms)
✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (4.704307ms)
✔ a forge that makes no system webhook is said, never taken as heard (0.891043ms)
✔ the receiver tells what it verified and what it refused (10.094685ms)
✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (1.583493ms)
✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.562078ms)
✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.439447ms)
✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.247924ms)
ℹ tests 147
ℹ suites 0
ℹ pass 147
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 769.150674

**Merge check** at `9acd1f51` Judged: head `9acd1f51c5cf` merged into trunk `8d012fe4e270`; read beside it: mesh-controller `53a3c91f53ce`, mesh-controller-main `53a3c91f53ce`, mesh-host `cd13f7726ef0`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: gitea, mesh-delivery, mesh-provisioner-client) - `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, mesh-delivery, mesh-provisioner-client → ace, g14, novox, shanks; no bus step - tier 0: gitea, mesh-delivery, mesh-provisioner-client - ace: receives mesh-provisioner-client - g14: receives mesh-provisioner-client - novox: receives gitea, mesh-delivery, mesh-provisioner-client - shanks: receives mesh-provisioner-client - gitea provides npm-package-registry, git, gitea-read: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-provisioner-client is judged on its first machine - read by no module's build: modules/mesh-delivery/cmd/mesh-delivery/approval_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/manifest_test.go, modules/mesh-delivery/cmd/mesh-delivery/operator_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-provisioner-client/cmd/mesh-provisioner-client/whole_plan_test.go Run by the build seat on shanks as `build-1792179531703073074` (`builds --log build-1792179531703073074`). ``` ✔ the accounts that may mark are the setting's, and only the mesh's own when it cannot be read (0.821462ms) ✔ the newest status of each context is kept, with what it said, when and by whom (24.122235ms) ✔ a commit merges only when every required status is a success; a warning blocks (0.74416ms) ✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.313175ms) ✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.971404ms) ✔ a note line is appended once, as the forge's user, in its own repository (19.642642ms) ✔ a note that cannot be written is said, never read as written (0.389886ms) ✔ one view per pull request, found by its marker; only the mesh's statuses (0.559628ms) ✔ a build machine taking the check is said on the head: building on which machine, since the local time (23.68976ms) ✔ the verdict heard while a 'building' write is in flight lands last and stays (9.267632ms) [gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check now pending; not written ✔ the verdict written while a start's read of the forge is in flight stays the newest status (1.727405ms) ✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.68928ms) ✔ a start heard after the verdict writes nothing (0.638759ms) ✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.753981ms) ✔ an old run's verdict redelivered after a recheck's pending is not written over it (1.115426ms) [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.232176ms) ✔ a rechecked head says where its new run is: building on which machine (1.129366ms) ✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.853762ms) ✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.6862ms) ✔ a recheck the forge does not take fails its caller, and the head is as it was (0.659419ms) ✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (10.059874ms) ✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (0.314954ms) ✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (3.826744ms) ✔ a repository as the mesh clones it is told from another (0.355815ms) ✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (4.610536ms) ✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (44.619089ms) ✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (23.917332ms) ✔ gitea_api still writes what an author writes (8.892058ms) ✔ gitea_branch_protection_set only strengthens (15.227678ms) ✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (51.497538ms) ✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (135.921116ms) ✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (15.803576ms) ✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (13.786097ms) ✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (26.300957ms) ✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (54.696263ms) ✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (20.869888ms) ✔ gitea_api sends the path it judged, and refuses moving a pull request's base (4.103128ms) ✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (6.644065ms) ✔ a rule named for a branch is not made weaker than the glob rule that guards it now (12.260995ms) ✔ a repository owner or name is never another path (0.320054ms) ✔ the judges, without a forge (0.333334ms) ✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.230293ms) ✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (1.571253ms) ✔ gitea_api never approves a pull request nor requests changes: those are the operator's (1.183497ms) ✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.668027ms) ✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each sibling head reviewed (80.866098ms) ✔ a verdict put out of date by a sibling's move is refused in its own words, and asked again once (20.080937ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (34.033408ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.617349ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (13.633125ms) ✔ a lookup the forge refuses is thrown, not read as no module (5.026082ms) ✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (6.601124ms) ✔ a new head beyond the newest 20 open pull requests is announced, exactly once (66.993419ms) ✔ a pass pages until it reaches back past its floor, and no further (24.243797ms) ✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (23.795541ms) ✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (6.590565ms) ✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (4.516535ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (4.299371ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.378116ms) ✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.846002ms) ✔ another branch's body carries no merge whitelist (0.291534ms) ✔ 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.351555ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (18.638317ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.221438ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.785011ms) ✔ no verdict sets warning on a required check; only a person's decision fails (1.137396ms) ✔ a commit status is set on the commit, under the merge check's context (47.835735ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.454396ms) ✔ a head announced is pending in the build queue, since the local time it was announced (0.285854ms) ✔ the vault's token is used, a setting of it is ignored and said once, without its value (3.165366ms) [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) ✔ both statuses name the siblings the verdict read, keeping the verdict word and the start of its reason within 140 characters (2.329913ms) ✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (0.441706ms) ✔ a verdict without siblings is said exactly as before (an older controller) (0.882863ms) ✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (1.021085ms) ✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (3.216396ms) ✔ a sibling closed unmerged puts the member's verdict out of date (0.421156ms) ✔ a move of the sibling's base puts it out of date, naming both commits (0.447346ms) ✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (3.742863ms) ✔ a merge of another head, or onto another base, is a move (0.982445ms) ✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.769611ms) ✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.67435ms) ✔ the group rule names every missing thing: the group status at each head read, and each sibling head's review (0.987484ms) ✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.264764ms) ✔ a consumer that asks nothing, or write, publishes: the package team (1.572802ms) ✔ a consumer that asks to read joins the readers, who write no package (0.511217ms) ✔ a reader is made, put on the readers team, and taken off the package team (0.590688ms) ✔ a publisher is made and put on the package team, as before (0.203153ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (35.752792ms) ✔ second start: reuses the kept token, mints nothing (27.93773ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (26.527899ms) ✔ 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 (31.393009ms) ✔ 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 (27.720257ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (22.902638ms) ✔ concurrent first calls share one mint (13.197659ms) ✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (15.661194ms) ✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (64.071458ms) ✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (7.108371ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (13.450583ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.955903ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (20.346891ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.260972ms) ✔ nothing to mint with and no token: the client says what is missing (0.187113ms) [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-RVtYuu/state/token ✔ the tools register once there is a way to a token, and the first call mints it (28.939955ms) [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-R2qB29/state/token ✔ a pull request can be closed, read and cleaned up through the tools (37.960294ms) [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-fNduG1/state/token ✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (74.562598ms) [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-zG2Bmh/state/token ✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (46.582667ms) [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-cpfLgk/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 (43.646505ms) [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-8oANv5/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 (43.3248ms) [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-yt2xOy/state/token ✔ a tools' account someone made an administrator is made a plain account again at the next mint (36.046977ms) ✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.69182ms) ✔ the manifest hands the tools their account, and the merge-ready authors name it rather than the administrator (0.825842ms) [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-HGkX0m/state/token ✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (39.989262ms) [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 (26.820914ms) [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-bamxZR/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 (45.580552ms) [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-XSjwHc/state/token ✔ a team another process made between the look and the create is found, not a failure (36.97584ms) [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-IcKYqm/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.846434ms) [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-pH0qRA/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) (36.826368ms) ✔ 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) (12.862024ms) [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 (3.391758ms) ✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (4.091108ms) ✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (4.92016ms) ✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.521608ms) ✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.621999ms) ✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.394736ms) ✔ a verdict that landed out of date keeps its account on the pull request (0.348305ms) ✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.565318ms) ✔ a signed event is published on the bus and acted on once (61.328619ms) ✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (40.080145ms) ✔ an event and the poll seeing the same head announce it once (0.491177ms) ✔ each forge event is named in the module's stream and trimmed (0.71522ms) ✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.775106ms) ✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.40692ms) ✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (4.704307ms) ✔ a forge that makes no system webhook is said, never taken as heard (0.891043ms) ✔ the receiver tells what it verified and what it refused (10.094685ms) ✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (1.583493ms) ✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.562078ms) ✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.439447ms) ✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.247924ms) ℹ tests 147 ℹ suites 0 ℹ pass 147 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 769.150674 ```

mesh-tools added the mesh/ready label 2026-10-16 19:45:28 +00:00

mesh-tools commented

2026-10-16 19:45:28 +00:00

ready at 9acd1f51c5

Reviewed by review-awg@novox: approved by review-awg (rounds 1-2), both checks green (147 TypeScript tests among them); the operator approved the merge into main in the terminal at 21:43 (ADR 0398). Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at 9acd1f51c5cffbaed2db37f555451218d3917dfb Reviewed by review-awg@novox: approved by review-awg (rounds 1-2), both checks green (147 TypeScript tests among them); the operator approved the merge into main in the terminal at 21:43 (ADR 0398). Marked through mesh-delivery.mark-ready (novox/hq issue 913).

mesh-tools merged commit 5652a14944 into main

2026-10-16 19:45:37 +00:00

mesh-tools deleted branch feat/agents-write-git

2026-10-16 19:45:37 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#338