RAGE: enforce strict integer types for zara-healthcheck policy bounds #85

New issue

Closed

opened 2026-09-08 02:02:56 +00:00 by nsaspy · 0 comments

nsaspy commented

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

Owner

HealthDomain still coerces history_limit, hysteresis_count, and max_evidence_bytes through int(...), so booleans, numeric strings, and fractional values can silently rewrite typed health policy.

Acceptance:

all three policy bounds accept only exact integers within their existing ranges;
malformed descriptors fail with HealthError before probe execution/state creation;
valid integers preserve current hysteresis/history/evidence semantics;
deterministic RED first, then exact-head source/install compatibility, registry/plugin tests, and generated Nix package builds green.

`HealthDomain` still coerces `history_limit`, `hysteresis_count`, and `max_evidence_bytes` through `int(...)`, so booleans, numeric strings, and fractional values can silently rewrite typed health policy. Acceptance: - all three policy bounds accept only exact integers within their existing ranges; - malformed descriptors fail with `HealthError` before probe execution/state creation; - valid integers preserve current hysteresis/history/evidence semantics; - deterministic RED first, then exact-head source/install compatibility, registry/plugin tests, and generated Nix package builds green.

nsaspy closed this issue

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

nsaspy referenced this issue

2026-09-08 02:03:50 +00:00

zara-memory: symbolic scoped memory integration #7