Comprehensive documentation of the task renumbering process: CONTENTS: - Problem statement (6 sets of duplicate numbers) - Complete renumbering map (old → new) - What changed vs what stayed the same - Task # vs Issue # explanation - Verification commands - Cross-reference guide for top 10 tasks HELPFUL NOTES: - Task #1 (Builder Rank) = Issue #28 - Task #7 (Whitelist Manager) = Issue #33 - New tasks start from #52 - All 51 tasks now sequential, no duplicates Reference: docs/procedures/task-renumbering-summary.md
5.7 KiB
Task Renumbering - Complete Summary
Date: March 19, 2026
Session: Chronicler #34
Action: Complete renumbering of all tasks to eliminate duplicates
Problem Statement
docs/core/tasks.md had duplicate task numbers that accumulated over time:
- Task #10: 2 instances
- Task #11: 3 instances (!)
- Task #12: 2 instances
- Task #21: 2 instances
- Task #26: 2 instances
- Task #28: 2 instances
This caused:
- Ambiguous references ("go look at Task #11" - which one?)
- Confusion in documentation
- Messy Kanban board titles
- Difficulty tracking task status
Solution
Complete sequential renumbering: Tasks #1-#51 in file appearance order.
Renumbering Map (Major Changes)
Tasks moved significantly:
| Old Task # | New Task # | Title |
|---|---|---|
| #40 | #1 | Builder Rank & Holly Tool Setup |
| #41 | #2 | Rank System Deployment |
| #42 | #3 | Pterodactyl Panel Update |
| #43 | #4 | PteroStats Extension Update |
| #44 | #5 | NC1 Node Usage Stats Not Reporting |
| #38 | #6 | Ghost CMS Security Update ✅ |
| #1 | #7 | Centralized Whitelist Manager ✅ |
| #2 | #8 | Command Center Root Cleanup ✅ |
| #3 | #9 | Fire + Frost Holdings |
| #4 | #10 | Staff Recruitment Launch |
Duplicate resolutions:
| Old Numbers | New Numbers | Titles |
|---|---|---|
| #10, #10 | #19, #25 | Firefrost Codex, Pokerole WikiJS |
| #11, #11, #11 | #20, #21, #26 | Mailcow ✅, AI Stack ⚠️, Modpack Monitor |
| #12, #12 | #22, #23 | Netdata, Department Structure |
| #21, #21 | #35, #36 | NextCloud Portal, "Coming Soon" Video |
| #26, #26 | #40, #41 | World Backup, Blueprint Extension |
| #28, #28 | #42, #43 | Discord Reorg, Firefrost: Eternal Skyforge |
Recent tasks (stayed mostly the same):
| Old Task # | New Task # | Title |
|---|---|---|
| #30 | #44 | Among Us Weekly Events |
| #31 | #45 | Pterodactyl Modpack Version Display |
| #32 | #46 | Server-to-Server SSH Key Setup |
| #49 | #51 | Ignis Protocol Implementation |
What Was Changed
1. tasks.md File
- All 51 task headers renumbered sequentially
- No duplicate numbers
- Completion markers (✅, ⚠️) preserved
- Task descriptions unchanged
2. Gitea Issue Titles
- 46 issue titles updated via API
- Format: "Task #X: Title"
- Issues #70-#73 skipped (not task format - these are from brainstorming ideas)
3. Kanban Board
- Card titles updated automatically (pulled from issue titles)
- Card positions unchanged
- Labels unchanged
- No workflow disruption
What Was NOT Changed
✅ Gitea Issue Numbers - These are permanent IDs (#19-#73)
- Issue #64 is still Issue #64 (just renamed from "Task #31" to "Task #46")
✅ Task Descriptions - Only headers changed
✅ Completion Status - ✅ COMPLETE and ⚠️ SUPERSEDED markers preserved
✅ Card Positions - Everything stayed in same Kanban columns
✅ Labels & Assignments - All metadata preserved
✅ Comments & History - Full discussion threads intact
Benefits Achieved
✅ Clean Sequential Numbering
- Tasks 1-51, no gaps, no duplicates
- Easy to reference unambiguously
✅ Consistency
- tasks.md matches Gitea issue titles
- Single source of truth
✅ Future-Proof
- New tasks just increment from #52
- No more duplicate confusion
✅ No Workflow Disruption
- Kanban board still works
- All in-progress work preserved
Important Notes
Task # ≠ Issue
Example:
- Task #1 (Builder Rank) = Issue #28
- Task #7 (Whitelist Manager) = Issue #33
- Task #46 (SSH Key Setup) = Issue #64
Why this matters:
- When referencing in code/docs: Use Task # (the logical number)
- When linking to Gitea: Use Issue # (the URL number)
Finding Tasks
In tasks.md:
grep "### 46\." docs/core/tasks.md
# Returns: ### 46. Server-to-Server SSH Key Setup
In Gitea:
- Search by title: "Server-to-Server SSH Key"
- Or use direct URL if you know Issue #:
/issues/64
Statistics
Total Tasks: 51
Tasks Renumbered: 51 (100%)
Gitea Issues Updated: 46
Gitea Issues Skipped: 4 (non-task format)
Duplicate Numbers Eliminated: 6 sets
Execution Time: ~2 minutes
Downtime: Zero (all changes via API)
Verification
Check for duplicates:
cd /firefrost-operations-manual
grep "^### [0-9]" docs/core/tasks.md | \
sed 's/### \([0-9]*\)\..*/\1/' | \
sort -n | uniq -d
# Should return nothing (no duplicates)
Check sequential numbering:
grep "^### [0-9]" docs/core/tasks.md | \
sed 's/### \([0-9]*\)\..*/\1/' | \
sort -n
# Should return 1 2 3 4 5 ... 51
Next Time You Add a Task
- Add to tasks.md with next sequential number (currently #52)
- Create Gitea issue with same title format: "Task #52: Title"
- Add to Kanban board in appropriate column
- Keep task numbers synchronized between tasks.md and Gitea
Cross-Reference Guide (Top 10 Tasks)
For quick reference, here are the most commonly referenced tasks:
| New # | Old # | Title | Gitea Issue |
|---|---|---|---|
| #1 | #40 | Builder Rank & Holly Tool Setup | #28 |
| #2 | #41 | Rank System Deployment | #29 |
| #6 | #38 | Ghost CMS Security Update ✅ | #32 |
| #7 | #1 | Centralized Whitelist Manager ✅ | #33 |
| #8 | #2 | Command Center Root Cleanup ✅ | #34 |
| #13 | #39 | Ghost CMS Buildout | #39 |
| #18 | #47 | Plane Project Management ✅ | #44 |
| #19 | #10 | Firefrost Codex - AI Assistant | #45 |
| #27 | #45 | Server Sunset Evaluation | #27 |
| #28 | #46 | Ghost CMS Music Player | #46 |
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️