mesh-delivery

Files

T

jschoubben b84db41198 DLV-F5r (indexer's case): the assigner's runtime answering after the indexer asked is followed within the bound

A case of the indexer's existing whole-module test: the assigner's first view is held until the
indexer has started, and only the placed node's toolchain counts once it answers (ADR 0621 §3).

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

2026-11-04 14:21:13 +01:00

cmd

DLV-F5r (indexer's case): the assigner's runtime answering after the indexer asked is followed within the bound

2026-11-04 14:21:13 +01:00

internal

DLV-I17, I18, I19, I20: the indexer keeps every contracts module's seat definitions on the bus

2026-11-04 14:18:17 +01:00

judge

DLV-I16: the judge refuses a contracts module claiming a seat, naming the seat

2026-11-04 14:06:03 +01:00

testdata/beside

Fall back to a captured copy only for mesh-host, which the checker places beside no mesh-delivery check (issue 1585)