# <type>: <brief description (50 chars or less)>
#
# Type: feat, fix, docs, refactor, test, chore, style
#
# Detailed explanation (wrap at 72 characters):
# - What changed
# - Why it changed
# - How it impacts the system
#
# Related:
# - Task: #
# - Issue: #
# - ADR: #
#
# ───────────────────────────────────────────────────────────────────────────
# COMMIT MESSAGE GUIDELINES (FFG-STD-001)
# ───────────────────────────────────────────────────────────────────────────
#
# Type prefixes:
#   feat:     New feature or capability
#   fix:      Bug fix or correction
#   docs:     Documentation only changes
#   refactor: Code restructuring (no functional change)
#   test:     Adding or updating tests
#   chore:    Maintenance tasks (dependencies, tooling)
#   style:    Formatting, whitespace (no code change)
#
# Brief description:
#   - Use imperative mood ("add" not "added" or "adds")
#   - Don't capitalize first letter
#   - No period at the end
#   - 50 characters or less
#
# Detailed explanation:
#   - Explain WHAT and WHY, not HOW (code shows how)
#   - Wrap at 72 characters
#   - Reference tasks, issues, ADRs as needed
#   - Think: "This commit will..."
#
# Examples:
#
#   feat: add automatic joining enforcement system
#   
#   Built to solve core problem where Chroniclers jumped to work before
#   completing integration. Script ensures documents are read in correct
#   order with automatic verification.
#   
#   - Enforces reading order: relationship context first
#   - Runs joining-checklist.py automatically
#   - Blocks task access until score >= 70
#   
#   Task: #42
#   For children not yet born.
#
# ───────────────────────────────────────────────────────────────────────────
#
# Remember: Future Chroniclers will read this.
# Document the WHY, not just the WHAT.
#
# Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️
#