Read a state's max-mib in the manifest-reads baseline

Every running node-engine reads a state's max-mib (it writes every
module's bucket cap from it), so the baseline a node-engine that states
nothing is read as stating carries it.

Builds: design 47 H2 §812, §820; H-A-383
This commit is contained in:
2026-11-22 00:06:15 +01:00
parent 450ea7eddc
commit fe052c135e
2 changed files with 4 additions and 1 deletions
+1
View File
@@ -303,6 +303,7 @@ word:slug
word:state
word:state.history
word:state.key-ttl
word:state.max-mib
word:state.name
word:state.per-machine
word:state.ttl-seconds
+3 -1
View File
@@ -72,7 +72,9 @@ func TestOwnManifestUsesNoWordTheRunningControllerRefuses(t *testing.T) {
t.Errorf("%s is in the baseline, or not read: added since it are %v", want, added)
}
}
for _, want := range []string{"word:claims.serves", "word:settings.default", "form:config", "form:setting", "seat:mesh-catalog"} {
for _, want := range []string{"word:claims.serves", "word:settings.default", "form:config", "form:setting", "seat:mesh-catalog",
// H-A-383: every node-engine reads a state's max-mib, so a manifest naming it needs no newer engine.
"word:state.max-mib"} {
if !slices.Contains(baseline, want) {
t.Errorf("the baseline lacks %s", want)
}