forked from lei.chen/myxce
Rongsong Shen
2b0a37acc7
Feature-level validation ran 4 parallel dimensions: requirements coverage (38 ACs, 33 full, 5 partial -- all tracing to the already-known bulk-insert partial-visibility gap plus an admitted commit-barrier-count inference), design/boundary alignment (ALIGNED, no drift), cross-task integration (SEAMS_SOUND, wire format/arithmetic/contracts verified consistent end to end), and mechanical checks including a live smoke boot (fresh single-node deploy, real array submission, one WAL record, all elements queryable) -- PASS. The coverage pass sharpened restore_job_array()'s known bulk-insert gap: it's a literal, code-proven violation of Requirements 2.3 and 9.4, not just a soft nuance -- a resource-exhaustion failure during the bulk-insert pass can permanently orphan array elements that exist and are addressable but never get scheduled. Filed as bug-1443 (.wolf/buglog.json) for tracking. User decision: GO, ship with the gap tracked rather than blocking on a fast-follow fix -- the trigger condition is narrow and every other validation dimension is clean. Closing bug-1443 needs a new kv.c/kvmgr.c primitive or a re-derive- and-renotify path, explicitly out of this spec's approved scope. spec.json phase -> implementation-complete. |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||