zara-comms: require exact integer attachment size metadata #67

New issue

Closed

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

nsaspy commented

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

Owner

Problem

CommsDomain.normalize_message currently uses int(item["size"]). Provider values such as True, "50", or 1.5 can therefore be silently coerced into attachment byte sizes.

Required behavior

attachment size must be an exact integer, excluding booleans
malformed numeric strings/floats/booleans fail structurally instead of being coerced
existing non-negative / 100 MiB bound remains enforced
deterministic regressions
full registry/install/Nix gate remains green

No Zara Core changes.

## Problem `CommsDomain.normalize_message` currently uses `int(item["size"])`. Provider values such as `True`, `"50"`, or `1.5` can therefore be silently coerced into attachment byte sizes. ## Required behavior - attachment `size` must be an exact integer, excluding booleans - malformed numeric strings/floats/booleans fail structurally instead of being coerced - existing non-negative / 100 MiB bound remains enforced - deterministic regressions - full registry/install/Nix gate remains green No Zara Core changes.

nsaspy closed this issue

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

nsaspy referenced this issue

2026-09-08 02:20:12 +00:00

Add passive bounded zara-healthcheck service #495