myxce/.kiro/specs/worker-rejoin-resync/spec.json
Rongsong Shen b0f2aea466
chore(gitea-sync): record first status-driven Gitea sync
- buglog: gitea_issue / gitea_synced_status for the 20 bugs created and the
  30 already-synced entries (#25/#35 reopened as partial)
- .kiro/specs/*/spec.json: "gitea" milestone/issue mapping for all 66 specs
  (65 milestones + 195 issues created, 158 closed at creation)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-24 10:22:05 +00:00

34 lines
2.4 KiB
JSON

{
"feature_name": "worker-rejoin-resync",
"created_at": "2026-08-10T00:00:00Z",
"updated_at": "2026-09-02T03:01:56Z",
"language": "en",
"phase": "implementation-complete",
"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": [],
"gitea": {
"milestone_id": 61,
"issues": {
"requirements_design": 246,
"implementation": 247,
"validation": 248
}
}
}