Give the forge an ssh name of its own, so it no longer merges with the operator's entry for its machine (issue 955, ADR 0409) #343

Merged

mesh-tools merged 1 commits from fix/955-forge-ssh-name into main 2026-10-17 00:05:58 +00:00

Conversation 3 Commits 1 Files Changed 8

+24 -10

mesh-tools commented 2026-10-17 00:02:01 +00:00

Member

Copy Link

Copy Source

Issue 955, ADR 0409 clause 1. After #340-#342, g14's operator account had two Host novox.internal entries (the mesh's 00-mesh shell login, and ssh-client's 10-forge with port 222), so the operator's ssh novox.internal went to the forge on port 222 and was refused.

• gitea's forge-account provider adds ssh_alias (mesh-forge) and host_key to each entry; known_host and ssh_base keep their old values so a machine whose ssh-client has not moved yet keeps working during the delivery (dropped later, ADR 0409).
• ssh-client: Host mesh-forge / HostName <ssh_host> / Port / HostKeyAlias mesh-forge / User git / IdentityFile / IdentitiesOnly; known_hosts line mesh-forge <host_key>; git rewrites the forge's https address to ssh://mesh-forge/.
• Tests updated; the render test failed before the change.

Reviewed (larger model) in 2 rounds, approved at 173d2f4 (tree 7bdbfd0); this forge commit carries the same diff. ADR 0409 clauses 2 and 3 (the key in the agents' account) wait for issue 989.

Issue 955, ADR 0409 clause 1. After #340-#342, g14's operator account had two `Host novox.internal` entries (the mesh's `00-mesh` shell login, and ssh-client's `10-forge` with port 222), so the operator's `ssh novox.internal` went to the forge on port 222 and was refused. - gitea's forge-account provider adds `ssh_alias` (`mesh-forge`) and `host_key` to each entry; `known_host` and `ssh_base` keep their old values so a machine whose ssh-client has not moved yet keeps working during the delivery (dropped later, ADR 0409). - ssh-client: `Host mesh-forge` / `HostName <ssh_host>` / Port / `HostKeyAlias mesh-forge` / User git / IdentityFile / IdentitiesOnly; known_hosts line `mesh-forge <host_key>`; git rewrites the forge's https address to `ssh://mesh-forge/`. - Tests updated; the render test failed before the change. Reviewed (larger model) in 2 rounds, approved at 173d2f4 (tree 7bdbfd0); this forge commit carries the same diff. ADR 0409 clauses 2 and 3 (the key in the agents' account) wait for issue 989.

mesh-tools added 1 commit 2026-10-17 00:02:01 +00:00

Give the forge an ssh name of its own, so it no longer merges with the operator's entry for its machine (issue 955, ADR 0409) 661b83249c

mesh-tools commented 2026-10-17 00:02:07 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@661b83249c2a — delivered since 2026-10-17T00:08:21Z

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

• tier 0: gitea, ssh-client
• ace: receives ssh-client
• g14: receives ssh-client
• novox: receives gitea, ssh-client
• shanks: receives ssh-client
• 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
• ssh-client 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 ssh-client is judged on its first machine

Machines

• gitea on every machine running it: sent
• ssh-client on every machine running it: sent

Transitions

• 2026-10-17 00:02 (new) → proposed (announced): novox/mesh-catalog#343's head announced
• 2026-10-17 00:04 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-17 00:04 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-17 00:06 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-17 00:06 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-17 00: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@661b83249c2a` — **delivered** since 2026-10-17T00:08:21Z **Delivery plan** — builds gitea, ssh-client → ace, g14, novox, shanks; no bus step - tier 0: gitea, ssh-client - ace: receives ssh-client - g14: receives ssh-client - novox: receives gitea, ssh-client - shanks: receives ssh-client - 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 - ssh-client 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 ssh-client is judged on its first machine **Machines** - gitea on every machine running it: sent - ssh-client on every machine running it: sent **Transitions** - 2026-10-17 00:02 (new) → proposed (announced): novox/mesh-catalog#343's head announced - 2026-10-17 00:04 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-17 00:04 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-17 00:06 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-17 00:06 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-17 00: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 added the mesh/ready label 2026-10-17 00:02:21 +00:00

mesh-tools commented 2026-10-17 00:02:21 +00:00

Author

Member

Copy Link

Copy Source

ready at 661b83249c

Reviewed by lead-57@novox: Reviewer (opus) approved 173d2f4 (tree 7bdbfd0) in round 2, the same tree as this forge commit: ADR 0409 clause 1, the forge's own ssh name, old entry keys kept for machines not yet moved. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at 661b83249c2af9d6b57a2edf1b2f3916f8509d81 Reviewed by lead-57@novox: Reviewer (opus) approved 173d2f4 (tree 7bdbfd0) in round 2, the same tree as this forge commit: ADR 0409 clause 1, the forge's own ssh name, old entry keys kept for machines not yet moved. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

mesh-tools commented 2026-10-17 00:04:58 +00:00

Author

Member

Copy Link

Copy Source

Merge check at 661b8324
Judged: head 661b83249c2a merged into trunk bb291b5ad8af; read beside it: mesh-controller b0d489a86c23, mesh-controller-main b0d489a86c23, 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, ssh-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, ssh-client → ace, g14, novox, shanks; no bus step

• tier 0: gitea, ssh-client
• ace: receives ssh-client
• g14: receives ssh-client
• novox: receives gitea, ssh-client
• shanks: receives ssh-client
• 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
• ssh-client 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 ssh-client is judged on its first machine
• read by no module's build: modules/ssh-client/cmd/ssh-client-tools/templates_test.go

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

✔ the accounts that may mark are the setting's, and only the mesh's own when it cannot be read (0.916671ms)
✔ the newest status of each context is kept, with what it said, when and by whom (29.730488ms)
✔ a commit merges only when every required status is a success; a warning blocks (0.819328ms)
✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.355187ms)
✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.955644ms)
✔ a note line is appended once, as the forge's user, in its own repository (16.115983ms)
✔ a note that cannot be written is said, never read as written (0.706547ms)
✔ one view per pull request, found by its marker; only the mesh's statuses (0.879451ms)
✔ a build machine taking the check is said on the head: building on which machine, since the local time (35.674852ms)
✔ the verdict heard while a 'building' write is in flight lands last and stays (9.794463ms)
[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.401913ms)
✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (1.533609ms)
✔ a start heard after the verdict writes nothing (0.524765ms)
✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.584257ms)
✔ an old run's verdict redelivered after a recheck's pending is not written over it (0.870234ms)
[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 (1.704882ms)
✔ a rechecked head says where its new run is: building on which machine (0.636335ms)
✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.555153ms)
✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.464352ms)
✔ a recheck the forge does not take fails its caller, and the head is as it was (0.419377ms)
✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (11.164735ms)
✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (0.368682ms)
✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (2.66794ms)
✔ a repository as the mesh clones it is told from another (0.258716ms)
✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (13.458823ms)
✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (52.089084ms)
✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (28.68201ms)
✔ gitea_api still writes what an author writes (8.705637ms)
✔ gitea_branch_protection_set only strengthens (16.995395ms)
✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (52.546814ms)
✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (172.555818ms)
✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (18.368151ms)
✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (14.492354ms)
✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (30.067592ms)
✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (65.941747ms)
✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (22.725915ms)
✔ gitea_api sends the path it judged, and refuses moving a pull request's base (5.588995ms)
✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (7.4179ms)
✔ a rule named for a branch is not made weaker than the glob rule that guards it now (12.997527ms)
✔ a repository owner or name is never another path (0.296768ms)
✔ the judges, without a forge (0.44755ms)
✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.306305ms)
✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (1.64566ms)
✔ gitea_api never approves a pull request nor requests changes: those are the operator's (2.39641ms)
✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.146225ms)
✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each sibling head reviewed (97.056915ms)
✔ a verdict put out of date by a sibling's move is refused in its own words, and asked again once (25.557752ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (36.339048ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.73492ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (15.617146ms)
✔ a lookup the forge refuses is thrown, not read as no module (5.742844ms)
✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (10.519143ms)
✔ a new head beyond the newest 20 open pull requests is announced, exactly once (94.973694ms)
✔ a pass pages until it reaches back past its floor, and no further (27.792419ms)
✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (29.731641ms)
✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (9.615836ms)
✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (7.734675ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (7.000165ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.358544ms)
✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.818087ms)
✔ another branch's body carries no merge whitelist (0.278002ms)
✔ 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.387167ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (21.121001ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.295563ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.799021ms)
✔ no verdict sets warning on a required check; only a person's decision fails (1.151362ms)
✔ a commit status is set on the commit, under the merge check's context (59.656613ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.714201ms)
✔ a head announced is pending in the build queue, since the local time it was announced (0.424036ms)
✔ the vault's token is used, a setting of it is ignored and said once, without its value (2.628816ms)
[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.651449ms)
✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (0.359826ms)
✔ a verdict without siblings is said exactly as before (an older controller) (0.898407ms)
✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (1.067905ms)
✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (1.925767ms)
✔ a sibling closed unmerged puts the member's verdict out of date (1.573746ms)
✔ a move of the sibling's base puts it out of date, naming both commits (0.413256ms)
✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.694084ms)
✔ a merge of another head, or onto another base, is a move (0.858833ms)
✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.822665ms)
✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.69251ms)
✔ the group rule names every missing thing: the group status at each head read, and each sibling head's review (0.976683ms)
✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.23432ms)
✔ a consumer that asks nothing, or write, publishes: the package team (1.778611ms)
✔ a consumer that asks to read joins the readers, who write no package (0.695677ms)
✔ a reader is made, put on the readers team, and taken off the package team (0.592392ms)
✔ a publisher is made and put on the package team, as before (0.237146ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (42.84259ms)
✔ second start: reuses the kept token, mints nothing (30.565056ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (34.489254ms)
✔ 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 (38.428081ms)
✔ 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 (32.714592ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (32.363162ms)
✔ concurrent first calls share one mint (16.680002ms)
✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (18.823757ms)
✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (88.205344ms)
✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (9.274415ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (18.427404ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.876015ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (21.355231ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (3.349069ms)
✔ nothing to mint with and no token: the client says what is missing (0.356319ms)
[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-OMCaXF/state/token
✔ the tools register once there is a way to a token, and the first call mints it (35.624105ms)
[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-2lJrE4/state/token
✔ a pull request can be closed, read and cleaned up through the tools (42.529232ms)
[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-Uheg8J/state/token
✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (78.109305ms)
[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-jzREMm/state/token
✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (57.778238ms)
[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-eikUAY/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 (52.214038ms)
[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-Fe34cy/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 (53.448757ms)
[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-gpyOg5/state/token
✔ a tools' account someone made an administrator is made a plain account again at the next mint (39.178731ms)
✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.877909ms)
✔ the manifest hands the tools their account, and the merge-ready authors name it rather than the administrator (1.384881ms)
[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-azZHS6/state/token
✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (41.02065ms)
[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 (34.23686ms)
[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-SBYL0V/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 (48.48738ms)
[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-kyHJaS/state/token
✔ a team another process made between the look and the create is found, not a failure (45.141246ms)
[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-qoJF9m/state/token
✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (42.69321ms)
[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-AMaEfC/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) (44.188098ms)
✔ 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.965945ms)
[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.445833ms)
✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (1.329046ms)
✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (6.35281ms)
✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.530827ms)
✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.614675ms)
✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.322416ms)
✔ a verdict that landed out of date keeps its account on the pull request (0.312267ms)
✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.534934ms)
✔ a signed event is published on the bus and acted on once (63.084331ms)
✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (45.73354ms)
✔ an event and the poll seeing the same head announce it once (0.590739ms)
✔ each forge event is named in the module's stream and trimmed (0.706146ms)
✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.543538ms)
✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.405068ms)
✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (5.289423ms)
✔ a forge that makes no system webhook is said, never taken as heard (0.762752ms)
✔ the receiver tells what it verified and what it refused (11.658493ms)
✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (0.996422ms)
✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.408257ms)
✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.326694ms)
✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.315142ms)
ℹ tests 147
ℹ suites 0
ℹ pass 147
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 861.283495

**Merge check** at `661b8324` Judged: head `661b83249c2a` merged into trunk `bb291b5ad8af`; read beside it: mesh-controller `b0d489a86c23`, mesh-controller-main `b0d489a86c23`, 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, ssh-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, ssh-client → ace, g14, novox, shanks; no bus step - tier 0: gitea, ssh-client - ace: receives ssh-client - g14: receives ssh-client - novox: receives gitea, ssh-client - shanks: receives ssh-client - 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 - ssh-client 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 ssh-client is judged on its first machine - read by no module's build: modules/ssh-client/cmd/ssh-client-tools/templates_test.go Run by the build seat on ace as `build-1792195323694556770` (`builds --log build-1792195323694556770`). ``` ✔ the accounts that may mark are the setting's, and only the mesh's own when it cannot be read (0.916671ms) ✔ the newest status of each context is kept, with what it said, when and by whom (29.730488ms) ✔ a commit merges only when every required status is a success; a warning blocks (0.819328ms) ✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.355187ms) ✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.955644ms) ✔ a note line is appended once, as the forge's user, in its own repository (16.115983ms) ✔ a note that cannot be written is said, never read as written (0.706547ms) ✔ one view per pull request, found by its marker; only the mesh's statuses (0.879451ms) ✔ a build machine taking the check is said on the head: building on which machine, since the local time (35.674852ms) ✔ the verdict heard while a 'building' write is in flight lands last and stays (9.794463ms) [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.401913ms) ✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (1.533609ms) ✔ a start heard after the verdict writes nothing (0.524765ms) ✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.584257ms) ✔ an old run's verdict redelivered after a recheck's pending is not written over it (0.870234ms) [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 (1.704882ms) ✔ a rechecked head says where its new run is: building on which machine (0.636335ms) ✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.555153ms) ✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.464352ms) ✔ a recheck the forge does not take fails its caller, and the head is as it was (0.419377ms) ✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (11.164735ms) ✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (0.368682ms) ✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (2.66794ms) ✔ a repository as the mesh clones it is told from another (0.258716ms) ✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (13.458823ms) ✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (52.089084ms) ✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (28.68201ms) ✔ gitea_api still writes what an author writes (8.705637ms) ✔ gitea_branch_protection_set only strengthens (16.995395ms) ✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (52.546814ms) ✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (172.555818ms) ✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (18.368151ms) ✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (14.492354ms) ✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (30.067592ms) ✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (65.941747ms) ✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (22.725915ms) ✔ gitea_api sends the path it judged, and refuses moving a pull request's base (5.588995ms) ✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (7.4179ms) ✔ a rule named for a branch is not made weaker than the glob rule that guards it now (12.997527ms) ✔ a repository owner or name is never another path (0.296768ms) ✔ the judges, without a forge (0.44755ms) ✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.306305ms) ✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (1.64566ms) ✔ gitea_api never approves a pull request nor requests changes: those are the operator's (2.39641ms) ✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.146225ms) ✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each sibling head reviewed (97.056915ms) ✔ a verdict put out of date by a sibling's move is refused in its own words, and asked again once (25.557752ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (36.339048ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.73492ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (15.617146ms) ✔ a lookup the forge refuses is thrown, not read as no module (5.742844ms) ✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (10.519143ms) ✔ a new head beyond the newest 20 open pull requests is announced, exactly once (94.973694ms) ✔ a pass pages until it reaches back past its floor, and no further (27.792419ms) ✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (29.731641ms) ✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (9.615836ms) ✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (7.734675ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (7.000165ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.358544ms) ✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.818087ms) ✔ another branch's body carries no merge whitelist (0.278002ms) ✔ 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.387167ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (21.121001ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.295563ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.799021ms) ✔ no verdict sets warning on a required check; only a person's decision fails (1.151362ms) ✔ a commit status is set on the commit, under the merge check's context (59.656613ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.714201ms) ✔ a head announced is pending in the build queue, since the local time it was announced (0.424036ms) ✔ the vault's token is used, a setting of it is ignored and said once, without its value (2.628816ms) [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.651449ms) ✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (0.359826ms) ✔ a verdict without siblings is said exactly as before (an older controller) (0.898407ms) ✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (1.067905ms) ✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (1.925767ms) ✔ a sibling closed unmerged puts the member's verdict out of date (1.573746ms) ✔ a move of the sibling's base puts it out of date, naming both commits (0.413256ms) ✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.694084ms) ✔ a merge of another head, or onto another base, is a move (0.858833ms) ✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.822665ms) ✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.69251ms) ✔ the group rule names every missing thing: the group status at each head read, and each sibling head's review (0.976683ms) ✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.23432ms) ✔ a consumer that asks nothing, or write, publishes: the package team (1.778611ms) ✔ a consumer that asks to read joins the readers, who write no package (0.695677ms) ✔ a reader is made, put on the readers team, and taken off the package team (0.592392ms) ✔ a publisher is made and put on the package team, as before (0.237146ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (42.84259ms) ✔ second start: reuses the kept token, mints nothing (30.565056ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (34.489254ms) ✔ 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 (38.428081ms) ✔ 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 (32.714592ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (32.363162ms) ✔ concurrent first calls share one mint (16.680002ms) ✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (18.823757ms) ✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (88.205344ms) ✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (9.274415ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (18.427404ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.876015ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (21.355231ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (3.349069ms) ✔ nothing to mint with and no token: the client says what is missing (0.356319ms) [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-OMCaXF/state/token ✔ the tools register once there is a way to a token, and the first call mints it (35.624105ms) [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-2lJrE4/state/token ✔ a pull request can be closed, read and cleaned up through the tools (42.529232ms) [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-Uheg8J/state/token ✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (78.109305ms) [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-jzREMm/state/token ✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (57.778238ms) [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-eikUAY/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 (52.214038ms) [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-Fe34cy/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 (53.448757ms) [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-gpyOg5/state/token ✔ a tools' account someone made an administrator is made a plain account again at the next mint (39.178731ms) ✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.877909ms) ✔ the manifest hands the tools their account, and the merge-ready authors name it rather than the administrator (1.384881ms) [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-azZHS6/state/token ✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (41.02065ms) [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 (34.23686ms) [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-SBYL0V/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 (48.48738ms) [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-kyHJaS/state/token ✔ a team another process made between the look and the create is found, not a failure (45.141246ms) [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-qoJF9m/state/token ✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (42.69321ms) [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-AMaEfC/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) (44.188098ms) ✔ 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.965945ms) [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.445833ms) ✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (1.329046ms) ✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (6.35281ms) ✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.530827ms) ✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.614675ms) ✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.322416ms) ✔ a verdict that landed out of date keeps its account on the pull request (0.312267ms) ✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.534934ms) ✔ a signed event is published on the bus and acted on once (63.084331ms) ✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (45.73354ms) ✔ an event and the poll seeing the same head announce it once (0.590739ms) ✔ each forge event is named in the module's stream and trimmed (0.706146ms) ✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.543538ms) ✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.405068ms) ✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (5.289423ms) ✔ a forge that makes no system webhook is said, never taken as heard (0.762752ms) ✔ the receiver tells what it verified and what it refused (11.658493ms) ✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (0.996422ms) ✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.408257ms) ✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.326694ms) ✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.315142ms) ℹ tests 147 ℹ suites 0 ℹ pass 147 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 861.283495 ```

mesh-tools merged commit 82df3bd589 into main 2026-10-17 00:05:58 +00:00

mesh-tools deleted branch fix/955-forge-ssh-name 2026-10-17 00:05:58 +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 mesh/ready

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#343