Rongsong Shen
b0f2aea466
- 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>
32 lines
1.3 KiB
JSON
32 lines
1.3 KiB
JSON
{
|
|
"feature_name": "commit-batch-window",
|
|
"created_at": "2026-08-31T14:07:43Z",
|
|
"updated_at": "2026-08-31T14:20:00Z",
|
|
"language": "en",
|
|
"phase": "initialized",
|
|
"approvals": {
|
|
"requirements": {
|
|
"generated": false,
|
|
"approved": false
|
|
},
|
|
"design": {
|
|
"generated": false,
|
|
"approved": false
|
|
},
|
|
"tasks": {
|
|
"generated": false,
|
|
"approved": false
|
|
}
|
|
},
|
|
"ready_for_implementation": false,
|
|
"sibling_specs": ["scheduler-dispatch-commit", "job-array-single-wal-record", "worker-rejoin-resync"],
|
|
"note": "Parked/tracked, not actively being pursued. Originally scoped narrowly as job-dispatch-commit-batching; broadened (2026-08-31, same session) to a general time-windowed batch-commit facility for ANY WAL-worthy fact needing a durability-gated external side effect, not just job dispatch -- job dispatch remains the motivating first use case. User assessed this as a substantial cross-cutting change (core commit pipeline, latency/throughput tradeoffs, hook/notification timing, soak-level correctness verification), not a small project. Revisit in a dedicated future session.",
|
|
"gitea": {
|
|
"milestone_id": 4,
|
|
"issues": {
|
|
"requirements_design": 60,
|
|
"implementation": 62,
|
|
"validation": 63
|
|
}
|
|
}
|
|
}
|