zara-coding: reject unsupported verification evidence statuses #171

New issue

Closed

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

nsaspy commented

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

Owner

Follow-up slice under #1.

TaskStateSession.record_evidence() currently accepts any non-empty status string. The symbolic state machine should accept only canonical verification outcomes so malformed/unknown statuses cannot pollute bounded task state or become ambiguous completion evidence.

Acceptance:

deterministic RED proving an unsupported status is rejected
canonical passing/failing statuses remain supported
rejection is explicit and leaves task evidence unchanged
focused tests + registry validator + source/install compatibility + nix flake check + package builds
no Core changes or private cross-plugin runtime

Follow-up slice under #1. `TaskStateSession.record_evidence()` currently accepts any non-empty status string. The symbolic state machine should accept only canonical verification outcomes so malformed/unknown statuses cannot pollute bounded task state or become ambiguous completion evidence. Acceptance: - deterministic RED proving an unsupported status is rejected - canonical passing/failing statuses remain supported - rejection is explicit and leaves task evidence unchanged - focused tests + registry validator + source/install compatibility + `nix flake check` + package builds - no Core changes or private cross-plugin runtime

nsaspy closed this issue

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

nsaspy referenced this issue from a pull request that will close it,

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

registry: reject non-canonical plugin search paths #395