jschoubben d539d7e4eb Take the runtime as a culprit only where its stub composes, so node-tools is never held for an error that names it (issue 774) ...

The culprit rule held a module whose stub made the composition fail otherwise. The runtime's stub carries no bundle,
so it always fails otherwise: any refusal naming node-tools (or a module whose name holds it) held the runtime, and
the node was then refused whole for the runtime's "0 bundle(s)".

Quick fix: never take node-tools as a culprit. Thorough fix: blames, the rule as one function, takes the runtime only
where its stub composes. Chose thorough: a runtime whose stub composes may still be held alone.

2026-10-30 19:44:08 +01:00

..

frombus

Take the runtime as a culprit only where its stub composes, so node-tools is never held for an error that names it (issue 774)

2026-10-30 19:44:08 +01:00

fromruntime

Read the bus through a module's declared states in frombus, with the runtime's adapter in fromruntime, so mesh-provisioner and disk-load compose from one reader instead of two copies (issue 1955)

2026-10-29 23:31:34 +01:00

judge

Keep as today what a node keeps today and what is held only behind it, saying how; a stub hands and collects nothing of its own (issue 1126)

2026-10-28 23:49:22 +01:00

composed_test.go

A runtime that already dropped a carried module's tools serves them again, read from what runs and its build (issue 1126, review)

2026-10-29 21:03:16 +01:00

composed.go

A runtime that already dropped a carried module's tools serves them again, read from what runs and its build (issue 1126, review)

2026-10-29 21:03:16 +01:00

credentials_needed.go

compose names the pair credentials a node's composition reads as consumer and provider, and frombus asks them sealed before it composes (issue 1126, ADR 0550 §5)

2026-10-26 19:18:46 +01:00

credentials_test.go

compose names the pair credentials a node's composition reads as consumer and provider, and frombus asks them sealed before it composes (issue 1126, ADR 0550 §5)

2026-10-26 19:18:46 +01:00

credentials.go

Compose each node's provisioning plans from the bus alone, in a Planning mode that reads no secret, so mesh-provisioner composes the plans the controller did (issue 1954 L6-P1, ADR 0570 clause 2)

2026-10-29 22:31:02 +01:00

fixture_test.go

Test the private network and the rest of the mesh over an Input (issues 1360, 1361). Tests ported from mesh-control 6c2a8d62 network_test.go and seat_pass_test.go with their values; written after the code, checked by breaking each rule in turn and seeing a test fail. Store-backed ones are rebuilt as Inputs; overlayPlace's own refusal of an endpoint off the tunnel's port, namesInTheMesh and the resolver's roster test are the controller's or the rendering's (1363).

2026-10-20 06:24:18 +00:00

input.go

A module composed as what runs of it serves its tools as they run, so the runtime no longer drops it (issue 1126)

2026-10-29 21:03:16 +01:00

network_test.go

Keep a machine that does not resolve on the private network at its place, so one machine's modules refuse only its own declaration (issue 1833)

2026-10-22 15:03:17 +02:00

network.go

A refusal for want of a provider names the modules another node cannot run in this composition, and a refusal naming no placed module is answered at once (issue 1126, probe #532)

2026-10-28 01:39:07 +01:00

node_test.go

Count a machine that does not resolve and holds a place as on the network for its name and the mesh's sources too (issue 1833)

2026-10-22 15:26:48 +02:00

node.go

Compose a node's placed data items from the bus and move the readings layout into the sdk, so disk-load measures without a composed file and restic, mounts, nfs-server and the self-check read one layout (issue 1955, ADR 0571 clause 3)

2026-10-29 23:16:56 +01:00

one_machine_alone_test.go

Count a machine that does not resolve and holds a place as on the network for its name and the mesh's sources too (issue 1833)

2026-10-22 15:26:48 +02:00

render.go

Compose each node's provisioning plans from the bus alone, in a Planning mode that reads no secret, so mesh-provisioner composes the plans the controller did (issue 1954 L6-P1, ADR 0570 clause 2)

2026-10-29 22:31:02 +01:00

rendering_test.go

Test the place half of the rendering over an Input (issue 1363). Fixtures from mesh-control 6c2a8d62 sendable_integration_test.go (the store, the given port) and local_network_test.go (the networks); written after the code, each rule broken in turn and a test seen to fail. Unit level 1.05 s of 2 s.

2026-10-20 06:35:09 +00:00

rendering.go

Compose as the controller does, so a node's shadow can answer same (issue 1126, C1 C2 C3 C5 C6, T1)

2026-10-28 09:36:36 +01:00

resolve_test.go

Compose a licence key the Input does not carry with a stand-in named foreseen; keep empty only where Keys is given and lacks the holder (review round 1, finding 3). The test failed first

2026-10-20 07:01:50 +00:00

resolve.go

A refusal for want of a provider names the modules another node cannot run in this composition, and a refusal naming no placed module is answered at once (issue 1126, probe #532)

2026-10-28 01:39:07 +01:00

rest_test.go

Test the private network and the rest of the mesh over an Input (issues 1360, 1361). Tests ported from mesh-control 6c2a8d62 network_test.go and seat_pass_test.go with their values; written after the code, checked by breaking each rule in turn and seeing a test fail. Store-backed ones are rebuilt as Inputs; overlayPlace's own refusal of an endpoint off the tunnel's port, namesInTheMesh and the resolver's roster test are the controller's or the rendering's (1363).

2026-10-20 06:24:18 +00:00

rest.go

A refusal for want of a provider names the modules another node cannot run in this composition, and a refusal naming no placed module is answered at once (issue 1126, probe #532)

2026-10-28 01:39:07 +01:00

seats_test.go

Test the private network and the rest of the mesh over an Input (issues 1360, 1361). Tests ported from mesh-control 6c2a8d62 network_test.go and seat_pass_test.go with their values; written after the code, checked by breaking each rule in turn and seeing a test fail. Store-backed ones are rebuilt as Inputs; overlayPlace's own refusal of an endpoint off the tunnel's port, namesInTheMesh and the resolver's roster test are the controller's or the rendering's (1363).

2026-10-20 06:24:18 +00:00