Standardize all command outputs to match Activity Tracker's style guide

[dmccoystephenson]

Summary

Audit and update all command output messages to fully conform to the formatting conventions defined in Activity Tracker's COMMAND_OUTPUT_STYLE.md.

---

Background

Activity Tracker maintains a style guide (COMMAND_OUTPUT_STYLE.md) that defines how all command output should be presented to players, covering box-drawing structure, ChatColor usage, progress bars, and label alignment. A full audit is needed to ensure every command is compliant with Activity Tracker's established conventions.

---

Requirements

Each command output must follow Activity Tracker's style rules:

• Structure: Empty line → ┌─ header → │ body lines → └───────────────────────── footer (25 ─ chars)
• Borders: ChatColor.GOLD on all box-drawing characters (┌ │ └ ─)
• Header: Name in ChatColor.YELLOW + ChatColor.BOLD, then ChatColor.RESET to prevent bleed, subtitle in ChatColor.GOLD
• Labels: ChatColor.GRAY; general values ChatColor.WHITE; positive numerics ChatColor.GREEN; rankings/commands ChatColor.AQUA; negative states ChatColor.RED
• Progress bars: 10-char █/░ bars in ChatColor.DARK_GRAY, enclosed in [ ], using createBar() / createRankBar() helpers
• Label alignment: Right-pad shorter labels so values align vertically within a block
• Errors: ChatColor.RED

---

Acceptance Criteria

• All command outputs audited against Activity Tracker's COMMAND_OUTPUT_STYLE.md
• createBar() and createRankBar() helpers present and used wherever metrics are displayed
• ChatColor.RESET inserted after every ChatColor.BOLD usage
• Labels are vertically aligned within each output block
• Footer is consistently ChatColor.GOLD + "└─────────────────────────" (25 dashes)
• No functional behavior changed — formatting and presentation only
• Outputs verified in-game or via reviewer walkthrough

References

• Activity Tracker's COMMAND_OUTPUT_STYLE.md