zara-github: reject fractional integer limit configuration #104

New issue

Closed

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

nsaspy commented

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

Owner

Problem

GitHubConfig.load() converts max_response_bytes and max_results with int(). Fractional float values such as 1.9 are silently truncated instead of failing the typed configuration boundary, which can materially change provider limits.

Slice

deterministic RED coverage for fractional integer-only limits;
accept actual integers and existing integer strings;
reject fractional floats instead of truncating them;
preserve boolean rejection and configured bounds;
exact-head compatibility, registry, plugin and generated Nix package gates before merge.

Dependency-ready zara-github correctness slice. No external todo work.

## Problem `GitHubConfig.load()` converts `max_response_bytes` and `max_results` with `int()`. Fractional float values such as `1.9` are silently truncated instead of failing the typed configuration boundary, which can materially change provider limits. ## Slice - deterministic RED coverage for fractional integer-only limits; - accept actual integers and existing integer strings; - reject fractional floats instead of truncating them; - preserve boolean rejection and configured bounds; - exact-head compatibility, registry, plugin and generated Nix package gates before merge. Dependency-ready `zara-github` correctness slice. No external todo work.

nsaspy closed this issue

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

nsaspy referenced this issue

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

zara-coding: reconcile frozen SPECs with repository evidence #459