Remediation for task cd3e0209 (Feature 19 follow-up). Fixes the re-review finding F19-01 MEDIUM: an oversized digit-only planning horizon became Infinity -> JSON null -> the API reset the field to default. Now requires a safe integer >= 1, shows a message and sends nothing otherwise, with a regression test.
Head: cd0ff68ea3 (base feature head 50428f0)
cd admin && npm test = 15 files, 214 passed; build ok.
Remediation for task cd3e0209 (Feature 19 follow-up). Fixes the re-review finding F19-01 MEDIUM: an oversized digit-only planning horizon became Infinity -> JSON null -> the API reset the field to default. Now requires a safe integer >= 1, shows a message and sends nothing otherwise, with a regression test.
Head: cd0ff68ea3cad03c94cb0b886b1439513736aa67 (base feature head 50428f0)
cd admin && npm test = 15 files, 214 passed; build ok.
A digit string too long for a safe integer became Infinity, which
JSON.stringify sends as null, and the API reads null as "reset to
default" -- so saving could silently replace the household's horizon.
Require a safe integer >= 1 and send nothing otherwise (F19-01).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Remediation for task cd3e0209 (Feature 19 follow-up). Fixes the re-review finding F19-01 MEDIUM: an oversized digit-only planning horizon became Infinity -> JSON null -> the API reset the field to default. Now requires a safe integer >= 1, shows a message and sends nothing otherwise, with a regression test.
Head:
cd0ff68ea3(base feature head50428f0)cd admin && npm test = 15 files, 214 passed; build ok.
Independent Codex gpt-5.6-terra review completed for this exact commit.