docs(job-array-single-wal-record): record fresh /kiro-validate-impl GO, close stale notes
spec.json: phase -> implementation-complete, new GO decision (2026-07-17) covering the full feature plus phase 7's residual-gap closure; prior decision preserved as prior_decision; bug-1443 known_limitations entry retired (closed by task 7.1) and replaced with the one limitation that is still genuinely open (task 7.2's first-boot promotion-ordering gap). tasks.md: task 3.1's implementation note updated from "open, unowned gap" to "closed by task 7.1" -- it predated that fix and had gone stale. Validation evidence: full C suite 9/9 green (incl. libxce test post rtti-fix), Go suite green (88.1% backend coverage), clean TBD/secrets grep, live array-soak smoke PASS (O(1) replay time confirmed at 2-element vs 10,000-element scale), cross-task integration verified at every seam phase 7 touched, 10/10 requirement groups covered, zero design drift, zero blocked tasks.
This commit is contained in:
parent
ccee18b0c9
commit
9cf61c9fc1
2 changed files with 12 additions and 7 deletions
|
|
@ -1,9 +1,9 @@
|
|||
{
|
||||
"feature_name": "job-array-single-wal-record",
|
||||
"created_at": "2026-07-09T17:20:00Z",
|
||||
"updated_at": "2026-07-16T06:15:00Z",
|
||||
"updated_at": "2026-07-17T09:47:00Z",
|
||||
"language": "en",
|
||||
"phase": "tasks-generated",
|
||||
"phase": "implementation-complete",
|
||||
"approvals": {
|
||||
"requirements": {
|
||||
"generated": true,
|
||||
|
|
@ -22,11 +22,16 @@
|
|||
"blocked_on": [],
|
||||
"validate_impl": {
|
||||
"decision": "GO",
|
||||
"validated_at": "2026-07-16T02:10:00Z",
|
||||
"validated_at": "2026-07-17T09:47:00Z",
|
||||
"known_limitations": [
|
||||
"bug-1443: restore_job_array()'s bulk-insert-phase failure can permanently orphan array elements (violates Req 2.3/9.4 literally); tracked in .wolf/buglog.json, not fixed in this spec"
|
||||
"First-boot promotion-ordering gap (documented in tasks.md task 7.2's Implementation Notes): a node's very first promotion evaluation in a fresh process runs before that node's own first persist_recover()/replay_wal() call, so the Live Apply Resource Fence is invisible to that one specific check. Every promotion evaluation after a process's first one is protected. Out of this spec's persist.c-only boundary; flagged for a dedicated ha.c follow-up, not tracked as a numbered bug."
|
||||
],
|
||||
"reopened_at": "2026-07-16T06:15:00Z",
|
||||
"reopen_reason": "User directed all of this feature's own open residual gaps be fixed (2026-07-16): bug-1443 (bulk-insert partial-visibility), task 4.2's boot-replay fence gap, and task 5.3b's bounded leak. Added as Phase 7 (tasks 7.1-7.3) in tasks.md. Unrelated pre-existing bugs 1437/1438 explicitly excluded from this reopening per user's scope decision."
|
||||
"prior_decision": {
|
||||
"decision": "GO",
|
||||
"validated_at": "2026-07-16T02:10:00Z",
|
||||
"reopened_at": "2026-07-16T06:15:00Z",
|
||||
"reopen_reason": "User directed all of this feature's own open residual gaps be fixed (2026-07-16): bug-1443 (bulk-insert partial-visibility), task 4.2's boot-replay fence gap, and task 5.3b's bounded leak. Added as Phase 7 (tasks 7.1-7.3) in tasks.md. Unrelated pre-existing bugs 1437/1438 explicitly excluded from this reopening per user's scope decision.",
|
||||
"note": "bug-1443 was closed by task 7.1 (commit dcf9f39); superseded by this validation's fresh GO."
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue