zara-coding: reject silent symbolic task-state process replacement after crash #166

New issue

Closed

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

nsaspy commented

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

Owner

Problem

TaskStateSession._request() calls start() on every operation. If the owned SWI-Prolog process has exited after task/evidence state was created, start() silently launches a fresh empty process before _request() checks liveness. That can turn state loss into ordinary task-not-found responses and lets a coding transaction continue against a replacement symbolic state owner.

Required slice

deterministic RED proving an exited previously-started task-state process is not silently replaced;
first start remains lazy/idempotent;
after unexpected process exit, fail closed with explicit CodingError until the owning plugin/session is restarted deliberately;
no hidden persistence or second runtime;
run focused task-state integration plus full registry/Nix/package gates.

Advances local ownership/integrity work for #1; Core #400 composition remains untouched.

## Problem `TaskStateSession._request()` calls `start()` on every operation. If the owned SWI-Prolog process has exited after task/evidence state was created, `start()` silently launches a fresh empty process before `_request()` checks liveness. That can turn state loss into ordinary `task-not-found` responses and lets a coding transaction continue against a replacement symbolic state owner. ## Required slice - deterministic RED proving an exited previously-started task-state process is not silently replaced; - first start remains lazy/idempotent; - after unexpected process exit, fail closed with explicit `CodingError` until the owning plugin/session is restarted deliberately; - no hidden persistence or second runtime; - run focused task-state integration plus full registry/Nix/package gates. Advances local ownership/integrity work for #1; Core #400 composition remains untouched.

nsaspy closed this issue

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