mesh-delivery

Files

T

jschoubben 4851475773 Asker rename R1: a build seat's streamed kind is sent on its queue's subject, the kind in the body

The generator wrote `accept.<stream>.<kind>` for a kind that rides a stream (step on check and delivery,
run on check), so the runner's step landed under the named worker `accept.check.*` with `step` read as
its asker. A-170 has the kind in the body only: the generated accept subject of a streamed kind is the
queue's, `accept.<stream>`; its generated names stay `<stream>.<kind>`. The three build seats'
contracts and fixtures are regenerated.

Builds: design 47 G §600, A-170, A-184

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

2026-11-12 18:23:48 +01:00

testdata/contracts

SD5, BG11, BLD10: the build modules' shared code moves into the delivery SDK

2026-11-12 05:18:34 +01:00

callers.go

SD5, BG11, BLD10: the build modules' shared code moves into the delivery SDK

2026-11-12 05:18:34 +01:00

clients_test.go

SD5, BG11, BLD10: the build modules' shared code moves into the delivery SDK

2026-11-12 05:18:34 +01:00

clients.go

SD5, BG11, BLD10: the build modules' shared code moves into the delivery SDK