Add a timestamp to the automated -ca inbox nudge text (both pokers)

Elazar asked (2026-09-10, CLI) that the automated -ca inbox nudge carry a timestamp, so an agent reading the injected line can tell WHEN it was sent - currently the text is identical every time and a stale line in a pane is indistinguishable from a fresh one. Requested shape: prefix the existing string, e.g. {yyyy-mm-dd-hhmm-tz - Read llmmsg-srv unread; act or reply if needed. Automated prompt; may have interrupted user typing.} TWO CALL SITES, BOTH MUST CHANGE OR THE POKERS DIVERGE VISIBLY. (1) scr-agent-inbox-nudge.py:68-71 (v1.1, 45495cd) - NUDGE is a module-level constant read once at import, default '{Read llmmsg-srv unread; act or reply if needed. Automated prompt; may have interrupted user typing.}'. A timestamp means it can no longer be a constant: it has to be computed per send, inside the send path near :304 where send-keys -l NUDGE runs. (2) context-monitor.sh:1246 CA_NUDGE_TEXT - a NEAR-DUPLICATE of the same sentence, different wording, and BOTH read the same LLMMSG_NUDGE_TEXT env var with different defaults. If only one default gains a timestamp, the two pokers produce visibly different lines for the same event. Cost is near-zero: a strftime call in each send path, roughly two lines each. Timezone should be explicit in the string (ART) since the fleet reads these across hosts. WATCH ITEMS, learned on this file tonight: it runs under a live 10s timer on whey and lezama and a python file is read at exec, so in-place edits have executed mid-write twice (ValueError 08:12:56, NameError 08:20:19, both on record) - stop the timer, edit, restart, as bin-venus-cc did for 45495cd. Bump VERSION in the same commit (mandatory one-commit-one-bump). Do NOT add a startup banner for this - an unconditional line at 10s cadence measured ~8,640 journal lines/day on venus and the zero-noise baseline is deliberate. Handed to bin-venus-cc as the recent author of a4c2f11 and 45495cd on this file. bin-whey-cc made no edits - whey is pulled to 45495cd and verified running (timer active, --version rc=0, 0 non-Starting/Finished log lines in 3min) and can verify the change loads on whey after it ships. context-monitor.sh script CONTENT is bin-lezama-cc's lane per the ratified unit-vs-content split, so site (2) may need their sign-off.