jschoubben bc289cbe04 The restart-on rename reads both list shapes ...

A resource composed in code carries restart-on as []string; the rename
only read []any, so the overlay's registry-trust reload kept its bare
reference, pointed at nothing, and the runtime was never restarted —
the trust was on disk and not in the daemon, with every check passing.
Diagnosed on the built-store-cross-node bed, run 8 (issues 042/048).

2026-09-17 23:35:12 +02:00

..

accesses_test.go

catalogue: a module accesses operator-owned data, and does not own it

2026-09-05 22:10:58 +02:00

bootstrap_cycle_test.go

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

bound_into_files_test.go

catalogue: announce a same-node provider at the port it is published on

2026-09-09 23:02:50 +02:00

bound_into_files.go

identity: a consumer's identity fits the tightest backend, via a slug (ADR 0054)

2026-09-05 02:51:39 +02:00

brokered_test.go

A consumer is a module on a machine, not a machine

2026-09-01 02:40:09 +02:00

build_test.go

The builder resolves the SDK from the mesh registry, and can publish packages

2026-09-16 10:27:26 +02:00

build.go

The builder resolves the SDK from the mesh registry, and can publish packages

2026-09-16 10:27:26 +02:00

co_located_test.go

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

computed_test.go

Where the answer to a requirement is allowed to live

2026-08-29 23:51:50 +02:00

contributes_test.go

fix: a require-only consumer of a parameterless provision still asks (and is minted a credential)

2026-09-06 23:20:58 +02:00

cron.go

catalogue: carry and validate a container schedule (ADR 0053)

2026-09-06 14:08:51 +02:00

declaration.go

The restart-on rename reads both list shapes

2026-09-17 23:35:12 +02:00

domain_test.go

Where the answer to a requirement is allowed to live

2026-08-29 23:51:50 +02:00

facts_test.go

The mesh's knowledge is a fact a module asks for, not three modules

2026-09-15 21:31:18 +02:00

facts.go

The mesh's knowledge is a fact a module asks for, not three modules

2026-09-15 21:31:18 +02:00

filtering_foundation_test.go

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

filtering_test.go

The firewall opens the port the mesh itself runs on

2026-09-15 00:54:31 +02:00

filtering.go

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

identity_test.go

Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation

2026-09-05 12:47:13 +02:00

identity.go

Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation

2026-09-05 12:47:13 +02:00

licence_test.go

catalogue: deliver a keyless same-node provider's served facts

2026-09-07 05:08:04 +02:00

machine_into_files_test.go

The routing record is 0066, not 0056

2026-09-11 00:09:56 +02:00

machine_into_files.go

The routing record is 0066, not 0056

2026-09-11 00:09:56 +02:00

machineside_test.go

What review found in the port machinery, fixed

2026-09-01 21:54:05 +02:00

manifest.go

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

names_test.go

catalogue: give host-network containers the mesh's names too

2026-09-07 03:44:28 +02:00

naming_test.go

Refuse an action where it was written, not on the machine

2026-09-01 02:55:56 +02:00

naming.go

A provision names the engine, because a consumer is coupled to one

2026-08-31 17:12:46 +02:00

needs_test.go

needs is now own-secrets, named for whose it is

2026-08-31 13:47:21 +02:00

parseall_test.go

A container may not mount a path the module never declared

2026-09-01 19:36:01 +02:00

port_into_files_test.go

A module can be told which port it was given

2026-09-15 13:20:01 +02:00

port_into_files.go

A module can be told which port it was given

2026-09-15 13:20:01 +02:00

print_rehearsal_test.go

The firewall opens the port the mesh itself runs on

2026-09-15 00:54:31 +02:00

provided_test.go

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

reflects_renamed_test.go

The restart-on rename reads both list shapes

2026-09-17 23:35:12 +02:00

resolve_loopback_test.go

A binding answered on this very node still carries an address

2026-09-14 21:11:37 +02:00

resolve_test.go

The controller's seat is mesh-controller; a foundation module on a second node is refused

2026-09-17 02:13:26 +02:00

resolve.go

A binding answered on this very node still carries an address

2026-09-14 21:11:37 +02:00

routing_test.go

The routing record is 0066, not 0056

2026-09-11 00:09:56 +02:00

runonce_test.go

catalogue: run-once is a step the host runs to completion (ADR 0052)

2026-09-05 23:57:33 +02:00

schedule_test.go

catalogue: carry and validate a container schedule (ADR 0053)

2026-09-06 14:08:51 +02:00

secrets_into_files_test.go

fix: fill a ptr-secret placeholder from the file-owner's credential, not the last consumer's

2026-09-06 13:46:55 +02:00

secrets_into_files.go

fix: fill a ptr-secret placeholder from the file-owner's credential, not the last consumer's

2026-09-06 13:46:55 +02:00

settings_test.go

A module can tell its provider what it needs

2026-08-29 23:35:43 +02:00

settings.go

Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation

2026-09-05 12:47:13 +02:00

showcase_manifest_test.go

A module can be told which port it was given

2026-09-15 13:20:01 +02:00

two_consumers_test.go

A consumer is a module on a machine, not a machine

2026-09-01 02:40:09 +02:00