docs-sync sentinel: replace dead strike/cooldown model with score-based routing enforcement

[maia-cloud-agent]

Summary

This PR syncs the documentation with the current Sentinel implementation by removing references to a dead "strike → 3 strikes → disqualified → cooldown" model and replacing it with the actual score-based routing enforcement mechanism.

Key Changes

intro/data-quality.mdx

Replay Checks Section:

• Changed node sampling description from "three randomly selected nodes" to "a sample of nodes" to reflect the actual implementation
• Removed the outdated strike-based model (strikes → disqualified → cooldown) and replaced it with the score-based approach: nodes receive lower scores for deviations, and nodes falling below the routing threshold are removed from production routing until recovery
• Clarified that removal is enforced by the routing layer, while Sentinel's role is measurement and scoring

Lag Checks Section:

• Clarified that lag checks are a separate check issuing eth_blockNumber calls (previously described as happening "during replay checks")
• Updated normalization reference from "30-day rolling average" to "average block production time"
• Changed "immediately blacklisted" to "removed from production routing" for severe lag cases
• Updated scoring language: nodes receive "lower scores" instead of "strikes"

Implementation Details:

• Replaced the fixed "forces rounds at least once per hour" with adaptive validation frequency based on traffic levels
• Changed transport failure handling from "do not count as strikes" to "do not penalize a node"

provider/lag-checks.mdx

• Updated the severe lag consequence from "immediate temporary removal" to "removed from production routing" for consistency with the new model

Purpose

The documentation previously described an outdated model that no longer exists in the codebase. This PR aligns the documentation with the actual Sentinel implementation: a scoring system where nodes are continuously evaluated, and routing decisions are made downstream based on trust scores, rather than a rigid strike count system.

[kodus-routemesh-hosted]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​