mesh-delivery

Files

T

jschoubben bd13302ecf DLV-FB1: the forge bridge says a branch's end as branch-deleted and answers bridge_tags

The bridge consumes the forge module's forge.delete and writes a branch-deleted message on FORGE for a deleted
branch (never the trunk, never a tag), so the builder removes the branch's tagged versions (design 51 *The forge
bridge says a branch's end*). Only the forge module's account may say forge.delete: the bus refuses it from
another (a case of the bridge's whole-module test). bridge_tags, served by a new tools bundle, answers a
package's git tags by prefix through the forge module's gitea_api, for the builder's floor.

One unit test merged into another, so the tags test adds no function (test budget).

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

2026-11-04 11:44:53 +01:00

testdata

Carry each named path's git object in the merged and pull messages of a module whose every artifact names its paths, read at its manifest's commit (issue 1758, I6, ADR 0499 §3)

2026-10-22 18:13:25 +02:00

acts_test.go

Stop the forge bridge performing mesh/check: the forge module writes it (R2-1)

2026-10-22 21:40:09 +02:00

acts.go

Stop the forge bridge performing mesh/check: the forge module writes it (R2-1)

2026-10-22 21:40:09 +02:00

bridge_test.go

DLV-FB1: the forge bridge says a branch's end as branch-deleted and answers bridge_tags