The forge bridge, the indexer and the teller run beside today's mesh-delivery, and the view shows candidates and fingerprints (design 47 R3c, issues 1235-1241, 1209)
#5
Merged
mesh-toolsmerged 10 commits from feat/delivery-parts into main2026-10-19 18:05:16 +00:00
Design 47 milestone R3c (ADR 0437 §1, §4, §5, §8): one delivery group with mesh-catalog's feat/delivery-parts (merged first: gitea_commit_trees and the head branch in gitea_open_pulls).
1235: module mesh-delivery-forge-bridge writes the forge's pull requests as pull messages on its stream FORGE (events forge.**), from gitea.pull.updated/closed, with their module directories.
1236: on a merge into main it reads the merge commit's trees once (gitea_commit_trees) and writes one merged message.
1237: at start and each reconnect, one pull message per open pull request (gitea_open_pulls).
1238: module mesh-delivery-indexer writes candidates. (a group is the branch name; trunk-like branches make none) from FORGE.
1239 (+1209): at each merged message the indexer writes modules. with mesh-sdk's SourceFingerprint from the merge's trees and the inputs the newest successful trunk build recorded; a narrow: context, another repository's context, or Unpinned gets none with its reason.
1240: module mesh-delivery-teller runs and logs that it waits for the gate's asks (the watch comes with the gate in R3d; no timer in these parts, ADR 0437 §8).
1241: the view reads candidates and modules and shows each module's fingerprint against its newest successful trunk build's.
No module of this repository commits its dependencies any more (the operator, 2026-10-19): vendor/ removed from all five modules; merge-check.sh fetches them, the pinned mesh-sdk taken from its clone beside the check through mesh-catalog's checks/deps (issue 1271: mesh-sdk is not yet cloned beside this repository's check).
Every criterion is cited by a test, each failed first. Review round 1 found the teller's integration test taking its result twice (it hung the first merge check for 10 minutes); fixed in 8e6a31bc. Merge check passed at 8e6a31bc (54 s). The head 24177aa6 is an empty commit on it, pushed only so the head is announced again: its check could not be asked (issue 1272, delivered) and a recheck from proposed is refused (issue 1274). This change of 1666 paths is also issue 1247's end-to-end proof. After the merge the three new modules are assigned to novox; the view moves on shanks.
Design 47 milestone R3c (ADR 0437 §1, §4, §5, §8): one delivery group with mesh-catalog's feat/delivery-parts (merged first: gitea_commit_trees and the head branch in gitea_open_pulls).
- 1235: module mesh-delivery-forge-bridge writes the forge's pull requests as pull messages on its stream FORGE (events forge.**), from gitea.pull.updated/closed, with their module directories.
- 1236: on a merge into main it reads the merge commit's trees once (gitea_commit_trees) and writes one merged message.
- 1237: at start and each reconnect, one pull message per open pull request (gitea_open_pulls).
- 1238: module mesh-delivery-indexer writes candidates.<group> (a group is the branch name; trunk-like branches make none) from FORGE.
- 1239 (+1209): at each merged message the indexer writes modules.<m> with mesh-sdk's SourceFingerprint from the merge's trees and the inputs the newest successful trunk build recorded; a `narrow:` context, another repository's context, or Unpinned gets none with its reason.
- 1240: module mesh-delivery-teller runs and logs that it waits for the gate's asks (the watch comes with the gate in R3d; no timer in these parts, ADR 0437 §8).
- 1241: the view reads candidates and modules and shows each module's fingerprint against its newest successful trunk build's.
- No module of this repository commits its dependencies any more (the operator, 2026-10-19): vendor/ removed from all five modules; merge-check.sh fetches them, the pinned mesh-sdk taken from its clone beside the check through mesh-catalog's checks/deps (issue 1271: mesh-sdk is not yet cloned beside this repository's check).
Every criterion is cited by a test, each failed first. Review round 1 found the teller's integration test taking its result twice (it hung the first merge check for 10 minutes); fixed in 8e6a31bc. Merge check passed at 8e6a31bc (54 s). The head 24177aa6 is an empty commit on it, pushed only so the head is announced again: its check could not be asked (issue 1272, delivered) and a recheck from proposed is refused (issue 1274). This change of 1666 paths is also issue 1247's end-to-end proof. After the merge the three new modules are assigned to novox; the view moves on shanks.
Reviewed-by: review-r3c@shanks at 24177aa654ab6b2b4b3daa61dd8e7a79b5a1266d
mesh/repo-check head 35ff62845811 merged into trunk 7f618177d677 beside mesh-catalog#374@75957fc3 — fail: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh):…
mesh/repo-check head 8e6a31bc6ab4 merged into trunk 7f618177d677 beside mesh-catalog#374@75957fc3 — pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh):…
mesh/merge-gate head 8e6a31bc6ab4 merged into trunk 7f618177d677 — pass: group feat/delivery-parts composed: every machine composes with the change as it d…
mesh/repo-check head 24177aa654ab merged into trunk 7f618177d677 beside mesh-catalog#374@75957fc3 — pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh):…
mesh/merge-gate head 24177aa654ab merged into trunk 1325c8b452c8 — pass: group feat/delivery-parts composed: every machine composes with the change as it d…
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Design 47 milestone R3c (ADR 0437 §1, §4, §5, §8): one delivery group with mesh-catalog's feat/delivery-parts (merged first: gitea_commit_trees and the head branch in gitea_open_pulls).
narrow:context, another repository's context, or Unpinned gets none with its reason.Every criterion is cited by a test, each failed first. Review round 1 found the teller's integration test taking its result twice (it hung the first merge check for 10 minutes); fixed in
8e6a31bc. Merge check passed at8e6a31bc(54 s). The head24177aa6is an empty commit on it, pushed only so the head is announced again: its check could not be asked (issue 1272, delivered) and a recheck from proposed is refused (issue 1274). This change of 1666 paths is also issue 1247's end-to-end proof. After the merge the three new modules are assigned to novox; the view moves on shanks.Reviewed-by: review-r3c@shanks at
24177aa654