(docs) Add burn period notice to validator guide

[joellidin]

Add 100% burn period notification to docs/validator.md to align with
other documentation files. This completes the documentation update to
reflect the transition period after Covenant72B training.

• Inform validators are burning 100% of emissions
• Link to neurons/burn.py implementation
• Note miner gradients are not being evaluated
• Reference upcoming Templar: Crusades announcement

Description

Related Issue(s)

• Closes #[issue number]

Type of Change

• Feature (adding new functionality)
• Fix (resolving a bug or issue)
• Docs (documentation updates)
• Refactor (code changes that don't affect functionality)
• Maintenance (dependency updates or other maintenance)
• Tests (adding or improving tests)
• Breaking change (fix or feature with incompatible API changes)
• Other: _____

Branch Naming

• My branch follows the project's naming convention (e.g., feature/add-new-capability)

Commit Messages

• My commits are small, atomic, and have proper commit messages
• Commit messages are in imperative mood with a capitalized summary under 50 chars

Code Quality

• I've performed a self-review of my code
• I've added appropriate docstrings following the project's conventions
• I've added proper logging where necessary (without trailing periods)
• I've applied linting and formatting with Ruff
• My code generates no new warnings

Testing

• I've added tests for new functionality or bug fixes
• All tests pass locally with my changes
• Test coverage has not decreased

Documentation

• I've updated documentation to reflect my changes
• I've updated comments in hard-to-understand areas

If this is a breaking change

Screenshots/Examples

Additional Notes

Summary by CodeRabbit

Release Notes

• Documentation
  • Introduced 100% Burn Period status (January 2026) clarifying that miners are not being evaluated and no emissions are distributed
  • Documented Covenant72B (72B parameters) training completion
  • Previewed upcoming Templar: Crusades competition system where training implementations are evaluated on target hardware with emissions awarded to fastest implementations

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Documentation files updated across the repository with warning banners announcing a 100% Burn Period as of January 2026, Covenant72B training completion, and the upcoming Templar: Crusades competition system. No functional code changes; purely informational content additions.

Changes

Cohort / File(s)	Summary
Documentation Status Updates README.md, docs/README.md, docs/miner.md, docs/validator.md	Added warning banners and status announcements indicating 100% Burn Period active, Covenant72B training phase, and reference to Templar: Crusades competition system. No functional or logic changes; content-only updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A burn period gleams, the docs now say,
No emissions flow on this quiet day,
Covenant's trained, the Crusade awaits,
Through warnings and banners we seal our fates! 📜✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title specifically references adding a burn period notice to the validator guide, which aligns with the primary change of adding documentation to docs/validator.md.
Description check	✅ Passed	The description provides a clear summary of changes and their purpose, though the template checklist items remain unchecked rather than properly completed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

❌ Your project status has failed because the head coverage (57.69%) is below the target coverage (85.00%). You can increase the head coverage or adjust the target coverage.

@@           Coverage Diff           @@
##              dev     #689   +/-   ##
=======================================
  Coverage   57.69%   57.69%           
=======================================
  Files          27       27           
  Lines        4990     4990           
=======================================
  Hits         2879     2879           
  Misses       2111     2111           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.