8bcfa09a87
- Created /tasks/ folder with individual task markdown files - Each task has frontmatter (number, title, priority, status, owner) - Blockers marked with blocker: true field - Sample tasks created: #26, #51, #87, #93, #94, #98, #99 Benefits: - Click individual tasks in Decap CMS instead of editing giant BACKLOG.md - Filter by priority (BLOCKER, P1, P2, P3, etc.) - Sort by status, number, blocker flag - Mobile-friendly (each task = separate entry) - BLOCKERS.md and BACKLOG.md remain as reference docs Task structure: --- number: 26 title: Task Name priority: P1 status: In Progress blocker: false owner: Michael full_spec: docs/tasks/full-spec-location/ --- Task content here...
938 B
938 B
number, title, priority, status, blocker, owner, full_spec
| number | title | priority | status | blocker | owner | full_spec |
|---|---|---|---|---|---|---|
| 94 | Global Restart Scheduler | P1 | Spec Complete | false | Unassigned | docs/tasks/task-094-global-restart-scheduler/ |
Task #94: Global Restart Scheduler
680-line spec complete — reduces manual server work
Overview
Centralized scheduler for all Minecraft server restarts across NC1 and TX1.
Features:
- Web UI for Trinity to manage restart schedules
- Per-server scheduling with drag-and-drop
- Pterodactyl API integration with rate limiting
- SortableJS for visual reordering
Status
Complete specification exists (680 lines including database schema, Express routes, EJS/HTMX templates).
Next Steps
- Review spec at
docs/tasks/task-094-global-restart-scheduler/ - Implement backend (Express + PostgreSQL)
- Implement frontend (EJS + HTMX + SortableJS)
- Test with Pterodactyl API
Links
- Full spec:
docs/tasks/task-094-global-restart-scheduler/