zara-coding: reject malformed task-state executable configuration before spawn #126

New issue

Closed

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

nsaspy commented

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

Owner

Problem

TaskStateSession only checks if not executable, so truthy non-text values, whitespace-only strings, and embedded-NUL executable values can survive construction and fail later in subprocess.Popen with raw type/OS errors. That weakens the task-state protocol's deterministic startup boundary.

Required behavior

task-state executable must be non-empty non-whitespace text;
reject embedded NUL/newline/carriage-return before process creation;
malformed configuration fails deterministically at construction with ValueError;
no process is spawned for invalid configuration;
existing SWI-Prolog startup/failure behavior remains unchanged;
full compatibility/registry/plugin/Nix package gates stay green.

Tracks bounded Prolog-RLM session configuration under #1.

## Problem `TaskStateSession` only checks `if not executable`, so truthy non-text values, whitespace-only strings, and embedded-NUL executable values can survive construction and fail later in `subprocess.Popen` with raw type/OS errors. That weakens the task-state protocol's deterministic startup boundary. ## Required behavior - task-state executable must be non-empty non-whitespace text; - reject embedded NUL/newline/carriage-return before process creation; - malformed configuration fails deterministically at construction with `ValueError`; - no process is spawned for invalid configuration; - existing SWI-Prolog startup/failure behavior remains unchanged; - full compatibility/registry/plugin/Nix package gates stay green. Tracks bounded Prolog-RLM session configuration under #1.

nsaspy closed this issue

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

nsaspy referenced this issue

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

zara-coding: validate collected worktree path shape #437