Found live during task 2.2 implementation (bug-1746): design.md claimed persist_submit_job_dispatch_fact's NULL-alloc case was "explicit, tested, backward-compatible" on both apply seams -- true for the DECODE side (apply_committed_entry/apply_wal_entry, bug-1678's actual fix target), but the ENCODE side (capnp_encode_joballoc) was never exercised with NULL before this feature and had a latent unconditional NULL dereference. Corrected all references to distinguish encode vs. decode safety and note the bug-1746 fix task 2.2 required. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y4M5MJM2zK6nU43da267Ku |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||