M1: nftables' setting allowances-max is marked runtime

The packet filter holder's tools read allowances-max themselves (config at
tools/index.ts); no file places it, so the manifest says "runtime": true
and the judge's placed-nowhere rule holds it as read by the module's code.

Builds: design 47 H2 H-A-430 (4)
This commit is contained in:
2026-11-22 01:45:28 +01:00
parent 872ed19648
commit 3ec18c9cd2
2 changed files with 2 additions and 0 deletions
+1
View File
@@ -95,6 +95,7 @@
"type": "number",
"description": "The most allowances this machine keeps, which allow refuses past (design 33 control-verbs §3): it keeps the rendered chain readable and allowed in one answer.",
"trusted": false,
"runtime": true,
"default": 100
}
},
+1
View File
@@ -353,4 +353,5 @@ test("the manifest serves the six verbs, requires the state per machine, invokes
assert.deepEqual(m.invokes, ["seat:node-engine.converged", "seat:mesh-hand-acts.hand-act"]);
assert.equal(m.emits, undefined, "the claim says the seat's event (H-A-317)");
assert.equal(m.config["allowances-max"].default, MOST);
assert.equal(m.config["allowances-max"].runtime, true, "the holder's code reads it itself; no file places it (H-A-430 (4))");
});