Rongsong Shen
6c908d5017
Design validation (2026-09-01) found and fixed 4 issues: a stale bug-1678 citation blocking reuse of persist_submit_job_dispatch_fact, missing XCE_WORKER_RECONCILING accounting against scheduler-dispatch-commit's dispatch-fail retry/terminal-fail classification, bug-1631 reactivation (job.allocs never released on RUN->PEND reconciliation), and an eager-vs- deferred mutation inconsistency between the new job.c functions and the bug-1679 explicit-notify precedent. design.approved and tasks.approved both set; tasks.md drafted (7 major/19 sub-tasks) and passed two rounds of independent task-graph sanity review. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y4M5MJM2zK6nU43da267Ku
26 lines
2.3 KiB
JSON
26 lines
2.3 KiB
JSON
{
|
|
"feature_name": "worker-rejoin-resync",
|
|
"created_at": "2026-08-10T00:00:00Z",
|
|
"updated_at": "2026-09-01T01:05:00Z",
|
|
"language": "en",
|
|
"phase": "tasks-generated",
|
|
"description": "Controller-initiated job-state reconciliation on worker rejoin: on reconnect, the controller asks the worker what really happened to jobs it believes are running there, and reconciles the answer idempotently, so facts lost to fire-and-forget notify drop (bug-1741) self-heal instead of leaving jobs stuck in RUN forever.",
|
|
"approvals": {
|
|
"requirements": {
|
|
"generated": true,
|
|
"approved": true
|
|
},
|
|
"design": {
|
|
"generated": true,
|
|
"approved": true,
|
|
"validation_note": "kiro-validate-design 2026-09-01: initial pass found 2 critical issues (stale bug-1678 citation blocking reuse of persist_submit_job_dispatch_fact; XCE_WORKER_RECONCILING vs. scheduler-dispatch-commit's dispatch-fail retry/terminal-fail classification). Fixed in design.md, then re-validated during the same pass and found 2 more (bug-1631 reactivation -- job.allocs never released when a RUN job reconciles back to PEND; eager-vs-deferred mutation-pattern inconsistency between the new job.c functions and the bug-1679 explicit-notify precedent). All 4 fixed directly in design.md; a further self-check found no additional issues. Self-approved per explicit user instruction to iterate to GO -- a human skim before /kiro-spec-tasks is still advisable given the scope of the changes."
|
|
},
|
|
"tasks": {
|
|
"generated": true,
|
|
"approved": true,
|
|
"validation_note": "kiro-spec-tasks 2026-09-01: 7 major tasks / 19 sub-tasks drafted covering all 33 requirement IDs (1.1-8.3) and every design.md component. Task-plan review gate passed after tightening 4 over/under-annotated _Depends:_ tags. Independent task-graph sanity review (fresh subagent, pass 1): NEEDS_FIXES -- Task 5 was a single-sub-task container (violates 2-level collapse rule), missing the design's scheduler-symbol-fence constraint, and no task verified the HA-redirect requirement for the 2 new opcodes (bug-1700 class). All 3 fixed. Sanity review pass 2 (fresh subagent): NEEDS_FIXES -- one dangling _Depends: 5.1_ left over from flattening task 5, fixed to _Depends: 5_. Auto-approved per -y flag."
|
|
}
|
|
},
|
|
"ready_for_implementation": true,
|
|
"blocked_on": []
|
|
}
|