T

jschoubben 2855ae7ebf Set the owed mesh/check through gitea_check_status, the one tool that writes it (issue 1301's delivery part, option A)

The forge's gitea_commit_status refuses the context mesh/check from R4e, so that only the checker's account, through
this bridge, can make a pull request pass the one required status.

2026-10-22 17:59:30 +02:00

modules

Set the owed mesh/check through gitea_check_status, the one tool that writes it (issue 1301's delivery part, option A)

2026-10-22 17:59:30 +02:00

.gitignore

Commit no module's dependencies: fetch them in the check, the pinned SDK from beside it (issue 1235)

2026-10-19 15:27:37 +02:00

merge-check.sh

Commit no module's dependencies: fetch them in the check, the pinned SDK from beside it (issue 1235)

2026-10-19 15:27:37 +02:00

README.md

Begin mesh-delivery with its README and its own check (ADR 0428)

2026-10-18 16:07:25 +00:00

README.md

mesh-delivery

Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).

Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/repo-check (this repository's merge-check.sh) and mesh/merge-gate passed.