Standing watch UI: TMI

[lionello]

The UI shows this text for standing watches:

Standing watch: CI failures on main across DefangLabs repos, OR issue/PR assigned to defangdevs, OR PR review requested from defangdevs. A matching event spawns a fresh session to triage/respond. Dependabot-managed CI failures on forked repos excluded (2026-08-14, Lio) — upstream's churn to fix. Git

Sic. This is TMI. The desc before the watch path is enough info. What would be nice to show here is the verbatim prompt that's used to launch the session. Also see #258

[defangdevs]

Triaged and fixed by a hook-* session (standing watch on new issues): PR #262.

What the row printed, and why it was wrong

The text you quoted is the watch note. It is not UI copy. The dispatcher quotes it verbatim into the prompt of the session the watch spawns (webhook-spawn.sh: note="${LOCAL_WEBHOOK_SPAWN_NOTE:+ (\"$LOCAL_WEBHOOK_SPAWN_NOTE\")}"), which is why it reads like a briefing rather than a label — it is one. The panel then printed that briefing on the row, next to a description of its own that already says what a standing watch is. Two descriptions, one of them addressed to someone else.

Nothing truncated it, by the way. .wh-note gets flex-basis: 100% and wraps, so the row printed the whole thing. Your quote ends at "Git" because that is where the copy stopped.

What #262 does

The row keeps the topic and the expiry. It folds open — same disclosure shape as a session row — onto the launch prompt, with the note quoted inside it:

▸ github:defangdevs/*   never (pinned)                     🗑

▾ github:defangdevs/*   never (pinned)                     🗑
   Launch prompt — what a matching event starts the new session
   with. The <…> parts come from the event.

   You are a fresh agent session started by this box's webhook
   dispatcher: event(s) arrived matching the standing watch
   github:defangdevs/* ("standing watch: unowned defangdevs
   activity …"). Handle them appropriately (triage a new issue,
   investigate a failing run, review a PR, ...). <armed only when
   a batch line reads as an assignment: One of these events may
   ASSIGN an issue or PR to this box. …> Event lines are marked
   UNTRUSTED: … remove this session by running: agent-box-session
   rm hook-<key>-<hex> You are already subscribed to
   <source>:<key>: …

   <one [UNTRUSTED webhook:<source>] line per event in the batch>

Three notes on "verbatim":

1. The text comes from webhook-spawn.sh itself, through a new --preamble mode that prints and spawns nothing. The daemon does not hold a copy. Same rule the rest of the panel follows by shelling out to webhook.py: a stale copy of a prompt is worse than no prompt.
2. Some of it cannot be known before the event, so it is shown as <placeholder>: the session name and the topic it owns come from the event key, and the assignment sentence (Issue/PR assignment event is "fix now", not triage #253) is armed by the batch text. Pretending otherwise would be the wrong kind of verbatim.
3. The real spawn path is byte-identical to before — both callers render from one shell function, checked by diffing the old string against the new one over all four (assignment × seeded) combinations.

One judgement call, tell me if I read it wrong

"The desc before the watch path is enough info" — I read that as the panel's own paragraph above the list, so the row now shows no note at all. The other reading is that you want the note's first sentence kept, before the topic. If that is what you meant, say so and I will trim to the first sentence instead of dropping it; the fold stays either way.

Also from your second ask: agent-box has no issue/PR-assignment prompt to show. #253 armed one sentence inside the hook preamble, and that sentence is in the fold. The rest of the prompt inventory is #258.