- 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>
35 lines
1.1 KiB
JSON
35 lines
1.1 KiB
JSON
{
|
|
"feature_name": "resreq-maxtasks-wiring",
|
|
"created_at": "2026-09-05T07:18:28Z",
|
|
"updated_at": "2026-09-06T10:20:00Z",
|
|
"language": "en",
|
|
"phase": "implementation-complete",
|
|
"approvals": {
|
|
"requirements": {
|
|
"generated": true,
|
|
"approved": true
|
|
},
|
|
"design": {
|
|
"generated": true,
|
|
"approved": true
|
|
},
|
|
"tasks": {
|
|
"generated": true,
|
|
"approved": true
|
|
}
|
|
},
|
|
"ready_for_implementation": false,
|
|
"implementation_complete": true,
|
|
"validate_impl_decision": "GO",
|
|
"related_specs": ["scheduler-allocation"],
|
|
"related_bugs": ["bug-1770"],
|
|
"motivation": "scheduler-allocation's task 5.3/6.2 review confirmed parjob_allocator's entire multi-host combinatorial allocation path (implemented, reviewed, and soak-tested by that feature) has zero live production reachability today, because no real job submission can ever produce xce_primary_resreq_t.maxTasks > 1. This spec exists to close that gap.",
|
|
"gitea": {
|
|
"milestone_id": 42,
|
|
"issues": {
|
|
"requirements_design": 189,
|
|
"implementation": 190,
|
|
"validation": 191
|
|
}
|
|
}
|
|
}
|