mesh-sdk

Files

T

jschoubben c94f30d398 Bind a consumer from the plan entry its key carries, not only from the plans

The seat keys a consumer's provisions from its wanted and newest builds but
keeps the plan of its wanted build alone, and the provider helper bound only
from plans: a requirement the newest build adds stayed asked with no word,
and the want waiting for it never moved (mcp-endpoint on ace and shanks).
A provision now carries the plan entry it was composed from; the helper
binds from it where no plan names the key, the plan winning where both do,
and says each key it can bind from neither (issue 1126 review 1).

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

2026-11-02 12:17:20 +01:00

harness

Bind every provider by mesh-provisioner's plans and provision keys instead of the controller's assignments, act once a provision's dependencies are provided, say the outcome in its entry, and retire a consumer only on the operator's yes (issue 1954 L6-P3, P4, ADR 0570 clauses 2, 3, 5)

2026-10-29 22:41:50 +01:00

consumers_test.go

2026-10-29 22:41:50 +01:00

consumers.go

Feature 57 (config and provisioning): release mesh-sdk, the reviewed release branch on top of main

2026-10-16 08:24:11 +00:00

ended_test.go

2026-10-29 22:41:50 +01:00

provider_test.go