Shelved PR 373 wf clock readout

Shelved: PR #373 — On-screen time-of-day clock (HH:MM readout on the RHUD)

State: Ray-shelved 2026-07-03 (Build 89 pick round). PR #373 was closed without merging; nothing from it is in Build 88/89.

WHAT

Adds a persistent Time: row to the full right-side HUD panel showing the current in-game time as HH:MM plus a daylight tag (Dawn / Day / Dusk / Night). Players who run the RHUD would see a literal on-screen clock that updates every second — e.g. 07:42 Day — so they can tell time of day at a glance without opening the map or watch. The row sits one line below the artillery pair and is written entirely client-side from the engine's daytime value (no server round-trip, JIP-safe).

WHERE

• PR: #373 — "feat(wf-clock-readout): add RHUD time-of-day row (HH:MM + Dawn/Day/Dusk/Night)".
• Branch / head commit: fable/wf-clock-readout @ a407d5889f39c36b08fe641a56a3313610b6c90f.
• Flag (if any): No flag / always-on. Rides the existing if (RUBHUD) guard that already wraps the whole full-mode RHUD block; with RUBHUD=false the row never renders (byte-identical to pre-patch). Author's rationale: daytime is a read-only client value that can't reveal hidden state, affect balance, or desync.
• Files touched: Client/Client_UpdateRHUD.sqf (new clock label at control index 29 / value at 30, IDCs 1374/1375; per-tick HH:MM + tag write) and Rsc/Titles.hpp (two new RscText controls RUBHUD_Clock/RUBHUD_Clock_Value added to the OptionsAvailable class). Mirrored across Chernarus + Takistan + Zargabad.

WHY SHELVED

Ray's reason (2026-07-03): "already in" — he considers time-of-day already covered.

IMPORTANT REVIVE NOTE (verbatim): A verification of the live tree (Build 88) found a day/night CYCLE simulation (Client/Functions/Client_DayNightCycle.sqf, daytime-based logic) but NO on-screen clock HUD readout — the RHUD (Client_UpdateRHUD.sqf) does not render a time-of-day row. So a visible clock readout does NOT currently exist on live; if Ray later wants a literal HH:MM readout on screen, this PR is the way to add it.

HOW TO REVIVE

• Recover from fable/wf-clock-readout @ a407d5889f39c36b08fe641a56a3313610b6c90f — the change is self-contained (one SQF + one HPP per map).
• Because it touches a CLIENT file, revival must bump the mission pbo filename and repoint the cfg (client changes are cached by filename and won't reach A2 clients in-place).
• Before rebasing, re-check the OptionsAvailable controls[] array and IDC allocation in the current Build 88+ Titles.hpp — confirm IDCs 1374/1375 and control indices 29/30 are still free (the RHUD layout has been reworked since; the arty pair 27/28 is already vacated).
• Optional design tweak if revived: consider gating behind a real WFBE_C_... flag so it can be dialled off in the lobby, rather than always-on under RUBHUD.