mesh-controller

Files

T

jochen cea59428b1 The forge's tests compose its code as a bundle the node's runtime serves (hq ADR 0198)

gitea's own code moves out of its runtime container (mesh-catalog, to-be 38 WP4c waves 2-3), so the three tests that composed the forge from the catalogue beside this checkout resolve its build as the code bundle, compose it beside the node's runtime, and read the forge's address from the words the runtime hands the module rather than from a sidecar's env.

2026-10-04 00:50:06 +02:00

broker

The node's runtime reads the consumers of the modules it carries (hq ADR 0198)

2026-10-03 22:30:55 +02:00

builder

Run the toolchain's esbuild as itself: npm installs its native binary in place of the script

2026-10-03 23:26:08 +02:00

catalogue

The forge's tests compose its code as a bundle the node's runtime serves (hq ADR 0198)

2026-10-04 00:50:06 +02:00

envfile

An address is read from the node's settings where it is used, never recorded with a port