Harden Warden response timing and transport validation

[MadMaxMangos]

Summary

Follow-up to #475 based on an adversarial review of the merged Warden redesign.

• drain queued Warden responses before advancing their deadlines, while preventing elapsed time from being charged to a state entered during the same world tick
• reject check plans whose maximum client result exceeds the exact 10,229-byte transport body budget
• distinguish transport overflow from the inner uint16 result limit in catalogue diagnostics
• centralize and compile-time pin the Classic CHECK_RESULT framing invariants

Verification

• built mangosd and mangos_tests in RelWithDebInfo
• full aggregate unit run: 309 tests passed
• CTest: 15/15 passed
• proto_boundary, build_policy, and warden_boundary passed
• each commit received a bounded Claude Opus 5 Max review; no blocking or unresolved important findings remain

No database, configuration, or submodule changes are included.

---

This change is 

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 4 complexity · 2 duplication

Metric	Results
Complexity	4
Duplication	2

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[AppVeyorBot]

✅ Build Mangos ZERO Server 22.04.474-vyhkckif completed (commit 279eed46a1 by @MadMaxMangos)