Rename mesh-control -> mesh-controller, substrate -> foundation
One name per thing, per the HQ glossary: the module/container/image/binary/repo becomes mesh-controller, the seat the-controller, and the store+broker pair the foundation (embedded base bundles, default template and example lock renamed with their go:embed directives). No behaviour change — a pure vocabulary rename. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
This commit is contained in:
@@ -72,11 +72,11 @@ func TestTheArchivesOwnIdIsReadFromTheSavedFile(t *testing.T) {
|
||||
// does not.
|
||||
func TestTheSavedTagsAreRead(t *testing.T) {
|
||||
saved := savedImage(t, map[string]string{
|
||||
"manifest.json": manifest(t, strings.Repeat("b", 64)+".json", "mesh-control:v1"),
|
||||
"manifest.json": manifest(t, strings.Repeat("b", 64)+".json", "mesh-controller:v1"),
|
||||
})
|
||||
got := Tags(saved)
|
||||
if len(got) != 1 || got[0] != "mesh-control:v1" {
|
||||
t.Errorf("tags = %v, want [mesh-control:v1]", got)
|
||||
if len(got) != 1 || got[0] != "mesh-controller:v1" {
|
||||
t.Errorf("tags = %v, want [mesh-controller:v1]", got)
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user