feat(net): frame timing section in SERVER_TRAFFIC, profiling messages

An optional section after marker 3 carries the report's frame timing; older readers stop before it and reports without it still read. Phase times go with their count so readers with fewer or more phases read them. PROFILE_REQUEST and PROFILE_RESULT are appended to the master messages (44, 45). Task 96.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Aaron Kimbrell
2026-09-29 22:06:29 -05:00
parent 06af6c3aaa
commit d0c7b089ff
5 changed files with 375 additions and 1 deletions

View File

@@ -1807,6 +1807,8 @@ static_assert(static_cast<int64_t>(MessageType::Master::LIVE_UPDATE_STATUS) == 4
static_assert(static_cast<int64_t>(MessageType::Master::LIVE_UPDATE_RETIRE) == 41);
static_assert(static_cast<int64_t>(MessageType::Master::CHAT_HANDOFF) == 42);
static_assert(static_cast<int64_t>(MessageType::Master::CHAT_SERVER_READY) == 43);
static_assert(static_cast<int64_t>(MessageType::Master::PROFILE_REQUEST) == 44);
static_assert(static_cast<int64_t>(MessageType::Master::PROFILE_RESULT) == 45);
// MessageType::Server: 3 enumerators
static_assert(static_cast<int64_t>(MessageType::Server::VERSION_CONFIRM) == 0);